Skip to content

Trust & security

Written for the personwho has to sign off on it.

SPOOON handles business correspondence and people data that can include sensitive information. These are the controls as built — not a roadmap dressed up as a datasheet.

ObserveOrganizeOptimize

Controls as built

  1. Identifiers are redacted before the model call

    Account numbers, phone numbers, email addresses and other personal identifiers are replaced with placeholders before any AI provider sees a message, then restored locally in the draft. Each draft states what was redacted.

  2. Access is enforced server-side, always

    Capabilities across roles, plus organization, workspace and inbox-membership scoping on every read and write. Object-level checks stop cross-tenant reads and ID guessing. A hidden button is never treated as a permission.

  3. An append-only ledger

    Every consequential action records actor, object, before, after, source, correlation ID, IP address and a device label. Records are never updated or hard-deleted, and message bodies and secrets are stripped before write.

  4. Authenticator app, enforced

    Any RFC 6238 app works. Secrets are encrypted at rest and never returned by the API, recovery codes are hashed and single-use, replayed codes are rejected, and an owner reset is logged and ends the user's sessions.

  5. Your mail infrastructure stays yours

    SPOOON is not a mail server. It reads and sends through your Google or Zoho account using provider-sanctioned methods, so SPF, DKIM and DMARC keep passing and nothing is scraped.

  6. What we will not claim

    We do not claim a compliance certification we have not been audited for, and we do not publish uptime we have not measured. Where a control is planned rather than live, the platform labels it that way.