Privacy Policy

Version 1.0 · Last updated November 10, 2026

Leo ("the Service", "we") is a Hebrew-first personal assistant powered by artificial intelligence, available at https://leo-web-bay.vercel.app and in the Android and iOS apps. This policy explains what data we collect, why, who we share it with, how long we keep it, and your rights. It covers the website, the apps, and any channels you connect (for example Telegram). The Hebrew version is the primary version; if they differ, the Hebrew version prevails.

Summary

• We collect only what Leo needs to work for you: your account, your chats, what you attach, and what you ask Leo to do.
• No ads, we do not sell data, and there are no third-party tracking or analytics tools on the website or in the apps.
• We do not use your data to train models, and our AI providers are contractually committed not to train on API data.
• Every action that leaves the Service (sending an email, creating a calendar event, updating a contact, generating a document) waits for your approval.
• You can view, edit and delete your data in Settings, and delete your account (see Delete Account).

Data we collect

Sign-in and account data

• Google account: name, email address, profile picture and account identifier, received when you sign in with Google.
• An internal user ID, and the date you consented to data storage.
• Business details you choose to enter (business name, logo, contact details, profession), used in documents Leo creates.

Content you create or send

• Chats: your messages and Leo's replies, chat titles, projects.
• Voice messages and call recordings: the recording and its transcript (see "Retention").
• Files and images you attach, and documents Leo creates for you (PDF, Word, Excel, PowerPoint).
• Memory: notes, facts and preferences you ask Leo to remember.
• Reminders, tasks and lists.
• Customers (CRM): contacts, interactions, deals and follow-ups you add. These are details of other people that you manage, and you are responsible for having the right to store them. We do not access your device's address book.
• Approval cards for actions (email draft, event, update) and your decision on each.

Data from Google (Gmail and Google Calendar)

When you sign in, Google asks you to grant Leo these permissions:

• Read email (gmail.readonly): to summarize recent emails, find an email or an address, and answer questions about your email, only when you ask. If you enable important-email alerts, the Service checks once a day for important unread emails and notifies you (only the IDs of emails already notified are stored).
• Send email (gmail.send): to send an email you prepared with Leo, only after you approve it on a card. We have no access to your Gmail drafts.
• Calendar events (calendar.events): to show your events and create an event, only after you approve it on a card.
• Google Drive files Leo created (drive.file, only if you turn on saving expenses to Drive): to keep a copy of invoices and receipts imported from your email. This permission gives access only to files and folders Leo itself created, not to the rest of your Drive.
• Read Google Drive files (drive.readonly, only if you turn on "Calls from Drive" and accept the explanation on that screen): to process call recordings your phone uploads to one folder you chose. Leo accesses only that folder, never opens recordings of people and numbers you excluded, and never changes or deletes any file in your Drive. The copy of the recording is deleted right after transcription, and the transcript and summary are deleted after the number of days you chose (30 by default). The other party's voice is in the recording too, so it is good practice to tell them the call is recorded.

We store your Google access token to carry out your requests. Email and event content is not stored separately, only to the extent it appears in a chat (for example a summary Leo wrote for you). You can revoke these permissions at any time in your Google account settings (myaccount.google.com/permissions). Deleting your data in Leo also deletes the token we store.

Saved logins (vault)

You can save a username and password for websites so Leo can sign in on your behalf in a task you approved. Leo (the model) never sees the password, and fills it in only on the website it belongs to. There are two kinds:

• Logins protected by a vault password: encrypted on your device with a key derived from a vault password only you know. The vault password is never sent to us or stored by us, so we keep nothing that would let us open or recover these logins. When you approve a use, only that login's details are sent over an encrypted connection, kept encrypted for at most five minutes for a single fill, and then deleted. Please note: as with any client-side encryption on a website, the code running in your browser is served by our server.
• Standard logins: encrypted on the server. The encryption key is kept in the server configuration, separately from the database, and every use is recorded in a log visible to you.

While a login is used, the details are typed into the website inside a cloud browser run by a sub-processor (Browserbase). Every save, approval and use is logged in a log visible to you, without the password values. Do not store one-time codes, backup codes, CVV or card numbers in the vault. Passwords typed in chat are masked and not stored, but it is better not to type them there at all.

Technical and usage data

• Usage and cost records: for each action (message, search, transcription, document) we record the action type, amount of usage and cost, without the content. This powers your usage screen, credit calculation and cost control.
• Notifications: a push token for your browser or device, to send you reminders and replies.
• Cloud browser: when Leo opens a website for you, the task's addresses, steps and screenshots are stored.
• Cookies: only cookies strictly necessary for sign-in and keeping your session. No advertising or tracking cookies.
• Server logs at our hosting providers (for example IP address and request time), for security and operations.

We do not collect location, financial data (there are no payments in the Service today), or information about other apps on your device.

Sensitive data

The Service is not designed to collect sensitive data (such as health information), but if you write it in a chat or attach it, it is stored and processed like any other content, in order to answer you. You can delete it at any time.

How we use data

