Updated October 13, 2026
Privacy Policy
Peasy is operated by Thoughtful Technology Company LLC.
Peasy stores the account, household, recipe, meal-plan, shopping-list, and preference data needed to provide the service. Supabase provides authentication and canonical cloud storage.
If Peasy offers starter recipes during account setup and you choose them, your diet preference, selected ingredients you dislike, cooking-time choice, and major-allergen answers go to Peasy's protected Supabase command to choose approved recipes. The answers are used for that one setup action, not saved as a food preference or allergy profile or sent to a search or model provider. The command retains a request digest to recognize an exact retry. The recipes added to your account are ordinary saved recipes with public links; you can edit or delete them. Peasy cannot guarantee that a recipe or ingredient is safe for an allergy.
Trials and subscriptions
Peasy keeps your account trial start and end, verified RevenueCat product and agreement identifiers, billing store, renewal and access-through state, checkout attempt leases, and webhook receipts. RevenueCat receives your non-guessable Peasy account identifier, original promotional-access expiry, and the purchase information needed to grant and manage access. When web checkout is available, RevenueCat Billing and its Stripe payment gateway process the contact, billing, payment, and transaction information needed for the purchase and subscription. Peasy receives subscription status and transaction identifiers, but not complete payment-card details. RevenueCat and Stripe may retain their own billing and transaction records under their policies and legal obligations after you delete your Peasy account.
A prepared assisted-import review draft is held for up to 24 hours to return an identical retry; the monthly usage record remains until account deletion.
Protected backups
When Peasy creates an offsite recovery backup, a GitHub Actions runner temporarily processes a copy of Supabase account and product records, authentication records, operational records, and protected uploaded files. The runner encrypts the backup before placing it in a private Cloudflare R2 bucket in the United States. Cloudflare receives the encrypted archive. Each copy is marked for expiry 14 days after creation; removal may take additional time.
Requesting account deletion blocks ordinary access and queues removal of live records. Records already included in an encrypted backup may remain there until that backup expires. Peasy will keep a restored service closed to users until account deletions are reconciled against the restored copy.
Public recipe links
Recipes saved after this public-link release receive a public link when saved. Recipes saved earlier remain private unless you choose Publish and copy link for that recipe. Anyone with a published link can read the current title, ingredients, instructions, notes, and your Peasy display name without signing in. If you save a photo with a published recipe, anyone with the link can see it. The photo remains in private Peasy storage, and the public page receives a short-lived image link; another person's recipe copy does not include your photo. A new recipe's link exists whether or not you send it to anyone. Each link uses a random recipe UUID, so one link does not reveal a sequence of your other recipes. Edits appear at the same link. Once published, a recipe has no stop-sharing setting in this version; deleting it makes its link unavailable.
Deleting a recipe or your account makes your link unavailable. If another person has already chosen Save to Peasy, their independent copy remains in their account with your display name as creator attribution and a separate public link. Peasy does not notify you when someone reads or saves a copy.
For email sign-up and sign-in, Supabase sends your email address and verification-code message to Resend (Plus Five Five, Inc.) for delivery. Peasy's optional three-day and one-day account-trial reminder emails are currently off. If enabled later, Peasy would send your email address, trial end date, reminder message, and delivery metadata to Resend. These email routes do not include your recipes, household details, or shopping lists. RevenueCat Billing sends separate subscription emails after a web purchase, such as purchase, renewal, payment-issue, cancellation, and account-management messages, using checkout contact information.
Peasy uses Proton Mail to receive, reply to, and retain messages you send to its contact address.
Data used by providers
When Peasy cannot prepare or translate a recipe deterministically, it sends the recipe route, language choices, extracted or copied recipe text, and any partial structured draft through OpenRouter to the configured zero-data-retention model endpoint. Recipe preparation may use a Microsoft Azure-hosted OpenAI model or Google Cloud Vertex AI; other model-backed paths use the Azure-hosted OpenAI route. If a pasted recipe URL is blocked, Peasy may also send that URL through OpenRouter's Exa page-retrieval tool and send the retrieved page content to the configured model to prepare a review draft. The model endpoint's zero-data-retention setting does not establish Exa's retention terms. When nutrition estimation is available, reviewed ingredient names, amounts, units, and preparations may also go to the configured model route to estimate nutrients. Original recipe photos and file bytes do not enter these model routes. Retailer searches are sent only to the provider needed for the action. Provider credentials remain on Peasy's backend. RevenueCat does not receive your recipes or household content.
If managed page retrieval cannot prepare a blocked recipe URL and you paste text copied from its page, Peasy sends that text with the source URL to its protected recipe-import service. If you use the optional Peasy Recipe Capture browser extension, it reads text and an image URL from the recipe page open in your browser after you click its toolbar action. The extension holds the capture temporarily in browser session memory and sends the text and source URL to the same protected service. Raw page text is not stored as a separate recipe record. A source image may appear during review; displaying it can request the image from its host. Where recipe photo saving is enabled, choosing to save that image causes Peasy's protected service to request it from its source website and store a private copy with your account and recipe. You can instead select your own JPEG, PNG, or WebP photo. Peasy stores the photo, its source URL when applicable, and technical file details in Supabase Storage and its database until you replace or delete the recipe or request account deletion. Photo bytes do not enter the recipe preparation model.
Shopping area and Kroger
A ZIP code you enter is Peasy's shopping-area preference for finding nearby stores across supported retailers. Where saving shopping preferences is available, Peasy retains that ZIP code as account data. The ZIP is entered into Peasy, not obtained from Kroger. An exact store you select is saved only in this browser profile for your Peasy account and may include its retailer-provided location identifier, display name, and address. The choice does not sync to another device. Peasy does not read your Kroger account's selected store.
When Kroger browsing is available and you request nearby stores or products, Peasy sends the ZIP code, selected Kroger location identifier, or grocery search terms needed for that request through its protected backend to The Kroger Co. Kroger returns store or product information for display. Product images may be loaded from their hosts, which receive ordinary network request information.
When Kroger cart transfer is available in Peasy's web app and you choose to connect, Kroger handles sign-in. Peasy then stores encrypted, account-linked authorization tokens on its backend, not your Kroger password. Only after you explicitly approve selected products and package counts does Peasy send Kroger the exact UPCs, quantities, and pickup or delivery item mode. Kroger controls the destination cart and checkout, and you must verify its selected store there. Disconnecting removes Peasy's stored authorization; requesting Peasy account deletion also removes it when backend deletion completes. Peasy does not save Kroger cart contents or cart history as account data.
Local data
The browser may keep an account-scoped cache and pending command data so confirmed content remains readable and eligible shopping checklist changes can recover after a connection interruption. Live product matches and prices are temporary. Your saved shopping ZIP remains Peasy account data until changed or removed with the account. Your selected exact store remains on this browser until you change the ZIP, deselect the store, or clear this browser's site data. Signing out does not by itself erase the account-isolated store choice. Service and infrastructure providers may retain limited security and operational logs under their own schedules.
Your choices
You can sign out at any time. You can request account deletion through Data Controls. A confirmed request immediately locks your Peasy account, including access for any remaining paid period. A protected backend process cancels renewal of any RevenueCat Billing subscription before it completes deletion, retries recoverable failures, and removes the account's product data. If you have an App Store subscription, you must cancel it separately through Apple. Account deletion does not automatically issue a refund. Limited security and operational logs, backups, and payment-provider records may remain under their applicable retention schedules or legal obligations.
Contact
Privacy questions can be sent to peasy@thoughtful.llc.