Clingeo · Legal & Trust
Subprocessors
Supplier review, processing roles, and the customer data processing chain.
Draft reviewed November 21, 2026
This draft register supports review of the customer-data processing chain. It is not a verified list of every supplier currently contracted or enabled in production. Confirmed services must be finalized before the corresponding customer processing begins.
1. Supplier review register
The entries below identify implementation candidates to verify, not an authorization to process data with every listed service. A supplier belongs in the adopted subprocessor list only when its actual role, contracting entity, locations, safeguards, and enabled service have been confirmed.
Scroll the table horizontally to see all columns.
| Service to verify | Potential processing purpose | Required confirmation |
|---|---|---|
| Supabase | Authentication, database, and object storage. | Contracting entity, active project, regions, backups, support, and DPA. |
| Vercel or actual hosting supplier | Hosting, delivery, and operational metadata. | Active hosting contract, log scope, regions, and support access. |
| OpenAI | Selected AI analysis, content, research, or image tasks. | Enabled tasks, entity, endpoint controls, retention, locations, and DPA. |
| Firecrawl | Public-site extraction where fallback is enabled. | Whether enabled, actual payloads, entity, terms, and locations. |
| Serpstat | Keyword and domain research involving personal information. | Actual payloads, role, entity, terms, and processing locations. |
| Resend or actual email supplier | Service messages and delivery metadata. | Active supplier, message scope, retention, entity, and locations. |
| Upstash / Sentry, if enabled | Rate limiting or diagnostics and performance. | Production enablement, identifier scope, redaction, terms, and locations. |
| Gemini / Perplexity, if enabled | Optional engine or research operations. | Actual routing, tier, product-specific terms, entity, and locations. |
2. Other recipients and destinations
Payment processors, independent identity providers, advertising recipients, and customer-selected publishing destinations may have roles different from a subprocessor. Describe those roles separately in the Privacy Policy and relevant agreement. The presence of a package or model label in source code does not establish production processing.
3. Customer authorization and changes
The completed DPA must specify general or specific authorization, the notice method and period for changes, an objection process, and an agreed remedy when a reasonable alternative is unavailable. Provider must impose appropriate written obligations on approved subprocessors and remain responsible as required by law.
Ask through the contact page for the current proposed processing schedule or procurement information. A functioning notice subscription and change log must exist before promising automated change notifications.
4. Processing locations
Supplier headquarters, contracting entity, database region, backup location, and remote-support access are different facts. Confirm all relevant locations and any restricted-transfer mechanism. This draft does not represent a particular supplier certification as a certification of Clingeo.
Contact and related documents
Contact Clingeo for an appropriate inquiry route. Please do not include patient information or credentials.