Service providers
Zaika uses a small set of companies to run the app. This list explains what each one may receive and why. Not every provider is used for every recipe import.
Last updated 7 September 2026
Recipe import and AI processing
These services run only after you give Zaika permission for AI processing. Depending on the source and which extraction route succeeds, an import may use one or more of them. We send the recipe source or content needed for that import, not your email address, profile, or the rest of your cookbook.
Anthropic structures recipe text into fields such as title, ingredients, and steps, translates saved recipe fields, and creates nutrition estimates. OpenAI is the configured fallback for those same purposes if the primary route fails.
Google Gemini can read supported public cooking videos, including relevant speech and on-screen text, when video understanding is needed.
Deepgram transcribes speech from supported recipe media. AssemblyAI is the configured transcription fallback.
Apify resolves supported public social-media links into the caption, attribution, and media needed for import processing.
Core app services
Supabase provides authentication, the private database, file storage, and server-side functions. It holds account details and the Zaika content you save.
Vercelhosts Zaika’s public website and web service routes, and processes the request metadata needed to serve them.
Expo supports app delivery and push notifications. A push token and the notification payload are sent when you enable notifications; recipe content is not put in notification bodies.
Resend delivers transactional emails such as account and deletion notices, using the destination email address and message contents.
Apple and Google provide optional sign-in, app distribution, and store billing. Zaika receives authentication tokens and purchase status, never your payment-card details.
Product reliability and subscriptions
RevenueCatverifies purchases and maintains subscription entitlement state using Zaika’s internal account id and store purchase information.
PostHogreceives Zaika’s internal account id and a limited set of typed product events. SDK lifecycle and screen autocapture are disabled. Masked replays of app sessions are sent only for accounts we have enrolled (internal team accounts, testers on pre-release builds, and people who asked us to look into a problem, for a limited time): about one screenshot a second with text, typed input, photos and system pickers masked on the device, plus taps, kept for 30 days. Nobody else’s sessions are recorded. Zaika does not send recipe text, imported URLs, search terms, names, email addresses, or your photos to PostHog.
Sentryreceives crash and performance diagnostics plus Zaika’s internal account id so a failure can be investigated. Zaika disables default PII collection and scrubs sensitive values before sending reports.
Changes and questions
We update this page before activating a new provider. If a change materially expands who receives recipe content or why it is processed, Zaika will ask for permission again before the next AI-assisted import.
Questions about a provider or its role: privacy@zaika.app.