Back to home page

Wersja polska

Amamable Privacy Policy

1. General provisions

This policy sets out how the data of users of the “Amamable” mobile application (the “App”) and of the amamable.com website (the “Website”) is processed.

The data controller is Grzegorz Szwed Development, ul. Twarda 18, 00-105 Warsaw, Poland, VAT ID (NIP): 5223280335, contact e-mail: info@amamable.com (the “Controller”).

2. Scope of the data processed

Depending on how the App is used, we may process the following data:

Account data:

• e-mail address (when registering by e-mail or signing in with Google/Apple),
• user name (set to the e-mail address by default; it can be changed),
• password — stored only in hashed form; when signing in with Google or Apple we store no password at all.

Profile data and dietary preferences:

• the number of people in the household,
• selected allergens and dietary preferences — provided voluntarily and used solely to filter recipes and build the meal plan,
• the App language,
• a profile photo and a short description (bio) on your author profile — provided voluntarily. Other App users can see them on your author profile, and the photo also next to recipes you publish. We store them together with your other data (section 7); you can change or remove them at any time in the App (Settings → Author profile), and we also delete them when you delete your account. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR) — providing the author profile feature, which you use voluntarily.

Data for calculating calorie requirements (optional):

• year of birth, sex, height, activity level and a daily calorie requirement entered by hand — your own only; for people without an account whom you add to your household (e.g. children) we store only the name you give, never their body data or calorie requirement, and each such person counts as one serving of the recipe,
• your weight — not a single value, but a history of measurements over time: every saved measurement has a date and a value, and the newest measurement is also your current weight, used for the calculations described below,
• who a planned meal is for (household members and number of guests).

This data may constitute data concerning health, so we process it only on the basis of your explicit consent (Art. 9(2)(a) GDPR), given in the App before it is first saved; we record the date and the version of the consent text you agreed to. The consent covers two purposes: (1) calculating a daily calorie requirement and comparing it with the calories of planned meals — a display-only view of the day's target, described below under “How we calculate calories” — and (2) recalculating the ingredient quantities of the dishes in the plan and the shopping list to match that requirement (same section, below); neither purpose is used for profiling, advertising or training AI models. Each family member enters this data only on their own account and gives consent personally; no one — including the family owner — can enter it on behalf of another person. Other members of your family see your calculated or entered calorie requirement in the App, but not your body data; the name of a person without an account can be seen and edited by all family members. You can withdraw your consent at any time in the App (Settings → Household & calories) — withdrawal deletes your body data, including your whole weight-measurement history, and any calorie requirement you entered by hand, restores a single serving for you in planned days from tomorrow (the same as when there is no requirement), and does not affect the lawfulness of processing before withdrawal. When we change the text of this consent — as with adding the second purpose described above — consent given under the earlier text stops covering the new purpose; we then ask for consent again, and until it is confirmed the data serves only the previous, narrower purpose. Body data and calorie requirements of people without an account that were stored in the App before this version of the privacy policy was introduced have been deleted.

How we calculate calories (algorithms):

All the calculations described below are deterministic — the same data always gives the same result — and do not use artificial intelligence models.

