Privacy Policy
In short. Tugloop has no account and no sign-in. Your progress is saved on your device. This version of the game shows no ads, offers no purchases and does not use your device's advertising ID. If you choose Accept on the privacy screen, Google Firebase records how levels are played and sends crash reports; if you choose Not now, it does not. You can change your choice at any time under Settings in the game.
1. Who we are
Tugloop ("the game") is published on Google Play by Capyful ("we", "us"). Capyful is the developer name of Ngô Phát Tài, an individual developer based in Viet Nam, who decides how the data described here is used (the "controller" under data protection law). Contact: capyfulstudio@gmail.com.
We do not run servers of our own. The services that receive data from the game are provided by Google, as described below. The game has no account system, and it never asks for your name, email address or phone number.
2. What stays on your device
These are stored in the game's own storage on your device and are not sent to us:
- your level progress and the coins you earn in the game ("coils");
- your settings (sound, music, vibration, board look, analytics on or off);
- your answer on the privacy screen;
- your Support ID, a random 8-character code created on your device (see section 8).
Uninstalling the game or clearing its storage deletes all of this, and we cannot restore it.
3. The privacy screen and your choices
- Before you answer. On first launch the game shows a privacy screen with links to this page and to the Terms of Use. Until you answer it, the game reads only what is stored on your device: it does not contact Firebase or any other service.
- Accept turns on Firebase Analytics (section 4) and Crashlytics crash reports (section 5).
- Not now leaves them off: no analytics events and no crash reports are sent, and events are not kept for later.
- After either answer, the game asks Firebase for game settings (section 6).
- Changing your mind. In Settings, Analytics: on / off switches analytics and crash reports. When you switch it off, analytics stops at once; crash reporting stops from the next time you open the game. A change applies from that moment on; it does not affect data already sent while your earlier choice was in place.
4. Analytics (Google Firebase Analytics), only after Accept
The game records these events:
| Event | What it contains |
|---|---|
| Level started / level ended | the level number, and whether it was won (or lost after running out of hearts and declining a revive) |
| Coins earned | how many coins were earned and where from (a win) |
| Firebase's automatic events | first open, session start, engagement time, screen views and app update |
Each event also carries the game version, device model, operating system version, language, and a country or region that Google works out from your IP address. Events are linked to an app instance ID that Firebase creates on your device. Analytics in this game does not read your advertising ID or your device's Android ID (the game does not ask for the advertising ID permission), and receives no advertising signals. The events contain no name, email address or Support ID.
We use these events only to see which levels are too hard or too easy and where players stop, so we can improve the game. We keep analytics data for 14 months. Google signals and the data sharing settings of Google Analytics are turned off for this game, so Google processes this data on our behalf as a service provider.
5. Crash reports (Google Firebase Crashlytics), only after Accept
If the game crashes or hits a serious error, a report is sent to Firebase Crashlytics: the technical details of the error (stack trace), the game's state at that moment, the game version, device model, operating system version, free memory and disk space, when the game was in the foreground, and a Crashlytics installation ID. We use crash reports only to find and fix bugs. Firebase keeps crash reports for about 90 days.
6. Game settings from the server (Google Firebase Remote Config)
After you answer the privacy screen, whichever answer you give, the game asks Firebase for updated settings. These settings control the minimum game version (if your version is too old, the game asks you to update from Google Play) and game options such as when a newer version is suggested. The request carries a Firebase installation ID, the game version, the device's language, time zone, country and operating system version. It carries no gameplay events, and it is used only to deliver these settings.
Updates through Google Play. After you answer the privacy screen, and each time you come back to the game, it asks the Google Play Store app on your device whether a newer version of Tugloop is available for you. If one is, Google Play's in-app update screen downloads and installs it, and the game asks you to update before you play on (the settings above can relax this). This check runs between the game and the Play Store app, under Google's terms; the game sends no data of its own for it, and if Google Play cannot be reached the game simply plays on.
7. Ads and purchases
This version of the game shows no ads, contains no advertising SDK and offers no purchases. If a later version adds ads or purchases, we will update this page and the Google Play "Data safety" section before that version reaches you (section 14), and the game will show you its new privacy text.
8. Your rights, deletion requests and the Support ID
Depending on where you live (for example under the GDPR in the EEA and UK, or the CCPA in California), you can ask to access, correct or delete personal data about you, to restrict or object to its use, or to receive a copy. We will not treat you differently for asking.
- To ask us: write to capyfulstudio@gmail.com. Contact us in Settings opens an email with your Support ID and game version filled in; in game version 1.0.0 that email is addressed to an older address, so please change the recipient to capyfulstudio@gmail.com before sending. We answer within 30 days.
- Deleting analytics data: if you accepted analytics, the email that Contact us opens also contains your Firebase app instance ID, a random identifier of this installation that Firebase already uses. Send it with your request and we will delete the analytics data linked to it through Google's deletion tools. If you chose "Not now", the email says "Analytics: off" and there is no analytics data to delete. Crash reports carry no such identifier and are deleted automatically after about 90 days; analytics records otherwise expire after 14 months. To stop new records, switch Analytics off in Settings.
- The Support ID only lets us recognise your messages; it is never sent with analytics or crash reports.
- Data on your device: uninstall the game or clear its storage.
- You may also complain to the data protection authority where you live.
9. Legal bases (EEA and UK)
| Use | Legal basis |
|---|---|
| Analytics and crash reports | Your consent (Accept), which you can change at any time in Settings |
| Game settings from the server | Our legitimate interest in running and tuning the game |
10. Who receives data, and where
Only Google receives data from the game: Google LLC and its affiliates (including Google Ireland Limited for users in the EEA and UK) as the provider of Firebase. Google may process data in the United States and other countries; transfers are covered by Google's data protection terms. We do not sell, rent or trade personal data for money.
11. Children
Tugloop is not directed to children under 13, and we do not knowingly collect personal data from children under 13 (or under the age of digital consent in their country). If you are a parent or guardian and your child plays the game, you can switch Analytics off in Settings and write to us with any question.
12. Security
Data sent by the game travels over encrypted connections (HTTPS) to Google. We hold no database of our own. Access to the Firebase console is limited to us and protected by two-step verification.
13. This website
This website uses no cookies, no scripts and no analytics. It is hosted on GitHub Pages, so GitHub's servers receive your IP address when you open a page, as with any website. See the GitHub General Privacy Statement.
14. Changes to this policy
If a new version of the game, or a change to its server settings, collects anything not described here, we update this page before that change reaches you, change the date at the top, and update the Google Play "Data safety" section to match. If the change needs your consent, the game asks you again.
15. Contact
Capyful — capyfulstudio@gmail.com