Subprocessors
The third parties that touch customer data in Abstract.
Version 2026-08-26 · superseded versions are kept in the repository history
Abstract is a processor. The people whose data it handles are mostly not its users: a lease abstract contains tenants, occupants and guarantors, with home addresses, payment obligations and personal guaranties, and the citation schema retains verbatim quotes from the source document. The list below is what that data passes through.
| Who | What they process | Where | Their documentation |
|---|---|---|---|
| Anthropic claude-opus-5 |
The full text of each uploaded lease, sent for extraction, and the structured abstract that comes back. This is the only subprocessor that sees document contents. | United States | trust.anthropic.com |
| Fly.io | Hosting. Holds the application, the SQLite database and the original PDF files on an attached volume — so effectively everything, at rest. | Phoenix, Arizona (phx) | fly.io/legal |
| Stripe | Subscription billing. Sees the account email and payment details. Never lease contents. Card numbers do not reach us at all. | United States | stripe.com/legal/dpa |
| Your SMTP provider SMTP_HOST |
Deadline notification emails: recipient address, lease name, obligation description and date. Whichever provider is configured for the deployment — [DECISION NEEDED: name the provider actually in use before publishing this page]. With none configured, notifications are written to disk and never leave the machine. | Depends on the provider | — |
| Customer-configured webhooks | If a customer registers an outbound webhook, the events they select are delivered to the endpoint they choose. That destination is their subprocessor, not ours — we name it here because the data does leave our systems. | Wherever they point it | — |
Not subprocessors
Worth stating plainly, because people assume otherwise: there is no analytics provider, no error-reporting service, no CDN, no session recording and no advertising or marketing pixel anywhere in Abstract. Nothing about a customer's use of the product is reported to a third party.
Changes
We will give 30 days' notice before adding a subprocessor or replacing one, by email to the account owner and by updating the version date on this page. If a customer objects within that window and we cannot resolve it, they may terminate for the remainder of their term and take their data with them — see the deletion and export terms in the DPA.
docs/ai-provider-diligence.md for what that claim rests on and
what still needs confirming in writing.
Questions
A customer's security reviewer should email privacy@abstract.local. A DPA template is available on request.