Privacy policy

What is stored

• The messages you send Leen, and its replies. This is what lets it hold a conversation instead of starting over each time.
• What you asked it to remember — reminders, tasks, lists and times.
• Facts you asked it to keep about you, or that came up in conversation and it kept in order to answer better.
• If you sent a file and did not ask for it to be kept — a pointer to it, not a copy. The file itself stays with Telegram, and Leen keeps only the identifier that lets it ask Telegram for it again if you ask about it.
• If you asked Leen to keep a file, it keeps a copy of its own, in S3 in Leen's own account, so it can give the file back whenever you ask. This happens only when you ask for it: a file that simply arrived is not kept. You can see what is kept ("what files do you have?"), ask for any of it back, and delete any of it — and deleting means the file itself, not just the record of it.
• Your Telegram user id, which is how Leen knows it is you. It does not receive your phone number.
• If you connected a Google account: the account address, the access keys it issued, and which permissions you approved — calendar, mail, or both.
• Operational records — how many requests were made, at what cost, and what failed. They do not hold the text of your messages, though a failure reason can quote a value you supplied, such as a date that could not be read.

Google data, separately

• Connecting Google is your choice, and Leen works without it. The calendar and mail are approved separately: you can connect a calendar without mail, or the other way round. If you have not connected either, nothing in this section applies to you.
• Your calendar events are not stored here as calendar records. They are read from Google at the moment you ask, and no table mirrors your calendar. What is kept: a reply that lists them is saved as part of the conversation, like any other message — so the text you were shown remains, even after you delete the event in Google.
• Your mail is not stored here at all. There is no message table, no copy and no cache — every read goes to Google at that moment. The same caveat applies: if Leen read you a message or summarised one, that text stays in the conversation like any other message.
• What Leen can do with your mail, and what it cannot: read, search, send and reply once you have approved it, save drafts, mark messages read, label them, and archive or bin them. Leen cannot delete mail permanently — the permission it asks for does not include that, and anything it puts in the bin stays recoverable by you.
• The access keys Google issues are stored encrypted (AES-256-GCM) and used only to carry out what you asked for.
• Leen does not use Google data for advertising, does not sell it, and does not transfer it to anyone beyond what is listed under "Who else sees it" below.
• No human reads your Google data — except with your explicit permission, for security or to investigate a fault, or where the law requires it.

Who else sees it

• Anthropic — to compose a reply, your message and the information relevant to it (including calendar events, and the contents of email messages Leen read for you) are sent to Anthropic's model. This is what lets Leen understand a free-form request, and it cannot be separated from the product.
• For mail this is worth saying plainly: if you asked Leen to read a message or search your inbox, the bodies of the messages it found are sent to the model. Leen does not scan your mailbox on its own and reads nothing you did not ask about — but what is read, is read by the model.
• And: if you ask Leen about a picture you sent, the picture itself is sent to Anthropic — there is no other way to read what is in it. Leen decides when to open one, and is built to do it only when your question needs what is in the picture; it is not opened just because you sent it.
• Amazon Web Services — Leen runs on AWS and stores its data there, in the European Union (Frankfurt).
• Telegram — the chat itself travels through Telegram, under their terms and privacy policy.
• Google — only if you connected a calendar or mail, and only to carry out what you asked.
• Beyond these, your information is not sold, rented or handed to anyone. There are no advertisers and no data brokers.

How it is kept

• The database is encrypted at rest, sits on a private network with no route to the internet, and every connection to it is authenticated and encrypted.
• Google access keys are encrypted separately, on top of the database encryption.
• Access to the chat is limited to an approved list of ids — anyone not on it cannot talk to Leen at all.
• No secret, key or token is ever written to a log, sent in a message or shown on a screen.

For how long, and how to erase it

• Your information is kept for as long as you use Leen, because that is precisely what makes it useful — an assistant that forgets every week is not an assistant.
• To disconnect Google: ask Leen, or revoke the permission directly in your Google account permissions. Either way the access keys are deleted here. Note that Google issues one key per account, so disconnecting ends both the calendar and mail — there is no way to revoke one and keep the other.
• Files you asked Leen to keep are kept until you ask for them to be deleted, and are not expired after some period of time. You can ask Leen to delete any of them at any moment, and the file itself is deleted — no earlier version is retained.
• To erase everything: write to the address above and ask. Everything tied to you — messages, reminders, memories, files you asked it to keep, and the Google connection — is deleted, with no copy kept. Your mail itself lives at Google and is not touched.

Children

• Leen is not intended for use by anyone under 16, and no information is knowingly collected from children.

Changes

• If this policy changes, the date at the top of the page changes with it. This version is effective from 2026-08-14.

Google data — Limited Use disclosure

Leen's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.