Skip to content

Ateria Privacy Policy

Last updated: 19 November 2026

This privacy policy explains how personal data is processed in connection with Ateria, a meal-planning app for iPhone and iPad (the “App”). It informs you in accordance with Articles 13 and 14 of the EU General Data Protection Regulation (GDPR) and, where it applies, the Swiss Federal Act on Data Protection (FADP). A German version is available at pakarinen.de/ateria/datenschutz.

1. Controller

The controller responsible for the processing of personal data described in this policy is:

Johan Pakarinen
Pakarinen Studio
Am Grat 6A
85139 Wettstetten
Germany

Email: hello@pakarinen.de
Phone: +49 151 57764016

In this policy, “we”, “us” and “our” refer to the controller. We have not designated a data protection officer, as we are not legally required to (Art. 37 GDPR, Section 38 of the German Federal Data Protection Act, BDSG).

2. Summary

  • The App works on your device. Everything you enter is stored locally on your device. Unless you sign in, the App has no account, does not connect to any server operated by us, and sends us nothing.
  • No tracking. The App contains no analytics, advertising or tracking technology and no third-party software development kits (SDKs). We do not sell personal data, share it for advertising, or use it to build profiles.
  • Sharing a household is optional. From version 1.1 of the App, you can share a household with other people through our server, paid for by a subscription. Both are optional and require you to sign in. Section 8 describes how they process data and applies only if you use them.
  • Drafting ingredients is not offered yet. No version of the App distributed on the App Store offers it. Section 8.3 describes how it processes data and applies only if the version of the App you use offers it.

3. Data stored on your device

Everything you enter into the App is stored only on your device, in the database that iOS provides: your recipes and their photos, ingredients, weekly meal plan, meal history, shopping list and staples, the number of adults and children in your household with each child’s year of birth, the allergens recorded for the household, and your settings. The App does not ask for anyone’s name, and allergens are recorded for the household as a whole, not for any individual.

We have no access to this data. It is protected by your device’s encryption and is included in your device backups according to the backup settings you have chosen. Apart from those backups, and unless you share a household (Sections 7 and 8.2), no copy of it exists anywhere else, and deleting the App deletes it.

Some of this data, such as the number of people in your household, the children’s years of birth and the household’s allergens, may relate to people other than you. Please enter it, and share it in a household, only with their knowledge or, for a child, as a person with parental responsibility. We do not obtain this data from any other source.

The App can export your recipes as a tab-separated text file (TSV). The export is created on your device, and only you decide whether and with whom to share it.

4. Device permissions

The App asks for access to device functions only when you use a feature that needs it. You can grant or revoke each permission at any time in your device’s Settings.

Calendar. If you turn on calendar sync, the App asks for access to your calendars and writes your planned meals as events into a calendar you choose. It updates and removes those events when your plan changes; removing them is why the App asks for full access rather than write-only access. The App reads other events only to the extent necessary to keep its own events up to date, processes calendar data only on your device through Apple’s EventKit framework, and does not transmit it to us. Where your calendar events are synchronised afterwards (for example, to an iCloud or Google calendar) is determined by your own calendar account settings. You can revoke access in Settings → Privacy & Security → Calendars, or turn calendar sync off in the App.

Camera and photos. You can add a photo to a recipe by taking one with the camera or by choosing one from your photo library. The App asks for camera access the first time you use the camera. The photo picker is provided by iOS and gives the App only the picture you select; the App has no access to the rest of your library. Photos are stored with the recipe on your device.

Information stored on your device. The App stores information on your device, and reads it from there, only where this is strictly necessary to provide a feature you have expressly requested (Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act, TDDDG): the data you enter (Section 3), and, if you sign in, your session, a random identifier for your device and the household key (Sections 8.1 and 8.2). It stores and reads nothing on your device for any other purpose.

5. Downloading the App and Apple’s services

