Legal · template · October 21, 2026
Data Processing Addendum.
A template for a customer to review before connecting Microsoft 365. The contracting party is Wingmarked (entity to be named).
Draft pending counsel review. This template is not an offer to contract and is not signed. The company entity that would sign it is not formed yet.
1. Parties and status
This Data Processing Addendum is between the customer named in the order (the Customer) and Wingmarked (entity to be named) (Wingmarked). It forms part of the agreement under which Wingmarked provides its service to the Customer.
This is a template for review. It is a draft pending counsel review and is not an offer to contract. The Wingmarked entity is not formed yet.
2. Roles
The Customer is the controller of the personal data in its email and its account. Wingmarked processes that data as a processor, on the Customer's documented instructions, which are the agreement, this addendum and the Customer's settings in the service.
3. Subject matter
Reviewing the Customer's outgoing email after a sender presses send and before it is delivered; holding a message for the sender or a reviewer the Customer names; applying the exact edits a sender or reviewer approves; delivering the message from the sender's own mailbox; and, when the Customer's plan includes it, keeping a cited memory of what the Customer's people have said and been asked.
4. Duration
For the term of the agreement, and after it until deletion under section 10.
5. Nature and purpose of processing
Receiving, storing, checking, holding, editing and releasing email; reading mail through Microsoft Graph for Sent Items updates, notices, memory, the 90-day audit, the history import and draft review; sending sign-in codes and alerts; and keeping the audit record. Automated checks use AI models from Anthropic. Wingmarked does not sell the data and does not use it to train models.
6. Types of personal data
Email messages and their attachments, including any personal data the Customer's people write or attach; names and email addresses of senders and recipients; subjects and times; the facts, commitments and requests memory takes from that mail with the sentence each came from; users' and reviewers' names, titles, work email addresses and mobile numbers; passkey public keys; reviewer comments; and records of each action in the audit log.
7. Categories of data subjects
The Customer's employees and other senders; the recipients of their email and the people who write to them; reviewers the Customer invites, including outside counsel and accountants; and anyone named in the email itself.
8. Security measures
Wingmarked maintains the measures described at wingmarked.com/security, which forms part of this addendum as of the date the order is signed. Wingmarked will not materially reduce them during the term.
Wingmarked holds no SOC 2 report, ISO 27001 certificate or penetration test report. On request it answers the Customer's reasonable written questions about its measures.
9. Subprocessors
The Customer authorizes the subprocessors listed at wingmarked.com/legal/subprocessors and in Annex A. Wingmarked will give the Customer's admins notice by email before adding or replacing one, so the Customer can object. Wingmarked binds each subprocessor to obligations that protect the data at least as well as this addendum.
10. Deletion on termination
Raw messages are deleted after the Customer's retention period, 30 days by default, whether or not the agreement continues. The Customer can remove Wingmarked from its mail flow in one step at any time.
Within 30 days of the Customer's written request after termination, Wingmarked deletes the rest of the Customer's record: message metadata, decisions, holds, edits, comments, memory, users and reviewers. This deletion is done by hand today. Audit log rows are kept, because the database refuses their deletion; they hold ids, actions and settings, never a message body.
11. Personal data breach
Wingmarked will notify the Customer's admins by email without undue delay, and within 72 hours, after confirming a breach of the Customer's personal data, with what is known and what is being done. Reports to Wingmarked go to security@wingmarked.com.
12. Assistance
Wingmarked helps the Customer answer requests from data subjects with the tools in the service (export, correct, forget) and by hand where they do not reach. It gives the Customer the information it needs for a data protection assessment about the service.
13. Transfers
Data is processed in the United States and in Finland (Annex A). The transfer terms that apply to the Customer's data are to be completed by counsel.
14. Confidentiality
Anyone at Wingmarked who can reach the Customer's data is bound to keep it confidential. Reviewer comments, tracked changes and a Private reviewer's identity never reach recipients.
Annex A. Subprocessors
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Anthropic | The AI review of each message, the memory that reads sent and received mail, Ask, recommendations, the 90-day audit and the history import. | The message text and subject, up to three earlier messages in the thread, text from PDF and Word attachments, and what memory holds about the recipients. | Not set by us. |
| Cloudflare | Object storage (R2) for each raw message, and DNS for wingmarked.com. | Raw messages, sealed with the firm's own key before they leave our servers, so R2 holds ciphertext only. | Not set by us. |
| Neon | The managed Postgres database. | Everything except the raw message: senders, recipients, subjects and times; decisions with the short quotes they rest on; holds, edits and reviewer comments; memory; users and reviewers; the audit log. Agent facts and draft text are sealed with the firm's key. | AWS us-east-1, United States. |
| OVH | The edge server: the relay that receives mail from Microsoft 365 and the worker that checks and releases it. | Messages in memory while they are checked and released. Logs on the server never hold a body. | Not stated in our records. |
| Hetzner | The web server: wingmarked.com, the reviewer portal, the sender queue and the admin pages. | Messages a signed-in person opens, decrypted in memory to show them. Logs carry the route and timings, never a body. | Helsinki, Finland. |
| Twilio | Text messages: sign-in codes, reviewer invites, and hold alerts when web push cannot reach a person. | Mobile numbers, sign-in codes, and for a hold alert the subject line, the sender's name and the recipients' names. | Not set by us. |
| Microsoft (Wingmarked's own Microsoft 365) | Wingmarked'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. | For a hold notice: the subject, the recipients, the sender's quoted words and the suggested fix. A reviewer email names the sender and links to the review page, never any part of the message. | Not set by us. |
| Stripe | Billing, for a firm that pays. | The firm's name, the billing admin's email, the plan and the seat count. Card and bank details are entered on Stripe's own pages and never reach our servers. | Not set by us. |
| GitHub | Source code, automated tests, container images, and the deployment and operations workflows. | No mail. Production secrets are kept as encrypted repository secrets. Operations logs carry ids, counts and domains; the two that print a sign-in link or an API key are readable by repository admins only. | Not set by us. |
| Voyage AI | Search embeddings for memory. Only when semantic search is switched on. It is off by default. | A memory item's summary and its first quote; never a body or an address. | Not set by us. |
Annex B. Security measures
As described at wingmarked.com/security on the date the order is signed, and in the answers at wingmarked.com/security/questionnaire.