• Recipe calories and macronutrients are calculated on our server from the recipe’s ingredients. For each ingredient we take the average of the product label data for that ingredient collected in our database or, if there is none, a reference value from the public USDA FoodData Central or Open Food Facts databases. An AI model helps us match reference values to ingredients, but only outside the App (offline), and a human reviews and approves every value before it is used. Quantities in kitchen measures (e.g. a tablespoon, a piece) are converted to grams using conversion factors for the given ingredient (liquids without a factor: 1 ml = 1 g), solely for this calculation. An ingredient with no data or no conversion factor is left out — never counted as zero. We show the result only when the included ingredients make up at least 60% of the mass of the ingredients that could be converted to grams and are not fewer than those left out; otherwise the recipe is marked “no data”. Values entered by hand on the recipe always take precedence over calculated ones.
• The daily calorie requirement is calculated on our server from year of birth, sex, height, weight and activity level. Age is the current year minus the year of birth. For people aged 19 or over we use the Mifflin-St Jeor formula multiplied by an activity factor (from 1.2 for a sedentary lifestyle to 1.9 for very high activity). For people under 19 we use the Estimated Energy Requirement (EER) equations for children and adolescents published by the US Institute of Medicine (2005) — they take into account age, sex, weight, height and activity, and for children under 3 only weight. The result is rounded to 10 kcal. A requirement entered by hand always takes precedence over the calculation; if any of these data is missing, we assume 2000 kcal. We count the same for every guest and every person without an account.
• The day target in the plan is the sum of the requirements of the people eating that day’s meals (each person counted once) plus 2000 kcal for each guest. The App compares it with the calories of the planned meals (number of servings × calories per serving) and displays the result purely as a comparison view in the plan — a different mechanism from the ingredient recalculation described below, and it does not affect quantities.
• Recalculating ingredient quantities and the shopping list — when a meal includes people with a calculable or manually entered calorie requirement, the meal's budget is the sum of their requirements multiplied by that meal's share of the day. All dishes of that meal on a given day get a shared multiplier (the meal budget divided by the sum of the calories of one serving of each dish, multiplied by the number of people with a requirement), so that together they match the budget while the proportions between dishes stay as in the recipes; the multiplier is kept within the 0.5–2 range, and is clamped outside it, in which case the day may miss its target. A person without a calculable requirement (including every person without an account) and every guest each count as one serving of the recipe, regardless of the multiplier; the same applies when consent is missing or withdrawn, as described above. Whether a person's requirement is taken into account depends on the consent given on that person's own account — also when another family member plans the meal. A recipe without reliably calculated calories (see above) stays in the quantities written in the recipe and is not recalculated. Ingredient quantities also affect the generated shopping list. The recalculation happens automatically, without any extra action from you, when a dish is added, a plan is generated, a meal plan is inserted, or when the eaters, guests, time of day or a household member's requirement changes.

This is not automated decision-making within the meaning of Art. 22 GDPR. The calculations above — the day target view and the ingredient recalculation — are estimates and calculations that support the function you yourself request in the App (building the plan and shopping list), based on a transparent, deterministic algorithm described above, including fixed multiplier bounds (0.5–2). They do not decide your access to any service nor your legal or financial situation: you set the number of eaters and guests for each meal yourself, and you can review and change the generated plan and shopping list in the App at any time before you shop. For that reason, we consider that they do not produce legal effects concerning you or similarly significantly affect you. We do not use them to profile you for marketing, do not use them for advertising and do not share body data or calorie requirements with third parties — they are stored only by our hosting provider (Microsoft Azure, section 9), acting on our behalf. The legal basis remains your explicit consent described above, and withdrawing it deletes this data.

Content created in the App:

• recipes (names, ingredients, preparation steps, optional photos of dishes),
• meal plans (the calendar),
• shopping lists, including the e-mail addresses of people a list is shared with.

Shopping agent data (a premium feature):

• the names of the shopping list items the agent is run for, and the outcome of each one (added / not found / skipped),
• a simplified snapshot of the store page open in the App — processed on the fly to decide the next click,
• the remembered “list item = store product” match for your account and that store.

Section 5 covers the detail. We neither receive nor store your store login, password or cookies.

Cooking mode:

Step-by-step guidance through a recipe, together with the timer, runs entirely on your device and collects no data — see section 6.

Technical and diagnostic data:

• the version of the operating system and of the App,
• anonymized usage events (e.g. opening a screen) and error logs — used solely to improve stability and usability.

Signing in with Google and Apple:

If you sign in with a Google or Apple account, all we receive from those providers is your e-mail address and a confirmation of identity (a token). We get no access to your contacts, files or any other data held in those accounts. How Google and Apple process data is governed by their own privacy policies.