• To provide the service you asked for: answer you, perform actions you approved, keep reminders and create documents.
• To remember what you asked Leo to remember, and continue conversations.
• To send notifications you enabled.
• To manage your account, usage and credits, and prevent abuse.
• To secure the Service, fix problems and answer support requests.
• To comply with legal obligations.

Legal bases: your consent (given on the consent screen at first sign-in, which you can withdraw by deleting your data), performance of the service you requested, and legal obligations.

We do not use your data to train models, and our AI providers are contractually committed not to train on API data. We do not sell data, use it for advertising, or build marketing profiles.

Google API Services: Limited Use

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

In practice, data from Gmail and Google Calendar:

• Is used only to provide and improve the user-facing features you see and request in Leo (summaries, search, and sending or creating items you approved).
• Is transferred to third parties only as necessary to provide a feature you requested (for example the AI provider that processes the request), at your explicit request, for security purposes, or to comply with applicable law.
• Is not used for advertising, is not sold, and is not used to train generalized AI models.
• Is not read by humans on our team, unless you asked us to (for example in a support request) and consented, it is necessary for security or abuse investigation, or the law requires it.

Who processes data (sub-processors)

We use providers that process data on our behalf, under our instructions, only to run the Service:

• Anthropic (Claude): the AI that answers you. Receives your messages, attached files, transcripts, and email and calendar content Leo reads at your request. Includes web search and page reading, and running calculations in an isolated environment.
• Supabase: database, file and recording storage, and authentication.
• Vercel: hosting of the website and server.
• Google: sign-in, Gmail and Calendar (per the permissions you granted), and Firebase Cloud Messaging for app notifications.
• Soniox or Groq: transcription of voice messages and call recordings.
• Browserbase: cloud browser for opening websites for you, when the feature is enabled.
• Telegram, WhatsApp (Meta), Postmark: only if you connected such a channel (Telegram bot, WhatsApp, or writing to Leo by email), messages in that channel pass through them.
• ElevenLabs: song generation, only when the feature is enabled and you asked for it.
• Payment provider: if and when payments are enabled, payment details will be processed by a payment provider and not stored by us. We will update this policy beforehand.

Read-aloud runs in your browser or device, without a server. There are no advertising, analytics or crash-reporting providers.

International transfers: some providers are located outside Israel (mainly in the United States and Europe), so data is transferred to and stored outside Israel, subject to our agreements with the providers and applicable law.

Other sharing: we do not share data with others, except: at your request (for example an email you sent, or a contact you shared with your team in Leo), as required by law or court order, or to protect rights and safety and prevent fraud. If the Service is sold or merged, data will be transferred subject to this policy, and we will notify you in advance.

Retention

• Chats, files, memory, reminders, tasks and CRM: until you delete them, or until you delete all your data or your account.
• Voice messages: until you delete them. If you delete a recording, its transcript stays in the chat until the chat is deleted.
• Call recordings uploaded for transcription: deleted right after a successful transcription. If transcription fails, kept up to 24 hours for a retry.
• At the transcription provider: Soniox deletes the transcript right after we receive it. Groq receives the file for the request only.
• Login details in use (vault): the transit copy is deleted after one fill, and at most after five minutes.
• Google token: until you delete your data or account. Revoking access in Google stops access immediately.
• Usage and cost records: while the account exists, for your usage screen, billing and control, until account deletion.
• At Anthropic: per our agreement, API request data is retained for a limited period for safety and abuse monitoring, then deleted.
• Backups: copies in our database provider's backups are deleted according to its backup cycle.

We keep data longer only if the law requires it, and only as needed.

Your rights

Under the Israeli Protection of Privacy Law, 5741-1981 (including Amendment 13), and similar to the rights under the GDPR in Europe, you have the right to:

• Access your data and receive a copy. Most data is visible to you directly in Settings and your chats.
• Correct inaccurate data. You can edit notes, contacts and business details directly.
• Delete data: a voice message, a chat, a note, a contact, all your data, or your whole account (Delete Account).
• Withdraw consent and revoke Google permissions.
• Restrict or object to certain processing, and receive your data in a common format (portability).
• Complain to the Israeli Privacy Protection Authority, or to the supervisory authority in your country.

For requests: (support email not configured). We will respond within 30 days, and may ask you to verify your identity.

Security

• All communication is encrypted (HTTPS).
• Access to data is restricted per user at the database level (Row Level Security): each user sees only their own data, and what they chose to share with their team.
• Recordings and files are kept in private storage and opened only through temporary links.
• Vault logins are encrypted (as described above).
• Service keys and secrets are kept in the server configuration, not in the code.

No security is perfect. If we discover a security incident affecting your data, we will notify you and the authorities as required by law.

Age

The Service is intended for users aged 18 and over. We do not knowingly collect data from minors. If we learn that a minor is using the Service, we will delete the account.

Changes

If we change this policy, we will update the version and date at the top of this page. For material changes we will notify you in the Service and, if needed, ask you to consent again.

Contact

Privacy questions and requests: (support email not configured). See also the Terms of Use and Support.