Privacy Policy

Last updated: 5 November 2026 · Version 1.6

This policy explains what Atlas ("Atlas Assistant", "we") does with personal information when you use the Atlas Assistant website at https://assistant.atlassstudio.com, the Atlas Assistant bot on Telegram, and the ella-connector software. We are the controller of the information described in section 3. Contact: [email protected] · postal address provided on request.

1. The short version

Your assistant's AI engine (Claude Code from Anthropic or, where offered, Codex from OpenAI) runs on your computer, under your own account with that provider. It never runs on our servers, and we never see your Anthropic or OpenAI login.
Your messages, files and voice notes pass through our server on their way between Telegram and your computer, and are not stored by us. They exist in our server's memory only for the moment it takes to deliver them. Voice-note transcription is not offered yet; when it launches, voice notes will also be sent to Google to be turned into text, and we will update this policy first (section 4).
What your assistant remembers about you — notes, memory, logs — is stored on your computer, in ~/.ella/, not with us.
Chats answered by our server are different (WhatsApp, and Telegram when your assistant runs on our server rather than your computer). There, we keep the recent conversation and your assistant's memory notes on our server, encrypted, so your assistant can follow the conversation and remember you (section 3). Memory notes are deleted 30 days after they are saved, unless you choose to keep them longer.
We keep a small account record (section 3), the name of the permission level you chose, and a 30-day activity log of events and sizes, never content.
We do not sell your information, show ads, or train anything on your data.

2. Who this applies to

Anyone who visits the website, creates an account, talks to the bot or installs the connector, in any country. It is written to meet the Israeli Privacy Protection Law, 5741-1981 (including Amendment 13) and, for people in the EU and UK, the GDPR and UK GDPR.

You are not legally required to give us any information. It depends on your choice and consent — but without the account and pairing information below, we cannot provide the service.

3. What we collect and keep

Unless a row below says otherwise, we keep content from your chats for no longer than 30 days. Your saved memories are deleted 30 days after they are saved, unless you allow us to keep them longer. Your account details stay until you delete your account.