App Store. The App is distributed through Apple’s App Store. Downloading it requires an Apple Account. The data involved is processed by Apple (in the EU: Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) as an independent controller, under Apple’s terms and privacy policy (www.apple.com/legal/privacy). We receive no personal data from Apple about who downloaded the App. If you take out a subscription in the App, Section 8.4 describes what we receive about it.

Diagnostics shared by Apple. If you have agreed in your device’s settings to share analytics with app developers (Settings → Privacy & Security → Analytics & Improvements → Share with App Developers), Apple provides us with crash reports and aggregated usage statistics, such as the number of installations and sessions. Apple provides this information in a form that does not identify you. Insofar as it nevertheless relates to you, we use it only to find and fix faults (Art. 6(1)(f) GDPR; our legitimate interest is a working App). You can turn sharing off in the same place at any time.

TestFlight. If you test pre-release versions of the App through Apple’s TestFlight service, Apple provides us with your name and email address if you were invited by email, the device model and operating system version, crash reports, when you installed and used the beta, and any feedback and screenshots you choose to send. We use this information only to run the beta test and to fix the issues it reveals (Art. 6(1)(b) and (f) GDPR; our legitimate interest is a working App). Apple’s TestFlight terms and privacy policy apply to Apple’s own processing.

6. Contacting us

If you contact us by email, we process your email address, your name if you give it, and the content of your message in order to deal with your request (Art. 6(1)(b) GDPR where your request concerns the use of the App, otherwise Art. 6(1)(f) GDPR; our legitimate interest is answering you). We use Google Workspace for our email; the provider, Google Cloud EMEA Limited, Dublin, Ireland, acts as our processor. We delete your message once your request has been dealt with, unless statutory retention obligations require us to keep it (for business correspondence, six years under Section 147 of the German Fiscal Code, AO).

7. Households shared through iCloud

Earlier pre-release versions of the App shared a household between phones through Apple’s iCloud (CloudKit). A household created that way is stored in its creator’s iCloud account and shared by Apple with the people the creator invited. We have no access to it. In the version of the App distributed on the App Store, a household that already exists continues to synchronise through iCloud, but it is no longer possible to start or join a household through iCloud. Sharing a household through our server is described in Section 8.2.

What is shared in such a household is the household’s recipes and their photos, the meal plan and meal history, the shopping list and staples, shopping aisles, household settings including the allergens recorded for the household, and the number of adults and children with each child’s year of birth. Your calendar, your language setting and information about your device are not shared. The data stored in iCloud is held in the creator’s iCloud account under Apple’s iCloud terms, and can be removed in the iCloud settings of the creator’s device (Settings → [your name] → iCloud).

So that such a household stays up to date, the App registers with Apple’s push notification service. Apple uses the token it assigns for this to tell the App that something in iCloud has changed. We do not receive the token, and the App shows no notifications.

8. Optional features that use our server

Each feature described in this section is optional and is used only if you start it yourself. Sharing a household (Section 8.2) and the subscription that pays for it (Section 8.4) are offered from version 1.1 of the App. Drafting ingredients (Section 8.3) is not offered in any version of the App distributed on the App Store.

8.1 Your account (Sign in with Apple)

Sharing a household through our server, the subscription and drafting ingredients require an account, because the server must know who belongs to which household and which household a subscription pays for, and because the daily drafting limit applies per person. The first time you start, join or move a household, choose a subscription, restore a purchase or request a draft, the App asks you to Sign in with Apple. The App requests neither your name nor your email address from Apple; Apple provides our server only with an identifier that is unique to you and to the App. The name other household members see is the name you enter.

While you have an account, our server stores:

  • the account, its identifier, the identifier Apple assigned to you, and when the account was created and when you last signed in;
  • your sessions, each with the IP address and the App and operating-system version from which it was started;
  • whether household sharing and drafting are enabled for your account, and your subscription, if you have one (Section 8.4);
  • the households you belong to or have belonged to, your requests to join a household, and the invitations you have created (Section 8.2);
  • the number of drafts you requested on the last day you used drafting, to enforce the daily limit. Counts for earlier days are deleted. The total number of drafts per day for all users together, which does not identify anyone, is kept to monitor costs;
  • the number of times you linked a purchase to your account on the last day you did, to enforce a daily limit. Counts for earlier days are deleted.

