Privacy Policy
Ellipsa is a desktop assistant that runs on your own computer. This policy explains what information Ellipsa uses, where it is kept, who it is shared with, and the choices you have. In this policy, "we" and "us" mean the developer of Ellipsa, and "you" means the person using it.
1. The short version
- Your memory (the people, conversations, events, tasks and drafts Ellipsa builds up) is stored on your own computer, not on our servers.
- To understand and write text, Ellipsa sends the relevant pieces to OpenAI through a small relay we run. The relay passes requests through and does not store their contents.
- We do not sell your information, use it for advertising, or use it to train AI models.
- You decide what to connect and what Ellipsa observes, and you can delete everything at any time.
2. Information Ellipsa uses
Account information. When you sign in with Google, Ellipsa receives your name, email address and profile picture. Your email address is also used to confirm that you are an invited tester.
Services you connect. Ellipsa only reads a service after you connect it. Depending on what you connect:
| Service | What Ellipsa reads | What Ellipsa can do, with your approval |
|---|---|---|
| Gmail | Messages and their metadata (senders, recipients, subjects, dates, labels) | Create drafts, send email, apply labels, mark messages read |
| Google Calendar | Your events and their attendees (including their video-call links), and when you are free or busy | Create and update events, including sending invitations |
| Google Docs and Sheets | Only the files Ellipsa creates for you; it cannot open your other files | Create documents and spreadsheets, and edit the ones it created |
| Slack | Messages in the direct messages, group messages and channels you belong to, and the names and email addresses of members | Post messages |
| Notion | Only the pages you choose to share with Ellipsa when you connect, and who edited them | Create and update pages, if you grant that |
| GitHub | Issues, pull requests and comments you are involved in, and the people on them | Create issues and comments |
Inbox tidying. Unless you turn off "Keep my inbox clear" in Settings, Ellipsa moves automated mail (newsletters, promotions and notifications) out of your Gmail inbox on its own, without asking each time: it is archived, marked read and labelled "Ellipsa/Tidied", never deleted, and one click in the briefing puts it back. Mail from a person, starred mail, and notifications that need you (such as failed payments, security alerts and sign-in codes) are left where they are.
Activity on your computer. Depending on your settings, Ellipsa can observe the name of the app and window you are using, text visible on your screen (read on your computer), your clipboard, and audio from your microphone and computer during sessions you start. Each of these can be turned off in Settings, and specific apps and websites can be excluded.
Meetings. During a session you start, your microphone and your computer's audio are transcribed separately, so the transcript shows what you said and what others said. Unless you turn off "Name each speaker" in Settings, the computer's audio (or, when there is none, the microphone's) is also written to your computer, encrypted with a key used for that session only, until the meeting notes are written. It is then sent once to OpenAI to tell the voices apart, and deleted. If that cannot finish, it is deleted within a day. For a one-to-one call with a calendar invite, nothing is sent: the other person is named from the invite. To name the people on a call, Ellipsa also uses the calendar invite it matches the call to (by time or by its video-call link) and, during sessions you start, the names it read on your screen (for example in the meeting app); this happens on your computer, and those names go to OpenAI only as part of writing the notes. The transcript and notes are kept in your memory like any other conversation. When you choose to email the notes, they go through your Gmail to the people you pick.
What you tell Ellipsa. Your chats with Ellipsa, people you add, notes, decisions and settings.
Information about other people. Your email, calendar, messages and meetings naturally include information about other people, such as their names, email addresses and what they wrote or said. Ellipsa uses it only to help you, and you are responsible for having the right to share it with Ellipsa (see the Terms of Service).
3. How the information is used
Only to provide Ellipsa's features to you: building your memory of people and work, briefings, reminders and open loops, answering your questions, drafting emails and messages, scheduling, and the actions you approve. We do not use it for advertising, profiling for anyone else, or any unrelated purpose.
4. Where information is stored
Ellipsa's memory and the sign-in tokens for the services you connect are stored on your computer, in your user profile. We do not keep a copy. Anyone with access to your computer account may be able to access that data, so keep your computer secured.
5. Who information is shared with
OpenAI. To summarise, extract tasks, answer questions, transcribe audio, draft text and speak answers aloud, Ellipsa sends the relevant content (for example an email, part of a conversation, screen text, a short stretch of audio, or the recording of a meeting to tell its speakers apart) to OpenAI's API. Under OpenAI's API terms, this data is not used to train their models. OpenAI may keep it for up to 30 days to detect abuse, and then deletes it, unless the law requires otherwise. See OpenAI's privacy policy.
Our relay. Requests to OpenAI pass through a relay we run on Cloudflare, so that Ellipsa does not need to carry an OpenAI key. The relay checks that you are an invited tester and counts how many requests each tester makes per day, to limit costs. These counts are tied to your email address and are deleted automatically after two days. The relay does not store the contents of requests or answers. Cloudflare may keep standard technical logs as described in its privacy policy.
Usage and cost statistics. The relay also records, per tester, per day and per feature (for example meeting notes, live answers or chat), how many AI requests were made, how many tokens, seconds of audio, characters of speech and web searches each model used, and what they cost, so we can see what Ellipsa costs to run. Live transcription goes from the app straight to OpenAI, so the app reports the totals OpenAI gives it for each session (numbers only, never audio or text) to the relay. Unless you turn off "Help improve Ellipsa" in Settings, the app also sends anonymous usage events: which screens and features are used, how far setup gets, and errors (their type and a short message with email addresses, user names, links and long numbers removed). These never include your content: no messages, emails, names, titles, files or screen text. Both are stored in a Cloudflare database under a pseudonym derived from your account (not your email address), and are used only to improve Ellipsa.
The Mac waitlist. If you join the waitlist on our website, we store the email address you enter, the platform you asked for and the date, in the same Cloudflare database. We use it only to email you when that version of Ellipsa is available, and we delete it on request.
Beta requests. When you ask for the beta, on this website or by signing in to Ellipsa before you've been let in, we store your email address (for a sign-in, the one your Google account confirms), what you wrote about how you'd use it if you did, how you asked and when, and whether you've been let in. We are sent an email about your request (through Resend, an email service) so we can approve it. We use this only to decide who gets into the beta and to send you the installer, and we delete it on request.
Visits to this website. When you open a page of this website, it counts the visit through our relay: the page, the site that linked you here (if your browser says), the campaign name in the link (utm_source) if there is one, and whether you asked for the beta, joined the waitlist or played the film. The relay adds your country and whether you're on a phone or a computer, as Cloudflare reports them. To count a visitor once a day, it stores a code made from your IP address, your browser and the date with a secret; the code can't be turned back into your address and changes every day, and your address itself is never stored. No cookies are used and nothing is stored in your browser. These counts are used only to see how many people visit and where they come from.
The services you connect. When you approve an action, the content goes to that service (for example, an email you send goes through Gmail to its recipients).
Nobody else. We do not sell, rent or share your information with anyone else, except if required by law, or to protect against fraud or a security threat.
6. Google user data
Ellipsa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- Google user data is used only to provide and improve the features you use in Ellipsa.
- It is not transferred to anyone except OpenAI, as described above, when needed to provide those features, or when required by law.
- It is not used for advertising, sold, or used to determine creditworthiness or for lending.
- No person reads it, unless you give us permission for a specific message (for example when asking for help), it is needed for security, or the law requires it.
- It is not used to develop, improve or train general AI or machine-learning models.
Slack, Notion, GitHub, Linear and ClickUp data is handled the same way. Linear and ClickUp are connected with a personal API key you paste in Settings; it is stored on your computer like the other sign-ins.
7. Retention and deletion
- Ellipsa keeps information on your computer for the periods you choose in Settings, and deletes it after that.
- Settings → Delete all data permanently removes everything Ellipsa has stored. Uninstalling the app does not remove it on its own, so use that first.
- You can disconnect any service in Settings, and revoke access from the service itself: Google, Slack (your workspace's app settings), Notion (Settings → Connections) and GitHub. Disconnecting stops new access but does not delete what is already stored on your computer.
- To be removed from the waitlist, email us from the address you signed up with and we will delete it.
8. Security
Connections to Google, Slack, Notion, GitHub, Linear, ClickUp, OpenAI and our relay are encrypted. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.
9. Your rights
Because your data is stored on your computer, you can see, export, correct and delete it directly in Ellipsa. Depending on where you live, you may have further rights over your personal information, such as access, correction, deletion and objection. To use them, or to ask anything about the little we hold (your tester email and the daily request counts), contact us at the address below.
10. Children
Ellipsa is not intended for anyone under 18, and we do not knowingly collect information from children.
11. International use
OpenAI and Cloudflare may process information in the United States and other countries, which may have different data protection laws from yours.
12. Changes
We may update this policy. The current version will always be on this page with its date, and for significant changes we will let testers know before they take effect.