Subprocessors
Adatacore relies on a small number of infrastructure and specialist service providers. The exact data handled by each provider depends on the feature being used.
| Provider | Purpose | Typical data involved |
|---|---|---|
| Supabase | Database, authentication, storage and Edge Functions. | Account, profile, project, application, session and protected media data used by Adatacore workflows. |
| Vercel | Web hosting and content delivery. | Public and application page requests, standard network/request metadata and deployed site assets. |
| Resend | Transactional email delivery. | Email address and message content needed for the specific notification or inquiry email. |
| Groq | AI transcription draft processing for configured transcription workflows. | Audio submitted to the configured AI-draft workflow and associated request metadata. Human review remains part of the Adatacore transcription workflow. |
| ipwhois.io | On-demand approximate IP geolocation for authorized Trust & Safety review. | An IP address selected for a Super Admin security review. Returned location and network information is approximate and is not GPS data. |
How we use providers
Providers are used for defined infrastructure or product functions rather than for advertising access to contributor conversations or project data. Access by Adatacore staff is separately controlled through the platform's own authorization model.
Changes
This list may change as infrastructure or product features evolve. We will update the published page when a material provider is added or removed from the current platform stack.
Questions
For a project-specific data-processing requirement, raise it during project scoping. Contributors can use authenticated Workspace support for account-specific questions.