Privacy Policy

Account details. Your email address, a password (stored only as a salted hash by our authentication provider) or the fact that you signed in with Apple or Google, and a display name if you set one.

Household membership. Which family or household you belong to, your role in it, and the invites you send or accept. Everyone in a household can see the shared content in it, and can see the display names of the other members.

The content you enter. Shopping list items, meals, notes, saved and imported recipes, links or photos you import from, the stores you shop at, and what you have checked off. This is the substance of the app.

Voice transcripts. When you use voice capture or the hands-free cooking assistant, the audio is transcribed and we process the resulting text so we can act on it. We normally keep a hands-free cooking transcript only while the cook is active. Ending the cook clears it as part of that action; if the cook stays active but idle, an automated job clears it shortly after 24 hours since the last activity. Only if your household turns on “Help improve Peasy” may our authorized team review those cooking transcripts to improve the assistant; in that case we keep them until shortly after 90 days since their last activity.

Device push tokens. If you turn on notifications, we store the push token your device issues so we can send reminders and household notifications to it. Turn notifications off and we stop using it.

Subscription status. Your plan, whether it is active, when the current period ends, and an opaque customer or transaction identifier from Stripe or Apple.

Technical and diagnostic data. Basic server logs (request time, route, status, a request identifier), app version, and platform, kept for debugging, abuse prevention, and measuring usage against your plan’s AI allowance. Our logs are written to deliberately exclude recipe text, utterances, and email addresses.

We use the above to:

• run the app — sync your household’s list, save recipes, build shopping plans;
• turn what you say or import into structured items and steps;
• send the notifications you asked for;
• operate subscriptions: unlock paid features and count AI usage against your plan’s allowance;
• support you when you write in, and keep the Service secure and working;
• review hands-free cooking transcripts to improve the assistant, only if your household turns on “Help improve Peasy”;
• meet legal obligations.

We do not use your content to build advertising profiles, and we do not run third-party ad tracking in the app.

To import a recipe, understand a voice capture, or run the cooking assistant, we send the relevant text — the recipe content, the page or image you asked us to read, or your utterance — to third-party AI providers acting as our processors. They return structured results to us, and we use those to update your list or recipe.

We use these providers under terms that prohibit them from training their models on your content. We send only what the feature needs, and we do not attach your email address or account credentials to those requests. Providers may retain the request briefly for abuse monitoring under their own policies before deleting it.

If you would rather not have content processed this way, do not use the import, voice, or cooking-assistant features — typing items in by hand never involves an AI provider. “Help improve Peasy” is a separate choice: leaving it off prevents our team from reviewing your cooking transcripts, but it does not turn off the AI processing needed to provide a voice or cooking-assistant feature you choose to use.

PrepPeasy never receives, sees, or stores your card number, CVC, or bank details. If you subscribe on the web, Stripe collects and processes the payment on its own systems. If you subscribe in the iOS app, Apple does, using the payment method on your Apple Account.

What we store is only what we need to know whether to unlock your features: your plan, its status, its renewal date, and an opaque identifier that lets us match you to the record held by Stripe or Apple. Billing history, receipts, and card management live with those providers — Stripe’s customer portal for web subscriptions, App Store subscription settings for Apple ones.

We share personal information only with service providers that help us run PrepPeasy, and only for that purpose. They act on our instructions and are not permitted to use your data for their own ends. They are:

• our hosting and database provider, which stores your account and content;
• AI providers, as described in Section 3;
• a speech-to-text provider, for voice capture;
• Stripe and Apple, for payments and subscription status;
• Apple and Google push notification services, to deliver notifications;
• an email provider, for account and support email.

We also share information with the other members of your household — that is the point of a shared list — and we may disclose information if the law requires it, or to protect the rights and safety of our users or the Service. If PrepPeasy is ever involved in a merger or acquisition, we will tell you before your information becomes subject to a different privacy policy.

If you choose to import a recipe from Google Drive, PrepPeasy uses Google’s own file picker and requests only the drive.file scope. That scope gives us access only to the specific files you pick yourself, at the moment you pick them.

We cannot list, search, or browse your Drive, and we never see files you have not explicitly chosen. We read the content of a chosen file to extract the recipe, and we do not write to your Drive. PrepPeasy’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can revoke our access at any time from your Google Account’s third-party access settings.

On the web we use cookies that are strictly necessary to sign you in and keep you signed in. We do not use advertising cookies, and we do not sell or share data with ad networks.

