Privacy Policy for the Pastro App
This privacy policy applies to the progressive web app “Pastro”, available
at pantry.pastro.app. A
separate privacy policy applies to the website at
pastro.app.
Last updated: 16 November 2026
At a glance
- Pastro is free to use and ad-free. We do not sell data, do not evaluate individual people and do not run advertising tracking.
- The optional subscription Pastro Premium is sold by our reseller Paddle (Paddle.com Market Limited, London). Paddle is your contracting party for the purchase and handles the payment in its checkout, which the app loads only when you start the purchase. Card numbers and other complete payment details never reach us. Our servers store only the state of your subscription (status, end date, the identifiers at Paddle). In our Paddle account, we see what Paddle shows us about the purchase (such as email address, country, amounts, payment history), which we use only in connection with your subscription: for cancellations, withdrawals, refunds, queries, duplicate payments, chargebacks and bookkeeping (section 15).
- Your data is stored with our backend provider Appwrite in the EU (Frankfurt am Main region). Free-text content is additionally encrypted there.
- The AI features (receipt, voice input, recipes) are optional, run through Mistral AI (France) in the EU and require the consent of the person using them. In a shared household, shared entries such as the pantry go along as well (section 13). We do not store images or recordings.
- In a shared household, the members see the same content and each other's display name and email address.
- Audience measurement with Umami works without cookies, is pseudonymous and can be switched off in the settings; the app then no longer loads the script.
- You can delete your account yourself at any time in the settings. What remains for a while afterwards for the other members of your household or for legal reasons is set out in section 7.
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws is:
Jonas SiederZum Freibad 78
14943 Luckenwalde
Germany
Email: contact@
Further provider details can be found in the legal notice (imprint).
This privacy policy applies to the progressive web app “Pastro”
(hereinafter “app” or “Pastro”), available at
pantry.pastro.app. A separate privacy policy
applies to the website at pastro.app.
Data protection officer: No data protection officer has been appointed, because there is no obligation to appoint one: fewer than 20 people are permanently engaged in the automated processing of personal data, none of our processing operations requires a data protection impact assessment (Section 38 (1) BDSG, German Federal Data Protection Act), and none of the cases in Art. 37 (1) GDPR apply. Please send data protection enquiries to the contact address given above.
2. Overview of processing
Types of data processed:
- Account and contact data: email address; display name (when you sign in with Google, we take the name from your Google account; you can change it at any time); a user ID assigned by us; time of registration and of your last access; whether your email address has been verified; when signing in with Google, the link to your Google account together with the email address stored there and a link to your profile picture (section 10).
- Session data: for each sign-in, the IP address and location and network details derived from it (such as country, region, time zone and internet provider), the browser identifier and, derived from it, browser, operating system and device, for as long as the session exists (section 10).
- Content data: groceries recorded in the app (name, category, amount, price, purchase date, estimated expiry date, icon), purchase history, shopping lists, saved product adjustments (name, shelf life, category, icon), recipes (AI suggestions and your own) and your recipe requests (free text and whether they include your pantry).
- Image, document and audio data: photos, image files or PDF files of receipts as well as voice recordings, only if you use the AI features, and held by us only for the duration of processing (for retention by the AI provider see section 13).
- Preferences for recipes (optional): free text about taste and cooking habits, e.g. “spicy, no mushrooms, 30 minutes max” (section 13.3).
- Household data: assignment to your household, your role (owner or member), invitations sent by you or addressed to you with email address, time and status (section 11).
- Usage and settings data: colour theme, app language, hidden navigation areas, desired number of recipes per request, whether recipe suggestions include your pantry, order of your shopping lists, the version of the Terms of Use you accepted, the times of your AI consent and its withdrawal, weekly counters of AI requests (per person).
- Subscription data (only with Pastro Premium): the status of your subscription, the end of the paid period, whether it has been cancelled, the customer and subscription identifiers at Paddle and the times of the last confirmation from the cancellation page and from the withdrawal page; on the subscription at Paddle, your user ID and, for a withdrawal without a Pastro account, the time of the acknowledgement of receipt (section 15.1).
- Purchase and payment data (only with Pastro Premium): what Paddle shows us about the purchase in our Paddle account and through its interface: email address, name and address insofar as you enter them in the checkout (usually only country and postcode), for a purchase on behalf of a company its name and tax number, language, the payment method in shortened form (for cards: brand, last four digits, expiry date and name of the cardholder; for PayPal: the email address of the PayPal account), amounts including tax, invoice numbers, payment history, refunds and the state of your subscription; we do not receive card numbers (section 15.1).
- Details on the cancellation and withdrawal pages: kind of cancellation, reason for an extraordinary cancellation, desired date, for a withdrawal your name, in each case the email address of your account and the app language (section 15.1).
- Message content: what you write to us by email or tell us on the phone, for a call also your phone number (section 16).
- Proof of consent: time and wording of your AI consent or its withdrawal; after an account deletion additionally your user ID, a hash value of your email address and the time of deletion (sections 7 and 13).
- Meta and communication data: technically necessary access data (IP address, time, requested resource, status code, browser identifier) when the app and the servers are accessed (section 9); pseudonymous usage and event data of the cookie-free audience measurement (section 14).
Categories of data subjects: users of the app, including members of a shared household; people who are invited into a household; people who buy, cancel or withdraw from Pastro Premium; people who support Pastro via Buy Me a Coffee; people who send us a message; people whose details are contained in an uploaded receipt or a voice recording.
Categories of recipients:
- our backend provider including its sub-processors (cloud infrastructure, content delivery and web security, email delivery, error monitoring, support),
- the AI provider for receipt capture, voice input and recipe suggestions, as our processor; for the abuse monitoring of its interface at the same time under its own responsibility (section 13),
- the provider of the audience measurement including its sub-processors,
- Google as sign-in service (only when signing in with Google) and as provider of our contact mailbox, through which we also send the confirmation emails,
- Paddle, which sells Pastro Premium as a reseller in its own name, as an independent controller, together with the service providers Paddle uses for this, and Paddle.com Inc. as our processor for Paddle's additional script “Retain” (only in connection with Pastro Premium),
- Buy Me a Coffee and Stripe as its payment processor (only if you support Pastro there),
- in shared households: the other members of your household.
Details on the recipients and on transfers to third countries can be found in sections 5 and 6.
Purposes of processing:
- Provision of the app, its features and content.
- Registration, sign-in and management of the user account.
- Management of pantry, shopping lists, recipes and statistics.
- AI-assisted recognition of groceries from receipts (photo/PDF) and voice recordings, and of shopping list items from voice recordings.
- AI-assisted recipe suggestions, optionally from your pantry.
- Shared use in households including invitations.
- Proof of consents given and defence against legal claims.
- Security, prevention of abuse (limit on AI requests) and technical operation.
- Audience measurement and improvement of the app.
- Activation, display, cancellation and withdrawal of Pastro Premium as well as confirmation of cancellation and withdrawal by email.
- Receipt of voluntary support and bookkeeping.
- Responding to your enquiries.
3. Relevant legal bases
We process personal data on the following legal bases of the GDPR; in addition, the national data protection provisions in Germany apply (in particular the BDSG, the German Federal Data Protection Act, and the TDDDG, the German Telecommunications Digital Services Data Protection Act). Each section of this policy states which basis applies to the respective processing.
- Performance of a contract (Art. 6 (1) (b) GDPR): processing that is necessary to provide the features you request: user account and sign-in, storage and synchronisation of your pantry, shopping lists, product adjustments, recipes and statistics, storage of your preferences for recipes, the household feature including the shared use of the household data by all members, passing your details to Paddle when you start the purchase of Pastro Premium, the activation and synchronisation of your account's Premium status including the handling of your cancellation and your withdrawal (section 15.1), the processing of a voluntary payment initiated by you (section 15.2), and responding to your enquiries about the app.
- Consent (Art. 6 (1) (a) GDPR): the three AI-assisted features (receipt capture, voice input and recipe suggestions), that is, the transfer of your receipt, your recording or your recipe request together with preferences and, where applicable, pantry to the AI provider and the processing there (section 13). If another member of your household uses the AI features, shared household data that you entered (pantry, product adjustments) goes along as well; this is based not on your consent but on our legitimate interest (below, (f)).
- Legitimate interests (Art. 6 (1) (f) GDPR): technical operation, security and troubleshooting (server logs, session data), prevention of abuse (limit on AI requests), delivery of invitations to invited people, deletion of never-used accounts and expired invitations, privacy-friendly audience measurement without cookies (section 14), the cancellation and withdrawal pages including the confirmations, insofar as they are not already covered by (b), the search at Paddle for a subscription for an address entered on the withdrawal page, limiting the confirmation emails of these pages, the related notices to our mailbox, the verification of Paddle's notifications, ending duplicate subscriptions and subscriptions of deleted accounts, clarifying duplicate payments and chargebacks, and Paddle's additional script when you buy (section 15.1), passing shared household data to the AI provider when another member of your household uses the AI features (the household's interest in using its shared data together; section 13), processing details of other people that a receipt or recording happens to contain, such as the name of checkout staff (the interest of the person using the feature in recording their shopping; section 13), responding to messages that reach us with a voluntary support (section 15.2), responding to enquiries that do not concern the use of the app (section 16), and the retention of the proof of consent after an account deletion for the defence against legal claims (section 7). We name our interest in each case in the relevant section. You can object to these processing operations (section 8).
- Legal obligation (Art. 6 (1) (c) GDPR): the obligation to demonstrate consent under Art. 7 (1) GDPR (for as long as your account exists) as well as retention obligations under tax law: six years for business letters and eight years for accounting records such as the statements from Paddle on Premium subscriptions and the records of voluntary payments (Section 147 AO, German Fiscal Code; sections 15 and 16).
Special categories of personal data (Art. 9 GDPR): Pastro is not designed to process health data, religious beliefs or other special categories of personal data. We do not ask for such data and do not evaluate it. The preferences for recipe suggestions are meant for taste and cooking habits; the app explicitly asks you not to enter allergies, intolerances, illnesses or religious reasons there. Nevertheless, it cannot be completely ruled out that details you provide yourself, in the preferences, in recipe requests, in voice recordings or on receipts (for example pharmacy or drugstore products), indirectly allow conclusions about health or beliefs. We process such content only if you upload or enter it yourself, and only for the respective purpose. It goes to the AI provider only on the basis of the explicit consent of the person using the AI feature, given before first use and expressly naming this case (Art. 9 (2) (a) GDPR). You can save preferences even without AI consent; they only go to the AI provider with a recipe request, that is, with consent. Shared household data such as the pantry is not meant for such details; please do not enter them there either. You can delete such details yourself at any time and withdraw your consent (section 8). Voice recordings are exclusively converted into text; there is no recognition of people by their voice, and no biometric data is created.
4. Security measures
In accordance with Art. 32 GDPR, we take appropriate technical and organisational measures to ensure a level of protection appropriate to the risk. These include in particular:
- Transport encryption: Transmission between the app, our servers and our service providers is encrypted via HTTPS/TLS.
- Encrypted storage of content: Your free-text content is additionally stored encrypted in the database: the names of your groceries, shopping list entries, lists and product adjustments; title, ingredients, instructions and tips of your recipes; the text of your recipe requests and your preferences for recipes. Structured values such as categories, prices, amounts, dates and status fields are not separately encrypted. The encryption is performed server-side by our provider's database with a key managed by the provider. It protects the stored data against unauthorised access but is not end-to-end encryption: the app and we can read the content during operation.
- Storage in the EU: Data is held with our backend provider in the Frankfurt am Main region chosen by us (for access from third countries see section 6). The provider describes its security measures in security documentation that forms part of our data processing agreement.
- Access separation: Content data is isolated at household level through permissions; within the app, only the members of the respective household have access. Your preferences for recipes, your subscription row and your counter of AI requests are readable by you alone. The proof of consent is kept in an area that no app user can access. As the operator, we ourselves access stored data only where this is necessary for troubleshooting, for responding to your enquiry or for fulfilling a legal obligation.
- Server-side checks: The AI features check your sign-in, your household membership, your consent, your Premium status and your weekly limit server-side before any data goes to the AI provider. The consent is read from the separately stored proof, not from your settings. The Premium status is written by our server function, after notifications from Paddle, whose authenticity it verifies by a signature, or after a query directly at Paddle; an activation without a subscription we enter ourselves. The app can only read it. When the app calls the server function for your account, for example after the purchase or for the customer portal, the function verifies who is calling by a token signed by our provider; the cancellation and withdrawal pages work without signing in (section 15.1).
- Passwordless authentication: You sign in with a one-time code sent by email or with your Google account; we do not store passwords. Sessions end when you sign out and at the latest after one year.
- No content in logs: Our server functions do not write receipt texts, transcripts, recipe content, email addresses or names to logs; error messages contain technical details only.
- Backups: Automated backups of the database, once a day, kept for 7 days, then deleted automatically; stored with the same provider (section 6).
- Data minimisation: We collect only the data necessary for the respective purpose and delete data that is no longer needed automatically (section 7).
5. Processors, service providers and other recipients
We pass your data on only to the following parties. “Processor” means: the provider processes data exclusively on our instructions, and a data processing agreement under Art. 28 GDPR is in place with it.
Processors:
- Appwrite (backend, authentication, database, real-time synchronisation, server functions, hosting, delivery of the sign-in and invitation emails): The contracting parties are Appwrite Code LTD (Israel) and Appwrite Code, Inc. (USA). Storage and processing take place in the Frankfurt am Main region (EU) chosen by us, on infrastructure of the provider DigitalOcean. Appwrite uses sub-processors, including DigitalOcean, Fastly and Cloudflare (cloud infrastructure, content delivery, web security), Mailgun, Resend and SendGrid (delivery of emails such as one-time codes and household invitations), Sentry (error monitoring) and Help Scout (support). The provider and some of these sub-processors can access the data from the USA and Israel (section 6). The complete list forms part of the data processing agreement and can be requested from us.
- Mistral AI (AI models for text recognition, speech transcription and text generation): Mistral AI, 15 rue des Halles, 75001 Paris, France. Used only when the AI features are used and only with your consent (section 13). Our server functions use Mistral's EU endpoint: according to Mistral's commitment, the models run there in data centres in the EU and in EFTA states, and data is stored in the EU by default. Where Mistral uses sub-processors outside the EU, it states that it secures the transfer through standard contractual clauses (section 6).
- Umami (audience measurement without cookies): Umami Software, Inc., 28 Geary St, Suite 650 #243, San Francisco, USA. The audience data is stored in the EU region of the service (infrastructure at Hetzner Online GmbH, EU; analytics database at ClickHouse, Inc., USA/EU); for script delivery, hosting, network security and logging, the provider uses sub-processors based in the USA (including Cloudflare, Vercel, Amazon Web Services, Axiom). See sections 6 and 14.
- Google Workspace (contact mailbox): Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland, as provider of the mailbox contact@
pastro.app (section 16). Our server function also sends the confirmations about Pastro Premium (cancellation and withdrawal, section 15.1) and the related notices to us through this mailbox. - Paddle.com Inc. (Paddle's “Retain” service): Paddle.com Inc., 3811 Ditmars Blvd, #1071 Astoria, New York 11105-1803, USA. When you buy, Paddle's script always also loads the script of this service (section 15.1). According to Paddle's terms for this service, Paddle.com Inc. acts as our processor (section 6).
Independent controllers process data under their own responsibility according to their own privacy policies:
- Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) for the optional sign-in with your Google account (section 10).
- Mistral AI for the automated abuse monitoring of its interface, to which the transmitted data is subject for up to 30 days (section 13; Mistral AI's privacy policy at legal.mistral.ai).
- Paddle (Paddle.com Market Limited, 30 Old Bailey, London EC4M 7AU, United Kingdom; for purchases from the USA and from Canada, the responsible company of the Paddle group there) when you buy Pastro Premium: Paddle sells Premium as a reseller in its own name and processes your purchase and payment data under its own responsibility, together with the service providers Paddle uses for this; Paddle likewise operates its customer portal (section 15.1; Paddle's privacy notice at paddle.com/legal/privacy, requests to privacy@
paddle.com ). - Buy Me a Coffee (Publisherr Inc., San Francisco, USA), if you voluntarily support Pastro there (section 15.2).
Other recipients: the other members of your household, if you share a household (section 11).
6. International data transfers
Where your data is located. Your account and content data is stored in the EU (Frankfurt am Main region, section 5). AI processing runs through Mistral AI's EU endpoint in the EU and in EFTA states, and the audience data is located in Umami's EU region. Transfers to countries outside the EU or the EEA occur in the following cases:
- Appwrite: Israel and USA. Our backend provider operates and maintains the service through companies in Israel and the USA; some of its sub-processors are based in the USA. In the course of operation, maintenance and support, they can access the data stored in Frankfurt; such access counts as a transfer. In addition, sub-processors based in the USA process data during ongoing operation: emails with one-time codes and invitations may go through Resend or SendGrid, and connections to the app run through Fastly's content delivery network. Israel: adequacy decision of the European Commission under Art. 45 GDPR (Decision 2011/61/EU, reviewed and confirmed by the Commission in its report of 15 January 2024). USA: the European Commission's standard contractual clauses (module “controller to processor”) as appropriate safeguards under Art. 46 (2) (c) GDPR, part of our data processing agreement.
- Umami: USA. The provider is based in the USA and uses sub-processors there for script delivery, hosting, network security and logging. These temporarily process your IP address when your browser loads the script and sends events; according to its own statements, Umami itself does not store the IP address (section 14). Safeguard: standard contractual clauses (module “controller to processor”) under Art. 46 (2) (c) GDPR, part of the data processing agreement.
- Mistral AI: exceptional cases. According to its own statements, Mistral secures transfers to sub-processors outside the EU through standard contractual clauses (Art. 46 (2) (c) GDPR); Mistral maintains the list of its sub-processors in its Trust Center (trust.mistral.ai).
- Google Workspace: USA. With the contact mailbox, a transfer to Google LLC in the USA may occur. Google LLC is certified under the EU-US Data Privacy Framework; the transfer is covered by the adequacy decision of the European Commission of 10 July 2023 (Art. 45 GDPR). Our contract with Google additionally contains standard contractual clauses that apply should this decision cease to exist.
- Paddle: United Kingdom, and for purchases from the USA or Canada also there. If you start the purchase of Pastro Premium, the app passes the details listed in section 15.1 to Paddle.com Market Limited in London, and our server function exchanges details about your subscription with Paddle. For the United Kingdom, there is an adequacy decision of the European Commission under Art. 45 GDPR (Implementing Decision (EU) 2021/1772, extended by Implementing Decision (EU) 2025/2574 of 19 December 2025, valid until 27 December 2031). If you buy from the USA or from Canada, your contracting party and therefore the recipient is Paddle.com Inc. in New York or Paddle.com (Canada) Ltd. in Toronto respectively. For Canada, there is an adequacy decision of the European Commission (Decision 2002/2/EC). We base the transfer to Paddle.com Inc. in the USA on the fact that it is necessary for your purchase and for activating Premium in your account (Art. 49 (1) (b) GDPR). Paddle processes your purchase data under its own responsibility and, according to its own information, passes it on to group companies and service providers also outside the EU and the United Kingdom, for example to the USA; for this, Paddle uses standard contractual clauses according to its own information.
- Paddle.com Inc. (Retain): USA. When the additional script “Retain” (section 15.1) loads, Paddle.com Inc. receives your IP address and details of your browser, and only when you start a purchase or open the payment page. Safeguard: standard contractual clauses of the European Commission (module “controller to processor”) under Art. 46 (2) (c) GDPR, part of Paddle's data processing agreement for this service.
- Google sign-in and Buy Me a Coffee. If you sign in with Google or support Pastro via Buy Me a Coffee, these providers process your data under their own responsibility, including in the USA. We receive from them only the details named in sections 10 and 15.2 respectively.
Please note that in the USA, despite the agreed safeguards, access by government agencies under local law cannot be completely ruled out.
Copy of the safeguards. You can request a copy of the standard contractual clauses or further information on the safeguards from us; an informal message to the contact address is sufficient. The contractual terms of Umami (umami.is/dpa), Mistral AI (legal.mistral.ai) and Paddle for the Retain service (paddle.com/legal/data-processing-addendum) are publicly available.
7. Retention period and deletion of data
We store personal data only for as long as is necessary for the respective purposes. In detail:
- Account data, settings and content data: for as long as your user account exists.
- Sessions: The session data stored for a sign-in (section 10) exists until you sign out, for one year at most. The link to your Google account exists until your account is deleted.
- Deletion of the account: You can delete your account yourself at any time in the settings. This immediately deletes your user account including sessions and Google link, your settings, your preferences for recipes, your counter of AI requests, your subscription row and the data assigned to you. Exceptions are the proof of consent (below), emails between you and us including our confirmations and notices about Pastro Premium (below, “Enquiries by email”) and, if you took out Pastro Premium, your purchase data at Paddle (below, “Premium subscription”).
- Shared households: If you are a member of a shared household, the shared household data remains (pantry, purchase history, shopping lists, product adjustments, recipes, recipe requests, statistics) for the other members when you delete your account, leave the household or an owner removes you. When the last member leaves the household, all household data is deleted.
- Purchase history: The entries of your purchase history (category, price, amount, purchase date; without item name and without assignment to a person) remain stored for as long as your household exists, even when the grocery has long been used up, because the household's statistics are built on them (the last 12 months are displayed). You can have the history deleted at any time with an informal message to us. If you are the only member of your household, it is also deleted when you leave the household or delete your account; in a shared household, it remains for the other members.
- Receipt images, PDF files and voice recordings: are transmitted to the AI provider only for the duration of processing and are not stored in Pastro, neither in the database nor in file storage or logs. Only the pantry or shopping list entries created from them are stored. At the AI provider, they are subject to abuse monitoring for up to 30 days according to its privacy policy (section 13).
- Recipe requests and AI recipe suggestions: In the recipe chat, at most 50 AI suggestions that are not favourites are kept; beyond that, the oldest suggestions together with their request are deleted automatically when the app loads and after every new request. Favourites and your own recipes remain until you delete them. You can clear the chat history yourself at any time.
- Preferences for recipes: until you change or delete them, until you withdraw your AI consent (they are deleted in the process) or until your account is deleted.
- Counters of AI requests: For each week in which you used AI features, we keep a counter for you. A nightly run deletes counters of past weeks automatically when they are older than 8 days, so that no usage profile is created.
- Premium subscription: The status and identifiers of your subscription (section 15.1) remain stored for as long as your account exists; an ended subscription remains as status “cancelled” until you take out a new one or delete your account. We do not store the details you enter on the cancellation or withdrawal page in the app; they appear only in the confirmation email to you and, for a withdrawal, an extraordinary cancellation, a cancellation to a later desired date or a cancellation that Paddle could not carry out, in a notice to our mailbox (section 16). How long we keep these emails is stated below under “Enquiries by email”. Apart from that, we store only the times of the last cancellation and the last withdrawal confirmation, in your subscription row or, for a withdrawal without a Pastro account, on the subscription at Paddle; it remains there for as long as Paddle stores the subscription. We keep the statements we receive from Paddle for bookkeeping as accounting records for eight years from the end of the calendar year (Section 147 (1) no. 4, (3) and (4) AO, German Fiscal Code); the same applies to the records of voluntary payments (section 15.2). Paddle stores your purchase and payment data as the seller under its own responsibility, according to Paddle for as long as the customer relationship exists and thereafter for the statutory retention and limitation periods; your user ID also remains there on the purchase and the subscription. You request the deletion of this data from Paddle (privacy@
paddle.com ). - Invitations and never-used accounts: An invitation into a household is valid for 10 days (from the last time it was sent) and is deleted automatically afterwards. Accounts that were created through an invitation or by requesting a one-time code but were never verified and never used are deleted automatically 10 days after they were created.
- Proof of consent: When you consent to AI processing or withdraw this consent, we record this separately from your other data: the time and the wording of the consent text as it was shown to you, in each case the current state. We are obliged to do so under Art. 7 (1) GDPR. This proof exists for as long as your account exists. If you delete your account, the proof is supplemented with the time of deletion and a pseudonymous hash value of your email address (not the address itself) and is kept together with your user ID until the end of the regular limitation period of three years from the end of the year of the account deletion (Sections 195, 199 BGB, German Civil Code), exclusively for the defence against legal claims (Art. 6 (1) (f), Art. 17 (3) (e) GDPR). After that, it is deleted automatically. If you never consented, no proof exists.
- Server and function logs: Access logs (section 9) are deleted automatically by our backend provider after 7 days.
- Backups: created daily, kept for 7 days, then deleted automatically. If you delete data, it is removed from the live system immediately; it may still be contained in the backups for up to 7 days. Backups are accessed exclusively in the event of a restore.
- Audience data: pseudonymous (section 14); deleted automatically by the provider after 6 months.
- Data on your device: the session until you sign out or delete your account, the offline mirror also until you switch household, the session storage entry until you close the tab, everything else until you clear the website data in your browser (section 9).
- Enquiries by email: until they have been dealt with conclusively, at the latest twelve months afterwards. If we have to keep a message under tax law, this is six years as a business letter and eight years as an accounting record, in each case from the end of the calendar year (Section 147 AO; section 16). The same applies to the confirmation emails about Pastro Premium and our notices about them.
8. Rights of data subjects
As a data subject, you have in particular the following rights under the GDPR:
- Access (Art. 15): information on whether and which personal data we process about you.
- Rectification (Art. 16): rectification of inaccurate or completion of incomplete data. You can change display name, pantry, lists, recipes, product adjustments and preferences directly in the app.
- Erasure (Art. 17): deletion of your data where the legal requirements are met. You can delete your account yourself in the settings (section 7). Shared data of a shared household remains available to the other members (section 11).
- Restriction of processing (Art. 18) under the legal requirements.
- Data portability (Art. 20): the data you provided in a structured, commonly used, machine-readable format. The app has no export feature; on request, we provide you with your account and household data as a JSON file.
- Withdrawal of consent (Art. 7 (3)): at any time with effect for the future; the lawfulness of the processing carried out until then remains unaffected. You withdraw your consent to the AI features in the settings in the “Account” section (“Withdraw consent and delete details”); this deletes your preferences for recipes; entries, recipes and product adjustments already created remain until you delete them (section 13).
- Complaint to a supervisory authority (Art. 77): without prejudice to other remedies, in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement.
Right to object (Art. 21 GDPR)
You have the right to object at any time, on grounds relating to your particular situation, to the processing of your personal data that is based on Art. 6 (1) (f) GDPR (legitimate interests, section 3). We will then no longer process the data unless we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. You can object to the audience measurement (section 14) without giving reasons: in the settings under “Tracking”; the switch applies to the device and browser in which you flip it. If your browser sends “Do Not Track”, this also counts as an objection. The app then no longer loads Umami's script. We do not engage in direct marketing.
For the data that Paddle processes under its own responsibility as the
seller of Pastro Premium (section 15.1), you can also
exercise your rights directly with Paddle: via
preferences.paddle.com or by
email to privacy@
The supervisory authority responsible for us is the State
Commissioner for Data Protection and for the Right of Access to
Information of Brandenburg (Landesbeauftragte für den
Datenschutz und für das Recht auf Akteneinsicht Brandenburg, LDA
Brandenburg), Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany,
phone +49 33203 356-0, email
Poststelle@
To exercise your rights, an informal message to the contact address given in section 1 is sufficient, preferably from the email address of your Pastro account. If we have reasonable doubts about your identity, we may request additional information (Art. 12 (6) GDPR). We respond within one month; in complex cases, this period may be extended by up to two months, of which we will inform you within the first month (Art. 12 (3) GDPR).
9. Provision of the app, hosting and local storage
Hosting and access data. Pastro is delivered on the infrastructure of our backend provider Appwrite (Frankfurt am Main region; for access from third countries see section 6). When the app is accessed and during every communication with the servers (including over the real-time connection and every call of a server function, for example for AI processing), technically necessary data is processed and logged: IP address, date and time, requested resource or function, status code, browser and operating system identifier and, for account actions, the approximate location derived from the IP address. These logs serve the delivery of the app, stability, security and the detection of abuse. They are deleted automatically after 7 days. The content of your requests (images, recordings, texts) is not logged. Of its own accord, the app connects only to the servers of Appwrite and, for the audience measurement (section 14), of Umami. Only when you start the purchase of Pastro Premium, open the payment page via a link from Paddle or switch to Paddle's customer portal are connections to Paddle and the services embedded by Paddle added (section 15.1). Appwrite delivers the app and data through its content delivery network (sub-processor Fastly); your browser connects to a node near you. Fonts, images, emoji data and scripts of the app do not come from any other providers, and the app loads no Google font. Only when you buy does the app load Paddle's script, which brings along a script of Paddle's “Retain” service, and in the checkout Paddle loads its own content, including fonts from Google.
Legal basis: Art. 6 (1) (f) GDPR (our legitimate interest in secure and trouble-free operation) and Art. 6 (1) (b) GDPR, insofar as the processing serves the provision of the features you request.
Local storage on your device. Pastro is an installable progressive web app. For its operation, information is stored on and read from your device:
- a session cookie of our backend provider that identifies you as signed in after sign-in. Because it belongs to the provider's address and not to pantry.pastro.app, some browsers block it; the app therefore also places the session key in your browser's local storage (
cookieFallback). Either exists until you sign out, for one year at most; - a service worker with a cache for app files (faster delivery, offline capability),
- a file you share with Pastro from another app (image or PDF), until the app opens it; it is then deleted immediately,
- an offline mirror (IndexedDB) with a copy of your household data (pantry, purchase history of the last 12 months, shopping lists, recipes, recipe requests, product adjustments) and your account data (your account as our backend provider keeps it, for example with user ID, display name, email address, verification status, settings and timestamps, plus your Premium status), so that the app starts immediately and shows your pantry even without an internet connection; your preferences for recipes are not mirrored. It is completely overwritten on every successful connection to the server and is deleted when you sign out, delete your account, switch household or when your session expires,
- an offline queue (IndexedDB) in which changes to your data are buffered when there is no internet connection and which is transmitted to the server the next time a connection is established,
- the data of the emoji picker (IndexedDB): the emoji list itself, your chosen skin tone and how often you picked which emojis, so that the most frequent ones appear first,
- entries in local storage (localStorage) for pure device settings: the chosen colour theme, whether the hints on swiping and on installation have already been shown or dismissed, whether the hint on product adjustments and the introductions to the individual app pages have been shown and whether you have objected to audience measurement (
umami.disabled, section 14), - an entry in session storage (sessionStorage) recording whether the dialog for installing the app is currently hidden (
pwa-hide-install); it applies only to the open tab and is deleted as soon as you close it.
None of these entries contains an identifier by which you could be recognised outside your account, and none is used for advertising or tracking purposes. This storage is necessary to provide the app you explicitly requested (sign-in, offline operation, your settings and remembering hints already shown so that you are not asked again) and is therefore exempt from consent under Section 25 (2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act). You can delete all entries at any time via your browser's website data; the app creates them anew the next time it starts, where they are needed.
Paddle's checkout. The checkout for Pastro Premium comes
from Paddle. The app loads it only when you tap “Continue to payment” or
open the payment page (pantry.pastro.app/zahlung) via a link
from Paddle. According to our measurement, Paddle stores nothing under
the address of the app. As soon as Paddle's script loads, Paddle's
service provider Cloudflare sets a cookie for paddle.com
that fends off automated access and expires after 30 minutes without
use. In its own window, Paddle sets further cookies and storage entries
and reads details of your device, mainly for payment processing, fraud
prevention and protection against automated access. Which entries these are and what for is decided by Paddle under its own
responsibility. The Cloudflare cookie is necessary for the payment you
requested (Section 25 (2) no. 2 TDDDG).
Details are given in section 15.1.
Camera, files and microphone. For photographing or uploading a receipt or a PDF file and for voice input, Pastro accesses the camera, file picker or microphone only after your selection or your permission in the browser. A photo is transmitted only after you have cropped and confirmed it. Microphone access exists only during an ongoing recording; if you discard a recording, it is deleted on your device and never transmitted. During a recording, Pastro may keep the screen awake (Wake Lock) so that the recording is not interrupted by the screen lock; no data is collected in doing so.
10. Registration, sign-in and user account
A user account is required to use Pastro. Pastro is aimed at people aged 16 and over (section 2 of the Terms of Use). You have two ways to sign in; the link in a household invitation also signs you in with your email address:
- One-time code by email (passwordless): You enter your email address and receive a one-time code with which you sign in. Requesting the code already technically creates an account with your email address; if you never enter the code, it is deleted automatically after 10 days (section 7). These emails, as well as the invitation emails for households, are sent via our backend provider and its email delivery services (sections 5 and 6).
- Google account: The sign-in is handled via Google; Google acts under its own responsibility in doing so. We receive from Google your email address and your name as stored in your Google account, as well as the information whether Google has verified the address, and a link to your profile picture. The name is used as the display name in Pastro if your account does not have one yet; you can change it at any time in the settings. Our backend provider stores the link to your Google account (Google user identifier, the email address stored at Google, the link to the profile picture and the access tokens issued by Google) so that later sign-ins can be assigned to your account; we do not use these details for any other purpose, and the app does not display the profile picture. We do not request any further permissions from Google. Display name and email address are visible to the members of your household; if another household invites your address, its members see your display name even before you accept (section 11).
As part of the user account, we process:
- your email address (sign-in and the confirmations about Pastro Premium; when you buy, the app passes it to Paddle's checkout, where it is fixed, and on the cancellation and withdrawal pages it identifies your account; section 15.1),
- your display name,
- your user ID, the time of registration and of your last access, and the verification status of your email address,
- session data: For each sign-in, our backend provider stores the IP address and location and network details derived from it (such as country, region, time zone and internet provider), the browser identifier and, derived from it, browser, operating system and device. This serves the management of your sessions and the security of your account. A session ends when you sign out, at the latest after one year (section 7).
- account settings: assignment to your household, colour theme, app language, hidden navigation areas, desired number of recipes per request, whether recipe suggestions include your pantry, order of your shopping lists, the version of the Terms of Use you accepted, and the times of your AI consent and its withdrawal (these only control whether the AI features are unlocked; the proof is kept separately, section 7),
- with Pastro Premium, your subscription data (section 15.1),
- optionally your preferences for recipes (section 13.3), which are stored separately and encrypted and are readable by you alone.
Your email address is not used for advertising purposes and is not passed on to anyone other than the recipients named in section 5 and, within your household, the other members (section 11).
Legal basis: Art. 6 (1) (b) GDPR; for the session data additionally Art. 6 (1) (f) GDPR (our and your interest in the security of the account).
Necessity of provision: The email address (or a Google account) is required to create a user account; without it, we cannot provide the app. All further details are voluntary; the AI features require your consent, all other features can be used without it. There is no statutory or contractual obligation to provide us with any further data.
11. Shared households
Pastro lets you use a household together with other people. Invited members can access the shared content: pantry, purchase history and statistics, shopping lists, saved product adjustments, recipes and the history of recipe requests.
- Invitations: You enter the email address of the person to be invited; only invite people who agree to it (Terms of Use, section 2). They receive an invitation email with a link via our backend provider; on the page that opens with it, they see this privacy policy and the Terms of Use before accepting the invitation. The invitation is valid for 10 days and is deleted automatically afterwards. If an address is invited for which no account exists yet, a provisional account is technically created that contains only the email address and a randomly assigned display name; if the invitation is not accepted, this account is deleted automatically after 10 days.
- Visibility: Within a household, the shared content as well as the display name, email address and role of the members are visible to the other members (member list in the household management), as are open invitations with the invited email address and, if a Pastro account already exists for this address, its display name. This also applies to the free text of your recipe requests. Deleting a recipe or entry removes it for all members. Your preferences for recipes and your settings are not visible to others.
- AI features in the household: If a member uses the AI features (section 13), shared household data is also transmitted to the AI provider: for recipe suggestions that include the pantry, the entire pantry of the household (names, amounts, remaining shelf life), for receipt capture and voice input the saved product adjustments. Therefore, only enter data into a shared household that may be processed in this way.
- Premium in the household: Pastro Premium and your weekly allowance of AI requests belong to you alone; the other members see neither your Premium status nor your counter of AI requests. If you switch or leave the household or an owner removes you, your subscription stays unchanged (section 15.1).
- What happens to the data: If a member leaves, is removed by an owner or deletes their account, the shared household data remains available to the other members (section 7). If you accept an invitation into another household, you switch to it; your previous household is deleted if you were its only member, otherwise it remains available to the other members. Therefore, please only enter data into a shared household that is intended for the other members.
Legal basis: Art. 6 (1) (b) GDPR (provision of the household feature you chose, including the use of the shared data by the other members). The transfer of shared data to the AI provider when another member uses the AI features is based on Art. 6 (1) (f) GDPR (section 3). Towards the invited person, the processing of their email address for delivering the invitation is based on Art. 6 (1) (f) GDPR (legitimate interest of the inviting member and the invited person in using the household together); the invitation email serves solely to deliver the invitation and contains no advertising. The automatic deletion of expired invitations and never-used accounts is based on Art. 6 (1) (f) GDPR (storage limitation, Art. 5 (1) (e) GDPR).
12. Core features: pantry, shopping list, recipes and statistics
To fulfil the actual purpose of the app, we process the content data you enter or create:
- Pantry: name, category, amount, price, purchase date, estimated expiry date and an optional icon per grocery, plus whether the entry was created manually or by AI and, for groceries recorded from a receipt, the name as printed on the receipt.
- Purchase history: For every grocery created, an entry with category, price, amount and purchase date is stored (without the name and without assignment to a person), which remains after the grocery has been used up (section 7).
- Shopping lists: lists you create and their entries, including ingredients you take over from a recipe and items you dictate (section 13.2).
- Product adjustments (“Pastro learns from you”): If you adjust the shelf life, category or icon of a grocery, Pastro remembers name, shelf life in days, category and icon for your household and takes them into account in future captures (section 13). You can view and delete the saved adjustments in the settings.
- Recipes: your own recipes as well as AI suggestions (section 13.3) with title, ingredients, instructions, tip, category, tags, servings and an estimated calorie figure; plus the favourite flag. If you mark a recipe as “cooked”, the amounts used are deducted from your pantry.
- Statistics: evaluations of your household for the last 12 months: spending and a roughly estimated saving derived from it (from the purchase history), distribution by category, and an overview of how much of your pantry is still fresh, expiring soon or expired (from the pantry).
Expiry dates, calorie figures and the “saving” are estimated automatically and are non-binding; what this means for you is set out in section 3 of the Terms of Use.
Legal basis: Art. 6 (1) (b) GDPR.
13. AI-assisted features
Pastro offers three optional features based on artificial intelligence: receipt capture from receipts (13.1), voice input for pantry and shopping list (13.2) and recipe suggestions, optionally from your pantry (13.3). The following applies to all three:
Consent. Neither the app nor our server functions start any of these features for you without your prior consent. Before first use, the app shows you a notice about which data goes to which provider for which purpose and what happens to it there, and you can consent or decline. Without consent, you do not start any AI processing; all other features remain usable (you can also record groceries and recipes manually). We record your consent and its withdrawal as proof (section 7). The consent expressly also covers the case that a receipt, a recording or an entry exceptionally contains details that allow conclusions about your health or beliefs (section 3).
Withdrawal. In the settings in the “Account” section via “Withdraw consent and delete details”, at any time with effect for the future. This deletes your preferences for recipes; entries, recipes, recipe requests and product adjustments already created remain until you delete them. We record the withdrawal as well. The lawfulness of the processing carried out until then remains unaffected.
Household data. The AI features work with the data of your household: recipe suggestions with the entire pantry (if they include it), receipt capture and voice input with the saved product adjustments. This data therefore also goes to the AI provider when another member of your household uses the feature with their consent, even if you have not consented yourself. This is based on our legitimate interest and that of your household in using the shared data together (Art. 6 (1) (f) GDPR, sections 3 and 11). If a receipt or recording contains details of other people, such as the name of checkout staff or a voice recorded along the way, we process them only because they cannot be separated (Art. 6 (1) (f) GDPR); they are not stored.
Place of processing and provider. Processing begins in server-side functions at our backend provider in Frankfurt am Main (EU). As the AI provider, we use exclusively Mistral AI (Mistral AI, 15 rue des Halles, 75001 Paris, France, EU), for text recognition (OCR), speech transcription and text generation. Our server functions use Mistral's EU endpoint; according to Mistral's commitment, the models run there in data centres in the EU and in EFTA states (sections 5 and 6). No other AI service and, in particular, no speech recognition of the browser or operating system is used.
Storage at the AI provider. Mistral AI processes the data as our processor on the basis of a data processing agreement. The transmitted inputs and outputs are not used to train the models; we have expressly excluded this use in our account. To automatically detect abuse of its interface, Mistral AI retains the transmitted inputs and outputs for up to 30 days according to its privacy policy and deletes them afterwards; Mistral AI itself is responsible for this check, and Mistral AI's privacy policy (legal.mistral.ai) applies in this respect.
Background processing. Processing continues on our servers even if you close the app in the meantime. Results appear the next time you open the app or via real-time update.
Limit. The number of AI requests is limited per person to 5 per week, with Pastro Premium to 30. The counter is kept server-side and moves with you, so switching household does not bring a new allowance (section 7). Which limit applies is read by the server function from your Premium status before every request (section 15.1). Voluntary support (section 15.2) does not raise this limit.
Labelling and limits of the AI (Regulation (EU) 2024/1689, Art. 50). All results of the AI features are generated automatically and may contain errors: recognised items, estimated shelf lives, recipes, calorie figures. In the recipe chat you interact with an AI system; AI-generated recipes are labelled as such in the app and marked as AI results in our data. Please check the results: in particular ingredients, if you have allergies or intolerances. There is no decision based solely on automated processing with legal effect or similarly significant impact within the meaning of Art. 22 GDPR.
Legal basis: Art. 6 (1) (a) GDPR (consent), for indirectly sensitive details Art. 9 (2) (a) GDPR (section 3); towards the other members of your household for the shared data and for details of other people on receipts and in recordings Art. 6 (1) (f) GDPR (above); for the proof of consent Art. 6 (1) (c) in conjunction with Art. 7 (1) GDPR; for the limit on requests Art. 6 (1) (f) GDPR.
13.1 Receipt capture (receipt as photo, image or PDF)
You can photograph a receipt, upload an image, submit the receipt as a PDF file (at most 7 MB) or share an image or PDF with Pastro from another app. You can crop images before sending. The file goes through our server function to Mistral AI's text recognition (OCR); for a PDF file, the whole file goes to Mistral, and at most the first 10 pages are read. The items are extracted in structured form from the recognised receipt text. In doing so, the language model receives the complete recognised receipt text (including date, store, total and payment method, insofar as they appear on the receipt), the current date and your saved product adjustments (name, shelf life, category, icon; at most 200) so that your corrections are taken into account. The recognised items end up in your pantry; the estimated expiry dates are calculated by our system from the purchase date and the estimated shelf life.
Data processed: the receipt file and the content recognised from it. A receipt may contain personal data (e.g. date/time, store, payment method, purchased products, names of checkout staff). Please do not submit receipts that you do not want to have processed, and receipts of other people only with their agreement. The file is not stored in Pastro (section 7).
13.2 Voice input (dictate your pantry or shopping list)
You can dictate your pantry or items for your shopping list. The recording takes place locally on your device after you have granted microphone access; you can pause, discard or finish it. After finishing, it is transmitted to our server function, converted into text by a transcription model from Mistral AI and then structured by a language model into grocery entries or, for the shopping list, into entries of the list that was open when you tapped the microphone. For better recognition, up to 100 names from your product adjustments and, if the app is set to German or English, the app language are passed to the transcription. For the pantry, the language model then also receives the product adjustments with all details (name, shelf life, category, icon; at most 200, as in 13.1).
Data processed: the voice recording, the text created from it and the recognised items. The recording serves exclusively the conversion into text; your person is not identified by voice. Please only dictate what you want to record, and make sure that no other people are recorded. The recording is not stored in Pastro (section 7).
13.3 Recipe suggestions
In the recipe chat, you can have dishes suggested that match your pantry, optionally with a wish in free text (e.g. “something light for dinner”). By default, your request is transmitted to our server function together with a list of your household's pantry (names, amounts and remaining shelf life, at most 150 entries), the app language, the current date, the desired number (one recipe, up to three if you have Pastro Premium) and, if stored, your preferences. From this, the AI generates the desired number of recipe suggestions, which are stored in your household and displayed in the chat. If a suggestion does not match the pantry, the server function asks the model a second time with the same conversation history.
Without pantry. If you untick “Use pantry” in the recipe chat, neither the pantry list nor the date is sent; the suggestions are then based only on your request and your preferences. The tick only applies to your own requests. Whether a request included the pantry is stored with it and shown in the chat, including to the members of your household. The button for food that expires soon always includes the pantry, and a retry sends a failed request the way it was made.
Preferences (optional). You can store preferences that are sent automatically with every recipe request, for example “spicy, no mushrooms, 30 minutes max”. They are meant for taste and cooking habits; please do not enter allergies, intolerances, illnesses or religious reasons (see section 3). The preferences are stored encrypted, are readable by you alone and are not visible to household members. You can save them even without AI consent; they are only sent with a recipe request. You can change or delete them at any time; when you withdraw your AI consent, they are deleted.
Data processed: your request text, the pantry list (only with pantry), the preferences where applicable, and the generated recipes. Suggestions that are not favourites and their requests are cleaned up automatically (section 7). Request texts are visible to the members of your household (section 11).
14. Audience measurement with Umami
We use the web analytics service Umami (provider: Umami Software, Inc., San Francisco, USA) to see how many people use Pastro, which features they use and where errors occur, and to improve the app accordingly. When the app loads, your browser loads a script from the provider's servers and sends usage events there, unless you have objected (below); in doing so, it technically transmits your IP address.
What is collected:
- Page views within the app and events that we trigger in the code (e.g. “scan started”, “recipe generated”, “onboarding completed”), in each case without content: no receipt texts, transcripts, recipe or request texts, preferences, names or email addresses are transmitted. For individual events, technical attributes are collected, such as an error reason, a category or a count. Parameters from web addresses are removed before transmission.
- Technical details that the script reads from your browser or that your browser sends along: browser, operating system, device type, language, screen size and the previously visited page (referrer).
- Derived from the IP address: the approximate location (country, region, city). According to its own statements, Umami does not store the IP address itself; sub-processors in the USA process it temporarily to deliver the script, for network security and for logging (section 6).
How Umami works:
- No cookies are set and no identifiers are stored on your device.
- To distinguish visits by the same person, Umami forms a hash value from details such as website, browser identifier and IP address together with a secret value. This secret value changes at the beginning of each month. Within a month, Umami can therefore pseudonymously attribute recurring visits to the same person; after that, it cannot. There is no recognition across other websites.
- We do not link the audience data to your account and do not evaluate individual people. Umami shows us totals, trends and event frequencies and, alongside them, individual pseudonymous sessions (approximate location, device, browser, pages visited and events within one month); we look at these only for troubleshooting.
- The data is stored in the EU region of the service (sections 5 and 6) and is deleted automatically by the provider after 6 months.
Objection. You can switch off audience measurement for
your device at any time: in the settings under “Tracking”. The
app then places an entry umami.disabled in your local
storage; nothing else is stored. From the next start, the app no longer
loads the script; until then, the entry mutes it. If your browser sends
“Do Not Track”, the app does not load the script at all.
Legal basis: Art. 6 (1) (f) GDPR (legitimate interest in privacy-friendly audience measurement and improvement of the app). In favour of this balance: no cookies, no advertising, no selling or sharing of data, no link to your account, no content, pseudonymous attribution only within one month, storage in the EU and a simple objection. The script stores nothing on your device and reads only the technical details named above that it needs for counting; we therefore do not obtain consent under Section 25 TDDDG.
15. Pastro Premium and voluntary support
Pastro is free to use and has no advertising. Two things optionally cost money: the optional subscription Pastro Premium, which is sold by our reseller Paddle and whose checkout the app displays (15.1), and voluntary support via Buy Me a Coffee outside the app, which unlocks nothing (15.2).
15.1 Pastro Premium: purchase through Paddle
Who sells and who is responsible for what. Pastro
Premium is sold by Paddle.com Market Limited, 30 Old Bailey, London EC4M
7AU, United Kingdom (“Paddle”), as a reseller in its own name; for
purchases from the USA and from Canada, it is the responsible company of
the Paddle group there. Paddle is your contracting party for the purchase
and takes care of payment, taxes, invoices, refunds and questions about
the payment. Paddle is itself responsible for this processing; Paddle's
privacy notice applies
(paddle.com/legal/privacy).
We are responsible for the app loading Paddle's checkout and passing the
details listed below to Paddle, and for everything we ourselves do with
details from Paddle. You can address questions and rights concerning
this transfer to us or to Paddle
(privacy@
What the app passes to Paddle. Only when you tap
“Continue to payment” does the app load Paddle's script from
cdn.paddle.com and open Paddle's checkout over the app
(buy.paddle.com). Before that, the app opens no connection
to Paddle. In the process, Paddle technically learns your IP address,
details of your browser and device and the address of the app page from
which you buy. The app also passes your email address
(it is fixed in the checkout so that purchase and account match), your
user ID (so that we can assign the purchase to your
account; Paddle stores it on the purchase and the subscription) and the
app language (for the language of the checkout). Paddle
receives these details as soon as the checkout opens, even if you do not
complete the purchase. Without them, you cannot buy Premium.
The payment page. Links in Paddle's emails, for example
to pay or to change the payment method, may lead to our payment page
pantry.pastro.app/zahlung. It can be reached without signing
in. If its address contains an identifier from Paddle, it loads Paddle's
script straight away, and Paddle opens the matching checkout; Paddle
then receives the address of the page including this identifier.
Without an identifier, the page loads nothing from Paddle.
The checkout. What you enter in the checkout (payment method, country, postcode and, depending on the payment method, further details) goes directly to Paddle, not to us. In its window, Paddle embeds its own service providers and sets cookies on its own addresses and those of these providers: for payment processing, fraud prevention, protection against automated access, translations and error reports. In our measurements in November 2026, these included Stripe (payment processing and fraud prevention), Cloudflare (protection against automated access), Google (Google Pay and fonts), Localize (translations) and Sentry (error reports). Which services Paddle uses is decided by Paddle and may change. According to our measurement, Paddle stores nothing under the address of the app (section 9).
Paddle's additional script “Retain”. Together with the
checkout, Paddle's script loads a further script of the Paddle service
“Retain” (formerly ProfitWell) from public.profitwell.com.
Through this service, Paddle controls, among other things, how failed payments are retried. We do not need the script for the purchase itself; we cannot
switch it off because it is a fixed part of Paddle's script. When it is
fetched, the service learns your IP address, details of your browser and
that the request comes from pantry.pastro.app. We pass no
identifier of yours to this service, and the app loads the script only when you start a purchase or open the payment
page. The service is provided by the US company Paddle.com Inc., according
to Paddle's terms as our processor (sections 5 and
6).
What we receive from Paddle and store. Paddle notifies our server function through signed notifications when something changes in your subscription. The function verifies the signature, queries the current state directly at Paddle and writes from it one row per person, linked to your user ID: the status of the subscription (such as active, payment overdue, cancelled), the end of the paid period or the cancellation date, whether a cancellation is scheduled, the customer and subscription identifiers at Paddle, the time of the last synchronisation and the times of the last cancellation and the last withdrawal confirmation. Right after the purchase, the function also queries the purchase transaction at Paddle to assign it to your account; Paddle's response also contains the shortened payment details, of which the function takes over only the subscription identifier. It does not store names, addresses or payment details. From the row, the app knows whether you have Premium; in the app, only you can read it, and no one can change it from the app. If a second subscription is created for you, for example from two checkouts opened at the same time, our server function ends it immediately, and we arrange the refund. If your account is deleted while the checkout is still open and the purchase arrives afterwards, our server function likewise ends the subscription immediately, and we arrange the refund.
What we see in our Paddle account. As the provider of Pastro, Paddle shows us the purchases: your email address, name and address insofar as you enter them in the checkout (usually only country and postcode), for a purchase on behalf of a company its name and tax number, the payment method in shortened form (for cards: brand, last four digits, expiry date and name of the cardholder; for PayPal: the email address of the PayPal account), amounts, the payment history, invoices, refunds and the state of your subscription. These details come from Paddle. We use them only to handle your withdrawal, your cancellation or a refund, to answer questions about your subscription, to clarify duplicate payments and chargebacks and for our bookkeeping. We do not use them for advertising. We do not see card numbers.
Emails. Paddle sends you the confirmation of your purchase, invoices and notices about payments, cancellations and refunds. From us, you receive a cancellation confirmation after a cancellation via the cancellation page and an acknowledgement of receipt after a withdrawal via the withdrawal page. Our server function sends these two emails through our mailbox at Google Workspace (sections 5 and 16).
Customer portal. If you tap “Manage subscription” or “Reactivate subscription” on the “Pastro Premium” page in the settings, the app fetches a link to Paddle's customer portal from our server function and switches to it. The server function requests this link from Paddle using your customer identifier. It signs you in to the portal without you having to sign in at Paddle and expires after some time; the app does not keep it. In the portal, you change your payment method, see your invoices and can cancel or revoke a cancellation. Paddle operates the customer portal under its own responsibility.
Cancellation page. At
pantry.pastro.app/kuendigen, you can cancel without signing
in. You enter the kind of cancellation, the desired date and the email
address of your Pastro account, and optionally a reason for an
extraordinary cancellation. Our server function looks up the account for
this address and its subscription and carries out the cancellation at
Paddle to the end of the current billing month. If you choose a later
date, your cancellation first goes only as a notice to our mailbox, and
we carry it out at Paddle in the right month.
The page only shows that your statement has been received, with the
date and time, and you can save it as a file. Whether a subscription is
running under the address and when it ends is stated only in the
confirmation by email to the address of your account.
For an extraordinary cancellation, a notice with the reason and the
account address additionally goes to our mailbox so that we can review
the reason.
If Paddle cannot carry out the cancellation at that moment, for example
in the half hour before a charge, the page asks you to try again, and a
notice with your details and the account address goes to our mailbox so
that the cancellation is not lost.
Only the time of the last cancellation confirmation is stored in your
subscription row, so that at most one confirmation per hour is sent when a
cancellation does not trigger anything new at Paddle. Because the page works
without signing in, someone who knows your address can cancel your
subscription there to the end of the paid period; the page does not
show them whether a subscription is running under it, except when the
cancellation cannot be carried out at that moment (for example in the
half hour before a charge or in the event of a disruption at Paddle or
our mail server). The confirmation email shows you every such
cancellation.
Withdrawal page. At
pantry.pastro.app/widerrufen, you can withdraw from the
contract for Pastro Premium without signing in. You enter your name and
the email address of your Pastro account. Our server function looks up
the account for this address and its subscription. If it finds none,
for example because the account has already been deleted, it asks
Paddle whether there is a customer with this address and a running
subscription; the address entered then goes to Paddle, even if there is
no customer there. If there is a subscription, the function sends you an
acknowledgement of receipt by email, and a notice with name, address and
subscription identifier goes to our mailbox. This is how we forward your
withdrawal to Paddle: if it arrived in time, we end the subscription at
Paddle and arrange the refund there. The function notes the time of the
acknowledgement in your subscription row or, if there is no account any
more, on the subscription at Paddle, so that at most one acknowledgement
per hour is sent. The page only shows that the withdrawal has been
received, with the date and time, regardless of whether a subscription
is running under the address (except in the event of a disruption at
Paddle or our mail server), and you can save it as a file. Because it
works without signing in, someone who knows your address can declare a
withdrawal there; the acknowledgement of receipt shows you every such
withdrawal.
When the account is deleted, our server function cancels your running subscription at Paddle to the end of the paid period and deletes your subscription row (section 7). If the subscription cannot be cancelled at that moment, for example in the half hour before a charge, your account remains, and the app asks you to try again later. Your purchase, your subscription including the user ID and your invoices remain stored at Paddle under Paddle's responsibility. If you switch or leave the household, an owner removes you or the household is dissolved, this does not change your subscription.
Legal bases: Art. 6 (1) (b) GDPR for passing your details to Paddle when you start the purchase (you request the purchase, and we assign it to your account), for the activation and synchronisation of the Premium status and the link to the customer portal (our contract for the use of the app with you) and for handling your cancellation and your withdrawal: we receive your statement, carry out the cancellation at Paddle or forward the withdrawal to Paddle and confirm receipt to you by email. The law requires the cancellation page, the withdrawal page and the confirmations from the seller (Sections 312k and 356a BGB, German Civil Code), here Paddle. We provide them in the app because you take out Premium here and Paddle obliges us to do so. Insofar as Art. 6 (1) (b) GDPR does not cover this, we rely on Art. 6 (1) (f) GDPR: Paddle and we have a legitimate interest in giving you a simple way to cancel and withdraw and in being able to prove receipt of your statement. Art. 6 (1) (f) GDPR also applies to the verification of the signatures of Paddle's notifications, the search at Paddle for a subscription for the address entered on the withdrawal page (our and your interest in a withdrawal arriving even after an account deletion), the notices to our mailbox, ending a duplicate subscription or a subscription of a deleted account, clarifying duplicate payments and chargebacks, limiting the confirmation emails (our interest in preventing abuse, duplicate payments and payments without consideration) and the additional script “Retain” (without Paddle's script, we cannot offer you the checkout). Loading Paddle's script and the Cloudflare cookie are necessary for the payment you requested (Section 25 (2) no. 2 TDDDG); Paddle is responsible for the entries in its checkout. Art. 6 (1) (c) GDPR in conjunction with Section 147 AO applies to the retention of the accounting records (section 7).
15.2 Voluntary support via Buy Me a Coffee
Anyone who wishes can support the project voluntarily via the platform Buy Me a Coffee. This is a payment with nothing in return: it does not unlock any features, does not lift any limit and is not a purchase of Pastro Premium. No flag is created on your Pastro account, and the app learns nothing about a support.
- Only a link: The row “Support Pastro” in the settings opens a window with a link that opens the Buy Me a Coffee page in a new tab. Nothing from Buy Me a Coffee is embedded in the app, and the app passes nothing when opening it (the link sends no referrer). Only when you tap the link does your browser call up the Buy Me a Coffee page, which thereby receives the usual connection data such as your IP address.
- External provider: The provider is Publisherr Inc., 2193 Fillmore Street, San Francisco, CA 94115, USA. Buy Me a Coffee is independently responsible for everything you enter there (payment method, name or pseudonym, email address, message); its privacy policy applies (buymeacoffee.com/privacy-policy). Processing there also takes place in the USA (section 6).
- Payment processing: The payment is processed by Stripe, to a Stripe account of the controller connected to Buy Me a Coffee. Stripe processes the payment data under its own responsibility (stripe.com/privacy, section 6).
- What we see: In the Buy Me a Coffee account and in the connected Stripe account, we see the details these services show to the recipient of a payment: name or pseudonym, email address, amount, time, payment method and any message. We do not link these details to Pastro accounts and use them only for bookkeeping and, if you leave us a message, to reply to you.
Legal bases: Art. 6 (1) (b) GDPR for the processing of the payment initiated by you; Art. 6 (1) (c) GDPR for the retention of the accounting records under tax law (8 years, Section 147 AO, section 7); Art. 6 (1) (f) GDPR for replying to a message you leave with your support (our and your interest in a reply).
16. Contact
If you contact us (for example via the app's feedback feature, which
opens your email program with the address
contact@
The contact mailbox is operated via Google Workspace. The provider is Google Cloud EMEA Limited, 70 Sir John Rogerson's Quay, Dublin 2, Ireland, with which a data processing agreement is in place. Google receives, stores and technically processes the messages; this may involve a transfer to Google LLC in the USA, which is secured by the EU-US Data Privacy Framework; should this decision cease to exist, our contract contains standard contractual clauses (section 6). We also send the confirmations about Pastro Premium through this mailbox (section 15.1). If you do not want this, you can also write to us by post at the address in section 1.
We delete enquiries once they have been dealt with conclusively, at the latest twelve months afterwards. If we have to keep a message under tax law, this is six years as a business letter and eight years as an accounting record, in each case from the end of the calendar year (Section 147 AO).
Legal basis: Art. 6 (1) (b) GDPR (enquiries in connection with the use of the app) or Art. 6 (1) (f) GDPR (legitimate interest in handling enquiries); for retention under tax law Art. 6 (1) (c) GDPR.
17. Changes to this privacy policy
We adapt this privacy policy as soon as changes to the processing make
this necessary (new features, changed service providers or
sub-processors, changed legal situation). The current version linked in
the app (pantry.pastro.app) applies; the date of the last
update is stated at the beginning, and we will send you earlier versions
on request. In the event of significant changes, we will inform you in
an appropriate manner, for example by a notice in the app. If the AI
processing changes significantly, we will ask for your consent again.
This is a translation provided for convenience. The German version is the authoritative text, as the underlying obligations arise from German law.