Privacy policy

Who we are

Food Roulette is made by Kliker Studio, the name Viktor Komaretskii PR Vrcin publishes under. We decide how your personal data is used, which makes us its controller.

Viktor Komaretskii PR Vrcin

Address

Moravicka 2A, 11224 Vrcin, Grocka, Serbia

Registration number (matični broj)

67917707

Tax ID (PIB)

114871442

Email

support@klikerstudio.com

What we collect and why

The app doesn't ask for your location or contacts, doesn't collect your files or device name, and doesn't use the camera. It has no push notifications, no advertising SDKs, no payments and no analytics other than Firebase.

Using the app without an account

You don't need an account. The first time you open the app, it creates a random secret that identifies your account, which stays anonymous until you sign in. Your phone holds the secret in encrypted storage, and we keep only a hash of it, so we can recognise your phone and sync your data.

How long: until you delete your account.

Signing in with email

Signing in is optional. If you choose Sign in with email, we keep your email address so we can sign you in. Resend delivers the email with your code, so it gets your address too. The other members of your household see your address.

A code works for 10 minutes, and an address can ask for at most 5 codes an hour. We keep a record of each code we send, with the code stored only as a hash.

How long: your address and the code records stay until you delete your account. If an address asked for a code but never signed in, nothing removes its records on its own: they stay until the person asks us to delete them.

Your name

You can add a name in Profile if you want to. The other members of your household see it.

How long: until you remove it or delete your account.

Your dishes and plans

We keep your dishes with their recipe texts and notes, your ingredients, saved week plans and daily targets, so the app can sync them. We also keep which week plan you're cooking from and since when, its dates, which shopping-list items you've ticked and when, and which of the app's pictures you picked for each dish and ingredient. Your household sees the plans you make as household plans.

Each time you add a dish, an ingredient, a plan or a household, share or import something, or ask for a change to a cooking plan, our server keeps its reply, so that sending the same request twice can't create a duplicate. The reply can hold the item you saved or the text you sent.

How long: your dishes and plans stay until you delete them or your account. A stored reply stays for at least 24 hours. After that it goes the next time you do one of those things, or when you delete your account, so it can outlast something you deleted.

Telling the app how you cook

You can type or paste a recipe, or say how you cook a dish, and ask in your own words for changes. A language model running on our own server turns what you send into the dish's cooking plan: portions, ingredients, steps, a cooking time and a video link if you gave one. If the text gives no cooking time, the model may estimate one.

We keep the cooking plan with the dish, and each text you send. If formatting fails, the plan also keeps the text that failed, so you can see it.

How long: a cooking plan stays until you delete it, its dish or your account. Each text you send is kept while it waits for the model, and for 7 days after it's formatted, fails or you replace it, longer if the cooking service was off. A text that failed also stays on the plan until you send something new, edit the plan or delete it. A change you ask for can also stay in a stored reply (see “Your dishes and plans”).

Talking to the app

The app uses the microphone only after you tap the mic and allow it. It never saves your voice and never sends it to our server. Your phone's speech service turns what you say into text, and the app treats that text like anything you type: it reaches our server only when you tap Save.

The speech service is Google's on most Android phones. The service decides whether your voice is handled on the phone or sent online, under its provider's own privacy terms. You can take back the app's access to the microphone at any time in your phone's settings, and keep typing instead.

Watching videos

If a cooking plan has a YouTube link, the app shows the video's thumbnail, which it loads from YouTube before you tap anything. When you tap it, the video plays in YouTube's own player inside the app, and YouTube may show its own ads in it. Both connect your phone to Google, which receives your IP address and whatever its player collects. The player may also store cookies or similar data on your phone. Links to other sites open outside the app.

The player uses YouTube API Services. By watching a video in the app, you agree to the YouTube Terms of Service, and Google's privacy policy applies to what YouTube collects.

Households

If you create or join a household, we keep its name, members, owner and invite code, its week plans, who cooks each meal and which shopping-list items are ticked. We also keep the members' dishes those plans use, with their recipe texts, notes and ingredients.

Every member sees all of this, along with each other's email addresses and names, and it's saved in the offline copy on each member's phone. Members also see those dishes' cooking plans, with the text sent for a plan while it waits to be formatted or after formatting failed.

How long: a household lasts until its last member leaves. It's then deleted, and its week plans become that member's own. Your dishes go with your account. Plans you made as household plans belong to the household and stay with it when you leave or delete your account.

Sharing

When you share a dish, an ingredient or a week plan, we keep a copy of it under a code. The copy doesn't carry your name or email address. Anyone with the code or link can see it and copy it.

A shared household plan carries copies of every member's dishes in it, so one that another member shares includes yours. Shared dishes, on their own or in a week plan, carry their cooking plans, but not the texts you sent for them.

How long: until you revoke the share or delete your account. A household plan another member shared keeps its copies of your dishes until that member revokes it or deletes their account. Copies people already saved stay with them.

