Trust and transparency
Subprocessor register
This register identifies service providers that may process customer or account information to deliver Accagrity. The exact provider, region, retention configuration, and feature scope may vary by deployment and contract. Contract customers should rely on their signed order and DPA for binding details.
| Provider | Service | Data scope | Location |
|---|---|---|---|
| Neon | PostgreSQL database hosting | Account, workspace, document metadata, audit records | [INSERT PROCESSING LOCATIONS] |
| Cloudflare R2 | Private object storage | Uploaded documents, revisions, export archives | [INSERT PROCESSING LOCATIONS] |
| Upstash | Redis and queue infrastructure | Rate-limit state, authentication secondary storage, queued jobs | [INSERT PROCESSING LOCATIONS] |
| OpenAI | Model-assisted transformation and analysis where enabled | Content required for the requested model operation | [INSERT PROCESSING LOCATIONS AND RETENTION SETTINGS] |
| Stripe | Subscription checkout, billing, and customer portal | Billing identity and payment-related subscription data | [INSERT PROCESSING LOCATIONS] |
| Resend | Transactional email delivery | Email address and operational message content | [INSERT PROCESSING LOCATIONS] |
Accagrity will provide notice of material subprocessor changes where required by contract or law. Customers may raise a documented objection on reasonable data-protection grounds under their DPA.
Questions and subprocessor objections: admin@accadpro.com.
Last updated: 3 September 2026. Replace bracketed deployment details before relying on this register contractually.