Feedback submission content and subscription cancellation reason:

The content of a feedback submission you send us in the App or on the Website (an idea, a bug report, praise), together with its context (screen, moment), platform, App version, language and the optional consent to a reply by e-mail, is personal data; its content may include sensitive data if you include it yourself. Only the Administrator has access to submission content (the admin panel), and we delete it together with your account (section 8). If you give consent to a reply by e-mail, we reply to your e-mail address as account-service correspondence related to the submission — independent of marketing consent (section 11) and without adding your address to the newsletter list. If you cancel a paid subscription through Google Play, the App Store or Stripe and state a cancellation reason in that payment provider's own form, we receive that reason from the provider (the Google Play cancellation survey, the Stripe feedback field, or Apple's system code) and record it in the same submissions module, to better understand why people leave.

Reason for cancelling a subscription (optional):

When you cancel your premium subscription, the next time you open the App or the web client we may ask you why — you choose one of a closed set of codes (e.g. “too expensive”, “I rarely use it”) and can optionally add free text of up to 500 characters. Answering is entirely voluntary — the question can always be skipped without giving a reason, and this has no effect on the cancellation itself, which happens in the App Store, Google Play or the Stripe portal. The saved reason code and free text are used solely to improve the product and the offer (to understand why users cancel) — we do not use them for profiling or advertising. We store them together with your other account data (section 7) and delete them when you delete your account.

3. Purposes of processing

We process data for the following purposes:

• creating and running your user account in the App;
• storing recipes, building meal plans and generating shopping lists — on the basis of the data you enter (the App runs on deterministic algorithms; user content is not used to train artificial intelligence models);
• sharing shopping lists with the people you choose;
• running the shopping agent — deciding the next action on the store page, remembering “list item = product” matches and accounting for the monthly pool of items (section 5);
• improving the operation and security of the App (logs, telemetry, error reporting), including the success rate of the shopping agent on the basis of a run log that carries no user identifier;
• handling user requests and communication related to the App;
• contacting you about developing the App (an e-mail survey now and then, or a short phone call) — only with your separate consent (section 11);
• meeting the Controller's legal obligations.

The legal basis for processing is, as applicable: necessity for the performance of a contract (Art. 6(1)(b) GDPR), the Controller's legitimate interest (Art. 6(1)(f) GDPR) or the user's consent (Art. 6(1)(a) GDPR). Data for calculating calorie requirements is processed only on the basis of explicit consent (Art. 9(2)(a) GDPR).

If you report a forgotten password, we send a one-time password-reset link to your e-mail address — this is account-service mail, necessary for the performance of the contract (Art. 6(1)(b) GDPR), independent of marketing consent (section 11) and sent regardless of its state. We send it through Brevo (section 9), which acts as our processor for this purpose only — your address is not added to the newsletter list because of it.

4. The App's access to the camera, photo library and location

The App may ask for camera permission (android.permission.CAMERA) and access to the photo library only when you choose one of the features below yourself. Using them is entirely optional.

• Recipe photo — you add it to your recipe and we display it alongside that recipe.
• Profile photo — we display it on your author profile (section 2).
• Recipe import from a photo — we send the photo of a recipe page or of a dish through our server to an AI model (Microsoft’s Azure OpenAI service, section 9), which reads the recipe from it. In the mobile app, the same photo is then saved as the photo of the newly created recipe — you can remove it like any other recipe photo.
• Quick inventory — we send the photo of your fridge or cupboard through our server to an AI model (Azure OpenAI), which returns a list of the products visible in it. The photo serves only that one request: we store neither the photo nor the recognised product list — the list exists only on the App’s screen, and your activity history records just the number of products recognised.

Import from a photo and quick inventory also draw on a free pool of 10 AI calls per account (without premium) — to account for it, we record only the fact of a successful call (feature, source, date), never the photo’s content or the recognised product list. This record is deleted together with the account.

