Sub-processors

This page provides a transparency list of current sub-processors that may process data for TryOdi.

1. Approach

1. Sub-processors are used only as needed to provide, secure, maintain, and improve TryOdi.
2. Where applicable, we use data processing agreements, standard contractual clauses, or equivalent safeguards.
3. Provider changes are reflected on this page.
4. This page should be read together with the Privacy Policy.

2. Sub-processor List

Provider	Category	Purpose	Data types	Transfer region	DPA / Privacy
Vercel AI Gateway	AI gateway and routing	Routing server-side text generation, image generation, and brand summarization requests to configured model providers	Prompts, brand context, website excerpts, generated content, technical metadata	Global / provider dependent	Privacy, DPA
OpenAI	Underlying AI model provider	May serve configured Gateway text or image models, depending on routing and fallback settings	Prompts, brand context, website excerpts, generated content, technical metadata	Global / provider dependent	Privacy, DPA
Microsoft Azure / Azure OpenAI	Underlying AI model provider	May serve configured Gateway text models when Gateway routing selects Azure-backed endpoints	Prompts, brand context, website excerpts, generated content, technical metadata	Global / provider dependent	Privacy, DPA
Firecrawl	Website analysis	Website page extraction for brand setup and brand intelligence	Public website URLs, extracted website text, technical metadata	Global / provider dependent	Privacy
Zernio	Social publishing	Social account connection, scheduling, publishing, media handoff, and status sync	Connected account metadata, post content, media URLs, publishing metadata	Global / provider dependent	Privacy
Cloudflare R2 / S3-compatible storage	Cloud object storage	Storage for generated and uploaded post media	Media files, file metadata, storage keys	Account configuration dependent	Privacy, DPA
Railway	Managed PostgreSQL hosting	Primary application database infrastructure	Account, brand, post, billing reference, usage, and operational data	Provider dependent	Privacy, DPA
Lemon Squeezy	Payment infrastructure	Checkout, subscriptions, trial conversion, billing, tax, and payment events	Customer references, subscription data, transaction metadata, billing data	Global / provider dependent	Privacy, DPA
Resend	Transactional email	Verification, password reset, notification, contact, and transactional emails	Email address, message metadata, delivery metadata	Global / provider dependent	Privacy, DPA
Google OAuth	Authentication	Optional Google sign-in	Authentication profile data such as name and email	Global / provider dependent	Privacy
GitHub OAuth	Authentication	Optional GitHub sign-in	Authentication profile data such as username and email	Global / provider dependent	Privacy
Vercel	Hosting and infrastructure	Website and application hosting, edge/runtime infrastructure, queues or cron where used	Request metadata, logs, deployment and runtime metadata	Global / provider dependent	Privacy, DPA

3. Notes

1. This is a living inventory and may be updated as infrastructure changes.
2. Some providers may act as independent controllers for parts of their services, especially payment, social platform, and OAuth workflows.
3. TryOdi does not intentionally send payment card numbers to its own application servers; checkout is handled by the payment provider.
4. AI Gateway model creator prefixes, provider routing, BYOK settings, and fallback lists can affect which underlying model providers process AI prompts and outputs.