Third-party services
Managed-cloud service roles, data categories, and customer controls for Cossistant.
This page describes the current managed Cossistant Cloud architecture. It is an engineering inventory, not a promise that every vendor processes every customer's data or a substitute for the applicable privacy policy, DPA, or vendor trust documentation. Configuration and vendors can change; the review date above makes that drift visible.
Self-hosters choose and operate their own processors. Start with the Self-Host overview.
Managed-cloud inventory
| Service | Role | Data that may be processed | Customer or operator control |
|---|---|---|---|
| Vercel | Next.js web hosting and edge delivery | Web requests, IP/network metadata, rendered application traffic | Managed-cloud infrastructure |
| Railway | API and service hosting | API traffic, service logs, application data handled by the API | Managed-cloud infrastructure |
| PostgreSQL / Drizzle | Primary application database/toolkit | Organizations, websites, contacts, visitors, conversations, configuration | Retention/deletion through product and operator workflows |
| AWS S3 / CloudFront | Upload and media storage/delivery | Attachments, avatars, brand assets, object-request metadata | Limit uploads; remove objects; self-host alternative available |
| Upstash | Workflow/QStash job delivery | Job payloads and delivery metadata | Operator configuration; avoid unnecessary PII in jobs |
| Better Auth | Authentication framework | Account/session/OAuth data stored in the Cossistant stack | Account and OAuth-provider controls |
| Google and GitHub OAuth | Optional sign-in providers | OAuth identity/profile fields and authorization metadata | User chooses provider; revoke through provider settings |
| Polar | Subscription and payment lifecycle | Customer, subscription, entitlement, and usage identifiers | Disabled in self-host mode with POLAR_ENABLED=false |
| Resend | Managed transactional/inbound email | Recipients, message content, delivery/suppression metadata | Provider choice; SES self-host path available |
| AWS SES | Optional/self-host email transport | Recipients, message content, inbound mail, lifecycle metadata | Selected with EMAIL_TRANSPORT_PROVIDER=ses |
| OpenRouter | AI model and embedding gateway | Prompts/context sent for enabled AI features, model and usage metadata | Operator model/key policy; do not send context the model does not need |
| Tinybird | Inbox analytics and live presence | Visitor/activity/conversation metric events, page/acquisition/location context | Server and browser flags can disable it in self-host deployments |
| DataFast | Hosted site analytics script | Site visit/browser analytics defined by its script | Self-hosters can set NEXT_PUBLIC_DATAFAST_ENABLED=false |
| OpenStatus | Uptime/status monitoring | Endpoint availability and request metadata | Managed-cloud monitoring configuration |
Visitor context
Cossistant's visitor record can include language, timezone, browser/OS/device, screen and viewport, current page, sanitized referrer, campaign/click IDs, and server-enriched location. Anonymous identity itself is a website-scoped ULID in localStorage, not a browser fingerprint. See Visitors and Contacts before deciding what your application collects or associates with a signed-in person.
Security and privacy evaluation
Do not infer a blanket compliance guarantee from a vendor's inclusion here. Before relying on a service, review that vendor's current security/trust center, subprocessor list, DPA, processing regions, retention/deletion controls, incident terms, and your own configuration. Encrypt traffic, minimize payloads, rotate credentials, restrict access, and test deletion/export workflows at the application layer.
For a contract-specific or current subprocessor question, contact support@cossistant.com rather than relying on a static documentation page.
Was this page helpful?
Open a prefilled documentation issue so the team can act on your feedback.