PrepCart privacy
This is written in plain English and describes exactly what the code does. PrepCart is operated by Tom McCarthy. We store the minimum needed to plan your week, fill your cart and email you about it. Your data is never sold, and never used to decide anything about your health: the service gives no medical, dietary or dietitian advice. Privacy questions and requests: support@getprepcart.com.
What is stored, and where
In your browser (chrome.storage.local, only on the computer where the extension is installed, never synced):
| Key | What |
|---|---|
profile | your household as you described it: each person's name, age, sex, height, weight, activity, goal and daily targets, how strict they are, allergies and foods to avoid, what they eat outside the plan, breakfast and snack choices, your cooking equipment, your meal prep schedule (which days you cook and who they feed), the day your week starts, what you usually pick on the shelf (own brand, a mix, brands you know, or organic and premium) and the products you always buy (a brand and an item, such as Heinz baked beans) and what PrepCart has learned you like when it shops (for example "regular chicken over organic", "loose lemons over bags", "skips cashews": things you told it, or habits it noticed two or three times and asked you about once; each can be removed in Settings, and a "No" to its question is remembered so it isn't asked again), and any changes you made for a particular week |
chat | the conversation that built the profile |
plan | the current week: the plan, its outline and cook sessions, pantry ticks, the plan's id, whether you approved it, the history of swaps, and any product you picked for a list line this week with Swap |
account | your sign-in session token, email, first name, role and household |
installId | a random id for this install, used to rate-limit sign-in codes |
site, stores | the website address and a cached copy of the store configuration and store health, so the cart feature knows what the supermarket's pages look like |
micHintShown, tip and voice flags | whether you have seen a hint and whether spoken replies are on |
recentErrors | the last 20 errors the panel hit (what kind, a short message with any email address, token or long number removed, the screen and step), so a problem report can include them |
cartRun, prepcartCartKept | the cart run in progress (so it can carry on), and the products you chose to "Keep it as is" at the end of this week's run (so you're not asked again); the latter holds this week only |
imports | the recipes and shopping list you added for this week (the recipe as it was read out of your photo, text or link, never the original file); cleared with the week, and the recipes stay in your library until you delete them |
orderPlaced | whether the store's order-confirmation page was seen, for which store and when (see "The order-confirmation page" below) |
Signing in on the website sets one cookie, pc_session, holding your session; it is HttpOnly and lasts 90 days or until you sign out. If you correct the country the website guessed ("Not in Australia? Change"), a second cookie, pc_country, remembers your choice for a year; it holds only a country code. The website also keeps one value in localStorage, pc_consent: whether you accepted, dismissed or declined the cookie banner or notice (see Meta, below).
On the PrepCart server (Postgres on Vercel; the schema is in server/sql/):
| Table | What | Why |
|---|---|---|
users | email address, first name, country, timezone, email preferences, your Google account id (sub) if you sign in with Google, the link you signed up through if it carried a ?ref= label (e.g. "ozbargain"), and onboarding_prefill: if you arrived from the macro calculator, the targets and stats you typed there (goal, sex, age, height, weight, activity, training days), so onboarding can start from them | sign-in, pricing by country, cook-day emails at the right hour |
households, household_members | who shares a plan: the owner, the one other adult they invited, and the brand the household bought from | one subscription, two sign-ins; the brand drives theme, tone and emails |
subscriptions | Stripe customer and subscription ids, status, currency, renewal date | the paywall; no card numbers ever reach PrepCart |
founding_spots | for the first 200 Australian sign-ups (founding members, A$10 a month): the spot number, first name, email, household, the link it came from (a ?ref= label such as "ozbargain"), and when it was held, paid, ended or refunded | to keep the founding-member count true and to give a returning founder the normal price |
household_profiles | your household profile as the extension keeps it once onboarding has finished: each person's name, age, sex, height, weight, activity, goal, how strict they are, allergies and foods to avoid, what they eat outside the plan, breakfast and snack choices, cooking equipment, the meal prep schedule and any changes for a particular week, the store you shop at, your saved recipes, what you love to eat and how much cost matters to you (keep an eye on it, somewhere in the middle, not much, or a weekly number you gave, and a week you asked us to bring closer to it), what you usually pick on the shelf, the products you always buy and what PrepCart has learned you like when it shops (removable one by one, or all at once, in Settings); never email addresses; one row per household, replaced on every change | so a returning household opens on "Same as usual this week?" instead of starting again, on a new computer or after reinstalling the extension; both adults in the household share it |
plans | the week's plan, one row per household and week: the recipes, cook sessions and schedule, the shopping list, the weekly budget and currency, whether there are kids, each adult's daily calorie and protein target, and the portions: each person's name, how strict they are, serves and grams per meal, breakfast and snack extras, top-ups and what they eat outside the plan | the proposal and cook-day emails, and the portions the extension shows |
email_log | which email went to whom, for which plan and session | so nothing is sent twice |
login_codes, sessions | hashed sign-in codes (with the install id that asked), hashed session tokens | sign-in without passwords |
invites, invite_log | the invited address, their first name and which person in the plan they are, the hashed invitation code, when it was sent and how many times; invite_log keeps a count of invitation emails per household for the last 30 days | the one invitation each account can send, and the cap on invitation emails |
google_signins | email, install id and time of each Google sign-in | rate-limiting sign-ins |
stripe_events, resend_events | Stripe and Resend event ids | so a retried webhook is a no-op |
waitlist | if you join the waitlist (where PrepCart isn't open yet): your email, the country you chose, the time you ticked "Email me when PrepCart launches in my country", the page you were on, the brand, and whether you unsubscribed | one confirmation email now and one email when PrepCart opens in your country, nothing else; the link in either takes you off the list. Never sent to Meta or anyone else |
trials | if you start a free trial on a partner offer: a one-way hash of your email (lower case, without a +tag or Gmail dots) and of the card fingerprint Stripe gives us, the subscription id, the link it came from, and the time; never the email, the card or its fingerprint | one free trial per person; kept after an account is deleted so a trial can't be taken twice |
billing_reviews | a note, with the email, when a card's country differs from the price charged | a human looks; nothing is cancelled automatically |
cart_spend | for a signed-in household, one row per finished cart run: the store, the week, how many people and planned meals, your cost answer, PrepCart's estimate, the store's cart total and item count, the total of cart items that weren't on the list (an amount only), and for each list line its name, amount, the product chosen, pack size, packs, price, whether it went in, the recipes it came from, and what the week needed, what was bought and left over and why that product; and whether the order was placed and when (see "The order-confirmation page" below); never names, emails or addresses | to make the estimate and the list quantities accurate, and to see what households typically spend; the founders' view shows medians only, by household size and cost answer, with any group under three runs hidden; never shared or sold |
cart_runs | your household's current cart run: the store, which step it is up to, each item's name and whether it is in the cart yet, start and update times; replaced by the next run | so a run that was interrupted can carry on where it stopped |
reports | a problem you report from the panel ("Report a problem"): what you wrote, who sent it (so we can reply), and, if you leave "Include technical details" ticked, the extension version, the store, the screen and step, the last 20 errors, the cart run's summary (the list lines and the products chosen) and the plan's id; never passwords, payment details, addresses, cookies or tokens. You can see exactly what's included before sending. Each report is also emailed to support@getprepcart.com | to fix what went wrong and reply to you; kept 90 days |
error_groups, error_events, error_alerts | errors the extension and the server hit, counted: the kind of error, a short message and stack with any email address, token or long number removed, the extension version, the store, the screen and step, a page-element name when a store's page has changed, and a one-way hash of the extension's random install id; no name, email, household, page content or anything you typed | to find and fix bugs, and to notice quickly when a supermarket changes its site; kept 90 days |
cart_corrections | each "Add N more", "Reduce to N", "Keep it as is" or Swap tap at the end of a cart run: the store, the ingredient, the plan's amount, what was in the cart and what it became, and the product names; no household, person or email | to fix the quantities and products people keep correcting; the founders see a ranking by ingredient |
recipe_library | the recipes you added from a photo, a PDF, pasted or spoken text or a link, and recipes you saved from a plan: each one's name, ingredients, method, serves and tags, and its source (the link if there was one, otherwise just "photo", "PDF" or "text"); never the photo, PDF or text itself; you can delete a recipe from My recipes, and Delete my account removes them all | so a recipe you added is there again in later weeks |
demand_events | the anonymous usage log (see "The anonymous usage log" below): an event name, coarse details from a fixed list and a time; no household, account or person | to learn what households keep, swap, skip and can't get, and to improve plans and product matches; kept 24 months |
unknown_ingredients | recipe ingredient names the ingredient database doesn't know yet, how often plans used them and one recipe they appeared in; no household or person | so the database grows; nothing about an unknown ingredient is guessed |
product_matches | for each store and search term, which product was chosen and how often it was swapped; no household | better product matches over time |
recipe_feedback | when a recipe is swapped or kept: a fingerprint and name of the recipe, the household's profile tags (such as "vegetarian" or "no fish"), the reason you gave, the brand and the household id | better recipes over time |
store_runs, store_health | anonymous cart-run outcomes: store, config version, step, ok or not, the failing selector key; no user, product or account data | to notice when a supermarket changes its site and show you the list instead |
store_diagnostics | sanitised Diagnostics captures you choose to send (page structure, product names, prices and sizes only; never account, cart or Rewards data), kept while a store is failing | so the selectors can be fixed quickly |
recipes | the public recipe library on the website; no user data | the recipe pages |
email_suppressions | a hash of each address that bounced, complained, or asked not to be invited, with the reason and time; never the address itself | so we never email it again |
quality_runs, quality_profiles | the founders' test runs of the planner on made-up households; the id of the founder who started one | checking plan quality; no customer data |
Sign-in codes, session tokens and invitation codes are stored only as salted SHA-256 hashes. Codes expire after 10 minutes and allow 5 attempts.
Not stored on the server: your chat, voice audio (see "Voice" below), the photos, PDFs and text of recipes you add (read, then discarded), your supermarket credentials or anything from your supermarket account. From your supermarket cart, only the spend record above (the cart's total and item count at the end of a run, and the products PrepCart added).
Who else sees data
- Anthropic (Claude) is the AI PrepCart uses. It is sent only what each use below needs. We do not send your email address, and we do not send names except a first name you type yourself into a chat or a week's note. These are all its uses:
- Planning: your setup conversation, the note you add to a week, the household as ages, goals, diet and foods to avoid, and the week's dishes, to plan the week, write the recipes and their methods, and swap a recipe when you ask. - The basket check: before your cart is filled, the approved shopping order (each line's ingredient, amount and recipes) and the store's real products for it (names, sizes and prices), with your shopping preferences in plain words, to choose the right pack for each line. - The week manager: before shopping, the whole week, the household as above and the shopping order; after the cart is filled, what the store's cart holds against the order, what couldn't be found and the store's notes. It suggests edits and fixes, each checked by code, and none is applied until you tick it. - Recipe imports: the photo, PDF, pasted or spoken text, or recipe page you add, to read the recipe out of it (see "Adding recipes" below). - Chat with your shopper: the one-line message you type during a cart run. It is not stored or logged. - Product names: a store product PrepCart can't place is described once (what food it is and in what form) from its name and size only, and the answer is shared. - Dish pictures and card lines: a recipe's name and a stock photo's description, or a short line about a published dish; nothing about you. Keys live only in the server's environment.
- Pexels and Unsplash (free stock photo libraries), when the operator has turned dish photos on (
PEXELS_API_KEY,UNSPLASH_ACCESS_KEY): PrepCart searches them with a recipe's name or its main ingredient ("chicken curry"), never anything about you or your household, and each photo is found once and reused for everyone. Pexels photos are served from PrepCart's own site. Unsplash photos load straight from Unsplash, as Unsplash requires, so when you view one (in an email or on a recipe card page) your email app or browser asks Unsplash for it and Unsplash sees the usual details of that request (your IP address and browser). Anthropic (above) sees the recipe's name and the photos' library descriptions, to check a photo shows the dish. - Google, if you choose Continue with Google: Google tells PrepCart your verified email address, your name and a Google account id, nothing else; PrepCart never receives a Google access token and cannot read anything in your Google account.
- Stripe handles payment. PrepCart receives the customer id, subscription status and currency, never card details. Stripe's customer portal (Manage billing on your account page) is where you update your card, see invoices and cancel.
- Resend sends the emails: sign-in codes, invitations, the welcome email after you pay, the weekly proposal, cook-day recipes and the waitlist confirmation. Resend tells us when an email bounces or is marked as spam, and we stop emailing that address.
- Meta (Facebook and Instagram ads): the website uses the Meta Pixel for advertising measurement, to see which ads bring people to PrepCart and whether they go on to sign up. It records which page was viewed, a recipe or calculator view, a click to install PrepCart or to sign up (not counted while you're signed in with an active subscription: our server checks that from your sign-in, and nothing about it goes to Meta), joining the waitlist (the fact that the form was sent, not what was in it), starting checkout (the price and currency shown, nothing you typed), and an account being created and a subscription starting after you pay. The pixel sets Meta's own cookies in your browser, and Meta sees your IP address and browser details as with any web request. No email, name, phone number, address, plan, chat or household data, and no PrepCart account or customer id, is ever sent to Meta, hashed or otherwise, from the browser or from our server: our server never contacts Meta at all. The extension, your account page and the admin pages never load the pixel.
- In the UK, the EU and the EEA (and whenever we can't tell where you are), the pixel runs only if you click Accept on the cookie banner. Until then nothing from Meta loads. - Everywhere else (including Australia and New Zealand), the pixel runs by default and a small notice says so. - To opt out, click Decline on the banner or notice, or "Cookie settings" in the footer and then Decline. The pixel stops at once and won't load again in that browser. Your choice is kept in your browser, so clearing site data or using another browser asks again. You can also limit ad tracking in your Meta account's ad settings.
- Woolworths and Coles: the cart feature acts in your own signed-in tab, at human pace, and never touches checkout, payment, address or account settings. PrepCart's server never visits a supermarket site.
The order-confirmation page
Once you have allowed PrepCart on woolworths.com.au (Chrome asks the first time you fill a Woolworths cart), the extension can see the address and the title of your Woolworths tabs, as Chrome reports them. It uses that for one thing: noticing when a tab reaches Woolworths' own order-confirmation page, which is the only sign that you placed the order PrepCart filled. When it does, it sends PrepCart's server the name of the store and nothing else (not the address, not the title, nothing on the page), once for each tab and page, signed in as you. The server marks your last cart run at that store as placed, with the time, so that what was left over from it can carry into next week's plan. The extension does not open, read, click or change anything on that page, keeps no list of the pages you visit and sends nothing for any other page. Today this is wired to Woolworths only. It is why PrepCart's answer to Chrome's "Web history" question is no: no browsing history is collected, only this one store-name signal.
Adding recipes
When you add a recipe from a photo, a PDF, pasted or spoken text, or a link, the extension sends it to PrepCart's server, which reads the recipe out of it using Anthropic's AI (for a link, the server opens that public web page itself). The photo, PDF or text is read in the server's memory and then discarded: it is not kept, not logged and not stored. What is kept is the recipe that was read out of it (its name, ingredients, method and serves, and the link if there was one) in your household's recipe library, so it is there again in later weeks. Delete a recipe from My recipes, or delete your account, and it is gone.
The anonymous usage log
Unless you switch it off in Settings ("Share anonymous usage to improve PrepCart"), the extension sends short events about what households do with a plan: a meal kept, swapped or skipped, a line approved, edited or removed, a product confirmed or out of stock, a cart completed. Each event carries only coarse details from a fixed list: the store, whether the household is solo, a couple or a family, the week, the meal type, a recipe, ingredient or product name as a short word, a reason from a fixed list, or a count. The server keeps only those fields. Names, emails, addresses, chat text, notes, health details and anything that looks like an email address, a phone number or a street address are dropped before anything is written, and no household id, account or person goes with an event, so an event cannot be traced back to you. It is used to learn what households keep and what is hard to get, and so to improve plans and product matches. The raw events are deleted after 24 months. Switch it off and nothing is sent; the server also honours the setting from your saved profile.
Voice
The microphone button uses Chrome's own speech recognition. Chrome, not PrepCart, may send what you say to Google's speech service to turn it into text, under Chrome's and Google's terms. PrepCart receives only the text, which is treated as if you had typed it, and never receives or stores the audio. Chrome asks once for permission to use the microphone.
Logs
Server logs record durations, status codes and error types. Errors are also counted in our own error table (above); we don't use any outside error-tracking service. They never contain email bodies, sign-in codes, tokens, API keys or your messages.
Emails
Every email names the sender and links to a settings page where you can turn emails off without signing in. Approving a week, in the extension or from the email, sends all its recipes in one email, then each meal prep's recipes at the time you chose. Turning emails off stops the weekly proposal, the recipes and the cook-day emails; sign-in codes still arrive when you ask for one. An address that bounces or marks us as spam is put on the suppression list (hashed) and gets nothing more, sign-in codes included; the account page says so and how to reach us.
Recipe cards. The cook-day and all-recipes emails, and the extension's recipe view, link to that meal prep's recipe cards on getprepcart.com (/cook/<link>). The link is signed, needs no sign-in and stops working after six weeks; anyone you forward it to can read those recipes (names, ingredients, steps and serves; no people's names, targets or email addresses). The page remembers which steps and ingredients you ticked in your own browser (localStorage) and keeps a copy of the page for offline use (a service worker cache); neither is sent to PrepCart. The cook-day email attaches the same cards as PNG images.
Deleting your data
Settings → Start over clears without closing the account: Re-plan this week deletes this week's plan and the cart run (the household profile stays); Start fresh deletes the household profile, every plan and the cart run, on the server and in the browser, and the subscription and sign-in stay as they are.
Settings → Delete my account removes your user record, sessions, codes and invitations. For a household owner it also removes the household, its household profile, its plans, the cart run, its spend records, its recipe library, its problem reports, the email log and cancels the Stripe subscription (a founding-member spot keeps its number, so the count of 200 stays true, but its name, email and household are removed); the other adult loses access at the same time. The browser copy is cleared by removing the extension (or from Settings on delete). Product-match, recipe-feedback, correction and unknown-ingredient rows carry no name, email or household and stay.