Privacy policy
“Sloik” (Słoik, formerly “My Pantry”) for Android · version of 12 November 2026 · Polski (the Polish version prevails) · Deutsch · Čeština · Español
In short: your household data (home stock, receipts, expenses, recipes, calendar) is stored in Google Firebase in Warsaw and only the people in your household can see it. Receipt photos stay on the phone. The phone reads receipts and recipes, without AI. With your consent we receive the text of accepted receipts, without account data, to improve reading. We do not sell data. The app may show Google AdMob ads.
1. Controller
The controller is Marcin Krawczyk, ul. Zięby 40A/19, 02-808 Warszawa, Poland, e-mail: happscc@gmail.com. We answer all questions about your data at this address.
2. What we process and why
| Data | Purpose | Legal basis (GDPR) |
|---|---|---|
| Account: e-mail address, name from your Google account or entered at sign-up, account ID, leaflet country chosen in the app, date and time of the last backup restore | sign-in, showing the other household members who changed what, leaflets from the right country after signing in again, limiting how often a backup can be restored (once in 12 hours) | Art. 6(1)(b) contract; for the date of the backup restore Art. 6(1)(f) (security of the service) |
| Household data: products, stock, expiry dates, shopping list (incl. leaflet offers pinned to it), recipes, meal plan, calendar (events, reminders and who to remind), expenses, recurring costs, limits, change history | running the app and syncing between the household’s phones | Art. 6(1)(b) |
| Recipe photos taken with the camera or picked from the gallery | showing the photo with the recipe; the photo is scaled down and stored in the household data, so the household’s members can see it | Art. 6(1)(b) |
| Receipts: store (name, tax ID, address), date, items, amounts, warranty (until when, for what), currency and rate for a receipt from abroad; masked receipt text as a sample in your household | adding purchases and expenses, price history, reading statistics in your household | Art. 6(1)(b) and (f) legitimate interest (reading quality) |
| Receipt samples sent to us (only with consent): the text read from an accepted receipt and the accepted version (store, date, items, amounts), app language, currency and app version; no photos, no payment data (masked on the phone), no account or household ID | improving receipt reading, also for other stores and countries; asked after the first accepted receipt, withdraw in Settings → Receipts | Art. 6(1)(a) consent |
| Ads (Google AdMob): advertising ID, device information and ad consent | showing ads (when they are on); consent to personalised ads is collected by Google’s dialog before the first ad, change it in Settings → Ad privacy | Art. 6(1)(a) consent and (f) |
| Receipt photos | text recognition on the phone; photos are not uploaded to the app’s server | Art. 6(1)(b) |
| Crash reports: phone model, Android and app version, error trace, installation ID | fixing bugs; can be turned off in Settings → About | Art. 6(1)(f) |
| Device integrity token (Firebase App Check with Google Play Integrity), installation ID (Remote Config) | abuse protection, app configuration | Art. 6(1)(f) |
| Messages sent with “Report a problem”, “Send feedback”: the text, the sender’s address and, added by the app, app version, phone model, Android version, language and a short household tag (the household ID cannot be recovered from it); a screenshot or masked receipt text only when you attach them | replying and improving the app | Art. 6(1)(f) |
| Notice of withdrawal from the agreement made in the app: the account’s e-mail address, name, date and time of the notice, date the account was created, app language and version | receiving the notice, sending the confirmation by e-mail (we get a copy), proof of the withdrawal | Art. 6(1)(c) legal obligation and (f) establishing and defending legal claims |
Our legitimate interest (point f) is running and securing the app, fixing bugs, improving receipt reading and replying to messages.
An e-mail address is needed to create an account, and the app cannot be used without one. All other data you provide voluntarily by using the features.
The app does not collect location, contacts or browsing history. We make no decisions based solely on automated processing and do not profile users; personalised ads (only with consent) are chosen by Google.
The app sends no data to artificial intelligence (AI) services such as language models. Text and barcode recognition runs on the phone.
3. Recipients
- Google (Firebase): sign-in (Authentication), database (Cloud Firestore, Warsaw region), configuration (Remote Config), protection (App Check, Google Play Integrity), crash reports (Crashlytics), sending confirmations of withdrawal (Cloud Functions and Gmail). Google acts as a processor.
- Google AdMob: ads (banners), when they are on. Google is a separate controller here; policy: policies.google.com/technologies/ads.
- Google Play: the app rating dialog is shown by the Play Store; Google receives the rating and review under the Google Play policies.
- Open Food Facts (after scanning a barcode): the product’s barcode only.
- USDA FoodData Central (after choosing “Search USDA”): the search phrase.
- NBP or Frankfurter (European Central Bank rates) (for a receipt in another currency): only the currency and date the app fetches a rate for.
- The phone’s speech recognition (“Add by voice”): the recording is processed by the speech service set on the phone, usually Google.
- Google ML Kit: document and barcode scanning, text recognition and recipe translation run on the phone; only the needed modules and language models are downloaded from Google, without receipt or recipe contents.
- Recipe websites: when importing, the app downloads the page directly from its server. Pages opened in the import browser may set their own cookies; those websites’ privacy policies apply there.
- Store chains’ websites: leaflet offers come from the app’s database, and opening a leaflet page takes you to that chain’s website.
- Other members of your household: all household data and your name.
Google may also process data outside the European Economic Area under standard contractual clauses or a European Commission decision (EU-US Data Privacy Framework).
4. Retention
- Account and household data (incl. recipe photos and the calendar): until the account or household is deleted. History entries older than 3 months are deleted automatically.
- Crash reports: up to 90 days.
- Notices of withdrawal and their confirmations: 3 years from the notice.
- Receipt samples sent with consent: as long as they serve improving reading, at most 5 years. We do not store the account or household with them. Withdrawing consent stops further samples; we delete earlier ones on request by e-mail while the account exists (after it is deleted they can no longer be found).
- E-mails: until the matter is closed, at most 2 years.
- Data on the phone (receipt photos, drafts, settings): until deleted in the app or the app is uninstalled.
5. Your rights
You have the right of access, rectification, erasure, restriction of processing, portability and to object to processing based on legitimate interest. You can withdraw consent at any time (Settings → Receipts, Settings → Ad privacy); this does not affect the lawfulness of processing before the withdrawal. Export all household data in the app: menu ☰ → Backup (JSON file). Delete your account and data in the app: Settings → Account → Delete account, or follow Delete your account.
You may lodge a complaint with the President of the Polish Personal Data Protection Office (UODO, ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl) or with the supervisory authority in the country where you live.
6. Children
The app is meant for adults and is not directed at children under 16.
7. Security
Data is encrypted in transit. Only members of a household with a confirmed account can access its data, enforced by database security rules. Payment data on receipts is masked on the phone before a receipt’s text is sent as a sample.
Using online services carries the usual risks: malware on the phone, password phishing, account takeover when a password is weak or reused, and other people reaching an unlocked phone. Use Google sign-in or a strong, separate password, a screen lock and an up-to-date system, and give the household invitation code only to people you trust.
8. Changes to this policy
Significant changes are announced in the app or on this page, with the date of the new version.