Privacy

Recipes, plans, grocery lists, cook logs, and profile details are private to your account by default. Database access rules tie them to your Zaika user id; privacy is not only a visual setting in the app.

A recipe becomes available to someone else only when you explicitly create a share link or send it to another Zaika user. Shared content includes its creator attribution. You can revoke a public link, and direct-share recipients can report or block unwanted content.

Account and profile information: email address, internal user id, authentication provider details, and optional name, handle, and profile image. We use this to sign you in, sync your account, show attribution, and support sharing.

Cookbook content: source links, pasted text, recipe scans and photos, parsed recipes, ingredients, steps, notes, tags, plans, grocery lists, cook history, share records, and content you send to or receive from another user. We use it to provide the features you choose.

Preferences and goals: language, diet or observance choices, cuisine regions, appliances, measurement style, recipe-source preferences, notification choices, and optional calorie or protein goals. We use these to tailor cooking, planning, and notification features.

Device and service information: push token, app version, device and operating-system details, subscription entitlement and store purchase status, product interactions, and crash or performance diagnostics. These support notifications, purchases, reliability, fraud prevention, and product improvement.

If you join the pre-launch waitlist, we store your email address and whether a referral brought you there. The public landing-page analytics id is random and is not joined to your email address.

Link, pasted-text, photo, audio, and video imports, recipe translation, and nutrition estimates can use external AI, media-resolution, and speech-to-text services. Before the first assisted feature, Zaika explains what can be sent and asks for your explicit permission. Declining leaves manual recipe entry and all non-AI features available.

Depending on the import, processing can include the source URL and public source content, text you pasted, images you selected, the relevant audio/video, or saved recipe fields needed for the translation or nutrition estimate shown to you. The purpose is limited to resolving, transcribing, structuring, translating, or estimating the submitted recipe. We do not include your email address, profile, or unrelated cookbook content in those provider requests.

See the maintained service-provider list for the current AI and transcription recipients. You can withdraw permission in Settings at any time; future AI-assisted imports, translations, and new nutrition estimates then stop until you consent again. Withdrawal does not undo processing that already completed.

Zaika caches structured results from public source links so the same public link does not require a second billable extraction. This de-identified cache is not readable from a user account and does not contain the identity of the person who first imported the link. Private scans and pasted family recipes are not eligible for the public catalog.

A Zaika user can ask someone at home for a recipe by sending them a link. The person who answers needs no account. What they send — a voice recording, a photo, typed text and the name they choose to sign with — is stored for the person who asked, as part of their private cookbook. We do not collect the responder’s phone number or email address.

When the person who asked turns a response into a recipe, the recording, photo or text is sent to the same AI and transcription providers listed on the service-provider page to transcribe and structure it. The response page says so before anything is sent. The kept recording plays back only to the person who asked, and to anyone they later choose to share that recipe with by turning on “include the voice notes” for a shared cookbook. Recordings never enter the public catalog.

A response that is not turned into a recipe is deleted 14 days after the request it answered expires (requests expire after 60 days). A recording kept with a recipe stays as long as that recipe does. If you sent a recording and want it removed, email privacy@zaika.app with the name you signed with and the dish; we will confirm with the person who asked and remove it.

If you save a favorite grocery store using your location, Zaika stores the selected store name and precise coordinates in your private profile. If you separately enable “notify near stores,” the device registers an operating-system geofence around those saved coordinates so it can remind you about unchecked grocery items.

Background location is optional. Zaika does not keep a continuous route or location history. You can turn store proximity off, remove a saved store, or revoke location permission in system Settings. Push notifications are also optional and can be disabled by category in Zaika or entirely in system Settings.

Zaika sends a limited, typed set of product events to PostHog and associates them with an internal user id after sign-in. SDK screen, touch, and app-lifecycle autocapture are disabled. Events do not include recipe text, imported URLs, search terms, names, email addresses, or precise location.

Zaika records masked session replays only for accounts we have enrolled: internal team accounts, testers on pre-release builds, and people who asked us to look into a problem and agreed to a recording, for a limited time. If that is you, PostHog receives about one screenshot a second of what was on screen, plus your taps and the internal user id, so a problem you report can be watched and reproduced instead of described. Text, typed input, photos and system pickers are masked on the device before anything is sent: what you wrote, imported or photographed stays on your phone, and only the app’s own labels and messages remain readable. Recordings are kept for 30 days, and an enrolment lapses on its own. For everyone else the release does not record sessions: no screenshots, screen recordings, or tap recordings are sent, and product analytics is limited to the typed events described above.

Sentry receives scrubbed crash and performance diagnostics plus the internal user id needed to investigate a failure. Default personally identifying collection is disabled. RevenueCat receives the internal user id and app-store purchase information needed to verify subscription access. Zaika never receives your payment-card details.

Zaika does not sell personal information, show third-party advertising, or use this data to track you across other companies’ apps or websites. The full operational list is on the service-provider page.

We keep your account and private cookbook while the account is active. You can request deletion in Settings. Access on that device ends immediately, followed by a 30-day recovery window in case the request was a mistake. An intentional new sign-in during that window explains and cancels the scheduled deletion; merely reopening a still-signed-in app does not.

After the recovery window, Zaika permanently removes the account and its private content from the primary application systems and deletes or de-identifies account-linked processor records where supported. Limited security, transaction, tax, dispute, or abuse-prevention records may be retained only when required for a legal or legitimate operational obligation.

No longer have the app? Request deletion from the web using an emailed verification code. Deleting Zaika does not cancel an App Store or Play Store subscription; the deletion flow provides a direct link to manage it.

Settings lets you withdraw future AI processing permission, control notification categories, disable store proximity, manage shared links, and request account deletion. System Settings controls camera, photo-library, notification, and location permissions. Subscription settings are managed by the app store that billed you.

To ask for a copy, correction, or deletion of your information, or to object to a use not exposed in Settings, email privacy@zaika.app. We may need to verify that the account belongs to you before acting.

We will update this page when collection or processing changes materially. If an AI-processing change materially expands the recipient or purpose, Zaika will ask for permission again before the next assisted import.

Privacy questions: privacy@zaika.app. General help: support@zaika.app.