A sub-processor is a company that handles data on our behalf while we run
the platform. Each is bound by a written contract that limits its use of the
data to providing its service to us. This list is part of the
data processing addendum; we update it here and email
organization admins at least 30 days before adding a sub-processor that will
handle personal data, so they can object.
Infrastructure
| Provider |
Service |
What it processes |
Location |
Transfer mechanism |
| Amazon Web Services |
EC2 (application host), RDS (PostgreSQL), S3 (exports, backups), SES (email), Secrets Manager |
Everything the platform stores and sends: account data, research, audit log, exports, outgoing mail |
[REVIEW: AWS region] |
[REVIEW: AWS DPA with SCCs] |
| Stripe |
Payments, subscriptions, invoices, billing portal |
Organization name, billing email, card details (never seen by us), plan and payment history |
United States, EU |
[REVIEW: Stripe DPA; Data Privacy Framework] |
| Sentry (Functional Software, Inc.) |
Error tracking, only where a DSN is configured |
Stack traces, request URL, the signed-in account’s numeric id (never the email) |
United States |
[REVIEW: Sentry DPA] |
Data sources called on your behalf
These services receive a query the platform makes to answer your request.
They see the query (a contract address, a transaction hash, a token symbol)
and our server’s IP address; they do not receive your account data.
| Provider |
Service |
What it processes |
| Public Ethereum RPC endpoints: dRPC, Tenderly, MEV Blocker (CoW DAO), PublicNode (Allnodes), bloXroute, Nodies, 1RPC (Automata), LlamaNodes |
Ethereum JSON-RPC (chain head, block, transaction and receipt lookups, token names and decimals, historical contract reads). Free public endpoints, no account with us; each request goes to one of them, chosen per request |
Hashes and addresses you look up [REVIEW: public endpoints publish privacy policies but sign no DPA; confirm this is acceptable for a query-only flow] |
| Sourcify, Etherscan |
Contract ABI fetching for event decoding |
Contract addresses |
| DeFiLlama |
Protocol and timeline metadata import |
Protocol identifiers; no user data |
Optional features
| Provider |
Service |
What it processes |
When |
| Google |
Sign in with Google (OAuth) |
Your Google account’s email, name and identifier |
Only if you sign in with Google |
| Google |
Google Analytics 4 (site analytics) |
Pages viewed, referrer, browser and device type, approximate location derived from the IP address; with consent, a pseudonymous browser identifier in the _ga cookies. Never your account data. [REVIEW: Google Ads Data Processing Terms; Data Privacy Framework] |
Cookieless page-view signals always; cookies only if you allow analytics in the banner |
| Anthropic |
The research assistant |
The question you type and the research pages of your own spaces that the assistant reads to answer it, subject to the plan’s token budget |
Only when you use the assistant; nothing is sent to train models [REVIEW: confirm Anthropic commercial terms] |
Changes
| Date |
Change |
| 2026-10-01 |
First published list. |
