Referenced by the SafeRedact Data Processing Agreements. Controllers receive at least 30 days’ notice before a sub-processor is added or replaced, and may object within 14 days.
Last updated 22 October 2026
Documents are opened, parsed, redacted and exported inside the Controller’s browser. Document files are never transmitted to or stored on SafeRedact systems. Text extracted from those documents is transmitted to the AI sub-processor for classification, together with the details of the data subject that the user enters for the case (such as name, email address, telephone number, reference numbers and other names), so that the subject’s own information is not redacted from the disclosure. SafeRedact does not store either at rest. Data-subject records the Controller saves for reuse are held in the Controller’s browser, and their details reach SafeRedact only inside a classification request. Account, security, usage and billing records are stored as set out below.
| Sub-processor | Role | Data processed | Location |
|---|---|---|---|
| Anthropic, PBC | AI classification (Claude API), standard route; in-app help assistant where enabled | Text extracted from documents and the case’s data subject details, transiently; help questions | Stored in the United States; processing may also occur in Europe, Asia or Australia |
| Amazon Web Services, Inc. | AI classification (Amazon Bedrock), UK and EU route | Text extracted from documents and the case’s data subject details, transiently | European regions, including London |
| Supabase Inc. | Authentication and database | Account records, security logs (including IP address and user agent), and content-free per-file, usage and route-change records | AWS us-east-1 (United States) |
| Vercel Inc. | Application and API hosting | Request metadata; extracted text in transit only | AWS Europe (London) |
| Stripe, Inc. | Payment processing | Billing contact and payment records | United States |
| Plus Five Five, Inc. (Resend) | Email to users and to SafeRedact staff | User email addresses; sign-in links, agreement copies, receipts and case notices; staff notices of account events | AWS us-east-1 (United States) |
| Slack Technologies, LLC | Notifications to SafeRedact staff | Account events carrying the user’s email address and file counts, and feedback submitted in the application; no document content | United States |
SafeRedact does not store document content or extracted text at rest. On the standard route, extracted text sent to Anthropic is retained by Anthropic for no longer than 30 days for abuse monitoring and is never used to train models, under Anthropic’s Commercial Terms and Data Processing Addendum. On the UK and EU route, detection runs on AWS infrastructure that does not store or log the text, does not use it for training, and does not make it available to the model provider. Account, security and usage records are retained for the term of the service agreement and deleted within 30 days of termination or on written request; billing records are kept for as long as the law requires. Resend keeps copies of the emails it sends, and Slack keeps staff notifications in SafeRedact’s workspace, under their standard retention. Saved data-subject records are stored in the Controller’s browser and removed when the Controller deletes them or clears site data.
Application hosting and the API run in AWS Europe (London). Account, security and billing records are stored in the United States, where emails and staff notifications are also handled. On the standard route, extracted text is classified by Anthropic, which stores API data in the United States and may process requests there or in selected countries in Europe, Asia and Australia; on the UK and EU route, it is classified in European regions, including London. Transfers from the EEA are made under the Standard Contractual Clauses (Commission Decision 2021/914, Module Two, or Module Three where the Controller is itself a processor) completed in the annex to the EU DPA; transfers from the United Kingdom are made under the ICO’s International Data Transfer Agreement. Each sub-processor is engaged under a written data processing agreement incorporating the Standard Contractual Clauses where applicable. SafeRedact provides the information a Controller reasonably needs for its own transfer impact assessment.
Anthropic, PBC: ISO 27001:2022, ISO 42001, SOC 2 Type II. Supabase Inc.: SOC 2 Type II. Vercel Inc.: SOC 2 Type II. Amazon Web Services, Inc.: ISO 27001, SOC 2 Type II. Stripe, Inc.: PCI DSS Level 1, SOC 2 Type II. Plus Five Five, Inc. (Resend): SOC 2 Type II. Slack Technologies, LLC: SOC 2 Type II, ISO 27001. These are certifications of the sub-processors, not of SafeRedact.
Questions about this schedule, or a notification preference for sub-processor changes?
Contact us Back to legal