Koel

Privacy Policy

Last updated 29 July 2026

Koel reads your mail. That is the whole product, so this page is specific about what that means: what is fetched, what is written down, who else it reaches, and how long it stays. Where the honest answer is uncomfortable, it is the answer written here.

1.What Koel reads, and what each permission is for

When you connect your Google account, Koel asks for the permissions below and nothing else. Each one exists to power a feature you can see in the app.

  • Your Google account email and basic profile. To identify the account you connected and address you by name.
  • Gmail (gmail.modify). To read your mail, draft and send replies and follow-up nudges after you explicitly approve them, and organise messages with labels. Koel never permanently deletes anything in your mailbox.
  • Google Calendar (calendar.readonly, calendar.events). To show today's events in your brief and in the Inbox agenda, and to create or change an event when you ask for one.
  • Google Tasks (tasks). To read your reminders, and to add, complete, reschedule or delete one when you tap — so your reminders stay in sync with your phone.
  • Google Drive — read-only (drive.readonly). To list file names, types and dates so Koel can find the document a message refers to. Koel does not sync or copy your Drive files.

How the reading works in practice: the first sync looks back seven days and each run reads at most 500 messages; chats and drafts are excluded, and so is anything under a label you tell Koel to skip; attachments are never fetched — Koel reads the plain-text or HTML part of a message and nothing else.

2.What Koel stores

Koel is not a viewer onto Gmail — it keeps a copy of what it reads in its own database, so the queue works without going back to Google every time.

  • Your messages. Subject, sender and recipient names and addresses, the message snippet, the full set of message headers, and up to the first 4,000 characters of the message body — plus the summary, category and draft reply Koel generates from them.
  • Your Google tokens. The access and refresh tokens for each Google account you connect, held in our Supabase database, encrypted at rest by the provider and readable only by your own account and Koel’s server jobs.
  • Replies you approved. The full text of every reply Koel sent for you, its recipient, and whether it succeeded, failed, or could not be verified.
  • Sync diagnostics. For each sync, up to 25 records of messages that were skipped — including their sender address and subject line — so failures can be debugged.
  • Everything you type. Tasks, notes on a message, feedback you send, workspace names, and the email address of anyone you invite.
  • An action log. What was done, when, and by whom — including recipient addresses and subject lines for sends, and invitee addresses for invites.
  • Your account. Your email address and display name. Your password is never stored by Koel; sign-in is handled by Supabase.

3.Who else sees it

Koel is not the only system that touches your mail. These are all of them, and what each one receives.

  • Google Gemini, through Lovable's AI gateway. This is what actually reads your mail. For every new message, it receives the sender's name and address, the recipient address, the subject, up to 4,000 characters of the body, your first name, your own email addresses, and the names of your workspaces. It returns the importance, category, summary and draft reply. A second, smaller call sends a subject line and the first 400 characters of a message when Koel drafts a follow-up nudge.
  • Anthropic (Claude). Receives only what you type into the command palette or the Brainstorm screen. It is not sent your mail.
  • Resend. Receives the email address of someone you invite, to deliver the invitation.
  • Supabase. Hosts the database and handles sign-in. Everything described in section 2 lives there.
  • Google Fonts. Every page load fetches fonts from Google, which means Google sees your IP address and browser.

There is no analytics, no tracking pixel, no advertising network and no third-party script anywhere in Koel. Your data is not sold, and it is not shared with anyone not listed above.

4.Google user data, specifically

Koel'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.

You can read that policy in full at developers.google.com/terms/api-services-user-data-policy. Google data is used only to provide the features described on this page. It is not used for advertising, it is not sold, and no model is trained on it by Koel. As set out above, message content is sent to Google Gemini through Lovable's gateway for classification and drafting; how those two companies handle it is governed by their own terms, which Koel cannot vary.

No person at Koel reads your mail as a matter of routine. Someone may need to look at a specific record to fix a fault you report, to deal with a security problem, or where the law requires it.

5.How long it is kept

Indefinitely. Koel has no retention window and no automatic deletion — stored messages, bodies, headers, drafts, sent copies and log entries stay until someone removes them.

You are in control of the clock. Disconnect any connected account at any time from Settings → Connections: the stored Google tokens for it are deleted and all further reading stops immediately. Ask for deletion and we purge the stored tokens and the derived data — messages, summaries, drafts, sent copies and log entries — for your account.

6.What you can do about it

  • Disconnect a mailbox at any time from Connections.
  • Delete a task, revoke an invite, or remove someone from a workspace, from the app.
  • Ask for a copy of your data, or for your account and its data to be deleted, by writing to vv4567@gmail.com. There is no self-serve export or delete button yet — the request is carried out by hand, and we would rather say so than put up a button that does not work.

7.Security, and its limits

Your tokens and the data derived from them live in our Supabase backend. Traffic runs over HTTPS, storage is encrypted at rest by the database provider, and every row is access- controlled per user by row-level security, so one account's data cannot be read by another through the app. It is never sold and never shared with third parties beyond the processors named in section 3, and it is used solely to provide the Koel service to you. Your sign-in session is kept in your browser's local storage.

What Koel does not claim: no security certification, no audit, and no second layer of application-level encryption on top of the provider's encryption at rest. Background jobs on the server use a key that can read across accounts, because that is how syncing works.

8.Cookies

One cookie, sidebar_state, which remembers whether the sidebar is open and lasts seven days. Your sign-in session and two display preferences are kept in local storage. None of it is used for tracking.

9.Children

Koel is not intended for anyone under 18, and accounts should not be created for them.

10.Changes, and how to reach us

This policy changes when the software does — the date at the top is the version. For anything at all, including a deletion request, write to vv4567@gmail.com. The Terms of Service cover the rest of the relationship.

Questions, requests or complaints: vv4567@gmail.com. Koel is early software and these pages are written by the people who build it, not by lawyers — they describe what the software actually does today, and they change when it does.

← Back to Koel