Trust and compliance
Subprocessors
Mimiqo uses selected service providers to operate the platform. Depending on the features used, these providers may process data on behalf of Mimiqo.
Current provider categories
Mimiqo may use providers responsible for hosting and infrastructure, databases and authentication, AI processing, error monitoring, and platform integrations.
How to read this page
For each provider, we publish their name, purpose, general information about region or transfers, and a link to the relevant privacy or DPA documentation, if available.
| Provider | Purpose | Region | Data | Info |
|---|---|---|---|---|
| Supabase | Database, authentication, storage | Configured per current deployment and vendor setup | Account data, content items, analyses, tokens (encrypted) | Learn more |
| Vercel | Hosting and application execution | Configured per current deployment and vendor setup | Request data, serverless execution | Learn more |
| OpenAI | AI analysis and content generation | May involve processing outside EEA depending on vendor setup and transfer basis | Captions, content fragments (per-request, not retained for training) | Learn more |
| Meta | Platform integrations | Subject to Meta platform architecture and terms | Account IDs, tokens, post data, media | Learn more |
| Sentry | Error monitoring and diagnostics | Configured per current deployment and vendor setup | Error stack traces, request metadata, browser/device info. IP addresses scrubbed, user identified by anonymous ID only, all PII patterns automatically redacted before transmission. | Learn more |
This list may be updated from time to time as Mimiqo's infrastructure changes.