Your session is stored only in the Keychain of the device on which you signed in. Signing out in the App (Settings → Account → Sign out) also ends the session on the server if your device is online at that moment. A session that is not ended this way, for example because you deleted the App, remains stored on the server until you delete your account.

Server logs. For each request to the server, our hosting provider records in its logs the IP address, the time, the address requested (for a photo, this contains the household’s identifier) and technical details of the connection and the App, such as the App version. Its network also derives an approximate location (country, region and city) and the network operator from the IP address and records them. We use the logs only to keep the server secure and working and to prevent abuse (Art. 6(1)(f) GDPR; our legitimate interest is a secure and reliable service); we do not use them to locate or identify anyone. The logs are deleted after at most seven days.

8.2 Household sharing through our server

You can share your household with people you invite, so that everyone’s device shows the same recipes, plan and shopping list. Nothing is shared until you start a household or ask to join one. The screen on which you do so explains what will be stored and, before the allergens are stored, asks for your explicit consent. A household cannot be shared through our server without this consent (Section 10).

How it works. A shared household is stored on our server, hosted by Supabase in Frankfurt am Main, Germany (Section 9). Each device in the household sends its changes to the server and retrieves those of the other members. While the App is open, it keeps a connection to the server open to learn that something has changed; messages over that connection only indicate that something has changed, never what.

Invitations. The person who starts a household is its administrator. To invite someone, the administrator creates an invitation, consisting of a link, a QR code and a code, which can be used once and expires after seven days. The invited person signs in with Apple and asks to join under a name of their choice, and is admitted only once the administrator approves. For each invitation, the server stores a cryptographic fingerprint (hash) of the code, never the code itself, together with who created it and when it was created, expires, and was used or revoked. If the App is not installed, the link opens a page on pakarinen.de that displays the code. The code is contained in the part of the link that browsers do not transmit to the server, so it never reaches that website.

Data stored for the household: recipes and their photos, the meal plan and meal history, the shopping list and staples, shopping aisles, household settings including the allergens recorded for the household, and the number of adults and children with each child’s year of birth. When an item is deleted, the server keeps only a record of what was deleted and when, so that every member’s device deletes it too.

Data stored about you as a member: the name you entered for the household, your role, the date you joined, and, for each of the household’s records, whether you were the last person to change it. While you are editing something, the server stores a note that you are doing so, with a random identifier the App created for your device so that the household can distinguish your devices. When you stop editing, the note is emptied; it is removed from the server with the household’s first change once a day has passed. The server also stores when you consented to the allergens being stored and which version of the consent text you were shown. The legal basis for storing the allergens is your consent; the legal basis for keeping this record is our obligation to be able to demonstrate your consent (Section 10).

What other members see about you: the name you entered for the household, your role, the date you joined and, while you are editing something, the fact that you are editing it. If you ask to join, the administrator sees the name under which you asked, and you see the administrator’s name.

Not shared: your calendar, your language setting, your Apple Account and information about your device.

Access and encryption of the allergens. The members of the household can read and change the household’s data. The allergens recorded for the household are encrypted on the members’ devices with a key that only the members hold (end-to-end encryption). The key passes from one member’s device to another’s in encrypted form, protected by a secret value that is transmitted only in the invitation link or in a code displayed on a member’s device and never reaches us. If iCloud Keychain is turned on for your Apple Account, the App also stores the key there, so that your other devices signed in to the same Apple Account receive it. According to Apple, iCloud Keychain is end-to-end encrypted; neither Apple nor we can read the key. We therefore cannot read the allergens at any point; the server can see how many allergens are recorded and when an entry changes, but not which allergens they are. Until the key is retrieved, the server stores it in its encrypted form: with an invitation, it can be retrieved for as long as the invitation is valid; otherwise, for one day. An expired key is deleted from the server within one further day.