We use privacy-respecting, aggregate product analytics (PostHog) to understand which features are used and where the app breaks — for example, how often imports fail. This analytics does not use cookies, does not build advertising profiles, and does not track you across other sites. We keep it at the level of counts and events, not the content of what you added.

We keep your account and content for as long as your account is open, because that is what makes your list and saved recipes there when you come back. Server logs are kept for a short operational window. Without “Help improve Peasy,” ending a cook clears its hands-free transcript synchronously. If the cook remains active but idle, our every-minute retention job normally clears it within about a minute after 24 hours since its last activity. If your household turns the setting on, we may keep and review those transcripts until the same job runs after 90 days since their last activity. Turning it off removes your household’s transcripts from research review right away; a transcript may still remain briefly, within the ordinary activity window, while an active cook needs it.

To delete your account, email support@preppeasy.com from the address on the account and ask us to delete it. We will verify it is you and delete your account and personal content within 30 days, except for records we are required to keep (for example, payment records kept for tax and accounting purposes, which live with Stripe or Apple).

Content you contributed to a shared household may remain visible to the rest of that household after you leave — remove it before you go if you would rather it did not. Deleting your account does not cancel an Apple subscription; cancel that in App Store subscription settings too.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising, as those terms are used under California law. We have not done so in the past 12 months.

PrepPeasy is not directed at children under 13, and we do not knowingly collect personal information from them. Accounts require you to be at least 13. If you believe a child under 13 has created an account or given us information, email support@preppeasy.com and we will delete it promptly.

Depending on where you live — including California under the CCPA/CPRA, and the EEA and UK under the GDPR — you have rights over your personal information. We extend the substance of these rights to everyone who uses PrepPeasy:

• Know and access — ask what we hold about you and get a copy.
• Correct — fix inaccurate information; you can edit most of it in the app.
• Delete — have your account and personal content erased.
• Port — receive your data in a portable, machine-readable format.
• Object or restrict — object to certain processing, or ask us to limit it.
• Withdraw consent — where we rely on consent (such as “Help improve Peasy,” notifications, or Google Drive access), withdraw it at any time.
• Non-discrimination — we will not degrade your service for exercising these rights.

Exercise any of them by emailing support@preppeasy.com. We will verify your identity through the email address on the account and respond within the time the applicable law allows. An authorized agent may make a request on your behalf with proof of authority. If you are in the EEA or UK, our legal bases for processing are performance of our contract with you (running the Service), our legitimate interests (security, abuse prevention, improving the Service), consent (where asked for), and legal obligation — and you have the right to complain to your local supervisory authority.

We use encryption in transit, access controls, and database-level row-level security so that a household’s data is reachable only by its members. No system is perfectly secure, and we cannot guarantee absolute security — but if a breach affects your personal information, we will notify you and any regulator as the law requires.

Our infrastructure and our service providers are located in the United States, so if you use PrepPeasy from elsewhere your information is transferred to and processed in the United States under appropriate safeguards.

Before launch, preppeasy.com collects a smaller, separate set of information to run the founders waitlist:

• Your email. We use it to hold your spot, confirm your signup, and send your founder-checkout link and launch updates.
• Confirmation (double opt-in). We send a confirmation email after you sign up, and your spot does not count against the founder cap until you confirm it.
• Beta interest and “what’s missing.” Two optional questions after you join — whether you would like to beta test, and anything free-text you tell us is missing. Both are optional and skippable.
• Your mobile number (optional). After you join, you can add a mobile number. If you do, we use it for a small number of texts about your spot and launch day — nothing else. We never sell or share it, you can reply STOP to any text to stop them, and you can ask us to delete the number at any time using the address below.
• How you found us. If you arrived via a link or campaign, we store the attribution (UTM parameters) and the page that referred you along with your signup, so we know which channels are working.

We use Resend to deliver waitlist emails, PostHog for the same cookieless, aggregate analytics described in section 7 — no cookies, no cross-site tracking, and never your email address — and Sentry to catch and diagnose errors on the site, which likewise never receives your email address. The public founder counter on the page shows only an aggregate count of confirmed signups; it is never broken out by individual.

To be removed from the waitlist, or with any question about what we hold, email support@preppeasy.com.

If we change this policy, we will update the “Last updated” date above, and for material changes we will tell you in the app or by email before they take effect.

Questions, requests, or concerns about privacy? Email support@preppeasy.com.