Privacy Policy

Last updated: August 13, 2026

EmailOps is a local-first, open-source email client for macOS, Windows, and Linux, developed by Gerónimo Di Pierro (“I”, “me”). This policy explains what data EmailOps accesses, how it is used and stored, and the choices you have. Sections 1 to 6 cover the app; section 7 covers this website. The short version: your email never touches my servers, because EmailOps has no backend.

1. Data EmailOps accesses

When you connect an email account (Google, Microsoft, or IMAP/SMTP), EmailOps accesses, on your device:

Email messages — headers, bodies, attachments, and labels/folders, to display and organize your mail.
Sent mail — messages you compose are transmitted to your provider for delivery.
Calendar events — titles, times, attendees, and meeting links, to display your calendar and remind you of upcoming meetings.
Basic profile information — your email address and name, to identify the connected account in the app.

2. Google user data

If you connect a Google account, EmailOps requests the following OAuth scopes, each tied to a specific user-facing feature:

Read and modify Gmail (gmail.modify) — to download your messages for display and search, and to archive, label, and mark messages read/unread when you do so in the app.
Send mail (gmail.send) — to send messages you compose, only when you press Send.
Calendar events (calendar.events) — to display your calendar and to create or edit events you add in the app.
Calendar list (calendar.calendarlist.readonly) — to show which calendars the account can see, with their names and colours. This reads only the list of calendars, never their contents.
Basic profile (userinfo.email, userinfo.profile) — to label the account inside the app.

Limited Use disclosure: EmailOps’ 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.

EmailOps does not use Google user data to develop, improve, or train generalized artificial intelligence or machine learning models. AI features run inference only; no model is trained on your data.

3. Where your data is stored

All email and calendar data is stored locally on your computer, in a SQLite database inside the app’s data directory. Search indexes and AI embeddings are computed and stored locally. OAuth tokens and passwords are stored in your operating system’s secure credential store — the macOS Keychain, Windows Credential Manager, or the Linux Secret Service — never in plain files. EmailOps has no backend: there is no server of mine for your mail to pass through, and I cannot access your data. The app has no cloud sync, no telemetry, and no analytics — for the website, see section 7.

4. When data leaves your device

EmailOps transmits data only in these cases, always over encrypted connections (HTTPS/TLS):

To your email provider (Google, Microsoft, or your IMAP/SMTP server) to sync mail and calendars and to send messages you compose.
To a remote AI provider, only if you opt in. By default, all AI features (drafting, summarizing, chat, classification) run entirely on-device using a bundled local model. You may optionally configure a local Ollama instance (stays on your machine) or a remote provider (OpenRouter). If you choose a remote provider, the content needed for the feature you invoke (e.g. the message being summarized) is sent to that provider and is subject to its privacy policy. This is off by default and used only for actions you initiate.
Model downloads. The app downloads AI model files from Hugging Face. No user data is sent in these requests.

I never sell your data, never share it with advertisers, and never transfer it to third parties except as described above.

5. Data retention and deletion

Your data stays on your device until you delete it. Removing an account in EmailOps deletes its locally stored mail and calendar data and its stored credentials; uninstalling the app removes all local data. You can revoke EmailOps’ access to your Google account at any time at myaccount.google.com/permissions (or the equivalent Microsoft page). Revoking access does not delete anything on your Google account — it only stops EmailOps from accessing it.

6. Security

Credentials live in your operating system’s secure credential store; all network traffic uses TLS; email HTML is sanitized before rendering; remote images are blocked by default. Your local database is protected by your operating system user account (I recommend full-disk encryption: FileVault, BitLocker, or LUKS). On Linux, EmailOps refuses to start if no Secret Service provider is available, rather than falling back to storing your credentials somewhere less protected.

7. The website

This policy also covers getemailops.com. The site is a static page: no accounts, no forms, no newsletter. The only thing it collects is basic traffic statistics.

Analytics. I use Umami, which I host myself on my own server. It records the page visited, where you arrived from, your browser, your operating system, and your approximate location (country and region). Your IP address is used only to derive that location and to generate an anonymous visit identifier. It uses no cookies, stores nothing on your device, and cannot follow you across other sites. That is also why there is no consent banner to click.
Docs search. Search runs entirely in your browser, against an index downloaded along with the page: your query is never sent to a search service. The terms you search for are recorded in Umami, so I can see which topics the documentation is explaining badly. They are trimmed to 80 characters and tied only to that anonymous visit identifier — never to a name, an email address, or your EmailOps account.
Hosting. The site is served from AWS Amplify which, like any web host, processes the requests needed to deliver the page to you.

No advertising, no third-party trackers, no data sold or shared. The legal basis is legitimate interest in understanding how the site is used (Art. 6(1)(f) GDPR).

On deleting your statistics: I can’t, for the same reason this is private in the first place. No cookie, account, or identifier ties those visits to you, so I have no way of telling which ones are yours — Art. 11 GDPR covers exactly this case. If you would rather not appear at all, I honour your browser’s Do Not Track signal: with it enabled, nothing is recorded. Any content blocker stops the analytics too, and you lose nothing on the site.

8. Changes and contact

I will post any changes to this policy on this page with an updated date. Questions or requests: hello@getemailops.com.