Security questionnaire · October 21, 2026
Security questionnaire.
Answers to the common SIG-Lite and CAIQ questions, kept brief. Every answer is true of the system as it runs today; where something is not in place, the answer says no. Security contact: security@wingmarked.com.
Not in place
- No SOC 2 report and no ISO 27001 certificate.
- No penetration test has been performed.
- No cyber insurance is in place.
- No Business Associate Agreement is offered. Wingmarked is not set up for HIPAA-regulated data.
- No signed Data Processing Addendum yet. The template at /legal/dpa is a draft pending counsel review, and the company entity that would sign it is not formed.
- No uptime commitment or service level agreement.
- No written incident response plan. Paging and the runbook exist; the plan does not.
- No automated dependency or vulnerability scanning in the build.
- No database row-level security. Tenant isolation is enforced in application code.
- No tested restore from backup. Database backups are the managed provider's.
Company and assurance
- Who is the contracting entity?
- Wingmarked (entity to be named). The company entity is not formed yet.
- Do you hold a SOC 2 report or ISO 27001 certificate?
- No.
- Has an independent penetration test been performed?
- No.
- Do you carry cyber liability insurance?
- No.
- Will you sign a Business Associate Agreement?
- No. Wingmarked is not set up for HIPAA-regulated data.
- Will you sign a Data Processing Addendum?
- A template is published at /legal/dpa for review. It is a draft pending counsel review and cannot be signed until the entity exists.
- Who do we contact about security?
- security@wingmarked.com.
Data handled
- What customer data do you process?
- Outgoing email of the senders a firm routes through Wingmarked: the full message with attachments, the sender and recipients, and the subject. When the firm's plan includes memory, also received mail from known contacts and replies in the firm's own threads, read through Microsoft Graph and stored sealed like outgoing mail. Account data: names, work email addresses and mobile numbers of users and reviewers.
- How long do you keep message bodies?
- The raw message is deleted after the firm's retention period, 30 days by default, by a nightly job; each deletion is an audit row. A message still held or waiting to be released is kept until it is decided. A shorter period is set on request; there is no admin control for it yet.
- What do you keep after a body is deleted?
- The record: sender, recipients, subject and times; each decision with the short quotes it rests on; holds, edits and reviewer comments; memory (commitments, asks, facts and notes, each with the one sentence it was taken from); the audit log. There is no automatic deletion of this record today.
- Where is data stored?
- The database is Neon in AWS us-east-1, United States. Raw messages are in Cloudflare R2, sealed. The web server is Hetzner in Helsinki, Finland; the edge server that runs the relay and the worker is OVH. We do not pin a region for R2 or the edge server in our records.
- Is customer data used to train AI models?
- 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 (https://www.anthropic.com/legal/commercial-terms).
- Do you have a zero data retention agreement with your AI provider?
- Not one we can show you. Some background work (memory extraction and rule trials) goes through Anthropic's Batch API, which holds a request until it is processed.
- Who are your subprocessors?
- Listed at /legal/subprocessors with what each does and what data it touches.
- Can we export or delete our data?
- An admin exports the record (one row per message, never a body) and the memory from the admin pages, and can correct or forget any remembered line; a forget is permanent. Deleting the whole record is done by us on written request; there is no self-serve deletion yet. Audit rows are never deleted: the database refuses it.
Encryption
- Is data encrypted at rest?
- Raw messages are sealed with AES-256-GCM under a 256-bit key that belongs to the firm alone, generated when the firm is created and stored wrapped by a master key. Agent facts, draft text, recommendation rationale and integration signing secrets are sealed the same way. The rest of the database is stored by Neon, which encrypts it at rest with AES-256; we add no encryption of our own to it.
- Is data encrypted in transit?
- Yes. TLS 1.2 or later is required on every encrypted connection to our servers: the site and the relay refuse older versions. Mail reaches the relay over TLS from Microsoft 365 and goes back over TLS 1.2 or later to a connector pinned to the relay's certificate. The site is HTTPS only with HSTS. The database connection requires TLS, and Neon accepts no other kind.
- How are keys managed?
- The master key lives in the servers' environment and in an encrypted repository secret, never in the code. Rotation rewraps every firm's key in one transaction and touches no message; each rewrap is an audit row. Session tokens, API keys, sign-in codes and links are stored only as hashes.
Access control
- How do your customer's users sign in?
- With a passkey, or with Microsoft 365 sign-in, or with a six-digit code by text message. There are no passwords. Guest reviewers can also use a single-use emailed link that expires in 15 minutes.
- Do you enforce multi-factor authentication?
- Not as a separate step. A passkey is bound to the device and asks for the device's own unlock where the device supports it. Microsoft 365 sign-in follows the firm's own Entra policies, including its MFA. A text code is a single factor and is the fallback.
- What are the session rules?
- A session lasts 30 days in an httpOnly, Secure, SameSite=Lax cookie that holds a random token; only its hash is stored. It is replaced when a person's privileges change and can be revoked. Text codes expire in 10 minutes and lock after 5 attempts, with at most 3 sent per number every 10 minutes.
- How are roles separated?
- A firm has admins and members. A reviewer sees only the holds routed to them, with the authority their grant gives (return to the sender, or edit and release). A connected tool or Claude connector acts only on its own reviewer's queue in one firm.
- Who at Wingmarked can reach production?
- Production is reached through the repository's GitHub Actions workflows, which sign in to the servers with one SSH deploy key, and by SSH with that key. Operations workflows print ids, counts and domains, never a message. There is no formal access review.
Application and change management
- How are changes made and reviewed?
- Every change is a pull request. The build runs lint, type checks, unit and end-to-end tests and the quality gates on every one. Changes to the mail path wait for the owner's approval; other changes merge when every check passes.
- Do you scan dependencies for known vulnerabilities?
- No. No automated scanning is configured in the build.
- How is the AI kept from acting on instructions inside an email?
- 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, which code checks before anything is applied: the text must occur once, the replacement stays within three times the length, a changed figure needs evidence from an attachment or the thread, and nothing in the signature or quoted history is touched.
- How are tenants isolated?
- Every table carries the firm's id and every query is scoped by it in code; a test checks the column on every table. Each firm has its own encryption key. There is no database row-level security.
Infrastructure and operations
- How is the relay protected?
- It accepts connections only from Exchange Online's published outbound ranges and refuses anything else at connect, before a sender is named. It offers TLS 1.2 or later with a Let's Encrypt certificate and refuses older versions. The connector the setup creates sends only over TLS and checks the certificate's name.
- What do you log?
- JSON logs without bodies or secrets, kept on each server and rotated at five files of 20 MB per service. The web logs the route and timings of each request, never a body, an address or a query string. No third-party logging or crash reporting service is in use.
- Do you keep an audit trail?
- Yes. Every decision, edit, comment, approval, return, release and notification is an audit row. The database refuses any update or delete on the audit table. An admin reads it on the audit page.
- How are you alerted to problems?
- The worker texts the operator when a release fails its last retry, the relay stops answering, a job waits more than 10 minutes, or a job is given up.
Continuity
- What happens to our mail if Wingmarked is down?
- If the relay cannot be reached, Exchange Online keeps the message queued and retries for up to 24 hours, then it flows when the relay answers. If the automatic check runs past the firm's timeout (8 seconds by default), the original is released as written and the delay is logged.
- Do you have backups and a recovery plan?
- The edge server holds no state and has a written rebuild procedure. The database is a managed service whose backups are the provider's; we have not tested a restore.
- Do you offer an uptime commitment?
- No.
Incidents
- Do you have an incident response plan?
- Not a written one. Paging and the operations runbook exist.
- How will you tell us about a breach of our data?
- By email to the firm's admins, as the draft Data Processing Addendum sets out. Reports to us go to security@wingmarked.com.
Microsoft 365
- What permissions does the app request?
- Mail.ReadWrite, Mail.Send, User.Read.All and RoleManagement.ReadWrite.Directory on Microsoft Graph, Exchange.ManageAsApp on Exchange Online, and sign-in scopes. Each is listed with why at /security. Application permissions reach every mailbox in the tenant unless your admin limits them with an Exchange application access policy.
- How do we remove Wingmarked?
- Remove Wingmarked on the setup page deletes the transport rule and both connectors; routing stops at once. A held email goes back out through the inbound connector the removal deletes, so the step first counts any email still waiting and asks what happens to it: decide them first, send them all as written and then remove (removal waits until every one is handed back, and stops if any is refused), or remove anyway, confirmed by typing your company's short name, which leaves them unsent and tells each sender to send again from Outlook. The server refuses a removal that would strand mail. Deleting the transport rule by hand stops routing too, but does not settle held mail. To end the app's access, delete Wingmarked under Enterprise applications in Entra.