Data protection
Subprocessor List
Last updated August 23, 2026
This page identifies third parties Docket may use to process Customer Data. A provider receives data only when its feature is needed and enabled; the presence of an integration does not mean every provider receives information for every case.
Docket does not use Customer Data to train AI models. Docket’s production inference route has model-training and prompt-sharing opt-ins disabled and uses model providers that commit not to train on API business data. OpenRouter routes the request and the current underlying model provider is OpenAI. Provider-side operational or abuse-monitoring retention can still apply even though the data is not used for training.
See the official OpenRouter data-collection documentation and OpenAI business-data commitments.
| Provider | Purpose | Data involved | When used |
|---|---|---|---|
| OpenRouter | AI inference gateway and request routing | Scoped prompts, model responses, and request metadata needed for a case | Active for automated case investigation |
| OpenAI | Current AI model inference provider | Scoped prompts, selected case context, and generated responses | Active through OpenRouter; direct API routing may be used when configured |
| Stripe | Checkout, payment confirmation, refunds, and payment-risk controls | User and firm contact details, payment amount, customer and transaction identifiers; no uploaded case records | Only for paid investigations |
| Resend | Transactional email delivery | Recipient name and email address, message subject, and the minimum case-status content needed for the notification | When email delivery is enabled |
| Exa | Public-web research search | Research queries, public protocol names, and public blockchain identifiers; not source-document contents | When a case requires external research |
| Jina AI | Retrieval of public webpages selected during research | Public URLs and retrieved public-page content | When a case requires public webpage retrieval |
| Alchemy | Blockchain RPC, transaction, token, and Beacon data | Public wallet addresses, transaction hashes, contract addresses, block identifiers, and validator identifiers | When supported chain data is needed |
| Etherscan | Explorer and verified-contract data | Public addresses, transaction hashes, contract identifiers, and supported query parameters | When explorer data is needed |
| Zerion | Public wallet portfolio and activity data | Public wallet addresses, chains, token identifiers, and transaction references | When portfolio or activity enrichment is needed |
| CoinGecko | Asset identity and market-price data | Asset identifiers, symbols, networks, contract addresses, currencies, and timestamps | When valuation support is needed |
| Coinbase | Public exchange-rate and market reference data | Asset and currency pairs and timestamps; no customer exchange credentials | When an applicable public rate is used |
Hosting and storage
Docket-operated application, database, and case-workspace infrastructure is not a third-party subprocessor. Docket will add any external hosting, database, backup, or object-storage provider to this list before that provider is authorized to process production Customer Data.
Changes and objections
Docket will update this page before a material new subprocessor begins routinely processing Customer Data and, when reasonably possible, give subscribed customers at least 15 days’ advance notice. Customers may object on reasonable data-protection grounds as described in the DPA.
To receive change notices, email privacy@docketcrypto.com with the subject “Subscribe to Docket subprocessor updates.”