Security and trust

Your mail is the most private thing you own.

MorningZero touches some of your most sensitive data, so we hold it the way we’d want ours held: the minimum, encrypted, never sold, never trained on, gone when you say. Below is what has been checked by others, and what we do ourselves.

Attestations

What has been checked, and by whom.

Two of these are third-party: someone outside this company looked at us. The third is our own assessment, published in a public register under our own name. They are labelled accordingly, because the difference is the whole point of publishing them.

Verified · August 2026

CASA, App Defense Alliance

Assessed by a third party

The Cloud Application Security Assessment is what Google requires before an application may keep access to Gmail data. We completed it against the OWASP Application Security Verification Standard and a lab Google authorises validated the result: authentication and session handling, encryption in transit and at rest, dependency and vulnerability scanning. Our assessment covered 28,718 dependencies. Failing it would cost us Gmail access altogether, which is why it is the check we treat as the floor rather than the ceiling.

Standard
OWASP ASVS
Scope
28,718 dependencies scanned
Validated by
An authorised independent lab
Verified
August 2026
About this assessment →
Verified publisher

Microsoft identity verification

Assessed by a third party

Microsoft verified, through its Partner Network, that the company behind MorningZero is a real and identifiable legal entity. The practical effect is on the consent screen: when you connect an Outlook.com or Microsoft 365 mailbox you see a verified mark next to our name rather than the "unverified" warning an anonymous application gets. It is an identity check, not a security audit — it tells you who you are granting access to, which is a different and narrower question than how that access is protected.

Programme
Microsoft Partner Network
Checks
Legal identity of the publisher
Shown on
Outlook and Microsoft 365 consent screen
Status
Verified publisher
About this assessment →
CSA STAR Level One: Self-Assessment — Security, Trust, Assurance & Risk
Self-assessment · published 11 September 2026

CSA STAR Level 1

Our own self-assessment, published

The STAR Registry is the public register enterprise buyers use to vet cloud vendors. Level 1 is a self-assessment: we answered the Cloud Security Alliance's Consensus Assessment Initiative Questionnaire (CAIQ v4.0.3) across every control domain — governance, encryption and key management, identity, logging, incident response, supply chain — and published the answers under our own name. Nobody audited those answers; that is what Level 2 is for. What it gives you is a complete, specific, on-the-record account of how we handle data, which you can read in full before you connect a single mailbox.

Questionnaire
CAIQ v4.0.3
Listed as
Serveka Technologies — MorningZero
Service model
SaaS
Published
11 September 2026
Read our answers →

How we hold it

The commitments behind those answers.

Least-privilege OAuth

Gmail and Outlook connect through Google and Microsoft's own consent screens — we never see or store your password for them, and you can revoke MorningZero's access from your provider at any time. Signing in and granting mailbox access are separate grants, so revoking one does not silently keep the other alive.

App passwords, for providers without OAuth

Some providers — Yahoo, iCloud, Fastmail and similar — offer no OAuth for mail, only an app-specific password you generate in their settings. Connecting one of those means we hold that password: encrypted with AES-256-GCM under its own encryption secret, separate from the one protecting our OAuth tokens, never logged, never returned by our API, and permanently deleted the moment you disconnect the mailbox. Gmail and Outlook never use this path, and MorningZero will refuse a Gmail or Outlook address here and send you to the OAuth screen instead.

Encrypted in transit and at rest

All traffic is encrypted in transit with TLS, and HSTS keeps browsers on it. Your OAuth tokens, app passwords, cached message bodies and any message queued for sending are encrypted with AES-256-GCM before they're written, and the storage our database sits on is encrypted at rest by our infrastructure provider. Connections to mail servers require TLS too — we never fall back to an unencrypted session, and we reject a server whose certificate does not check out.

We don't hoard your inbox

Message bodies are not warehoused: they are read from your provider when you open a message and held in an encrypted cache for about ten minutes, then discarded. Attachments never leave your provider. What we do store is what the features need — subjects, senders, labels, timestamps, previews, AI summaries and the search vectors built from them, plus the things you create here: drafts, messages queued to send, and your conversations with the assistant.

Never trained on your email

We do not use the content of your mail to train general-purpose AI models. The model providers that process it act as our processors and are contractually bound not to train on it — we pay for the tiers where that's the deal, because some free tiers let the provider learn from what you send. Your corrections tune labeling for your own account and nobody else's.

Nothing happens behind your back

No auto-send, ever: the assistant drafts and you press Send. When you mark a thread Done or Not for me, we add a MorningZero/Done or MorningZero/Not for me label at your provider, and archive it there if you chose that at setup. Copying your other labels and Zero's tags into Gmail or Outlook is a separate switch per mailbox, off by default. Every rule records what it did in an audit view, and sessions are revocable per device with a single “sign out everywhere”.

Delete means delete

Disconnect a mailbox and its messages, labels, rules, drafts, assistant conversations and learned preferences are deleted in one transaction, along with the token or app password we held. For Google we also revoke the grant at Google; Microsoft offers no revocation call, so remove the app from your Microsoft account to cut it there too. Delete your account and all of it goes, along with your access tokens. You also choose how much history is imported in the first place.

No ads. No selling.

Your mail is never sold, never shared with advertisers, and never used for ad targeting. Our use of Google and Microsoft data follows their Limited Use requirements — full stop.

Scopes

What we access — and why.

We ask only for the scopes the features you use actually need. This is the whole list. The Gmail and Outlook connect guides go through what each line of the consent screen means.

Messages in the mailboxes you connectTo triage, label, search, summarise and draft replies inside the app — on your behalf, never for anyone else. Gmail and Outlook over OAuth; Fastmail, iCloud, Yahoo, Zoho and the other app-password providers over IMAP.
Google & Microsoft calendarsTo show your daily agenda and create the events you ask for. Read and write scoped to features you use.
Account identityYour name and email, to sign you in and keep your connected inboxes attached to one account.

Compliance

The policies we are held to.

MorningZero’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Microsoft mail and calendar data accessed through the Microsoft Graph API is held to the same restrictions.

Wherever you live, you can ask what data we hold, have it corrected, get a copy, or delete it — we extend those rights to every user, not only where a law requires them. Email us to exercise any of them. Full detail lives in our Privacy Policy and Terms. Serveka Technologies maintains a register of the subprocessors that touch your data; ask and we will send it.

Found a vulnerability?

Report it to security@morningzero.com — the same address published in our security.txt. Include the details and the steps to reproduce. We acknowledge reports within three business days, and we ask for a chance to fix an issue before it is disclosed publicly.

Anything else, including a DPA request, goes to support@morningzero.com.