Privacy policy
Cue, at cuebot.me. Last updated 5 November 2026.
This page says what Cue stores about you, why, where, who else sees it, and how to make it go away. It is written to be read, not skimmed past.
What Cue stores
- Your Telegram identity. Your Telegram user id and the chat id Cue uses to message you. Not your phone number, which Telegram does not share with bots.
- Your conversations with Cue. Every message you send it and every reply it gives, including the steps it took in between. Cue keeps these so it can carry on a conversation and, in future, remember what you have told it.
- Your reminders. The text and times of reminders you set, and what happened to each one (sent, done, snoozed, skipped).
- Your Google Calendar access. If you connect your calendar, Cue stores the token Google issues so it can act for you while you are away, for example to check your calendar before an 8am reminder. Cue reads your calendar events when a conversation needs them and does not keep a separate copy of your calendar.
- Your time zone, taken from your Google Calendar settings when you connect.
Cue does not store your name, email address, contacts, location, or anything from your Google account beyond the calendar access above.
How it is protected
Each person's data is kept in its own encrypted file, with its own encryption key. Those keys are themselves encrypted by a master key held in Google Cloud's key management service, outside Cue's servers, where it cannot be copied out. Every use of that service is logged by Google. Cue's own logs record timings and counts, never message content.
Honestly stated: because Cue works for you while you are away, its server can decrypt your data without you present. There is no admin screen that reads anyone's conversations, and decryption happens only along the paths that serve you, but this is a system you trust the operator to run properly, not one where the operator is technically unable to look. If you need the latter, Cue is not the right tool.
Where it is kept
On a server in Singapore run on DigitalOcean. Backups of that server are encrypted copies of the same files.
Who else sees it
- Anthropic provides the language model that reads your messages and writes Cue's replies. Anthropic does not use this data to train its models and does not retain it beyond its standard short-term operational limits.
- Google handles the calendar itself, under your own Google account and Google's privacy policy.
- Telegram carries the messages, under Telegram's privacy policy.
- DigitalOcean hosts the server and Google Cloud holds the master key. Neither can read your data.
Nobody else. Cue does not sell data, share it with advertisers, or use it for anything other than being your assistant.
Google user data
Cue's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Calendar data is used only to provide the features you ask Cue for; it is never transferred to others except as needed to provide those features, never used for advertising, and never read by a human except with your permission, for security, or as required by law.
Your choices
- Disconnect your calendar at any time by telling Cue "disconnect my calendar". Cue revokes its own access at Google and deletes the token.
- Delete everything by telling Cue "delete everything about me" and confirming with the button it shows. Your encrypted file, your reminders, your conversations, and Cue's record of you are deleted, and its calendar access is revoked. Events already on your Google Calendar stay, because they are yours. The deletion is immediate and cannot be undone.
- You can also revoke Cue's access from your Google account at any time under myaccount.google.com/permissions.
Changes and contact
If this policy changes in a way that matters, Cue will tell you in Telegram before the change applies. Questions go to support@cuebot.me.