Information	Why we need it	Legal basis (GDPR)	How long
Account: your name; email address (if you sign up with email or Google); a salted scrypt hash of your password (never the password); your Google account ID (if you use Google sign-in); your Telegram user ID and display name (if you use Telegram sign-in or pair a computer); the name you give your assistant; the name you want the assistant to use for you on calls (optional); whether the assistant should address you in the masculine or feminine form in Hebrew (optional); your plan; sign-up and last sign-in times; the version of the Terms you accepted and when	to create and run your account, sign you in, and route your chat to your own computer and nobody else's	contract	until you delete your account
Connected computer: the name you gave it; a hash of its secret and of your key (never the secret or key themselves); pairing time; lock state; last-seen time	to authenticate your computer and deliver your messages to it	contract	until you disconnect the computer or delete your account
Permission level: the name of the level your computer reports when it connects (`chat`, `files`, `ask` or `full`), the time of each change, and the name of the computer it came from. Only the level name — never what your Claude did	our record of the level you chose, including that you selected `full`; shown to you on your dashboard	legitimate interests	until you delete your account. This history is kept even after you disconnect the computer, because it is our evidence of the level that was chosen
Usage counter: number of messages relayed per month	to apply your plan's limits	contract	13 months
Reminders: the text and time of reminders your assistant schedules through our server	to send you the reminder when it is due, even if your computer is off	contract	stored encrypted; deleted as soon as the reminder fires or is cancelled
Activity log: event type, time, and size only — e.g. "message in, 42 chars", "approval: allow", "paired"	security, abuse prevention, showing you your own recent activity, debugging	legitimate interests	30 days
Session cookie `ella_session` (and, for a few minutes during Google sign-in or connecting Google, `ella_oauth` / `ella_gconnect`, and `ella_terms_ok`, which carries your sign-up tick through Google sign-in; and `ella_src`, for up to 10 minutes during Google sign-in or sign-up, a short code of the link or post you came from, which we attach to your sign-up (it is our own cookie, not used to follow you around the web))	to keep you signed in; to protect the Google sign-in and Google-connect flows; to know which link or post brought you	contract / strictly necessary; legitimate interest (`ella_src`)	30 days / 10 minutes each
IP address	rate limiting and abuse prevention	legitimate interests	held in memory only; not written to our database, and we keep no web-server access logs of visitor IP addresses
Payment details (once paid plans open)	billing, tax and accounting duties	contract / legal obligation	handled by our payment processor; we never receive your full card number. Receipts are kept for the period tax law requires (7 years in Israel)
Email you send us	to answer you	legitimate interests	up to 2 years
Conversation (chats answered by our server only)	the recent messages and replies in each chat (up to about the last 20 exchanges), and the messages our server posts into that chat (call results, reminders that fired, files sent from your computer), with their times; the chat's language	so your assistant can follow the conversation — including after our server restarts — and knows what the server already told you	contract	stored encrypted; deleted 30 days after the chat's last message, when you say "forget" in that chat, or when you delete your account
Assistant memory (chats answered by our server only)	the notes your assistant keeps about you: what you ask it to remember, and ordinary facts it saves on its own, quietly, without telling you each time. If a fact is sensitive, it asks you first and saves it only on a clear yes (see "Sensitive details awaiting your answer" below). You can see, edit and delete these notes on your dashboard (My memory). They are deleted automatically 30 days after they are saved, unless you choose to keep them longer (see "Your consent to keep memories longer" below)	so your assistant remembers you between conversations	contract	stored encrypted; deleted automatically 30 days after they are saved, unless you have allowed us to keep your memories for longer: then until you or your assistant delete them, or you delete your account. Memories saved before this change are not deleted before 28 November 2026.
Your consent to keep memories longer (chats answered by our server only)	your choice "I allow my memories to be kept for more than 30 days", when you made it, the version of the wording you saw, and, if you withdraw it, when	to keep your saved memories after 30 days only if you ask us to, and to show that you did	your consent	until you delete your account. You can withdraw it at any time on your dashboard (My memory): memories older than 30 days are then deleted. The consent covers your memory notes only; your self-note, journal and conversation are always deleted 30 days after the chat's last message
Self-note (chats answered by our server only)	one short note (up to 800 characters) that the assistant writes and keeps about you for each chat, to remember how to talk with you and what matters to you. The assistant updates it by itself as the chat goes on; each new note replaces the old one. It can contain anything you told the assistant, including personal details. You can see, edit and delete it on your dashboard (My memory)	so your assistant can adapt to you between messages	contract	held encrypted in our database, for that chat only. Deleted 30 days after the chat's last message, when you send /forget in that chat (on WhatsApp, "forget" also works), or when you delete your account. Copies in our backups are kept for 30 days and then deleted
Journal (chats answered by our server, only if switched on)	a short dated log of what is going on in the chat (up to 60 entries of 300 characters), written by the assistant in the background, used to help it keep the thread	so your assistant can follow a long conversation	contract	stored encrypted with your conversation; deleted after 30 days of silence, when you clear the chat, or when you delete your account; you can see and delete entries in My memory
Sensitive details awaiting your answer (chats answered by our server only)	if the assistant notices a special-category detail (health, sex life, religion, politics, origin, union, genetic or biometric data, criminal record, financial or ID numbers), it does not save it. It asks you once, naming the detail	to ask for your clear yes before keeping anything sensitive	consent	held encrypted for up to 10 minutes; saved only if you clearly answer yes; any other answer, or the 10 minutes passing, deletes it
Files you share in a chat answered by our server	the text read from a file, or a description of a photo or PDF, plus its name	so your assistant can keep referring to it for a short while	contract	stored encrypted; deleted after 30 minutes
Phone calls (with your own ElevenLabs account, or — only for accounts we approve personally — with our built-in voice; offered to a closed group of users while in testing)	your ElevenLabs API key (stored encrypted) and the id of the phone agent we create in your ElevenLabs account — or, with the built-in voice, the id of your phone agent in our ElevenLabs account and the voice you chose; for each call you confirm or make to us: the number called (or your number, for a call to us), who it was to, what you asked us to do, its time and length; and a one-word record of when in the call the recording notice was played, a summary, and the transcript; a scrypt hash of your calling-in PIN; daily call counts; a one-way hash of the number called (not the number itself), kept 30 days, only to limit repeated calls to the same number; and, if you confirm it on the call card, whether to speak to the person you call in the masculine or feminine form, saved against a one-way hash of the number (not the number itself) so that the assistant speaks correctly next time	to place the calls you ask for in your own voice, to let you call in, to tell you how each call went, and to apply the daily call limits; to address the person you call correctly	contract	key and agent id: until you disconnect ElevenLabs or delete your account. Call details, summary and the number-called hash used for the daily limit: 30 days. The masculine/feminine choice for a number: 180 days after the last call you confirmed to that number, or until you delete your account or ask us to forget your calls; switching calls off alone does not delete it. Transcript: 7 days. The audio is recorded by ElevenLabs in your ElevenLabs account (with the built-in voice: in ours) and we delete that conversation there as soon as we have fetched its summary (and ElevenLabs is set to delete it within 2 days in any case). A built-in phone agent is deleted when you delete your account
WhatsApp opt-out record	the phone number and a flag that you were told you are talking to an AI and whether you sent STOP	to honour a STOP even if the number is later linked to another account	legitimate interests	we keep this record after you delete your account, so a STOP is still honoured if the number is ever linked to another account. We keep no message content in it
Voice billing record	for each use of built-in voice: date, seconds or characters used, and cost. It carries no content	for our own billing and plan limits	contract	kept for our accounts; after you delete your account the record is kept without anything that identifies you