Replacing the key. When a member leaves, is removed or deletes their account, that member’s devices delete the key, and the App removes it from that member’s iCloud Keychain. The first device of a remaining member on which the App is opened and that holds the key replaces it with a new one and encrypts the allergens again under it. From then on, the recorded allergens can no longer be decrypted with the former member’s key. The other members’ devices receive the new key, as described above, with the help of a code displayed on the device that replaced it. Encrypted keys not yet retrieved are deleted from the server at that point. So that the devices can tell which key is current, the server stores with the household a check value derived from the key, from which the key cannot be derived, and how many times the key has been replaced. The members can read both; neither can be used to decrypt the allergens. If every device of a household loses its key, the allergens have to be entered again.

Our access. As controller, we are technically able to access the household’s other data stored on the server; we do so only to keep the service working, to fix a fault you report, or where we are legally obliged to. All data is encrypted in transit and when stored on the server.

Leaving and closing. Any member can leave a household, and the administrator can remove a member. In either case, the member’s device keeps its own copy of the household’s data as a household of its own, and the household keeps what that member added. If the administrator leaves, the member who joined earliest becomes administrator. The administrator can also hand the role to another member; the server stores the pending hand-over until that member accepts or declines it. When the last member leaves, or the administrator closes the household, or nobody has paid for it for 60 days (Section 8.4), its records are deleted from the server immediately and its photos within 30 days. What remains on the server is a record, without the household’s content, that the household existed (when it was created and closed, and why; the key’s check value and how many times the key was replaced; and, for a household moved from iCloud, the identifier iCloud assigned to its creator), and a record of its invitations (fingerprints and dates). A photo no longer used by any record, such as one that has been replaced, is also deleted within 30 days.

After you have left, other members no longer see you. The server keeps your name in that household, the dates you joined and left, and who removed you, if anyone, until you delete your account, so that your device can be told what happened. A request to join, with the name under which you asked, is kept for the same period.

Households moved from iCloud. A household shared through iCloud (Section 7) can be moved to our server by its administrator with Move the household; from then on, this Section 8.2 applies to it. For a moved household, the server also stores the identifier that iCloud assigned to its creator for the App, so that the other members’ devices can recognise it as the same household. The copy left in iCloud remains in the creator’s iCloud account.

8.3 Drafting ingredients

Drafting ingredients is not offered in any version of the App distributed on the App Store. This section applies only if the version of the App you use offers it, for example a pre-release version distributed through TestFlight.

A recipe you add with only a name can have its ingredients drafted for you, for you to check and correct before anything is saved. Drafting starts only when you tap Draft ingredients.

For each recipe whose ingredients you have drafted, the App sends:

  • the recipe’s name;
  • the language of the draft (English or German);
  • up to 100 ingredient names that your recipes already use, so that the draft uses your spelling.

Nothing else is sent. In particular, the App does not send the composition of your household, the ages of its members or the allergens recorded for it; your methods, notes, photos, meal plan or shopping list; or your location or information about your device.

The request goes to our server, which checks that you are signed in and within the daily limit, forwards the request and returns the draft. Our server does not store the recipe name, the ingredient names or the draft, and does not write them to its logs. The draft is written by Claude, an AI model of Anthropic (Section 9). Anthropic receives the request from our server, not from your device, and without your account identifier or anything else that identifies you. Under its Commercial Terms, Anthropic does not use the request to train its models and deletes it within 30 days, unless its automated safety systems flag it as violating its usage policy, in which case it may keep it for up to two years, or the law requires it to keep it longer.

The draft is shown to you for review. Nothing is added to a recipe until you confirm the draft, and a drafted ingredient list is never treated as safe with regard to your household’s allergens until someone has confirmed it.

8.4 The household subscription

