Sanctuary

YOUR DATA, EXPLAINED

Privacy policy

Sanctuary is a personal calendar assistant operated for one authorized user, not a public sign-up service.

Last updated: 21 November 2026.

Information the app processes

The app processes the authorized user's Telegram messages and identifiers, Google Calendar events, scheduling preferences and calendar-action history. Calendar changes require explicit confirmation through the app's confirmation controls. Other Telegram users are ignored.

Google Calendar access

Google OAuth connects the user's primary calendar. The app reads event identifiers, titles, times, locations and other event fields needed for agendas, conflict checks and confirmed changes. Event snapshots can include descriptions and other fields returned by Google. The permission granted determines whether confirmed writes are available. OAuth credentials are stored in server configuration, not in public pages.

AI processing and third-party services

For natural-language requests, the app sends the user's request, limited recent conversation context, and compact calendar information (including event identifiers, titles, times and locations) to Google's Gemini API. It does not include calendar descriptions or attendee lists in its compact AI calendar context. Information supplied directly in a message may still be sent to Gemini. Calendar titles and locations may themselves contain personal information.

Telegram processes bot messages; Google Calendar processes calendar requests; Google Gemini processes AI requests; and Google Cloud hosts the deployed app and its data. These providers apply their own terms and data policies. Depending on the Gemini service tier and applicable terms, Google may use submitted content to improve its products. Do not submit information you do not want processed by these services.

Storage and retention

The server stores calendar-action records and event snapshots, pending confirmations, Telegram update identifiers, reminder delivery records, and limited chat history in SQLite. Chat history is trimmed to the latest 12 stored messages when a new interaction is saved; only history from the preceding 24 hours is used as AI context. Older messages can remain stored until another interaction trims them. Confirmation expiry does not delete the associated record.

Action records, reminder records and update identifiers have no automatic deletion schedule. They remain until the operator removes them or deletes the app's stored data. Copies retained in backups need separate deletion. Data stored by Telegram or Google is subject to those providers' retention policies.

Cookies, browser storage and logs

The dashboard uses a signed session cookie valid for up to seven days. Theme, animation and companion preferences are saved in your browser's local storage. There are no advertising trackers or third-party analytics embedded in the app. Server logs can record request paths, times, IP addresses and operational errors. The app is designed to avoid logging credentials.

Use and disclosure

Information is used to answer calendar questions, provide the dashboard, send reminders, process confirmed changes and maintain the action history. The operator does not sell personal data or use it for advertising. Data is shared with the service providers described above as needed to operate the app.

Access, revocation and deletion

The authorized user can revoke the app's Google access in their Google Account's third-party connections settings and stop interacting with the Telegram bot. Revocation stops future access but does not automatically erase server records. Contact the operator to request deletion of stored app data and any backups; deleting app records does not delete calendar events or provider-held messages.

Contact and changes

This deployment is maintained by its authorized user. For privacy, access or deletion questions, contact devanshpahuja07@gmail.com. The operator will update this page when the app's data handling changes.