Usage statistics and crash reports

The app sends these to Google so we can see how the app is used and fix what breaks.

Firebase Analytics is part of Google Analytics. It collects usage events on its own, such as first open, sessions, screen views, engagement and app updates. With them it sends Google the app-instance ID, the advertising ID where Android provides it, the device model, the Android and app versions, the language, and the country, worked out from your IP address. We add no events of our own and no user ID, so this data isn't linked to your account. The app has no setting to turn it off. See How Google uses information from sites or apps that use our services.

Firebase Crashlytics gets crash and error reports from the app's release version. A report holds the stack trace (the place in the code where the problem happened), the device model, the Android and app versions, an installation ID and technical log lines. It holds no email addresses, no names and nothing about your food.

How long: under Google's retention rules (crash data about 90 days).

What stays on your phone

The app keeps an offline copy of your dishes and ingredients with their cooking plans, your plans, targets and name, and your household members' dishes, email addresses and names. It also keeps its settings and any shopping-list ticks still waiting to be sent. Sign-in data sits in encrypted storage, and the pictures for the tiles and videos in a cache.

If Android's backup to your Google account is on, it includes all of this except the sign-in data and the picture cache.

How long: until you clear the app's data or remove the app.

Connecting to our server

Cloudflare carries all traffic to our domain, so it sees your IP address. Our server uses your IP address in memory to apply rate limits, which stop anyone sending too many requests.

The server's log records the time, the web address requested and the result of each request, with the address of our Cloudflare tunnel in place of yours. When a request goes over a rate limit, the log also records your IP address. That's the only time we keep it.

How long: the log lasts until the server is next updated. It lives only with the running server.

Backups

Every night our server copies the whole database into a backup on the same server. The last 14 nightly backups are kept, so a deleted account's data can stay in a backup for about two weeks, longer if the server was off some nights. A backup made by hand counts as one of the 14.

Emails you send us

Zoho Mail receives and stores what you send to support@klikerstudio.com. We keep it as long as we need to answer you and to keep a record of data requests.

This website

This website sets no cookies, and Cloudflare handles its requests. The website runs one script, Cloudflare Web Analytics, which counts visits and measures how fast the pages load. Each time you open a page, it sends Cloudflare the page's address, the address of the page that linked to it and how long the page took to load. From the request, Cloudflare also records your browser, operating system and type of device, and works out your country from your IP address.

The script sets no cookies and stores nothing on your device, and Cloudflare says it doesn't use it to fingerprint or follow individual visitors. We see only totals. The app doesn't use it.

Why we may use your data (legal basis)

We rely on two legal grounds:

• Providing the app you asked for: sign-in, sync, sharing, households and cooking plans.
• Our legitimate interest in keeping the app secure and working: rate limits, crash reports and usage statistics.

We don't use your data for advertising and don't sell it.

Who else handles it

• Cloudflare carries all traffic to our domain. Cloudflare's privacy policy
• Resend sends the emails with sign-in codes. Resend's privacy policy
• Zoho Mail receives and stores email sent to us. Zoho's privacy policy
• Google runs Firebase Analytics, Firebase Crashlytics and YouTube, provides speech recognition on most Android phones, and distributes the app through Google Play. Google's privacy policy, Privacy in Firebase

Our own server runs the API, the database, its backups and the language model. No outside AI service receives your dishes, your plans or the texts you send. The one exception is your voice, which your phone's speech service may send online (see “Talking to the app”).

These providers may process data outside your country, including in the United States, under their own data-protection terms.

Apart from us, these providers, your household and anyone with a share code or link, nobody else sees your data.

Security

• The app and this website work only over HTTPS.
• Our server stores install secrets, refresh tokens and sign-in codes only as hashes.
• The database can't be reached from the internet.
• On your phone, sign-in data is encrypted, and the rest sits in the app's private storage.

Your rights

Under Serbia's Law on Personal Data Protection (Zakon o zaštiti podataka o ličnosti), you can:

• see your data;
• have it corrected;
• have it deleted;
• get a copy of it;
• object to how we use it;
• ask us to restrict how we use it.

To delete your data, or to change or remove your name, use Profile in the app (see Deleting your account). For anything else, write to support@klikerstudio.com. We answer within 30 days.

You can also complain to the Commissioner for Information of Public Importance and Personal Data Protection (Poverenik, www.poverenik.rs), or, if you live in the EU, to your local data-protection authority.

Children

Food Roulette isn't directed at children under 13. If you're a parent and believe your child gave us an email address, write to support@klikerstudio.com and we'll delete the account.

Changes

We post changes to this policy on this page, with a new “Last updated” date.

Contact

For anything about your data or this policy, write to support@klikerstudio.com, or by post to Viktor Komaretskii PR Vrcin at the address under “Who we are”.

Technical details