Loading...
Data transparency
Providers are listed by function. A provider receives data only when the relevant website, account, payment, communication, or AI feature is used.
Last reviewed: July 12, 2026
| Provider | Purpose | Data categories | When used | Provider policy |
|---|---|---|---|---|
| Clerk | Authentication, account management, and session security | Account identifiers, name, email, authentication and session data | Used for account features | View policy |
| Vercel | Hosting, content delivery, performance, and aggregate analytics | Request, device, network, performance, and deployment data | Used across the website | View policy |
| Google Analytics | Optional website usage analytics | Consent-dependent browser, page, event, and approximate location data | Loads only after analytics consent | View policy |
| Stripe | International payment processing, billing, fraud prevention, and refunds | Billing identity, payment and transaction data | Used when Stripe is the selected payment provider | View policy |
| Razorpay | India-region payment processing, billing, fraud prevention, and refunds | Billing identity, payment and transaction data | Used when Razorpay is the selected payment provider | View policy |
| OpenAI | AI-assisted tool features | Feature input such as prompts, images, code, or issue descriptions | Used only by features configured for OpenAI | View policy |
| Anthropic and OpenRouter | Alternative AI-assisted analysis and generation | Feature input such as prompts, code, or issue descriptions | Used only when the relevant model provider is selected | View policy |
| Sanity | Content management and blog delivery | Published editorial content and content-management account data | Used for published content | View policy |
| Formspree and Resend | Contact-form delivery and requested or transactional email | Name, email, message, organization, and email delivery metadata | Used when a form or email workflow is requested | View policy |
This register is updated when a material provider or processing function changes. Customers with a separately agreed data-processing notification term receive notice through the agreed channel.
Contact contact@accessibility.build with the provider, processing function, and concern. Applicable contractual and legal rights remain unchanged.