Tropic Tumble: Kitchen Merge
Privacy policy
A plain-English description of what the game collects, what it does not, and the small number of choices you have as a player.
The short version
Single-player, no account, tiny footprint
Tropic Tumble: Kitchen Merge runs on your phone, does not ask for an account, and does not require your email address to play. The data we do handle is limited to what the game needs to save your progress on your device, deliver anything you buy from the App Store or Google Play, keep the game stable, and, if you opted in, help us understand what parts of the game people enjoy.
This policy applies only to Tropic Tumble: Kitchen Merge, published by JPott Studios. It does not apply to any other product.
Topics
What the game collects
Tap any topic to open it. Each one describes a single piece of data and what we do with it.
Your game progress, stored on your device
Your kitchen, unlocked recipes, currency balances, event history, and settings are stored locally on your phone. This information does not leave your device unless you send us a support message and attach a save file, or unless your phone's platform-level cloud backup is enabled and includes app data. In that case the backup is between you and Apple or Google, not between you and us.
A random device identifier for save integrity
When the game first starts, it generates a random string of characters and stores it alongside your save. This identifier is not your name, your email address, your phone number, or any other real-world identity. It exists so that if you contact support with a save issue, we can match the file you send us against a specific installation of the game. It is not shared with advertisers.
Purchase receipts
When you buy coins, gems, a bundle, or a subscription, the App Store or Google Play sends the game a receipt. We validate that receipt with Apple or Google so that the item you paid for actually arrives in your kitchen. The receipt is stored so we can restore your non-consumable purchases on a new install.
It contains the product identifier and the transaction identifier, and it does not contain your credit card number or your billing address.
Crash reports
If the game crashes, the platform sends us a technical report about what the game was doing at the moment it crashed. These reports describe the code path and the device model, not you. They do not include your save contents, your messages, or your photos.
On iPhone, crash sharing is controlled by the Analytics and Improvements toggle in your phone's Privacy settings. On Android, it is controlled by the Usage and diagnostics toggle. If you turn those off at the system level, crash reports do not reach us.
Optional gameplay analytics
The first time you launch the game, we ask whether you are willing to share anonymous gameplay analytics. If you say yes, the game sends events such as "started a shift", "finished the tutorial", "opened the merge board", or "spent gems on an upgrade". Those events help us understand which parts of the game are enjoyed and which parts confuse people.
If you say no, or if you turn analytics off later in Settings, the game stops sending these events. Nothing about your saved progress, your device identifier, or your purchases is tied to a real-world identity as part of this stream.
Just as important
What the game does not collect
Your real name, email, phone, address, or birthday
The game never asks for any of these. There is no account, no login screen, and no profile. If you write to support, you have shared your email with us at that moment. Otherwise, we do not have it.
Your contacts, photos, camera, or microphone
Tropic Tumble: Kitchen Merge does not request permission to use any of these, and would not be able to read them even if you granted a system-wide permission to another app.
Your precise location
The game does not use GPS or Wi-Fi triangulation. There is no map, no nearby-players feature, and no leaderboard tied to your city.
Advertising identifiers for cross-app tracking
On iPhone we do not call the App Tracking Transparency prompt because we do not track you across other apps or websites. We do not sell your data. We do not share your data with data brokers. We do not run in-app advertising networks that profile you.
Health, wellness, or biometric data
This is a cooking game, not a wellness app. Nothing in the game connects to Apple Health, Google Fit, or any similar service.
The rest
Third parties, children, and your rights
Third parties we rely on
To ship the game to your phone and keep it running, we rely on a small number of platform providers. Each one only sees the data listed above, and only for the purpose described.
- Apple App Store and Google Play. Deliver the game to your device, process purchases, and handle refunds. Their privacy practices are described on their own sites.
- Crash reporting. A crash reporting service processes the technical crash logs described above.
- Optional analytics. If you opted in to gameplay analytics, an analytics service receives the anonymous event stream described above.
Children
Tropic Tumble: Kitchen Merge is a family-friendly game with no chat, no user-to-user messaging, and no user-generated content that can reach other players. We do not knowingly collect personal information from children under the age of thirteen, or under the equivalent age in your region.
If you are a parent or guardian and you believe your child has provided personal information to us, please write to jpottstudios@gmail.com and we will delete it.
Data retention
Purchase receipts are retained for as long as your platform account owns the associated non-consumable content, so that a restore can work. Anonymous analytics events are retained for up to two years. Crash reports are retained by the crash-reporting service under its own policy.
Your choices and your rights
- Turn off analytics at any time in the in-game Settings screen.
- Turn off crash reports from your phone's system settings.
- Delete your on-device save by clearing the app's data, or by uninstalling the game. See our data deletion page.
- Ask us to delete a server-side purchase record by emailing support. See the deletion page for what that request should contain.
Changes to this policy
If we change this policy in a meaningful way, we will update the date at the top and, where it is relevant to a currently offered feature, note the change on this page for at least ninety days. Small clarifications and typo fixes do not count as meaningful changes.