Legal
Sub-processors
Draft — not yet reviewed by counsel
This is a beta draft, written to be complete enough for legal review, not yet reviewed by counsel. Do not treat it as final or binding until that review is complete and this frontmatter's status changes.
suo uses the following sub-processors to operate the service. This list will be kept current as the platform's infrastructure evolves, and this page's lastReviewed date will be updated whenever it changes.
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Cloudflare | Edge compute (Workers), per-index storage (Durable Objects, SQLite), the control plane database (D1), object storage for crawled pages (R2), approximate, sampled query analytics (Analytics Engine), and outbound email (Email Service, send_email) for sign-in codes | Account data, indexed content, query logs (no IP, no raw user identifier), crawled page snapshots, and the account email address and one-time sign-in code in each sign-in message |
Sign-in codes are sent from noreply@usesuo.com through Cloudflare's Email Service, so Cloudflare is the only sub-processor that handles the account email address in transit. The dashboard sends no other email today.
Notification of changes
Beta accounts will be notified of a new sub-processor, or a change in an existing one's role, before it takes effect where reasonably possible. As the beta moves toward general availability, this page will also carry a subscribe mechanism for change notifications.
Placeholder for legal review: a formal sub-processor change-notification and objection process (timeline, contact method) is intentionally not drafted above pending counsel's input, along with confirmation of Cloudflare's data-processing terms as they apply to this list.