1. Overview
Esker ("we", "the application") is an independently operated, self-hosted personal assistant intended primarily for use by its owner. It helps organize reminders, tasks, and calendar events through Telegram. Additional functionality, such as work-activity summaries or GitLab integration, is optional.
Questions about privacy or data removal may be sent to lobachevartem@gmail.com.
2. Information accessed and processed
- Google Calendar data: calendar identifiers, event titles, descriptions, start and end times, recurrence details, reminder settings and event identifiers, as needed to view, create, update or list events.
- Google OAuth credentials: authorization and refresh tokens needed for continued access to an authorized calendar.
- Telegram messages: the authorized user's chat identifier, text commands, assistant responses, and voice messages when submitted for speech recognition.
- Personal planning data: tasks, reminders, selected scheduling preferences and limited conversation history.
- Optional integrations: work-activity aggregates and GitLab metadata, when those modules are explicitly configured.
- Technical data: minimal diagnostic information and ordinary web-server request logs, depending on the hosting environment.
3. Google Calendar access and permissions
Esker requests the https://www.googleapis.com/auth/calendar.events scope to perform calendar actions requested by its user, including reading event details, creating events, changing times or reminders, and removing events where requested. Esker does not request Gmail or Google Drive access as part of its Google Calendar connection.
Google Calendar data is accessed only to support user-facing calendar and scheduling features and related user-directed summaries.
Google API Limited Use: Esker's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. How information is used
Information is used to interpret user commands, provide requested reminders or tasks, create and modify calendar events, produce relevant user-facing summaries, maintain conversation continuity, diagnose failures, and protect access to the application. Esker does not sell personal data, use Google user data for advertisements, or train generalized artificial intelligence models using Google user data.
5. Third-party services and AI processing
Esker interacts with Google Calendar and Telegram to provide their respective features. When an AI-based command is enabled, the user's command and a limited amount of relevant conversational or scheduling context may be sent to a configured language-model provider (currently, ProxyAPI) solely to interpret or fulfill the user-requested action. Voice messages may be processed by a configured speech-recognition provider.
These providers process transmitted data under their own terms and privacy practices. Esker does not intentionally provide Google OAuth tokens to an AI provider. Optional GitLab and activity integrations may use their own service APIs when explicitly enabled.
6. Storage and retention
Application records and OAuth credentials are held in storage controlled by the operator of the self-hosted Esker instance. The application retains a limited recent conversation history (up to the latest 30 exchanges in its current implementation). Tasks, reminders, calendar references and diagnostic records may be retained while needed for the relevant features or until deleted by the operator. Server logs and backups may have separate retention periods set by the hosting configuration.
Google event details are primarily managed in Google Calendar; Esker may store limited identifiers and contextual records needed to maintain application state.
7. Security and access
Use of the Telegram assistant is restricted to an authorized user identifier. Google access uses OAuth 2.0 and the provider's access controls. Credentials are not intended for public exposure. No online service or server can be guaranteed to be completely secure.
8. Control and deletion
Google account access can be revoked in the Google Account connections settings. Revoking access prevents future authorized Google API calls once credentials are invalidated; it does not automatically remove already stored local application records. The operator can remove local OAuth credentials, conversation history, tasks and reminders. Requests about deletion may be sent to the contact address above.
9. Children and changes
Esker is not designed for children or general public registration. This policy may change as integrations are added; material changes should be reflected on this page before new uses of Google data begin.