DRAFT, pending legal review. Not yet in force. Version 2026-11-04-draft2 · Effective date: [EFFECTIVE DATE]
Misenplease Privacy Policy
This policy explains what personal data Misenplease collects, why, how long we keep it, who we share it with, and your rights. It applies to the Misenplease app and the services behind it.
1. Who is responsible
The controller of your personal data is [COMPANY LEGAL NAME], [ORG. NO.], [ADDRESS] ("Misenplease", "we"). Privacy contact: privacy@misenplease.app · General support: support@misenplease.app.
2. What we collect
Account
- Email address, and your name if you give one.
- A password, stored only as a one-way hash.
- If you sign in with Google or Apple: the identifier they give us for your account (for Apple, possibly a private relay email address).
- Technical sign-in data: refresh tokens (stored hashed) and password-reset tokens (stored hashed, valid for 30 minutes).
- Your role (user or admin), your account status and your preview counter.
- Which version of these terms and this policy you accepted, and when. Whether, and when, you gave consent to health-related data (section 4).
Household and people. For each person you add:
- Adults: name, age, sex (optional), height, weight, activity level and goal (for example lose, gain or maintain weight). Optional calorie and macro overrides. Diet choices (for example vegan, vegetarian, pescatarian, gluten-free, dairy-free, nut-free, halal). Favourite cuisines, foods they dislike, number of meals and snacks, cooking-time preferences, weekly budget and grocery spend, preferred grocery chain, and batch-cooking preference.
- Children (about 4 months to 6 years): name, birth month (not the full date of birth), feeding mode (for example breast milk or formula), foods they dislike, allergen-introduction status per allergen (not yet tried, introduced, or paused after a possible reaction), and the planned dates for first tastes of allergens.
What you do in the app
- Generated meal plans and the meals in them, including adaptations for children and daycare days.
- Shopping lists and items.
- Freezer contents: batches, portions and dates.
- Favourite recipes, likes and dislikes of recipes, and which full recipes you have opened.
- Subscription status: free, trial, active or expired, and when it ends. Once in-app purchases are live, also the store's subscription identifiers. We never receive your card details; Apple and Google handle payment.
Guests (before sign-up)
- A random device identifier generated by the app (
X-Device-Id). It counts free recipe opens and limits misuse of the preview. - When you create an account, your opens are linked to the account.
Location
- With your permission, the app uses your device's approximate location on your device to suggest your country and nearby stores.
- Your phone's operating system (Apple or Google) turns the coordinates into a country.
- We do not store your coordinates on our servers. We store only the country and store chain you choose.
Technical data
- When you use the app, our servers receive standard technical data: IP address, device and app version, and request times.
- We use it to run, protect and debug the service.
- Server logs are kept for [LOG RETENTION, e.g. 30 days].
What we do not do
- We do not sell your personal data.
- We do not show third-party advertising.
- We do not build advertising profiles.
- We use no analytics tools. Our servers send crash reports to Sentry (see section 6), without names, email addresses or health data. If we add any other tool (for example for anonymous usage statistics), we will list it here first.
3. Why we use it, and on what legal basis
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Creating and running your account, signing you in | Account data | Contract (Art. 6(1)(b)) |
| Planning meals, portions, child adaptations, shopping lists, freezer and prices | Household, people and activity data | Contract (Art. 6(1)(b)); explicit consent (Art. 9(2)(a)) for diet choices and children's allergen statuses, see section 4 |
| Subscriptions and access control | Subscription data | Contract (Art. 6(1)(b)) |
| Free-use limits and abuse prevention (guests and accounts) | Device ID, preview counter, recipe opens; after you delete an account that used the free trial, a coded record (keyed hash) of its email address and Apple or Google sign-in ID | Legitimate interest (Art. 6(1)(f)) in a fair free tier and protecting the service: the free trial is once per person, not once per account |
| Security, debugging, keeping the service running | Technical data, logs | Legitimate interest (Art. 6(1)(f)) |
| Service emails (password reset, important changes) | Contract (Art. 6(1)(b)) | |
| Keeping records of which terms you accepted, and of your consents | Acceptance and consent records | Legal obligation and legitimate interest (Art. 6(1)(c), (f)) |
| Bookkeeping, if required for payments we receive directly | Transaction records | Legal obligation (Art. 6(1)(c)) |
4. Health-related data and your consent
Some information you give Misenplease is about health:
- diet choices for the people in your household (for example nut-free, gluten-free, dairy-free, vegetarian or halal-friendly);
- a child's allergen statuses, especially an allergen paused after a reaction.
We use this information only to plan safe and suitable meals for your household.
Diet choices and children's allergen statuses. We ask for your explicit consent before you first enter them. You give it once for your household, also on behalf of the children you add. You can withdraw it at any time in the app (Account → Health information).
If you withdraw consent:
- we delete the diet choices and children's allergen statuses stored for your household;
- Misenplease stops using them.
Important: without that information, Misenplease can no longer avoid foods your household must not eat, and it can no longer keep a paused allergen out of your child's plan.
Weight and height. Misenplease uses adults' weight and height only to calculate their calorie and nutrition targets, as part of planning their meals. They don't need the consent above. You can change them at any time, or enter your own targets instead.
Planned first tastes. The dates you plan for a child's first tastes of allergens are a schedule, not information about the child's health, so they don't need the consent above.
5. Children
You must be at least 16 to create a Misenplease account. Children in a household do not have accounts. Information about a child is entered by their parent or guardian, who decides what to enter and can change or delete it at any time. We use it only to plan the child's meals.
6. Who we share data with
We use these service providers (processors), bound by data-processing agreements, only to provide Misenplease:
| Provider | What for | Where |
|---|---|---|
| [HOSTING PROVIDER — UpCloud Ltd, planned] | Servers and database | EU (Stockholm, Sweden) |
| Google (Google Sign-In; Google Play) | Sign-in, app distribution and billing (Android) | EU/US, see Google's terms |
| Apple (Sign in with Apple; App Store) | Sign-in, app distribution and billing (iOS) | EU/US, see Apple's terms |
| [EMAIL PROVIDER — Resend or Postmark] | Sending service emails | [EU/US — to confirm] |
| RevenueCat (planned, before launch) | Managing in-app subscription status | US |
| Functional Software, Inc. (Sentry) | Crash reports from our servers, without names, email addresses or health data | EU (Frankfurt, Germany) [FOR LEGAL REVIEW: DPA and SCCs, as Sentry is a US company] |
| ngrok (test phase only) | Secure tunnel to our test server during testing | [EU/US — to confirm] |
We also use Replicate and OpenAI to create recipe illustrations. No personal data is sent to them.
Where a provider processes data outside the EU/EEA, we rely on safeguards: an adequacy decision (for example the EU–US Data Privacy Framework for certified companies) or the EU Standard Contractual Clauses. [FOR LEGAL REVIEW: confirm per provider.]
We share price searches with grocery retailers' public websites and apps only as generic product searches (for example "milk"). They contain no information about you.
We may disclose data if the law requires it, or to protect rights and safety.
7. How long we keep data
| Data | How long |
|---|---|
| Account and household data | As long as your account exists. Deleting your account in the app deletes it immediately from our live database, except the two records in the next rows. |
| Record that a free trial was used | If the deleted account used the free trial: a keyed hash of its email address and sign-in IDs, kept [RETENTION FOR TRIAL RECORDS, proposed 24 months] so the same person is not given a second trial. The hash cannot be turned back into your email address. |
| Backups | Until they expire, at most 14 days. |
| Refresh tokens | Expire after 60 days, or earlier when you sign out. |
| Password-reset tokens | Expire after 30 minutes. |
| Guest device ID and its recipe opens | [RETENTION FOR GUEST DATA — e.g. 12 months of inactivity]. When you delete your account, the recipe opens and free preview made on your device stay with the device, no longer linked to you. |
| Server logs | [LOG RETENTION, e.g. 30 days] |
| Records of accepted terms and consents | As long as the account exists, plus [PERIOD] where needed to show compliance |
Deleting your account does not cancel a store subscription. Apple or Google keep their own purchase records under their privacy policies. We also ask our billing processor (RevenueCat) to delete its record of you.
8. Your rights
You have the right to:
- access your data, and get a copy: the app can download everything stored about your account as one machine-readable (JSON) file;
- rectification: most data you can correct yourself in the app;
- erasure: delete your account in the app (Account → Delete account), or contact us;
- restriction of processing, and to object to processing based on legitimate interest;
- data portability for data you gave us under contract or consent;
- withdraw consent at any time (Account → Health information). This does not affect processing that happened before you withdrew.
To use these rights, contact privacy@misenplease.app. We answer within one month.
You can also complain to a data protection authority, for example:
- Sweden: Integritetsskyddsmyndigheten (IMY), imy.se
- Norway: Datatilsynet, datatilsynet.no
- Denmark: Datatilsynet, datatilsynet.dk
- Finland: Tietosuojavaltuutetun toimisto, tietosuoja.fi
- Netherlands: Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl
9. Security
- Data travels encrypted (HTTPS).
- Passwords and tokens are stored only as hashes.
- Access to production systems is restricted.
- The database is not reachable from the internet.
- No system is perfectly secure. If a breach is likely to put your rights at risk, we will notify you and the authorities as the law requires.
10. Changes to this policy
We will tell you in the app before material changes take effect. Where the law requires it, we will ask for your consent or acceptance again. The version and effective date are shown at the top.
11. Contact
[COMPANY LEGAL NAME] · [ADDRESS] · privacy@misenplease.app