Subprocessors
Who else processes data, and what they see
Every third party Pacterms sends data to, what it is used for, and which data reaches it. This list is maintained by hand and is accurate as of the date below.
Last checked: 2026-09-30
| Processor | Purpose | Data it receives | Region |
|---|---|---|---|
| Supabase | Database, file storage and session records | All stored application data | United States |
| Vercel | Application hosting and delivery | Request metadata and server logs | United States, with global edge delivery |
| Stripe | Subscription payments | Billing identifiers and payment status. Pacterms never stores card numbers. | United States |
| Telnyx | SMS delivery | Recipient phone numbers and message text | United States |
| Resend | Transactional email delivery | Recipient email addresses and message content | United States |
| Anthropic | Research flagging, and the assistant visitors type to. The agreement tools that drafted five descriptive fields were closed on 2026-10-21. See the AI use page. | What a user or a visitor types to the assistant, and research notes on public legal text. No clause language released by counsel is sent. | United States |
| DigiCert | RFC 3161 trusted timestamping | A SHA-256 fingerprint only. Document content is never transmitted. | United States |
| FreeTSA | RFC 3161 timestamping, used only when DigiCert does not answer | A SHA-256 fingerprint only. Document content is never transmitted. | European Union |
Notice of changes
Changes to this list are published here. There is no subscription mechanism yet — if you need advance notice of a change under a contract, say so and it will be written into that contract.