Sharing a household through our server requires a paid subscription. One member of the household takes it out, and it then covers everyone in the household; someone who joins a household with an active subscription does not need one of their own. You buy the subscription in the App through Apple’s App Store. Apple sells it in its own name and processes the purchase and the payment as an independent controller (Section 5); we receive neither your payment details nor any information about your Apple Account. The sales and payment reports we receive from Apple, which we keep for eight years under tax law (Section 147 AO), contain no data that identifies you.

So that our server knows the household is paid for, the App passes your account’s identifier to Apple with the purchase, and afterwards sends our server the purchase’s transaction number. Our server then retrieves the subscription’s status directly from Apple. Apple also informs our server when a subscription renews, ends or is refunded, and our server then asks Apple again. For each subscription, our server stores:

  • the type of subscription (monthly or yearly) and Apple’s transaction number for it;
  • when the current period ends, or a grace period that Apple allows after a failed payment;
  • whether it was refunded;
  • whether it was bought in Apple’s test environment, as purchases in TestFlight are;
  • the account it belongs to.

Other members of the household see only whether the household is paid for, not who pays. If the subscription ends, the household’s sharing through our server pauses until someone in it subscribes again; nothing on your device is deleted. If nobody in the household subscribes again within 60 days, our server closes the household and deletes the copy stored on the server (its records at once, its photos within 30 days); the App shows the date beforehand, and everything stays on your device. You manage and cancel the subscription on your device under Settings → [your name] → Subscriptions. Deleting your account deletes what our server stores about your subscription, but does not cancel it with Apple (Section 8.5).

8.5 Deleting your account

You can delete your account at any time in the App under Settings → Account → Delete account. This deletes your account from our server together with all data stored for it: the identifier Apple assigned to you, your sessions, whether sharing or drafting is enabled, what is stored about your subscription, your draft count and your count of linked purchases, the record of your sign-ins, and your memberships of households and requests to join them, with the names you gave. Deleting your account first takes you out of any household you belong to: if you were the administrator, the member who joined earliest takes over the role, and if you were the last member, the household is closed, its records are deleted immediately and its photos within 30 days. Our server then asks Apple to remove the App from the apps that use Sign in with Apple on your Apple Account. If that step fails, you can remove it yourself in your device’s Settings, under your Apple Account. Deleting your account does not cancel a subscription: it continues with Apple until you cancel it on your device, which the App points out before you delete.

Deleting your account does not affect the recipes, plan and shopping list on your device. Deleting the App does not delete your account; to delete it afterwards, sign in again and delete it in the App’s settings, or contact us (Section 1).

The following remains after a deletion, none of it linked to your account: what you added to a household that continues without you, the total number of drafts per day, for a household you created in iCloud and moved to our server, the identifier iCloud assigned to you, kept in the household’s record (Section 8.2), the server logs until they expire within seven days, the server’s backups for at most seven days, and any request Anthropic still holds within its 30-day period.

9. Recipients and processors

We do not sell, rent or otherwise disclose your personal data to third parties for their own purposes. Personal data is received only by the following recipients, and only in connection with the features described above:

  • Supabase Pte. Ltd., 65 Chulia Street, #38-02/03 OCBC Centre, Singapore 049513: hosting of our server, its database and file storage, sign-in and logs (Section 8). The database and file storage are located in Frankfurt am Main, Germany.
  • Anthropic, PBC, San Francisco, USA: writing ingredient drafts (Section 8.3), in the United States. Anthropic receives data only if the version of the App you use offers drafting and you request a draft.
  • Google Cloud EMEA Limited, Dublin, Ireland: hosting our email (Section 6), in the EU. Transfers to Google LLC in the United States cannot be ruled out.
  • Apple (in the EU: Apple Distribution International Ltd., Cork, Ireland): distributing the App, TestFlight, diagnostics, Sign in with Apple, iCloud, iCloud Keychain, the push notification service, and selling the subscription and telling our server its status (Sections 5, 7, 8.1, 8.2 and 8.4). Apple acts as an independent controller under its own privacy policy.