Photos are not used for biometric identification. The AI model receives a photo only to read a recipe or products from it; the content passed on is not used to train models.

You can withdraw the permissions at any time in your device’s system settings — the only effect is that these features can no longer use the camera or photo library.

Location and the recipe map — in the App and in the web app on the Website (/app) you can open a map of the recipes you saved from Google Maps links. The location permission (on Android android.permission.ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION, on iOS “while using the app”, in a browser — consent to share your location) is optional, and the App asks for it only when you choose “Share location” on the map. Your position is used only on your device — to centre the map and work out the distance to your recipes. Amamable does not store it and does not send it to its server or to analytics tools. With a recipe we store only the coordinates of the place, read from the Google Maps link you added to it yourself. The map is provided by Google Maps (Google Ireland Limited): to display the map, your device downloads map tiles from Google’s servers, so Google receives the technical data of those requests (including your IP address and the area of the map you are viewing — once the map is centred on you, also the approximate area you are in) and processes it under the Google Privacy Policy. Without location consent the map and the “Nearby” list keep working — distances are then measured from the centre of the map. You can withdraw consent in your device’s system settings or in your browser.

5. The shopping agent

The shopping agent (a premium feature) adds the items of your shopping list to the basket of a supported online grocery store. The store opens in a browser window inside the App, in your own session — you sign in directly with the retailer, and Amamable neither receives nor stores your store login, password or cookies.

To decide the next click, the App sends to our server, and from there to a language model (the Microsoft Azure OpenAI service): the name of the list item, a simplified snapshot of the store page visible at that moment (text, buttons, form fields) and a condensed history of the steps so far. If your data is visible on the open store page — a name in the account header, say, or a delivery address — it will be part of that snapshot. The snapshot serves only to decide the next action: we do not store it once the request completes, and it is not used to train models.

What we do store permanently:

• the “list item = store product” match — tied to your account and that store, so that next time the same product goes into the basket without asking the model; you overwrite it by choosing “Search differently” in the App;
• usage accounting — the item name, the store, the outcome and the source of the charge, needed to run the monthly pool of items;
• the run log — a condensed step history and the outcome of an item, stored without any user identifier and used solely to improve the agent's success rate; deleted after 90 days (we keep at most the 500 most recent runs per store);
• price observations — the product name and the price displayed on the store page, likewise with no link to your account.

The agent moves only within the pages of the permitted store and only fills the basket. It never signs in for you, never enters personal, address or payment data, and never places an order — where the page requires any of that, it stops and hands control back to you. These rules live in the App's code, not in the model's editable instructions. Purchases are made on the store's terms and under its privacy policy; with respect to your data the store is an independent controller, and Amamable is not a party to that transaction.

6. Cooking mode

Cooking mode — step-by-step guidance through a recipe, the timer and the hint listing the ingredients for the current step — runs entirely on your device, on the text of a recipe you already have in the App. Nothing about it is sent to our server, and it uses no AI models, no microphone and no camera. While you cook, the App keeps the screen awake and vibrates the device when the timer runs out.

7. Data storage

Data is stored on Microsoft Azure servers in the Poland Central region (European Economic Area).

Account-related data is stored for as long as you use the App and for as long as is necessary to meet legal obligations or pursue claims.

Technical data (logs, telemetry) is stored for a maximum of 12 months, unless the law requires a longer period.

Shopping lists may additionally be cached locally on your device so that they work without internet access.

8. Account and data deletion

You can delete your account together with all its data at any time (profile including your profile photo, recipes and their photos, meal plans, shopping lists, activity history, and the shopping agent data tied to the account: remembered product matches and usage accounting). Records that were never linked to an account — the agent's run log and the price observations (section 5) — do not allow you to be identified and stay in the database until their own retention periods expire.

