Same Same! — a matching game for toddlers, for Android.

Privacy Policy — Same Same!

Last updated: 2026-10-08
Applies to the Android app com.nikitapetrovapps.samesame.

Summary

Same Same! collects no data at all. The developer runs no servers, and the game sends nothing to anyone: it shows no advertising, contains no analytics and asks for no account. Everything the game remembers stays in its own private folder on the device.

The app plays fully offline. It holds the Android INTERNET permission for one reason only: Google Play needs the network to process the one-time in-app purchase and to offer app updates. Both go through the Google Play app on the device, not through the developer (see Purchases and updates).

What the game stores on the device

These records contain no name, age, photo, voice, location or device identifier — nothing that points at a person. They are removed together with the app, and also by Start over in the parents' menu.

What the game does NOT collect

Permissions

The app requests no Android runtime permissions — no camera, microphone, location, contacts or file access. It declares three install-time permissions that are needed only by Google Play: INTERNET and ACCESS_NETWORK_STATE (so Google Play can reach its servers for a purchase or an update check) and com.android.vending.BILLING (so the game can ask Google Play whether the full version is owned). The game itself opens no network connections of its own.

Links out of the app

The parents' menu — reached only after solving a simple arithmetic problem, so a child does not open it by accident — has a page listing the research the game is built on, and a short About & Credits page naming the illustrator who worked on some of the game's artwork. Tapping a source or the illustrator's portfolio link opens that website in the device browser, the same way both times. Those websites are run by other people and have their own privacy policies.

Apart from those two pages, the game contains no outbound links, and there are none anywhere in the part of the game a child plays.

Children

The game is made for children roughly between one and five years old. It is designed to meet the Google Play Families policy, the Children's Online Privacy Protection Act (COPPA) and the GDPR rules on children's data. Since the game collects nothing and stores nothing outside the device, there is no personal data of a child to protect, disclose or delete on request.

The game speaks to an adult in the parents' menu behind the arithmetic gate, and nothing from there leaves the device. The purchase is offered only there: a child playing rounds or browsing the album never sees an offer to buy anything.

Purchases and updates

The little town world is free and complete. The other worlds are unlocked by a single one-time in-app purchase, the full version, with no subscription. The payment is handled entirely by Google Play under Google's privacy policy: the developer neither receives nor stores card numbers, billing addresses, the Google account or any other payment details. The game only asks Google Play whether this account owns the full version and remembers the answer on the device.

When the app starts, it asks Google Play whether a newer version is available. If there is one, a small note offers to update; it can be dismissed, and a dismissed version is not offered again. That check is carried out by Google Play on the device, and nothing about the child or how they play is part of it.

Google Play Data safety, in plain words

Data collectedNone.
Data shared with third partiesNone.
Data encrypted in transitNot applicable — the game transmits nothing. Purchases and update checks are carried out by Google Play over its own encrypted connection.
Deletion requestNot applicable — uninstalling the app, or Start over in the parents' menu, removes everything the game has ever written.

Contact

For questions about this policy or the app's behaviour, contact nikitapetrovapps@gmail.com.

Changes

If this policy ever changes, the new version will be published at the same address with an updated "Last updated" date. The repository's git history records the diff.