Security · reviewed October 21, 2026

Your mail stays yours.

Wingmarked checks a firm's outgoing email between Send and delivery.  Microsoft 365 still signs and delivers every message from the sender's own mailbox.  This page says how we protect what passes through, what we keep, and who can reach it.

  • 01

    Your mail never leaves your mailbox's control.

    • Microsoft 365 still signs every message with DKIM, as it does today, and delivers it from the sender's own mailbox.
    • The relay accepts mail only from Microsoft's own outbound network, over a connector set to TLS only.
    • Removing Wingmarked is one step, and held mail is decided first.
  • 02

    We keep almost nothing.

    • Each stored message is sealed with a key that belongs to your firm alone.
    • Message bodies are deleted after 30 days, or sooner if you ask.
    • Memory keeps cited facts, never bodies.
    • Your mail is never used to train AI models.
  • 03

    Every action is on the record.

    • Every decision, edit, comment, approval, return, release and notification is an audit row your admin can read.
    • The database itself refuses any change to the audit log: no update, no delete.
    • Sign-in is by passkey, Microsoft 365 or a text code.  There are no passwords.

How mail flows

Wingmarked sits between Send and delivery, inside your own Microsoft 365 mail flow.  Nothing is installed on any device.

How mail flows through WingmarkedOutlook to your Microsoft 365, whose transport rule sends outgoing mail over TLS to the Wingmarked relay. The relay stores it sealed, the checks run, and the message goes back over TLS to your Microsoft 365, which signs it with DKIM and delivers it from your own mailbox.WINGMARKEDYour Outlook, any deviceThe sender presses Send.Your Microsoft 365A transport rule sends it to the relay.Wingmarked relaySeals and stores it, then accepts it.ChecksRules and AI.  Most mail passes.Your Microsoft 365Signs it with DKIM, sends it as you.RecipientFrom your own mailbox, as before.TLSTLS
  1. A transport rule in your Exchange Online sends outgoing mail from the senders you choose, to people outside your organization, to the Wingmarked relay.
  2. The relay seals the message with your firm’s key, stores it and records it before it accepts it, so a message is never lost between the two systems.
  3. The checks run: fixed rules first, then the AI review.  Most mail passes as written.  A message is held only for the sender or for a reviewer your firm named.
  4. On release, the message goes back over TLS to an inbound connector in your tenant that accepts mail only from the relay’s certificate.  Microsoft signs it with DKIM, as it does today, and delivers it from the sender’s own mailbox.
  5. The rule skips mail coming back from the relay, so nothing loops.  When the delivered message differs from what the sender wrote, Wingmarked replaces the sender’s Sent Items copy with what was delivered, where Sent Items updating is switched on.

The relay accepts connections only from Exchange Online’s published outbound address ranges and refuses every other address at connect, before a sender is named.  Nobody can hand the relay a forged message and have Microsoft sign it as yours.

Signed or encrypted mail (S/MIME, PGP) passes through untouched and cannot be held for review; the sender is told why.

Encryption

Every message is sealed with AES-256-GCM under a 256-bit key that belongs to your firm alone, before it leaves our server for storage in Cloudflare R2.  R2 holds ciphertext only.  Your firm’s key is created with its account and stored wrapped by a master key, which lives in our servers’ environment and our deployment secrets, never in the code or the database.

Rotating the master key rewraps every firm’s key in one transaction and touches no message.  Session tokens, API keys, sign-in codes and sign-in links are stored only as hashes.

Our database provider, Neon, encrypts the database at rest with AES-256 and accepts only TLS connections.  Neon's own controls are audited each year for SOC 2 and ISO by independent firms.

Neon’s security overview: https://neon.com/docs/security/security-overview

Mail travels over TLS in both directions.  The connector your setup creates sends to the relay only over TLS and checks the relay’s certificate name.  The inbound connector requires TLS and accepts only the relay’s certificate, which the worker presents on every release.  The site is HTTPS only, with HSTS, and the connection to the database requires TLS.

TLS 1.2 or later is required on every encrypted connection to our servers.

What we keep, and for how long