4. What passes through but is not kept

When your assistant runs on your computer, the following travel through our server to deliver them and are not written to disk or to any log: the text of your messages and your assistant's replies; photos, files and voice notes (streamed through with single-use, 10-minute tickets); and, at permission level ask, the description of the action your Claude is asking you to approve (the command, file path or URL) and your Allow/Deny answer.

Because this content does pass through systems we operate, we are responsible for protecting it in transit, and we do (section 8). But we do not read, analyse, keep or use it.

Chats answered by our server. When our server answers your chat (WhatsApp, and Telegram when your assistant runs on our server), it keeps the conversation, your assistant's memory notes and recently shared files as listed in section 3, encrypted at rest. It also keeps a short note about you for each chat (the self-note, section 3), and, if switched on for your chat, a journal, so it can adapt to you and follow the thread; both are sent to Anthropic, our processor, together with your messages. You can see, edit and clear them on your dashboard (My memory), or clear the self-note and journal by sending /forget in that chat. In these logs it writes only the kind and size of an event, never message text. Today the encryption key is held by our server. That protects the data if the database or a backup is copied, but it means someone with administrator access to the server could technically decrypt it. We do not read it as a matter of routine, and we open stored data only where there is a real need (section 8). We are working on giving each person their own key, so that we can delete your data but never read it, and we will update this policy when that is in place. Photos, voice notes and other media themselves are never written to disk.

Voice notes — the Google option (not in use). Besides the built-in voice below, a second way of transcribing voice notes is built but switched off. If it is ever switched on, for accounts we approve personally for built-in voice, a voice note you send will be turned into text by Google Cloud Speech-to-Text, a processor acting on our behalf that may process it outside Israel (section 9), so that your assistant can read it. The audio will be sent to Google for that one request and will be kept by neither Google (we will use it without data-logging) nor us; what we will record is the number of seconds transcribed, for our own cost control. Voice notes longer than one minute will not be transcribed. We will update this policy before this goes live.

Built-in voice (server-answered chats). Built-in voice is not part of any plan: it is available only to accounts we approve personally, whatever their plan (trial, Free or paid). For such an account, when your chat is answered by our server, a voice note you send on WhatsApp or Telegram is turned into text by ElevenLabs (speech to text), a processor acting on our behalf that may process it outside Israel (section 9), so that your assistant can read it; your assistant's answer can be turned back into speech by ElevenLabs (text to speech) in the voice you chose, and sent to you as a voice note. We do not keep the audio — a voice-note reply is held in our server's memory for at most 15 minutes so WhatsApp can fetch it, and is never written to disk. ElevenLabs keeps a copy of each spoken answer in our ElevenLabs account's history; we delete it there as soon as it is made. ElevenLabs may keep the text of a transcribed voice note in our account under its own retention terms. What we record, for our own cost control and billing, is the length of each voice note heard and spoken, ElevenLabs' charge for it, and the time; when you delete your account these billing lines are kept without anything that links them to you. You can turn voice-note replies off on your dashboard.

Your own ElevenLabs key (any account, at no charge from us). Any account that has phone calls switched on, trial, Free or paid, may instead connect its own ElevenLabs API key on the dashboard. Your voice notes are then transcribed, voice-note replies spoken, and phone calls run in your ElevenLabs account, under your own agreement with ElevenLabs, which is your provider for this, not our processor. We store your key encrypted (section 3), use it only for your own requests, never log it, and charge nothing for it; ElevenLabs bills you directly under its own terms, and we record no voice minutes for you. You can disconnect the key at any time on your dashboard; it is deleted when you do, or when you delete your account.

