What we store
An anonymous id. You can use mealprep without an account. The first time you generate, save, or subscribe, we set a random id in a cookie ("mp_uid") so your plan is still yours when you come back. Just browsing sets nothing.
Your food preferences. Diet type, allergies, calorie/macro targets, equipment, and cuisines — stored in your browser, and on your account too if you sign in (so they follow you across devices).
Your plans and saves. Generated weekly plans (we keep your 5 most recent, plus up to 5 you've pinned — older ones are deleted automatically) and recipes you've bookmarked. The recipes themselves are public content from recipe publishers, not personal data.
Services we use
Clerk handles sign-in if you create an account (your email, name, and login credentials live there, not in our database).
Stripe processes subscription payments. Your card details go directly to Stripe and never touch our servers — we store only a reference to your Stripe customer record and your subscription's status.
Edamam is where recipe search results come from. Your search is defined by your food preferences; no identity is sent with it.
PostHog may collect anonymous usage analytics (which pages are visited, whether a plan gets generated) to help us understand what's working.
Your data, your call
Both of these live on the account page and work with or without an account:
Export — download everything we store about you as one JSON file.
Delete — permanently erase all of it: plans, saves, preferences, your account if you have one, and your billing relationship (any active subscription is cancelled immediately). Stripe retains its own transaction records as required by financial regulations.
Contact
Questions about your data: pokebattler@outlook.com.