Your food life is not a product.

Who runs Splitdish

Splitdish is the controller responsible for the personal information described here and is operated under the name Splitdish. For privacy questions, complaints, or to start a rights request, contact hellosplitdish@gmail.com.

An email can start a request, but it does not prove who controls an account. Do not send passwords, identity documents, or account data by email. Splitdish will acknowledge the request and arrange separate secure verification and delivery before returning information or changing an account.

What Splitdish stores

• Your account identity, email address, display name, sign-in provider, and account preferences.
• Your personal recipes, recipe images, and temporary recipe-capture material.
• If you share a recipe link, its bearer token and limited server records used to prepare, read, and stop the link. Recipe content is read from its current source; the active link does not store a content snapshot.
• Your group memberships, shared group recipes, current menus, saved-menu references, shopping lists, staples, and kitchen-check results. If you use a temporary invite identity, Splitdish also stores its temporary group marker and the server-side hash and lifecycle state of the group's short-lived, multi-use link.
• Essential browser storage needed to keep you signed in, retry profile setup, remember your product and campaign measurement choices, and hold recently viewed group data in memory while this tab is open. An open list can queue ticks offline until the server confirms them.
• Limited operational and security records needed to keep the service working and investigate errors or abuse.

Splitdish uses this information to provide the service you ask for, keep shared group data in sync, protect accounts, and operate the service reliably. Optional measurement follows your choices and is never required to use Splitdish.

Photos and AI

A recipe photo is uploaded temporarily so Splitdish can read it, then the temporary source is deleted. A kitchen-check photo is used to compare visible ingredients with the current shopping list and is removed after processing, with lifecycle cleanup as a backstop.

Splitdish may send recipe-page text, recipe or kitchen-check photos, ingredient text, and the Pickle conversation for the feature you selected to Google Vertex AI. When you ask Pickle to plan with a Group, that request can also include bounded food details from the active Group's Menu and saved Group Recipes. Pickle reads those sources for planning; it does not change them. Wrapping up a menu and reusing a saved menu do not call an AI model. Generated or extracted results are still suggestions: check ingredients, quantities, allergies, dietary needs, and food safety yourself.

Pickle can keep its conversation and place in this browser tab's session storage so you can return after a refresh. It expires after 24 hours without foreground Pickle activity and is restored only after your verified account's current Group access is confirmed. It clears when you start over, save, sign out, change accounts or Groups, or lose Group access. Your unfinished Recipe draft remains separately recoverable if the conversation expires or cannot be restored. This information is not retained server-side or written to saved Recipes, Firestore, analytics, rate-limit records, or operational logs. Restoring it does not send another Pickle request. Converting a chat idea sends only the proposal you select for an editable Recipe draft; saving remains your choice. Google may retain limited service or abuse-monitoring records under its own service terms.

Splitdish does not use household food data for advertising and does not sell it. Google may retain limited service or abuse-monitoring records under its own service terms; deleting Splitdish data cannot delete records another provider must lawfully retain.

Speech in Pickle

Dictation uses your browser's speech-recognition service, which may process audio on this device or remotely. Splitdish does not receive or store raw audio, and the app cannot identify which route the browser uses. Your browser or operating system may ask for microphone permission. Dictation is available when your browser exposes speech recognition, though the service may still be unavailable.

While you record, recognized words stay in temporary memory in this page. Stop adds them to the composer for you to review. Only Send submits that text through the existing Pickle message path, where the existing conversation-draft rules described above apply. Speech text is not sent to analytics, logs, or Sentry.

Service providers

Splitdish uses Google Firebase and Google Cloud for sign-in, database, file storage, hosting, and AI processing. Google sign-in is optional. The production foundation may use Sentry for error-only monitoring, Microsoft Clarity for strictly masked session diagnostics, Google Analytics for consented product measurement, and Google Ads for consented campaign measurement.

Read the providers' own information at Google Firebase privacy and security, Google privacy policy, Sentry privacy, and Microsoft privacy.

When used, Sentry is limited to error monitoring without session replay or a Splitdish user identity. Clarity does not load unless you allow product measurement, keeps advertising storage denied, and does not receive a Splitdish user identity. Google Ads campaign measurement runs only after its separate choice; it records successful account creation and sanitized page visits. A valid ad click identifier may be included in the page location to connect a visit to a campaign. That choice grants Google's ad_storage and ad_user_data consent signals; ad_personalization remains denied. Splitdish does not send account details or enhanced-conversion data. These providers may process information outside your country using their contractual and legal transfer safeguards.

