Your workspace.
Your connections. Your choice.

What Zelos collects about you

Nothing. The people who make Zelos do not receive your mail, your calendar, your address, your name, a device identifier, usage statistics, crash reports, or a record that you installed it. There is no telemetry, no analytics, no automatic update check, no remote font, no remote image. The source is public. Outbound connections depend on your version and enabled features, as described below. The newer preview bundles dependencies for features such as PDF generation and email sending; it does not add app analytics.

This website is a static page on Netlify. It sets no cookies of its own and runs no analytics. Netlify keeps ordinary server logs for the requests that fetch it, under its own privacy policy. The wing introduction uses a session-only preference so it does not replay on every visit within the same tab.

Check for updates in the app asks GitHub for the latest public Zelos release only when you press it. That request includes no mail, calendar data, credentials or installed version. GitHub receives ordinary connection information, such as your IP address. Opening Settings does not start a check, and no update installs itself. The website demo does not perform this check.

What it reads, and where it keeps it

Zelos connects to your mail server over IMAP and only reads — recent messages from your inbox and from your sent folder. The sent folder is read by default, because what you promised is mined from what you yourself wrote; clear the sent folder's name under Settings → Email and it is left alone. It fetches them with BODY.PEEK, so nothing is marked read; it never sends, moves, labels or deletes a message. It reads your calendar the same way, from an address you give it. Each source you add in Settings is read from the one host its connector names.

Everything it reads, and everything it concludes, is stored in one folder on your own disk — ~/.zelos on macOS and Linux, your user profile on Windows — in a plain SQLite file with permissions limited to your account. Passwords, API keys and sign-in tokens go in your operating system's keychain (macOS Keychain, Windows DPAPI, Linux libsecret), never in a settings file; on a machine with no keychain they go in an encrypted file in that same folder, and the app tells you so.

The model you choose

To work out what needs you, Zelos sends what it read to a language model — and the model is the one thing here that is a third party. You pick it: a hosted provider you hold your own key for, or a model running on your own machine. What travels to a hosted model is message subjects, sender and recipient addresses, dates, and message bodies cut at 4,000 characters; calendar events — titles, times, places, who is invited, and their notes; your reminders; and the board it built last time, so it does not tell you the same thing twice. Turning Send message bodies off in Settings drops the bodies to a short stored snippet and drops event notes entirely — subjects, titles, dates and addresses still travel, because without them there is nothing to reason about. That request is inference only. Zelos trains nothing, operates no model, and keeps no copy of what it sent; how the provider treats it is governed by the provider's terms and the key you gave it.

A model served on your computer can process requests locally. A local or LAN address alone does not guarantee that: the server can be configured to route requests onward. Connected sources and optional services still use their own network connections.

Google user data

If you connect a Gmail or Google Workspace mailbox with Sign in with Google, Zelos asks Google for the https://mail.google.com/ scope, because it is the only scope Google offers for IMAP. Of what that scope permits, Zelos uses one part: reading. It does not send, compose, label, move, or delete mail, and it does not call the Gmail API.

Accessed: your mailbox, over IMAP, read-only, as described above. Used: to build the page Zelos shows you, to draft replies you send yourself, and to answer questions you ask about your own archive — all on your machine. Stored: on your own disk only; the sign-in token in your keychain. Shared: with nobody, except the model endpoint you configured, for the purpose above, at your direction. Never sold, never used for advertising, never read by a person at Zelos, never used to train or improve any machine-learning or AI model.

Zelos's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

During sign-in your browser talks to accounts.google.com, and Zelos exchanges the result at oauth2.googleapis.com; the same host refreshes the token while the app is sweeping. Mail itself comes from imap.gmail.com. You can revoke Zelos's access at any time at myaccount.google.com/permissions, and removing the mailbox in Settings deletes the token from your keychain. An app password works instead of sign-in if you prefer one.

Microsoft accounts

If you connect an Outlook.com, Hotmail, Live, MSN or Microsoft 365 mailbox with Sign in with Microsoft, Zelos asks for two permissions: IMAP.AccessAsUser.All, which opens the mailbox over IMAP, and offline_access, which lets it stay signed in. The same read-only rules apply; Zelos does not use the Microsoft Graph API and does not read anything but mail.

The sign-in is a code you type at microsoft.com/devicelogin; Zelos talks to login.microsoftonline.com to get and refresh the token, and to outlook.office365.com for mail. Revoke it under your Microsoft account's apps and services, or by removing the mailbox in Settings, which deletes the token from your keychain.

Other providers

iCloud, Yahoo, AOL, Fastmail, Zoho and self-hosted mail connect with an app password you create on the provider's site; Proton connects through Proton Bridge on your own machine. The password goes in your keychain and is sent only to the mail server you typed, over TLS — Zelos refuses to send it in the clear to any host that is not your own computer. When you type an address on a custom domain, Zelos asks your system's DNS resolver who handles that domain's mail; the domain goes to the resolver, your address does not.

AI access

If you turn on AI access in Settings, another AI client on your machine can read your board over MCP, using a separate token you mint and scopes you choose. That is a local connection you opened; nothing about it involves us. Every call it makes is logged in the app. Six of the seven tools it can be given only look; the seventh — the board — does the one thing opening Zelos does: a reminder you put off wakes up when its time comes, and Now is held to four items. Nothing sends, nothing deletes, nothing changes a setting.

Deleting everything

One mailbox

Settings → Email → remove the account. Its password or sign-in token is deleted from your keychain at the same moment; nothing else holds it. Then revoke Zelos at the provider if you signed in with Google or Microsoft.

All of it

Quit Zelos, then drag the Zelos folder to the Trash. Settings → Your data shows you where it is. That is every message, every conclusion, every setting. Keychain entries live under the service name com.zelos.app — remove the account first and they go with it, or delete them in Keychain Access, Credential Manager or your desktop's keyring.

Nothing remains with us

There is no copy anywhere else to ask us to delete. If you want to be certain of that, read the source: it is the whole program.

Children, changes, contact

Zelos is not directed at children under 13, and we have no way to know the age of anyone who runs it — we have no way to know that anyone runs it. If this policy changes, the change appears here with a new effective date; the app will not gain a new destination without this page saying so first.

Questions about this policy: open an issue at github.com/HoosAILLC/zelos. The source, the security document and the tests are at github.com/HoosAILLC/zelos.