5. What we never receive

Your Anthropic or OpenAI login (for Claude Code, ChatGPT or Codex), API keys or session; your ElevenLabs or other third-party keys (except an ElevenLabs key you connect for voice notes and phone calls — sections 3 and 4); the files on your computer (other than ones you or your assistant deliberately send through the chat); your assistant's memory and notes (when your assistant runs on your computer — for chats answered by our server, see section 3); your Obsidian vault; the local log at ~/.ella/ella.log; and the consent record at ~/.ella/consent.log (the permission level you chose, the Telegram account you approved, and each action you allowed or denied). All of these stay on your computer. For that information you are in control, and we are not its controller.

6. Sensitive information

We do not ask you for sensitive information and we do not save it without asking. If you tell your assistant something sensitive (for example about your health), it can pass through the conversation as described in section 4. The assistant will not save it to your memory notes, self-note or journal unless it first asks you and you clearly say yes (section 3). Your recent conversation, including what you wrote, is still kept encrypted for 30 days so the assistant can follow the chat. A sensitive detail you said yes to saving is a memory like any other: it is deleted 30 days after it is saved, unless you have separately allowed us to keep your memories for longer. You can clear it at any time (section 10).

7. Who else handles your information

Telegram carries everything you send to and receive from the bot. Bot chats are not end-to-end encrypted, and Telegram handles them under its own privacy policy as an independent controller.
Anthropic or OpenAI, whichever engine you use (Claude Code from Anthropic or, where offered, Codex from OpenAI), receives your prompts and your assistant's context from your computer, under your own account, not from us. Its privacy policy and your settings there apply. We have no access to that data and no say in how it is handled. For chats answered by our server, Anthropic receives your message, the recent conversation and your assistant's memory notes from our server, as our processor, under our API account. It may process them outside Israel (section 9).
Google, only if you choose "Continue with Google": we receive your Google account ID, name, and email address (only if Google reports it as verified). We request nothing else and get no access to your Gmail, Drive or contacts.
Our hosting provider (Vultr; server located in Tel Aviv, Israel) stores our database (including routine backups) and runs our server, as our processor.
Google Cloud Speech-to-Text — not in use yet (section 4). When voice-note transcription launches, it will, only when you send a voice note, receive the audio of that voice note, as our processor, to turn it into text for your assistant. It may process the audio outside Israel (section 9).
Payment processor (once paid plans open) — named at checkout.
Services you connect yourself on your own computer (for example ElevenLabs for voice, or any MCP tool) receive data directly from your computer under your own account with them.
ElevenLabs, for the built-in voice on accounts we approve personally (voice notes and phone calls, as our processor, in our ElevenLabs account — section 4) and, if you connect your own ElevenLabs key, as your own provider, in your own account under its own terms: it runs each call's conversation, including with a language model (currently Google's Gemini, hosted under ElevenLabs' own arrangements) which receives the call audio, what the other person says and the task you gave. Twilio carries your WhatsApp messages and our phone calls, as our processor. Both ElevenLabs and Twilio may process data outside Israel (section 9). Usually the person you call is not told at the start of the call that an AI is calling for you; for some kinds of calls (medical, legal, debt, emotional or negotiation matters) the assistant begins by saying that it is an AI assistant calling for you. If they ask whether they are speaking to an AI, the assistant says truthfully that it is. A short notice that the call is recorded is played near the start, as soon as the person answers the greeting, and in any case before the assistant says what the call is about; the call is recorded and transcribed as described in section 3.
Authorities, only where we are legally required to, and then only what is required.

We do not sell or rent personal information, do not share it for advertising, and do not use it for direct marketing.

8. Security

In summary: messages are routed only by your Telegram-verified account ID to the one computer paired with it; passwords are stored as salted scrypt hashes, and keys, device secrets and session tokens only as SHA-256 hashes, so a copy of our database logs nobody in; all traffic to our server is encrypted with TLS; pairing requires both a code and a confirmation at your keyboard; your permission level is chosen and enforced on your own computer and cannot be raised by our server — your computer only tells us its name.

Our staff do not read your conversations, self-note, journal or memory notes as a matter of routine. A member of our staff can open your saved memory notes if you give your permission in your chat (you reply ALLOW); each time is logged and shown on your dashboard. When our staff open your account's data with one of our administration tools, that is also logged and shown to you on your dashboard (the staff-access card). The log does not cover work done directly on the server itself, which we do only where there is a real need. Separately, the person who administers our server holds the technical means to open stored data, and we use it only where there is a real need, for example to investigate a security problem, abuse or a fault, to comply with the law, or to help with something you asked us for, and only as far as that need requires. We keep stored content for no longer than the periods in section 3.