Supabase, Anthropic and Google process personal data on our behalf and on our instructions, under data processing agreements in accordance with Art. 28(3) GDPR, and are contractually bound to protect it to the same standard as this policy.

We disclose personal data to authorities only where we are legally obliged to (Art. 6(1)(c) GDPR), and then only what our server stores. We cannot disclose the allergens, because we cannot read them.

Transfers to third countries (outside the EU/EEA).

  • Supabase is established in Singapore and may access data stored in Frankfurt from outside the EU/EEA, for example to provide support. There is no adequacy decision for Singapore; the transfer is safeguarded by the European Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR).
  • Anthropic processes drafting requests in the United States. Anthropic is not certified under the EU-U.S. Data Privacy Framework; the transfer is safeguarded by Standard Contractual Clauses (Art. 46(2)(c) GDPR).
  • Google may transfer email data to Google LLC in the United States. Google LLC is certified under the EU-U.S. Data Privacy Framework, so the transfer is covered by the European Commission’s adequacy decision for that framework (Art. 45 GDPR); Google’s data processing terms also include Standard Contractual Clauses.

The Standard Contractual Clauses are part of each provider’s data processing terms, together with the corresponding addendum for Switzerland. You can request a copy of the safeguards from us.

10. Legal bases

We process personal data on the following legal bases:

  • Performance of a contract (Art. 6(1)(b) GDPR): providing the features you choose to use (Section 8), in particular your account, household sharing through our server other than the allergens (below), its subscription and drafting, and answering requests that concern the App (Section 6).
  • Legal obligation (Art. 6(1)(c) GDPR): keeping the record of your consent to demonstrate it (Art. 7(1) GDPR; Section 8.2), keeping business correspondence where tax law requires it (Section 147 AO; Section 6), answering requests to exercise your rights (Section 13), and disclosures to authorities where we are legally obliged to make them (Section 9).
  • Legitimate interests (Art. 6(1)(f) GDPR): keeping the server secure and working, preventing abuse, the daily limits on drafting and on linking purchases, and server logs (Section 8.1); our legitimate interest is a secure and reliable service that is used as intended. Also fixing faults from diagnostics and TestFlight feedback (Section 5), where our legitimate interest is a working App, and answering other enquiries (Section 6).
  • Explicit consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR): allergens are data concerning health (Art. 4(15) GDPR), a special category of personal data (Art. 9(1) GDPR). The App records them for the household as a whole, without assigning them to any individual, and does not ask for anyone’s name. They are stored on our server for a shared household only with your explicit consent. The App asks for it on the screen where you start, join or move a household, by a separate switch that is off until you turn it on. A household cannot be shared through our server without this consent, because the household’s allergens are part of what every member’s device keeps in step. If you do not consent, the App continues to work on your device alone, and nothing is stored on our server.

You can withdraw your consent at any time with effect for the future, by leaving the household or deleting your account in the App, or informally by telling us (Section 1), in which case we end your membership of the household. Your withdrawal ends the processing on your behalf. The allergens recorded for the household remain stored for its other members, each of whom has given their own consent, until the household is closed; the administrator can close the household at any time, which deletes it from the server. Withdrawal does not affect the lawfulness of processing before it.

11. Retention