Optional measurement and cookies

Choose product analytics and masked session diagnostics separately from advertising measurement. Both are optional, and you can change your choices here at any time.

Essential browser storage keeps sign-in, security, shared updates, your saved measurement choices, and a memory-only Firestore cache for recently viewed group data and queued shopping ticks while this tab stays open. The app clears that cache when you sign out or switch accounts. A tick is not saved until the server confirms it; reloading or closing the tab while offline loses an unconfirmed tick. Before signing out with a tick still syncing, you can wait for it or discard it. These essential functions cannot be switched off inside Splitdish because the service would not work without them.

With product measurement allowed, Google Analytics may receive activity shapes such as a completed journey or a menu milestone, and Clarity may record a masked session. With campaign measurement allowed, Google Ads receives one direct conversion after a successful account creation, plus sanitized page-visit information. A single valid gclid, gbraid, or wbraid may accompany the page location. Splitdish does not send free text, recipe contents, group names, email addresses, account IDs, or enhanced-conversion data to these services. Google's ad_storage and ad_user_data consent signals follow your campaign choice; ad_personalization stays denied. The first-visit banner lets you accept or reject both purposes together, or open these settings to choose each separately. Turning measurement off never limits Splitdish.

Sharing inside a group

People in a group can see that group's members, recipes, menu, shopping list, and activity receipts. Personal recipes stay private until you share one. A shared group recipe becomes part of the group's data.

If you delete your account, your personal data and memberships are deleted. Shared group facts that other members still need can remain, but your user id, display name, and personal recipe link are removed and the visible attribution becomes “Former member.” A group containing only your account is deleted with your account.

Recipe links

Anyone who receives a recipe link can open that one current recipe while the link and its source remain available. Links do not expire by time; the sender can stop one at any time. Later edits appear when a friend reopens or refreshes the link. Group links also stop if the sender loses access to that group recipe. A recipient who chooses to keep the recipe saves an independent personal copy of its current content; stopping the link does not remove that copy.

When you open a recipe link and continue to sign-in, the current tab keeps the link access in session storage for up to 24 hours so it can return to that recipe. The bearer link is kept out of analytics and error reports. After a link is stopped or its source authority is lost, its server-side share record is scheduled for deletion 30 days later. Automatic cleanup may take longer than its scheduled time.

Why Splitdish uses this information

• To provide the account, group, recipe, menu, and shopping features you ask for and to apply these Terms.
• For Splitdish's legitimate interests in securing, maintaining, and improving a reliable service, where those interests do not override your rights.
• With your product-measurement choice for optional Clarity diagnostics and Google Analytics, and your separate campaign-measurement choice for Google Ads. You can change either choice without losing access.
• Where necessary to meet a legal obligation, including responding to valid information-rights requests.

How long information stays

Active account and group data stays while it is needed to provide Splitdish. Confirmed account deletion takes effect immediately in the live service, subject to short-lived operational logs, provider security records, and infrastructure backup or soft-delete periods that cannot be used as a user-facing restore.

Group deletion removes its required records and access before it completes. A few files can take a little longer to clear from storage.

Firebase may automatically remove an anonymous Auth identity under Firebase's own policy, including while its named temporary membership or profile records still exist. This does not remove those Splitdish-held records, and Splitdish does not currently run a scheduled sweep for that orphan case. Those records are removed when the user leaves, links a permanent credential, an owner removes them, the group is deleted, or a valid rights/deletion operation handles them; do not use a temporary account for information you need to keep.

Children and families

You must be 13 or older to use Splitdish. If you are under 18, ask a parent or guardian to review Splitdish with you. It does not ask for a date of birth or profile people for advertising, and the same high-privacy defaults apply to everyone.

Your choices and rights

You can correct your display name in Splitdish, change product or campaign measurement above, and delete a permanent account from Your account. Depending on the law that applies, you may also ask for access, correction, erasure, restriction, objection, or a portable copy of applicable personal information.

You may start a request through the contact address above. Splitdish will record the date and wording of the request, but will not disclose information or change an account based only on access to an email address. Use signed-in controls where available; Splitdish will arrange a separate secure verification and response for anything else. UK users may also complain to the Information Commissioner's Office.

Changes and contact

Important changes will be explained in plain language and the date at the top will change. For general questions, complaints, or to start a rights request, email hellosplitdish@gmail.com. Do not send identity documents, passwords, or account data by email. You can also read the Terms.