Privacy
Production subprocessors and service providers
The providers below support the current Urd Atlas production service. The table states the operational purpose and the principal data category involved.
| Provider | Purpose | Data category | Role |
|---|---|---|---|
| Clerk | Authentication and session management | Account identifier, email/profile data used for sign-in, authentication/session metadata | Authentication provider |
| Stripe | Checkout, subscription billing and customer portal | Billing contact details, Stripe customer/subscription identifiers, payment information handled by Stripe | Payment processor |
| Vercel | Web application hosting and deployment | HTTP request/operational metadata and application delivery data required to serve the service | Hosting/deployment |
| Supabase | Production PostgreSQL database | Account, entitlement, subscription reference, API-key metadata and operational application records | Database |
| Upstash | Production rate limiting | Rate-limit keys derived from request/client context and bounded request-control metadata | Rate limiting |
| GitHub | Source control and automated build/pipeline workflows | Repository code, generated publication artifacts and workflow operational metadata; not payment-card data | Source control/automation |
| AWS Public Blockchain Data | Upstream public blockchain source data | Public blockchain data; no Urd Atlas customer account data is required to obtain chain observations | Upstream data |
This list is intended to reflect actual production providers, not hypothetical future vendors. Material changes to processors that affect customer personal-data handling should be reflected here and in the Privacy Policy.