Two limits you should know about. First, whoever controls our server could inject text to a connected computer — which is why the permission level lives on your machine, and why we recommend chat, files or ask rather than full. Second, at level ask the approval question and your answer both travel through our server, so the approval step protects you against your Claude's mistakes, not against a compromise of our server. No system is perfectly secure. You are responsible for the security of your own computer, phone and Telegram account — turn on Telegram's two-step verification and a passcode.

If a security incident affects your information, we will notify the Privacy Protection Authority and you as the law requires.

9. Where information is processed

Our server and database are in Israel. The European Commission recognises Israel as providing adequate protection for personal data. One exception, not yet in effect: voice-note transcription is not offered yet. When it launches, sending a voice note will send its audio to Google Cloud Speech-to-Text, our processor, which may process it outside Israel, including in countries whose law protects personal data less than Israel's does. We will make that transfer to Google as our processor under Google Cloud's terms for its customers' data, and only for the one transcription request (section 4), and we will update this policy before it goes live. Telegram, Google (for sign-in), and Anthropic or OpenAI (whichever engine you use) process data in other countries under their own terms and safeguards. If we engage any other processor outside Israel and the EEA, we will use the safeguards the law requires, such as standard contractual clauses.

10. Your rights

Wherever you live, you may ask us to: see the information we hold about you; correct it; delete it; and tell you how it is used. Under the GDPR and UK GDPR you may also ask for a portable copy (you can download one yourself, see below), restrict or object to processing based on legitimate interests, and withdraw consent at any time.

You can do most of this yourself:

Delete your account from the dashboard (Delete my account). This immediately and permanently removes your account record, your key, your connected computer, its pending reminders, your usage counters, your activity log and your sessions from our database. Copies of our data made for safekeeping (backups) are kept for 30 days and then deleted. If you delete your account, your data leaves the live system at once and leaves backups within 30 days. Receipts, once they exist, are kept as tax law requires.
Download your data from the dashboard (Download my data, in My memory and in Account settings): a file with what we hold about your account. It leaves out your password, sign-in tokens, your ElevenLabs key and other people's details. For anything the button does not cover, write to us (below).
Delete what is on your computer: run ella unpair and remove the ~/.ella/ folder.
Choose how long your memories are kept: on your dashboard (My memory) you can allow us to keep your memories for more than 30 days, and withdraw that at any time. Without your consent, they are deleted 30 days after they are saved. You can also see, edit and delete each memory yourself at any time.
Delete your chat: clear the conversation in Telegram.

For anything else, write to [email protected]. We answer within 30 days. If you are unhappy with our answer you may complain to the Israeli Privacy Protection Authority or, in the EU or UK, to your local data-protection authority.

11. Cookies

We use only our own cookies, listed in section 3. All of them keep the service working, except ella_src, which only records where you came from: ella_session (keeps you signed in), ella_oauth (protects the Google sign-in flow), ella_gconnect (protects connecting a Google account), ella_terms_ok (remembers, for 10 minutes during a Google sign-up, that you ticked the box agreeing to these terms) and ella_src (for up to 10 minutes during Google sign-in or sign-up, a short code of the link or post you came from). Your language choice is kept as ella_lang, a key in your browser's own storage, not a cookie; it stays on your device and we never see it. No analytics, no advertising, no third-party trackers — which is why you see no cookie banner.

12. Children

Atlas Assistant is for adults aged 18 and over. We do not knowingly collect information from children; if we learn that we have, we delete it.

13. Database registration and data-protection officer

As we understand the Privacy Protection Law after Amendment 13, the duty to register a database applies mainly to public bodies and to data brokers holding information about more than 10,000 people, and the duty to appoint a data-protection officer applies mainly to public bodies, data brokers, and organisations whose core activity involves large-scale sensitive information or systematic monitoring of people. Atlas Assistant is none of these at its present size, and it does not keep the content of your messages (section 4). On that basis we have not registered a database or appointed a data-protection officer. We review this as the service grows; if the law requires either, we will do it and update this policy.

14. Changes

We will post changes here with a new date. For material changes we will also notify you by email, in the dashboard or through the bot before they take effect.

15. Contact

Atlas · postal address provided on request · [email protected]