A nightly job deletes each message after your firm’s retention period, 30 days unless you ask for less, and records each deletion in the audit log.  A message still held, or waiting to be released, is kept until it is decided.

What stays after the body is deleted is the record: who sent what to whom and when, the subject, each decision with the short quotes it rests on, holds, edits and reviewer comments, and the audit log.  We delete the record on written request.

Memory keeps cited facts, never bodies.  When your plan includes it, memory records the commitments your people made, what contacts asked for and told you, and notes, each with the one sentence it came from, quoted word for word.  A fact without its sentence is never stored.  An admin can correct or forget any line; a forget is permanent.

When your plan includes memory, received mail from your known contacts is read through Microsoft Graph and stored sealed like outgoing mail, on the same retention.  The 90-day audit and the history import keep no body at all.  Nothing read this way is ever checked, held or sent.

No log holds a message body or a secret, and logs stay on our own servers.  Card and bank details are entered on Stripe’s own pages and never reach us.

An admin can export the record (one row per message, never a body) and the memory at any time.

AI, and what it never does

Each message is reviewed by Anthropic’s Claude models: Haiku on every message, Sonnet when a message needs a second look.  The model sees the message, up to three earlier messages in the thread, text from PDF and Word attachments, and what memory holds about the recipients.

Your mail is never used to train a model.  Wingmarked calls Anthropic’s API under Anthropic’s commercial terms, under which content sent through the API is not used to train Anthropic’s models.  The terms: https://www.anthropic.com/legal/commercial-terms.

Email content goes into the prompt inside delimiters, and the prompt says it is data, never instructions.  The AI can only propose exact find-and-replace edits, and code checks each one before it is applied.  A body is never rewritten.

Access, and the record of it

People sign in with a passkey, with Microsoft 365, or with a six-digit code by text message.  There are no passwords.  Microsoft 365 sign-in follows your own Entra policies, including MFA.  A session lives in an httpOnly, Secure cookie holding a random token, and only its hash is stored.

Every table carries your firm’s id and every query is scoped by it; a test checks the column on every table.  A reviewer sees only the holds routed to them, with the authority their grant gives.

Every decision, edit, comment, approval, return, release and notification is an audit row your admin can read.  The database itself refuses any update, delete or truncate on the audit log, whoever asks.

On our side, production is reached through the repository’s deployment workflows with one SSH deploy key.  Operations tools print ids, counts and domains, never a message.  A sign-in link our operator issues into your firm is an audit row of its own.

If Wingmarked is down, mail is never lost

  • The relay stores each message, sealed, and records it before it tells Microsoft it has it.  A message is never lost between the two systems.
  • If the relay cannot be reached, Exchange Online keeps the message queued and retries for up to 24 hours.  It flows as soon as the relay answers.
  • If the automatic checks run past your firm's time limit, 8 seconds by default, the original goes out as written and the delay is recorded.  A firm can ask us to have it wait for the sender instead, who sends it in one tap.
  • A message routed to a reviewer waits for the reviewer either way, and a message stopped for fair housing is never sent by a timeout.
  • If the AI cannot be reached, the fixed rules still check every message, every admin page says so, and our operator is alerted.

Microsoft permissions

The Wingmarked app asks a Global Administrator for these permissions once, at consent.  Each is listed with why.

  • Mail.ReadWrite Microsoft Graph, application

    Update the sender's Sent Items to show what was delivered.  Write a hold notice and the welcome note into a sender's own Inbox.  Read mail, read only, for memory, the 90-day audit, the history import and draft review.

  • Mail.Send Microsoft Graph, application

    Send the setup test from the admin's own mailbox, send a reviewer's sign-in link from the sender's own mailbox, and send a draft when its owner taps Send on the Drafts page.

  • User.Read.All Microsoft Graph, application

    Match each sending mailbox to its Wingmarked user and resolve the addresses a person sends from.

  • RoleManagement.ReadWrite.Directory Microsoft Graph, application

    Give the Wingmarked app the Exchange Administrator role in your tenant, once, so it can create the connectors and the transport rule.  This is the broadest permission on the list.

  • Exchange.ManageAsApp Office 365 Exchange Online, application

    Create, read back and remove the two connectors and the transport rule, and read your accepted domains.

  • openid, profile, email, User.Read Microsoft Graph, delegated

    Sign the admin in after consent and read the organization's name and initial domain.

  • MailboxSettings.ReadWrite Microsoft Graph, application, optional

    Give draft review's Outlook categories their colors.  Not part of the standard consent; without it the categories are set without colors.