We keep personal data only for as long as it is needed for the purpose for which it was collected, unless statutory retention obligations require us to keep it longer:

  • data on your device: until you delete it or the App;
  • your account and the data stored for it: until you delete your account (Section 8.5);
  • sessions on the server: until you sign out or delete your account;
  • a household’s data: until the household is closed, then deleted immediately; its photos within 30 days. A household that has gone 60 days without anyone paying for it is closed. A record without the household’s content, and a record of its invitations, remain after closing (Section 8.2);
  • invitations: fingerprint and dates as long as the household’s record is kept; who created an invitation until that person deletes their account;
  • membership history and requests to join: until you delete your account;
  • what is stored about a subscription: until you delete your account;
  • notes that you are editing: removed with the household’s first change once a day has passed;
  • the household key on your devices and in iCloud Keychain: until you leave the household, are removed or delete your account; deleting the App does not delete it from iCloud Keychain;
  • a household key awaiting retrieval, in encrypted form: until it is retrieved, and no longer than its invitation is valid or, without an invitation, one day; then deleted within one further day;
  • the record of your consent: as long as your membership is kept;
  • your daily draft count: until the next day on which you draft;
  • your daily count of linked purchases: until the next day on which you link one;
  • server logs: at most seven days;
  • server backups: at most seven days (photo files are not included; the small preview images stored with recipes are);
  • drafting requests at Anthropic: at most 30 days, subject to the exceptions in Section 8.3;
  • emails: until your request has been dealt with, subject to statutory retention obligations (Section 6).

12. Security

We take appropriate technical and organisational measures to protect your personal data (Art. 32 GDPR). All communication between the App and our server is encrypted in transit (TLS). The server’s database and file storage are encrypted at rest. Access to each household’s data is restricted on the server to its members. The household’s allergens are end-to-end encrypted (Section 8.2). Invitation codes are stored only as cryptographic fingerprints.

13. Your rights

Under the GDPR, you have the right:

  • to request access to the personal data we hold about you (Art. 15 GDPR);
  • to have inaccurate data rectified (Art. 16 GDPR);
  • to have your data erased (Art. 17 GDPR);
  • to restrict processing (Art. 18 GDPR);
  • to receive your data in a structured, commonly used and machine-readable format, and to have it transmitted to another controller (data portability, Art. 20 GDPR);
  • to withdraw any consent you have given, at any time and with effect for the future (Art. 7(3) GDPR);
  • to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU Member State of your habitual residence, place of work or the place of the alleged infringement. The authority responsible for us is the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, Promenade 18, 91522 Ansbach, Germany). In Switzerland, you can contact the Federal Data Protection and Information Commissioner (FDPIC).

Many of these rights you can exercise directly in the App: you can edit or delete any data, export your recipes, leave a household and delete your account. For anything else, contact us (Section 1). On request, we provide the data our server stores for your account in a structured, commonly used and machine-readable format (JSON). We answer within one month (Art. 12(3) GDPR). Because our server stores neither your name nor your email address, we may ask you for additional information that allows us to identify your account (Art. 11(2) and Art. 12(6) GDPR).

Right to object (Art. 21 GDPR). Where we process your personal data on the basis of our legitimate interests (Art. 6(1)(f) GDPR), you have the right to object to that processing at any time, on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds for the processing that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims.

14. Further information

No obligation to provide data. You are not legally or contractually obliged to provide personal data. The App can be used without any data being transmitted to us. The features described in Section 8 require an account; without one, you cannot use them.

No automated decision-making. We do not use automated decision-making, including profiling, within the meaning of Art. 22 GDPR.

Children. The App is not directed at children. An account, and with it the consent described in Section 10, is intended for people aged 16 or over. People under 16 may sign in and join a household only with the agreement of a person with parental responsibility (Art. 8 GDPR). We do not knowingly store account data of children under 16 without that agreement, and we delete it when we learn of it. The only information the App holds about a child in your household is the year of birth, which you enter; the App does not ask for a child’s name. The year of birth leaves your device only if you share a household (Sections 7 and 8.2), and then only for that household. It is never sent for drafting.

Our website. The pages on pakarinen.de, including the page that displays an invitation code, are covered by the website’s own privacy policy at pakarinen.de/datenschutz.

15. Changes to this policy

We will update this policy when the App or the law changes. If the App gains a feature that sends data somewhere new, this policy will be updated before that feature becomes available. The date at the top of this policy (“Last updated”) shows when it was last changed. Earlier versions are available on request.

16. Contact

For questions about this policy or about your data, or to exercise your rights, contact us at hello@pakarinen.de or at the address in Section 1.