1. Who we are
Jarbake is made by Shon Pazarker, an individual, working under the name Equival, based in Israel ("we", "us"). We are the controller of your personal data. Equival is a working name, not a registered company.
- Contact for anything privacy-related: [email protected], telephone +972 53-430-9006
- Postal address: Yotveta 2/29, Holon 5850003, Israel
- We have no data protection officer (no legal duty to appoint one for this game).
2. The short version
- The game is free, has no ads and no purchases.
- We do not sell your data and do not track you across other apps or sites. We do not use the advertising identifier.
- You can play as a guest. You can sign in with Apple or Google to keep your progress if you change phone. Sign-in is not offered when your device says you are under 13.
- Usage statistics and crash reports are off until you say yes, are only offered if your phone says you are 16 or older (or does not tell us your age), and you can change your mind any time in Settings > Privacy.
- When the game starts it reads one small public settings file from our website. That request carries no account, no analytics ID and nothing from you (section 3).
- You can delete your account and your saved progress inside the game.
3. What we collect, why, and on what basis
| What | Why | Basis |
|---|---|---|
Game settings file (no identifiers). Each time the game starts it requests https://equival.io/games/jarbake/app-config.json and keeps the last copy on your device. The game adds no account ID, analytics ID or device ID, no query string and no custom header. Like any website, our hosting provider (Cloudflare) sees the IP address and standard request details of the connection. Cloudflare may keep technical logs for security and running its network under its own terms and retention, which we do not control. We do not receive, store or use those logs for anything else. This request happens before you answer the privacy question, and for every player including a child. |
Keep the game safe and working: a minimum app version, turning a feature or pack off if it proves unsafe, an optional maintenance message. | Our legitimate interest in keeping the game safe and working: we need to be able to ask for an update or switch off a feature that turns out to be unsafe. The request carries no account, analytics or device ID, and we do not keep your IP address. We treat it as strictly necessary for the game you asked to play, so it does not ask for consent. You can object at any time (section 8); the game also plays offline with built-in settings. |
| Account ID. A random ID created by our account service (Google Firebase Authentication) when you sign in with Apple or Google. If you play as a guest, no account is created on our servers: your progress stays on your device only. Not offered if your phone says you are under 13. | Keep your progress and link it to you across devices. | Providing the game feature you asked for (contract) |
| Sign in with Apple: Apple's user ID for our app. The app asks Apple for no name and no email. Apple may still pass an email address (including Apple's private relay address) in the sign-in token; if it does, Firebase Authentication may store it. We never read it, show it or use it. | Sign you in. | Contract |
| Sign in with Google: your Google account ID, plus the email address, name and profile photo link Google returns (the standard Google sign-in profile: email and profile). The game asks for no other Google permission and does not read your contacts, calendar, Drive or any other Google data. We do not show or use your email or name in the game. | Sign you in. | Contract |
| Saved progress (levels, stars, boosters, unlocked items, with a backup of an older save kept 30 days) stored in Google Cloud Firestore (Europe multi-region "eur3": Belgium and the Netherlands, with a witness copy in Finland) once you have signed in. Guests keep progress on the device only. | Cloud save and restore. | Contract |
| A "signed in earlier" flag on your device. A yes/no value with no ID, provider or email in it. Written when a sign-in succeeds and removed when you sign out or delete your account. | So that a phone you signed in on earlier starts your account's services again at launch instead of treating you as a guest. | Contract |
| Sign-in service start-up (Google Firebase Installations). The sign-in and cloud-save services are Google Firebase services. The game starts them only (a) when you start a sign-in, (b) when this phone's flag above says you signed in earlier, or (c) after you tap Allow. Starting them can register this app installation with Google's Firebase Installations service, which creates a random installation ID kept by Google and by the app. On iOS our test saw this registration happen once on a fresh install, and it still happened with Firebase's data-collection setting switched off. If you start a sign-in before you have answered the privacy question, that registration can therefore happen before your answer. It does not start usage statistics, crash reports or the server settings download. They stay off until you tap Allow. Nothing from Firebase starts for a player whose phone says they are under 13, except deleting an account created before the age answer. | Provide the sign-in and cloud save you chose. | Providing the sign-in and cloud save you asked for (contract). Because you started the sign-in, we treat this registration as strictly necessary for that service. We use it for nothing else until you tap Allow. |
| Age range (Apple Declared Age Range), iOS only, where the phone supports it. On first launch the game may ask Apple's system sheet for your age range. If you share it, only a coarse group is kept on your device: under 13, 13 to 15, 16 or 17, or 18 and over (as an on-device flag, never the exact age). We never send it to our servers or to Google, never put it in statistics, crash reports or logs, and never share it with anyone. If you decline, or the phone does not support it, the game only remembers that the question was asked. The answer stays on your phone until you uninstall the app, and signing out or deleting your account does not remove it, for child protection (section 6). Android does not use this feature in this version. | Protect children: under 13, the game offers no sign-in and starts no Google service (except deleting an account created before the age answer); under 16, it does not ask for consent to statistics or crash reports. | Our legitimate interest in protecting children: we use the band only on your device to keep sign-in and statistics off for players who are too young for them. It never leaves your device. You can object by declining Apple's question (the game then only remembers it was asked) or by uninstalling the app, which removes the record. |
| Usage statistics (only if you allow): events such as level started, level won, moves, time, app version, device model, OS version, language, approximate country and city worked out from your IP address (as Google states, the IP address itself is not stored by Google Analytics), and a random app-instance ID created by Firebase. | Understand which levels are too hard, fix balance, improve the game. | Your consent |
| Crash reports (only if you allow): stack traces, the text of error messages (app-generated, holding no name or email), device and OS details, app version, the Firebase installation ID and a crash-reporting ID. | Find and fix crashes. | Your consent |
| Game settings from our server (Firebase Remote Config; only if you allow): your country code, language, time zone, OS version, app ID. | Tune difficulty and seasonal content. Without your consent the game uses built-in settings and the public settings file above. | Your consent |
We do not collect your contacts, photos, precise location, health data, or advertising identifier, and we do not use your account ID, email or name inside usage statistics or crash reports. Statistics and crash data (Google Firebase Analytics, Crashlytics, Remote Config) are tied to a random analytics ID, not to your account (Firebase Authentication and Firestore), by us, and are kept separate from it. We cannot see how Google handles IDs internally, so this describes what we do.
Providing an account is optional. If you do not give us the data needed for sign-in, you can still play as a guest. Allowing statistics and crash reports is optional and never required to play.
Automated decisions. We do not make decisions about you by automated means that have legal or similarly significant effects, and we do not profile you.
Reminders and the rating request
If you turn reminders on (the game asks only after you have won a few levels, and the system asks you again), the game schedules at most two kinds of reminder on your phone itself: a comeback nudge after a day away and a heads-up about Winter Lights. The schedule is made and kept on the device. We send no message from a server, and we do not receive your answer to the permission question. The game may also show the Apple or Google system rating dialog after a winning streak. That dialog is run by Apple or Google; we do not see your rating or whether you gave one, and they handle it under their own policies. We can switch both off for everyone through the public settings file above.
4. Who receives your data
-
Google (Google Ireland Limited and Google LLC) as our processor, for Firebase Authentication and Cloud Firestore (sign-in, your account ID and the email, name and profile photo link if the provider returns them, saved progress), for Firebase Installations (the installation ID described in section 3), and, only if you allow, for Firebase Analytics, BigQuery (where we store exported statistics), Crashlytics and Remote Config. Google may only use it to provide those services to us. Account data and statistics/crash data are separate sets and we do not link them.
-
Cloudflare, Inc. as our processor, for two tasks. (1) Hosting the public settings file the game reads at start; it sees your IP address like any web host (section 3). (2) Deleting accounts: for every account deletion, whether you start it or the app runs it for a child, a Cloudflare Worker that we run at
api.jarbake.equival.ioreceives one request (POST /v1/account/delete). It carries your Firebase sign-in token (it holds your account ID, your sign-in provider and your email if there is one) in the request header and, when there is one, Apple's one-time authorization code in the request body. The Worker checks the token, deletes your cloud save documents and your Firebase Auth user through a Google service account kept as a Worker secret, and, when it has the code, revokes the link with Apple. The request carries no age and no reason, and the server does not record why an account is deleted, so the age answer never leaves your phone. The Worker keeps neither token nor code. It limits how often one account can call it, keyed to your verified account ID inside Cloudflare's rate limiter. It writes only a request number, the route and the result to its log, never a token, code, account ID or IP address. -
Apple and Google, as account providers, when you choose to sign in with them. They have their own privacy policies and are separate controllers for your Apple or Google account. When you use Sign in with Google, Google's sign-in software in the game may collect the data its own privacy manifest declares, under Google's privacy policy. We request only the default email and profile scopes and never store a phone number.
-
Authorities or courts, if the law requires it.
We do not sell your personal data, do not share it for advertising, and do not share it with data brokers.
5. Transfers outside your country
We are in Israel. The game is not offered in the EU, EEA, UK or Switzerland. The steps below are the onward processing by our providers.
- Saved progress: stored in Google Cloud Firestore in Europe (multi-region "eur3": Belgium and the Netherlands, with a witness copy in Finland). Google may copy it within those countries for backup and reliability, and Google staff outside Europe may be able to access it for support.
- Accounts: Firebase Authentication runs only from Google data centres in the United States, so your account record (ID, email, name, sign-in details and sign-in IP logs) is processed in the United States even though your saved progress is stored in Europe.
- Installation ID, statistics and crash data: processed by Google and can be processed in any country where Google operates, including the United States. Google does not let us choose a location for these.
- Cloudflare, Inc. is a US company; access from outside Europe is possible.
Our providers act for us under their data processing terms: Google's Cloud Data Processing Addendum and Firebase Data Processing and Security Terms, and Cloudflare's Data Processing Addendum. They use sub-processors, listed at firebase.google.com/terms/subprocessors, cloud.google.com/terms/subprocessors and cloudflare.com/gdpr/subprocessors. Transfers to the United States rely on those terms, which include standard contractual clauses. You can ask for a copy of the safeguards we use by writing to [email protected].
6. How long we keep it
| Data | Kept |
|---|---|
| Account (Firebase Authentication) and saved progress (Cloud Firestore) | Until you delete your account. Then the account and the save document are deleted from live systems, and from Google's backups within 180 days (Google's stated maximum; some of it is usually gone sooner). |
| Sign-in logs (Google) | Sign-in IP addresses are kept by Google for a few weeks. |
| Firebase installation ID (Google) | Kept by Google until the installation is deleted. When you withdraw consent or delete your account, the game asks Google to delete it. Google then removes related data from live and backup systems within 180 days. If a sign-in service is still in use, Firebase may create a new installation ID. Google also deletes an installation it has not heard from for about 270 days, though it does not promise this as a fixed rule. Deleting the game from your phone does not by itself delete the ID at Google. |
| Apple token and sign-in token (Cloudflare Worker) | Not stored. The deletion service logs only a request number, the route and the result code, never your token, code or ID; those logs are kept up to 7 days (3 days on Cloudflare's free plan). A count of requests with no identifiers is kept 3 months. |
| Settings-file requests (Cloudflare) | Set by Cloudflare under its own terms; we do not hold the IP addresses. |
| Usage statistics in Google Analytics | 2 months event-level retention. |
| Exported statistics in BigQuery | 60 days, then deleted automatically. |
| Crash reports | 90 days in Google's live systems, after which Google starts removing them; removal from Google's backups can take up to a further 180 days. |
| Records of your privacy choice and the signed-in-earlier flag | Stored on your device. Deleting the game removes them. When you delete your account the privacy choice is removed and asked again at the next launch. |
| Your age answer (an "asked" flag and the age group) | Stored on your device only, until you uninstall the app. Signing out or deleting your account does not remove it. The reason is child protection: if it were erased, a player whose phone said "under 13" could be offered sign-in or statistics again just by answering Apple's question differently. It is never synced, sent, logged, or tied to your account or analytics ID. |
| A temporary deletion marker | If an account deletion cannot finish (for example you are offline), the game keeps a marker on the device until it finishes. It holds a one-way scrambled tag of your account ID, made with a random salt, so the game can finish deleting the right account. It never leaves the device and is removed when the deletion finishes. |
If you decline statistics, nothing is collected. If you turn statistics off later, collection stops; data already collected is kept until its period ends unless you ask us to delete it (section 8).
7. Account deletion
In the game: Settings > Account > Delete account. You are shown what is deleted: your account, your levels and
stars, your boosters, and your settings and stats on this phone. For a signed-in account, the game first asks you
to confirm your sign-in on the phone (for Sign in with Apple this yields Apple's one-time code), then sends one request
to our server (POST /v1/account/delete) with your sign-in token and, when there is one, that code. The server deletes
your saved progress documents in Cloud Firestore and your Firebase Authentication account, and for Sign in with Apple
revokes the link with Apple. Every account deletion uses this same request, including the one the app runs for a child
(section 9), and the request carries no age and no reason: the server does not record why an account is deleted. Backups are erased within 180 days. Deletion needs an internet connection; if it is interrupted,
the game finishes it the next time it starts. As part of deleting, the game turns off statistics and crash reports,
asks Google to delete the Firebase installation ID, and resets the analytics ID before it removes its record of your
choices, so the next launch asks again and collects nothing before your answer. A guest has no account on our servers;
deleting the guest data removes it from the device, except the age answer, which stays until you uninstall the app (section 6). If you reinstall as a guest, progress cannot be restored.
Past statistics. Statistics and crash data are not tied to your account, so deleting your account does not by itself delete them. We cannot find that data by name. Before the game resets the analytics ID (when you withdraw consent or delete your account) it shows you the ID with a Copy button, with the line "Send this ID to [email protected] to erase past statistics". If you send us that ID we ask Google to delete the data for it and do so within one month. Otherwise it is deleted automatically after the periods in section 6. Once the ID is reset we can no longer find your data.
8. Your rights
Contact [email protected]. We answer within one month.
- Every player: access to what we hold about you, correction, deletion, objection (including to anything we do under our legitimate interests, section 3), withdrawing consent at any time (Settings > Privacy, as easy as giving it), and complaining to the data-protection authority where you live.
- Israel (Privacy Protection Law, as amended by Amendment 13): you may inspect the data we hold about you, ask us to correct it (and to delete it where the law allows), and complain to the Privacy Protection Authority. You are not legally required to give us data to play.
- California and other US states: to know what we collect, delete it, and correct it. We do not sell or share personal information for cross-context advertising. We do not discriminate for using your rights. See also section 9.
- Statistics and crash data: we cannot find your data by name. To exercise a right over it, send the "analytics ID" shown in Settings > Privacy (copy it before you reset it); you can also tap "Reset" to start a new analytics ID so future data is detached from past data. We then act within one month.
9. Children
Jarbake is made for a general audience. It is not directed to children under 13 and we do not knowingly collect personal information from them, except the technical request data described below.
Age check. On an iPhone that supports Apple's Declared Age Range, the game asks Apple once for your age range. If you or your parent shares it, only a coarse group is used. It stays on your phone: we never receive it, send it, log it, or put it in statistics. In places where the law requires Apple to share an age category with apps (for example Texas, Utah and Louisiana), we use it only to switch off the features below and never share it with anyone.
If the answer is under 13: Sign in with Apple and Sign in with Google are not offered, so no account or cloud save is created and nothing is sent to our account service or to any Google service, except deleting an account created before the age answer. Usage statistics, crash reports and server game settings are off and are not offered. You can still play as a guest; your progress stays on the device. If a phone had been signed in before the answer came, the game first shows you the note "Because of the age setting on this device, your account is being removed. Your progress stays on this phone." and, if you used Sign in with Apple, an optional button, "Also remove the Apple link" (it opens Apple's sheet and lets the server remove the link). The note shows before the deletion runs, so your sign-in token is still valid for that. Then the game deletes the account: your cloud save and your account at Google, through the same single account-deletion request to our server that every deletion uses, which carries no age and no reason. You keep playing as a guest. The deletion never waits for the Apple button. If you skip it, remove the link yourself in Settings > [your name] > Sign-In & Security > Sign in with Apple. If that deletion cannot finish at once (for example you are offline), the game signs the account out on the device, keeps a pending deletion, and refuses another sign-in until it is done.
If the answer is 13 to 15: we do not ask for your consent to statistics or crash reports, and both stay off. This is a protective default: in many countries a person under 16 cannot give that consent themselves, so we use 16 everywhere rather than keep a list. The game plays the same. You may sign in if you wish: that is a service you ask for.
If the answer is 16 or over, or we do not know your age: on Android, older iPhones, or if you decline Apple's question, the game cannot tell your age and treats you as 16 or over, so it asks the privacy question. Parents of younger children should use their phone's own parental controls.
What we still receive from every player, including a child: when the game starts it asks our website for the public settings file. Our hosting provider, Cloudflare, sees the IP address of that request. An IP address is a "persistent identifier" under US children's privacy law (COPPA). We use it only to deliver the file and keep the service working and secure ("support for the internal operations" of the service). We do not use it to contact anyone, build a profile or show ads, and we do not store it ourselves. Cloudflare may keep request logs for its own security and network purposes under its own terms and retention, which we do not control.
Parents. If you think a child gave us personal information, write to [email protected], +972 53-430-9006, Yotveta 2/29, Holon 5850003, Israel. We will review it, delete it and stop any further collection. You can ask to review or delete anything we hold about your child.
How long we keep children's information. If an account was created before the age answer, its data is deleted through our server as soon as the app learns the answer. It is gone from Google's backups within 180 days. Until the deletion is confirmed it is kept only so the deletion can finish, and the app retries on every launch. The request to our server is the same single account-deletion request every deletion uses, which carries no age and no reason; the server does not record why an account is deleted, and the age answer still never leaves your phone. After that we keep none on our servers for a player the age answer marks under 13. Request logs at our hosting provider are kept under Cloudflare's terms (section 3). We do not keep anything longer than needed to deliver the file.
Changes. If we add ads, purchases or new kinds of data, we will update this policy, and where state app-store laws require it we will tell Apple so a parent can be asked again before a child keeps using the app.
US state app-store laws (Texas, Utah, Louisiana)
Jarbake is available in Texas, Utah and Louisiana. Where those states' app-store laws apply, Apple gives apps an age category. We set the app's age rating and use the category only to enforce age restrictions, comply with the law and apply safety defaults (switching off features as above). We never share it with anyone, and we do not enforce our terms against a minor whose parent has not consented through the store. Free apps with no purchases are covered by these laws.
10. Security
Data travels over encrypted connections and is encrypted at rest by our providers (Google Firebase and Google Cloud, and Cloudflare). No system is perfectly secure. If a breach puts your rights at risk we will notify you and the authorities as the law requires.
11. Changes
We will change this policy when the game changes. If we add a new use of data (for example ads or purchases), we will update this page, change the date at the top and ask for your consent again where the law needs it.
12. Contact
Shon Pazarker, trading as Equival, Yotveta 2/29, Holon 5850003, Israel. Email: [email protected]. Telephone: +972 53-430-9006.