Effective 26 September 2026 · Last updated 20 October 2026
This policy explains how we process your personal data when you use the Krokiet app for iPhone and Android and the website krokiet.app. It is the information we must give you under Articles 13 and 14 of the GDPR. The GDPR applies to every user, wherever you live, because we are based in Poland. Section 14 adds what the laws of some other countries ask for. The English and Polish versions have equal force.
The controller of your personal data is Artur Witkowski, a sole trader, ul. Stefana Batorego 23/7, 81-365 Gdynia, Poland, NIP 5862405430, REGON 528542614 ("we", "us"). We operate the Krokiet app and the website krokiet.app. "GDPR" in this policy means Regulation (EU) 2016/679, the General Data Protection Regulation.
You can contact us at contact@krokiet.app, in English or Polish. We have not appointed a data protection officer, as the law does not require one.
Krokiet shows no ads and does no tracking. We do not sell personal data. We count a few things people do in the app, such as how often the Krokiet Plus offer opens, as anonymous daily totals. Section 2 explains what those totals hold.
| Category | Data | Source |
|---|---|---|
| Account | Email address, name, the cartoon face you pick, friend code, app language, your friends and friend requests | You |
| Apple or Google sign-in | Account id and sign-in tokens, your name from Google, and the address of your Google profile picture, which the app never shows | Apple or Google, if you sign in with them |
| Sign-in and sessions | Sign-in codes, and the IP address and device description of each session | Your device |
| Meals | Place, date, who was at the table, dishes, the lists they were scored in, scores, and names you type for people without an account | You and friends who record meals with you |
| Dish photos | Photos you take or pick for a dish | You |
| Menu photos | Images of menu pages, the dish names and prices read from them, and the fact that you made the scan | You |
| Places you add | Name, address and map pin of a restaurant | You |
| Location | Your phone's coordinates and the area of the map on screen | Your device, if you allow it |
| Notifications | A push token for each phone you are signed in on, its platform (iOS or Android), the kinds of notification you have switched off, and the text of each notification, which names the friend it is about | Your device, if you allow notifications |
| Reports | What you reported and anything you wrote. A bug report adds the app and system versions, the screen you were on and whether you shook the phone to open it | You |
| Crash reports | The error, phone model, system and app versions. For an error on our server, the error and which kind of request failed. No name, email address or account id | Your device, or our server |
| Update checks | System version, app version and a random id for this install | Your device |
| Krokiet Plus | Whether you have it, the plan (monthly, yearly or for life), when it ends or renews, whether a payment failed, whether it was a test purchase, the store you bought it in, and the frame you pick for your face | Apple or Google, through RevenueCat, and you for the frame |
| Unlocked bills | Which bill you unlocked with a one-time payment, and when | You, with Apple or Google confirming the payment through RevenueCat |
| Purchase records at RevenueCat | Your account id, the store's transaction ids and purchase history, the price and currency, the country of your store account, and the app and system versions | Your device, and Apple or Google |
| Anonymous counters | Daily totals of a fixed list of events, such as "the Plus offer opened from a paper", "a purchase started" or "a bill was shared". Each total holds the event, the day, the platform (iOS or Android) and the app version. No name, email address, account id, device id or IP address | Your device |
| Emails to us | Your email address and message | You |
Your phone sends each counted event to our server while you are signed in. The server checks the session so nobody can send made-up numbers. It then adds one to that day's total and writes down nothing about who sent it. To stop one account from inflating a number, the server counts each account's events for one minute, in memory only. The daily totals cannot be linked to any person, so they are not personal data. The check of your session is, and section 3 gives its legal basis.
Some data about you may come from other people. A friend who records a meal you were at enters who sat at the table and the scores given there, including yours. If you have no account, the friend types a name for you. We use that data for the same purposes and on the same legal bases as data you give us yourself. If you later join Krokiet through an invite link, you take those scores into your own account and this policy applies to you in full.
The website krokiet.app sets no cookies and runs no scripts. When you open a page, our server receives your IP address and browser details so it can send the page back. It keeps no access log.
The articles below are articles of the GDPR.
| Purpose | Data | Legal basis |
|---|---|---|
| Create your account, sign you in and send sign-in emails | Account, Apple or Google sign-in, sign-in and sessions | Performance of the contract, Art. 6(1)(b) |
| Record meals, scores, photos and friends, and let friends see them | Meals, dish photos, account | Performance of the contract, Art. 6(1)(b) |
| Record people without an account in meals, using the name a friend types | Meals | Legitimate interests, Art. 6(1)(f), of our users in keeping a full record of who ate what at their table |
| Show places near you and add places to the map | Location, places you add | Performance of the contract, Art. 6(1)(b) |
| Send notifications when a friend sends you a request, accepts yours or adds you to a meal | Notifications, account | Performance of the contract, Art. 6(1)(b). The app sends nothing until you allow notifications on your phone |
| Read dish names and prices from menu photos with OpenAI | Menu photos | Performance of the contract, Art. 6(1)(b). When you photograph a menu, you ask us to read it |
| Protect accounts and limit abuse, including sign-in limits and ten menu scans a day | Sign-in and sessions, menu photos | Legitimate interests, Art. 6(1)(f), in preventing account takeover and abuse |
| Find and fix bugs, and deliver app updates | Crash reports, bug reports, update checks | Legitimate interests, Art. 6(1)(f), in an app that works |
| Review reports and hold back filtered content | Reports, places you add, menu lines | Legitimate interests, Art. 6(1)(f), in keeping users safe. For notices of illegal content, also legal obligation, Art. 6(1)(c), under Regulation (EU) 2022/2065, the Digital Services Act |
| Keep daily backups | All data in the database | Legitimate interests, Art. 6(1)(f), in recovering from a failure |
| Keep your scores in meals other people were at after you delete your account | Meals | Legitimate interests, Art. 6(1)(f), in keeping other users' meal records complete |
| Answer data rights requests and complaints | Emails to us, account | Legal obligation, Art. 6(1)(c), under Articles 12 to 22 of the GDPR and Polish consumer law |
| Answer support emails | Emails to us | Performance of the contract, Art. 6(1)(b) |
| Serve the website | IP address, browser details | Legitimate interests, Art. 6(1)(f), in delivering the page you asked for |
| Sell Krokiet Plus, unlock it on your account and show its status in Profile | Krokiet Plus, purchase records | Performance of the contract, Art. 6(1)(b) |
| Count events in the app as anonymous daily totals, to learn which parts of the app and of the Plus offer work | The account id from your session, used only to confirm that a signed-in account sent the event and for the one-minute limit | Legitimate interests, Art. 6(1)(f), in improving the app without profiling anyone |
Where we rely on legitimate interests, you can object on grounds relating to your particular situation. Section 11 explains how.
We do not rely on your consent for any processing. Location and notifications need your permission on the phone, and you can turn either off at any time in your phone's settings. The rest of the app keeps working.
Krokiet makes no decision about you based solely on automated processing, including profiling, that has legal or similarly significant effects on you, as described in Article 22 of the GDPR. An automatic filter holds back new place names and menu lines that contain swearing, links or phone numbers. Only their author sees them until a person reviews them.
To create an account you must give an email address and a name. This is a requirement of the contract. Without them we cannot provide the service. No law requires you to give us any data.
Everything else is optional. Photos, menu scans, notifications and Apple or Google sign-in are your choice. Location is optional too, and the rest of the app works without it. The app asks for it once after your first sign-in, then only when you tap something that needs it. Your coordinates answer one request for nearby places, and we do not store them. The only location we store is the pin of a place you add by hand.
Your meals, scores and photos are visible to you and to the friends you have both accepted. A friend also sees scores that either of you entered for someone without an account. Your friends see the list of your friends, with their names and faces, so they can ask them to be friends too. Nobody else sees that list. Someone who shares a friend with you can see your name, your face and the friends you have in common, and can send you a friend request. There are no public profiles, no feed, no comments and no messaging.
Places added by hand and menu lines read from photos are visible to all Krokiet users, without the name of the person who added them.
If you send an invite link to someone you scored at your table, whoever opens it sees the name you typed for them, your name and how many scores are waiting. The link works once and expires after seven days.
A person you report is not told who reported them.
Besides the users described above, the recipients of your data are the service providers in section 6 and the companies in section 7. We disclose data to public authorities only when the law obliges us to.
These companies process personal data on our behalf and only on our instructions. Each is bound by a data processing agreement under Article 28 of the GDPR. DPF is the EU-US Data Privacy Framework and SCCs are the standard contractual clauses. Section 8 describes both.
| Provider | Purpose | Data | Location | Safeguard |
|---|---|---|---|---|
| DigitalOcean | Server and database | All data except photos | Frankfurt, Germany | DPF and SCCs |
| Cloudflare (R2) | Photo storage and database backups | Dish photos, backups | Western Europe | DPF and SCCs |
| Resend | Sign-in emails, and report emails to us | Email address, name, report content | Ireland | DPF and SCCs |
| OpenAI | Reading menu photos | Menu page images | United States | DPF and SCCs |
| Sentry | Crash reports from the app and errors on our server | Crash reports | Germany | DPF and SCCs |
| Expo (650 Industries) | App update checks and sending notifications | System version, app version, install id, push tokens, notification text | United States | SCCs |
| GitHub | Running the nightly backup job | Database backup, in transit only | United States | DPF and SCCs |
| RevenueCat | Checking purchases with Apple and Google | Account id, purchase records | United States | SCCs |
Krokiet asks OpenAI not to store menu photos. OpenAI does not train its models on API data, and may keep a request for up to 30 days to monitor abuse. Anything else in the frame goes to OpenAI too, so point the camera at the menu, not at people.
Expo passes each notification to Apple or Google, which deliver it to your phone.
These companies are not our processors. Each acts as a separate controller for its own processing, and its own privacy policy applies.
OpenAI, RevenueCat, Expo and GitHub process data in the United States. DigitalOcean, Cloudflare, Resend and Sentry process it in the EEA, but they are US companies and may be able to access it from the United States.
For these transfers we rely on one or both of two safeguards. The first is the EU-US Data Privacy Framework, for providers certified under it, on the basis of the European Commission's adequacy decision of 10 July 2023 (Implementing Decision (EU) 2023/1795). The second is the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914. The table in section 6 shows the safeguard for each provider. You can ask us for a copy of the standard contractual clauses.
| Data | Period |
|---|---|
| Account and everything you record | Until you delete it or your account |
| Sign-in codes | 10 minutes, never included in backups |
| Sessions, with IP address and device description | 30 days after last use, or until you sign out or delete your account |
| Sign-in attempt counters | In memory, under one minute |
| Push tokens | Until you sign out on that phone or delete your account, or until Expo tells us the app is gone from the phone |
| Per-account limit on the anonymous counters | A few minutes, never saved to the database |
| Anonymous counters | Indefinitely, as they hold nothing about anyone |
| Krokiet Plus on your account | Until you delete your account |
| Purchase records at RevenueCat | Until you delete your account. We delete them at RevenueCat along with it |
| Menu photo images | Not stored by us. Up to 30 days at OpenAI |
| Text read from menu photos | As part of the restaurant's menu in Krokiet |
| Invite links | Until used, or seven days |
| Messages to us | 3 years from the last message about the same matter |
| Reports | While the reporter's account exists, then kept without a link to the reporter |
| Crash reports | Up to 90 days at Sentry, then deleted |
| Server system logs | Rotated by size. The server keeps no access log, and the app server logs only errors |
| Database backups | 90 days |
We use a backup only to recover from a failure. If we restore one, we apply again every deletion made after the date of that backup.
In the app, open Profile, tap Delete my account, then Delete it permanently. Deletion is immediate and cannot be undone.
We delete your account, email address, name, face, friend code, sessions, push tokens, the link to your Apple or Google account, your friendships, your purchase records at RevenueCat and every photo you took, image files included. Meals that were yours alone and scores that nobody else could see are deleted too.
Data that is part of other people's meals stays, with no link to you.
If you want these remaining scores deleted as well, email us and we will delete them. When a meal is deleted, its photos and their files are deleted with it.
Deleting your account does not cancel a Krokiet Plus subscription. Cancel it first in your App Store or Google Play settings, or it keeps renewing. Apple and Google keep their own record of the purchase, so you can bring Plus back on a new account with "Restore purchase" on the Krokiet Plus screen.
Under the GDPR you have the right to
These rights apply as far as the GDPR provides. Using them is free of charge.
To use a right, email us. The app has no export button, so we send copies of your data by email. We answer within one month of receiving your request. For complex or numerous requests we may extend this by two more months, and we will tell you within the first month (Article 12(3)). If we have reasonable doubts about who is asking, we may ask you to confirm the request from the email address on your account.
You have the right to lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, or with the supervisory authority in the EU country where you live or work, or where you believe the infringement took place (Article 77).
You must be at least 16 years old to use Krokiet, as the terms of use also state. Article 8 of the GDPR sets 16 as the age from which a person in Poland can consent to an online service on their own, and we use the same age as our minimum. If we learn that a user is under 16, we delete the account. If you believe someone under 16 has an account, email us. Krokiet is not directed at children under 13. If we learn that an account belongs to a child under 13, we delete it, as we do with any account of a person under 16.
We are based in Poland, so the GDPR and the rest of this policy apply to every user, wherever you live. This section adds what the privacy laws of some other countries ask us to tell you. It takes away none of the rights in the other sections.
To run Krokiet we send personal data to the providers in section 6. This table names each recipient, the country where it processes the data, what it receives and why.
| Recipient | Country | Data | Purpose |
|---|---|---|---|
| DigitalOcean | Germany | All data except photos | Server and database |
| Cloudflare (R2) | Western Europe | Dish photos, backups | Photo storage and database backups |
| Resend | Ireland | Email address, name, report content | Sign-in emails, and report emails to us |
| Sentry | Germany | Crash reports | Crash reports from the app and errors on our server |
| OpenAI | United States | Menu page images | Reading menu photos |
| Expo (650 Industries) | United States | System version, app version, install id, push tokens, notification text | App update checks and sending notifications |
| GitHub | United States | Database backup, in transit only | Running the nightly backup job |
| RevenueCat | United States | Account id, purchase records | Checking purchases with Apple and Google |
DigitalOcean, Cloudflare, Resend and Sentry are US companies and may be able to access the data from the United States. The data travels over the internet, encrypted with TLS, each time you use the feature it serves. The database backup goes once a night, and a crash report goes to Sentry when the app crashes or our server hits an error. Each provider keeps it for the periods in section 9. These transfers are needed to provide the service. If you do not want one, you can stop using the feature behind it, such as menu scans, or delete your account.
Switzerland. Under the Federal Act on Data Protection, Germany, Ireland and the other EEA countries give adequate protection. For the United States we rely on the Swiss-US Data Privacy Framework for providers certified under it, and otherwise on the standard contractual clauses in section 8.
Japan. Under the Act on the Protection of Personal Information, the EEA has an adequacy finding from Japan's Personal Information Protection Commission. Providers in the United States process data under contracts that require GDPR-level protection, and we rely on those contracts as the measures the Act asks of a recipient abroad. The United States has no general federal privacy law. Sector rules and the laws of some states cover privacy there. Section 12 describes our security measures.
South Korea. The table gives the recipient, country, data and purpose of each transfer that the Personal Information Protection Act asks for. The paragraph under it says when and how the data is sent and how to refuse. Section 9 says how long each recipient keeps it.
Under Brazil's General Data Protection Law, the LGPD, the person in charge of processing personal data, the encarregado, is Artur Witkowski, at contact@krokiet.app. Write to that address to use your rights under Article 18 of the LGPD. You can also complain to the National Data Protection Authority, the ANPD.
Residents of some US states, such as California, Virginia and Colorado, have rights under state privacy laws. They can ask what personal data we hold about them, get a copy, correct it and delete it. They can also opt out of the sale or sharing of their data, of targeted advertising and of profiling. We do none of those things. We do not sell or share personal data, we show no ads and we profile nobody. To use any right, email us. Using it does not change how we treat you. If we refuse a request, you can appeal by replying to our answer.
If you live in India or in any other country, send any question or grievance about your data to contact@krokiet.app. Artur Witkowski handles grievances and answers within one month. You can also complain to the data protection authority in your country.
The date at the top of this page shows when this policy last changed. If we make a material change, we will email you before it takes effect.
Artur Witkowski
ul. Stefana Batorego 23/7, 81-365 Gdynia, Poland
NIP 5862405430, REGON 528542614
Write to us in English or Polish. We answer support email within two business days and data rights requests within one month.