Application permissions reach every mailbox in your tenant unless your admin limits them with an Exchange application access policy.

Removing Wingmarked

One step: Remove Wingmarked on the setup page deletes the transport rule and both connectors, and routing stops at once.  Nothing else in Microsoft 365 is touched.

Held mail is decided first.  The step counts every email still waiting and offers three ways on: decide them yourself, send them all as written and then remove, or remove anyway, confirmed by typing your company’s short name, which leaves them unsent and tells each sender.  The server refuses a removal that would strand mail.

To end the app’s access, delete Wingmarked under Enterprise applications in Entra, and check Roles and administrators for the Exchange Administrator role the app was given.

Subprocessors

The services that process your data for us.  What each one touches, and where, is at /legal/subprocessors.

  • AnthropicThe AI review of each message, the memory that reads sent and received mail, Ask, recommendations, the 90-day audit and the history import.
  • CloudflareObject storage (R2) for each raw message, and DNS for wingmarked.com.
  • NeonThe managed Postgres database.
  • OVHThe edge server: the relay that receives mail from Microsoft 365 and the worker that checks and releases it.
  • HetznerThe web server: wingmarked.com, the reviewer portal, the sender queue and the admin pages.
  • TwilioText messages: sign-in codes, reviewer invites, and hold alerts when web push cannot reach a person.
  • MicrosoftWingmarked's own mailboxes: a hold notice by email when it cannot be written into the sender's own Inbox, email to reviewers who chose it, and notices to a firm's admins when its mode changes.
  • StripeBilling, for a firm that pays.
  • GitHubSource code, automated tests, container images, and the deployment and operations workflows.
  • Voyage AI · when switched onSearch embeddings for memory.

For your security team: our security questionnaire answers the common SIG Lite and CAIQ questions in plain yes and no, and prints or downloads as one document.

Report a vulnerability

Send what you found and the steps to reproduce it to security@wingmarked.com.  Use only an account and mail of your own, and do not read, change or delay anyone else’s mail.  We reply to every report and tell you when the fix is live.  The same contact is published at /.well-known/security.txt.

Questions a firm asks first

Can Wingmarked staff read our mail?
Each stored message is sealed with your firm's own key.  The service opens it to check and deliver it, and shows it only to a signed-in person at your firm or a reviewer you named.  Our operations tools print ids, counts and domains, never a message, and no log holds a body.  Production is reached only through our deployment workflows, and a sign-in link our operator issues into your firm is a row in your audit log.
Is our mail used to train AI?
No.  Wingmarked calls Anthropic's API under Anthropic's commercial terms, under which content sent through the API is not used to train its models.  We train no models of our own.
What happens if Wingmarked goes down?
Mail is never lost.  Exchange Online queues it and retries for up to 24 hours while the relay is unreachable.  If the checks run past your time limit, the original goes out as written, or waits for the sender if your firm asked for that.
How do we remove it?
Remove Wingmarked on the setup page deletes the transport rule and both connectors, and routing stops at once.  Any held email is decided first: you settle it, send it all as written, or leave it unsent with each sender told.  To end the app's access, delete Wingmarked under Enterprise applications in Entra.
Where is our data stored?
The database is Neon in AWS us-east-1, in the United States.  Raw messages are in Cloudflare R2, sealed with your firm's key, so R2 holds ciphertext only.  The web server is Hetzner in Helsinki, Finland, and the server that runs the relay and the checks is OVH.
Who are your subprocessors?
Anthropic, Cloudflare, Neon, OVH, Hetzner, Twilio, Microsoft, Stripe and GitHub, plus Voyage AI only when it is switched on.  Each is listed with what it does and what data it touches at /legal/subprocessors.

Security contact

Questions, reports and requests to delete a record go to security@wingmarked.com.