Platelab Privacy Policy

Effective date: August 18, 2026

Platelab is an iOS app that generates recipes, plated-food images, and cooking guidance. This policy explains what information the app handles and how. Platelab is operated by Ryan Dewsbury.

No accounts

Platelab does not require or offer user accounts, sign-in, or user profiles. The app has no concept of "your account" on our servers — there is nothing to register and nothing tied to your identity on our side beyond what is described below.

What we collect and send

When you ask Platelab to generate a recipe, an image, or a chat response, the recipe text, chat message text, and related prompt content you enter are sent from the app to our server, which forwards that content to Google Gemini (Google's AI model service) to produce the generation. Google's handling of that content is governed by Google's own terms and privacy policy for the Gemini API.

We do not collect names, email addresses, or other account-identifying information through the app, because the app does not have accounts.

What stays on your device

Your chat history is stored only on your device (in the app's local storage). We do not retain a copy of your chat conversations on our server, and we do not associate chat history with you as a person.

Server-side caching, keyed by dish — not by you

To avoid regenerating the same recipe or plated-food image repeatedly, our server caches generated recipes and images. This cache is keyed by the dish itself (for example, a normalized recipe/dish identifier), not by any per-user or per-device identifier. In practice this means:

• A cached recipe or image can be served back to any user of the app who requests the same dish — the cache is shared, not personal.
• We do not maintain a per-user history or profile of what you have generated on our server — the only per-subscription record is the short-lived verification cache and request count described under "Subscription billing", which stores how many requests were made, never what they were.

What we do not do

• No analytics or usage-tracking SDKs.
• No advertising and no ad networks.
• No sale, rental, or sharing of your data with third parties for marketing or advertising purposes.

Subscription billing

Platelab is offered via an auto-renewable subscription. All billing — including your payment method, subscription status, and the 7-day free trial — is handled entirely by Apple through the App Store. We do not receive or store your payment card details. Our server verifies subscription status using a signed transaction provided by Apple's StoreKit framework, which confirms that a subscription is active without exposing your payment information to us.

That signed transaction contains an Apple-assigned subscription identifier (the "original transaction ID"). To avoid re-checking Apple's signature on every single request, and to enforce a daily usage limit per subscription, our server stores that identifier: as a short-lived verification cache entry (kept at most 24 hours), and as a per-day request counter (kept about 48 hours). Both expire automatically. The identifier is assigned by Apple and is not linked to your name, email address, or any account with us — we have no way to turn it back into your identity — but it is a per-subscription identifier, so we describe it here rather than claim we hold nothing.

AI-generated content

Recipes, images, and other content Platelab generates are produced by an AI model and may be inaccurate, incomplete, or unsafe if followed literally — including for matters of food safety (such as cooking temperatures, allergens, or storage times). Use your own judgment. See the Terms of Use for the full disclaimer.

Data retention

Server-side cached recipes and images are retained to serve future requests for the same dish and are not tied to an individual user.

The one piece of per-subscription data we do hold is the Apple-assigned subscription identifier described under "Subscription billing": an entitlement cache entry (up to 24 hours) and daily usage counters (about 48 hours), both of which expire on their own. The same identifier also appears in our server's operational logs, which are retained on our hosting provider's standard schedule and used only for debugging and abuse prevention. None of it is linked to your name, email address, or an account with us.

If you would like us to delete data associated with your subscription, or you have questions about a specific cached item, contact us using the details below.

Children

Platelab is not directed at children and is not intended for use by anyone under the age of 13.

Changes to this policy

If this policy changes, we will update the effective date above and revise the copy hosted at this same URL. Continued use of the app after a change constitutes acceptance of the revised policy.