The quickest way is in the App itself: menu → Profile → “Delete account” — the data is deleted immediately. You can also send a message from the e-mail address linked to the account to info@amamable.com with the subject “Account deletion” — we will delete the account and its data within 30 days and confirm it to you. Once deleted, the data cannot be recovered. Step-by-step instructions: amamable.com/delete-account.html.

Data we are legally required to retain (e.g. accounting records) may be kept longer — strictly to the extent necessary.

9. Recipients of the data

Data may be passed to the following categories of recipient:

• Microsoft Azure — hosting of the application, the database and files (Poland Central region, EEA);
• Google and Apple — solely for handling sign-in, if you use it;
• Google (Google Maps, Google Ireland Limited) — provider of the recipe map in the App and on the Website, as regards the technical data of map display requests (section 4); Amamable does not pass your position or your recipes’ content to Google (Google Privacy Policy);
• Microsoft (the Azure OpenAI service, Poland Central region) — solely for AI-based features, including recipe import from a photo and quick inventory (section 4) and the shopping agent (section 5); the content passed on serves only to carry out that one request and is not used to train models;
• the online stores the shopping agent works with (including Frisco and Chefs Culinar) — to the extent that you use their service yourself in the App's window; with respect to that data the store is an independent controller and applies its own privacy policy;
• payment and subscription providers (Google Play / App Store) — if you use the paid version of the App;
• bodies entitled to it under the law (e.g. public authorities).

In every case we pass on only the data necessary for that purpose. We do not sell user data.

10. Cookies on the Website

The amamable.com website uses cookies to analyse traffic (Google Analytics) — only after consent is given in the cookie banner. Consent can be withdrawn by clearing cookies in the browser. The mobile App itself uses no cookies.

11. Marketing and newsletter

If you give a separate, voluntary consent to this, we will process your e-mail address in order to send you Amamable marketing messages — information about news, recipes and promotions. The legal basis is your consent (Art. 6(1)(a) GDPR and Art. 10 of the Polish Act on Providing Services by Electronic Means). Consent to marketing is independent of accepting this Privacy Policy and of using the app — you can withdraw it at any time by clicking “Unsubscribe” in the footer of every message or by turning off the marketing consents in the app settings. Withdrawing consent does not affect the lawfulness of the processing carried out before the withdrawal. To handle the mailing we use the Brevo platform (Sendinblue GmbH), which processes the data on our behalf as a processor within the European Union.

Helping develop the App (optional):

If you tick “I want to help develop the app”, we may now and then send a short survey to your e-mail address or call you to ask for a short conversation about how you use the App. This is a separate, voluntary consent, independent of the marketing consent and of using the App; the legal basis is your consent (Art. 6(1)(a) GDPR). Giving a phone number is optional, and we keep it only for this purpose for as long as the consent stands — withdrawing the consent in the app settings or deleting your account deletes the number. Withdrawing the consent does not affect the lawfulness of processing carried out before the withdrawal.

12. Your rights

You have the right to:

• access your data and obtain a copy of it;
• rectify (correct) your data;
• erase your data (the “right to be forgotten”);
• restrict processing;
• data portability;
• object to the processing of your data;
• withdraw consent (to the extent that processing is based on consent) — withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal.

To exercise these rights, contact the Controller at the e-mail address given in section 1.

You also have the right to lodge a complaint with the competent supervisory authority (in Poland: the President of the Personal Data Protection Office).

13. Providing data is voluntary

Providing personal data is voluntary, but the absence of some data may make certain features of the App unusable (for example, without an e-mail address an account cannot be created, and without allergen information allergens cannot be filtered out of the meal plan).

14. Data security

The Controller applies technical and organisational measures to protect the data processed, appropriate to the risk to users' rights and freedoms, in particular: encryption in transit (HTTPS), storing passwords only as hashes, restricted access to data, and protection of the cloud infrastructure.

15. Changes to this privacy policy

This privacy policy may be updated from time to time. Users will be informed of material changes through a notice in the App or on the website.

Version: 3.2.0 | Date: 26 October 2026