Privacy policy

The short version: this site runs no analytics, shows no ads and sets one functional cookie. It stores what you type into the beta form, because that is what the form is for. If you use the Meltemi desktop app, your mail lives encrypted on your own machine and never passes through this site — the only server-side pieces are the narrow sync endpoints described below, and each one stores the least it can.

Who is responsible

The controller for everything on this page is Entro314 Labs ΜΟΝΟΠΡΟΣΩΠΗ Ι.Κ.Ε. (Entro314 Labs Single Member P.C.), Cheimarras 3, 135 61 Agioi Anargyroi, Greece — reachable at ⟨contact email — fill before deploy⟩. Full identification is on the legal notice.

Visiting the site

There is no analytics script, no advertising code, no tracking pixel and no third-party embed on any page. The site’s hosting infrastructure processes your IP address and request metadata in ordinary server logs for the time needed to deliver pages and defend against abuse — the legal basis is legitimate interest in operating and securing the site (Art. 6(1)(f) GDPR).

The one cookie, NEXT_LOCALE, is set when you choose a language and only remembers that choice. It is described in full in the cookie statement; it needs no consent banner because there is nothing non-essential to consent to.

The beta form

The form asks for your email address and, optionally, what you use now and what you hate about it. That is the whole table — the address is stored trimmed and lowercased so asking twice stays one entry, and there is no way to read the list back over the web.

• Purpose: sending you a build and the messages around it. Nothing else — the address is not added to any other list.
• Legal basis: steps taken at your request prior to entering into a contract (Art. 6(1)(b) GDPR).
• Retention: until the private beta ends or you ask to be removed, whichever comes first. Write to ⟨contact email — fill before deploy⟩ and the row is deleted.

The sync backend, if you connect the app

The desktop app can register a device against this site to sync a small set of things across your own machines. Everything below is scoped to a device token you hold; none of it exists unless you turn the feature on, and the legal basis for all of it is performing the service you asked for (Art. 6(1)(b) GDPR).

• Device record — a label you chose and a hashed token. The plaintext token exists only in the registration response, on your machine.
• AI usage ledger — per-call accounting rows: feature, provider, model, tokens, duration, cost. Numbers about calls, never the content of your mail or of the call itself.
• Managed AI relay — if you choose the hosted AI tier, the text you send is forwarded to the AI gateway and the model provider serving the request, and the answer streams back. The server keeps an accounting row per call (model, tokens, cost, status) — not the conversation. The other AI tiers never touch this server at all.
• Settings snapshots — one blob, encrypted on your device before upload. The server stores ciphertext it cannot read.
• Gmail push — if you enable it, your Gmail address and an opaque history number, so the app learns “something changed” without polling. No message content is ever delivered here.
• One-click unsubscribe — when someone leaves a list you mailed, the endpoint records a campaign number and a derived token. The token cannot be reversed into an address; the app matches it locally against its own recipients.
• Image proxy — when the app loads a remote image through the proxy, the image’s host sees the proxy instead of you. The proxy forwards no cookies and no referrer, and stores nothing.

What never happens

Your mail is not stored on, relayed through or readable by this site. Nothing here is sold, rented or handed to advertisers, and nothing is collected that could be. Credentials for your mail provider travel from your machine to your provider and stop there.

Where the data lives

The database runs in Helsinki, Finland (EU). The site itself is served from a hosting platform whose edge network handles requests worldwide; where infrastructure processing happens outside the EU, it is covered by the provider’s EU standard contractual clauses. If you choose the managed AI tier, your request is also processed by the AI gateway and the model provider serving it, for the duration of the call.

Your rights

You can ask for access, correction, deletion, restriction, portability, or object to processing (Arts. 15–21 GDPR) by writing to ⟨contact email — fill before deploy⟩. Deleting a device deletes every row that hangs off it — the ledger and settings tables cascade. You can also complain to the Hellenic Data Protection Authority (dpa.gr) or the supervisory authority where you live.

Leaving, with your data

Portability is designed in rather than granted on request: your mail is a file on your own disk, any conversation exports as .eml, and triage state rides standard IMAP keywords other clients can read. The sync data above is deletable on request and worthless without your device — there is nothing to migrate away from.

Changes

When this page changes, the date at the top changes with it. A change that widens what is collected will be announced to beta participants at the address they gave, before it takes effect.