ToyPop Privacy Policy

Effective 22 October 2026. Updated 22 October 2026.

David Yerushalmi publishes ToyPop, a game intended for players of all ages, including children under 13. This notice describes the game accounts, cloud saves, optional features and the service providers used by ToyPop.

Support, privacy and account-deletion requests: davegd1994@gmail.com. Publisher address: Dolev 14, Harish, 3761429, Israel. Publisher/legal contact: hotnetsec@gmail.com, +972509445593. The support inbox and publisher/legal contact serve different purposes.

Cloud guest accounts and game progress

Native gameplay connects to the ToyPop service and creates or resumes a guest workshop. A guest does not have to supply an email address, a real name, a birth date or a local PIN. Guest accounts still have a persistent account identifier; their records are not anonymous or deidentified merely because they have no email address.

The service stores the account identifier and workshop information needed to run the game: board and inventory, virtual balances, orders, toy collection, preparation and assembly, progress, reward claims, settings, inbox and game-event state. Game requests also include action/item identifiers and duplicate-prevention references. Daily/weekly functions use the device's time-zone setting. The app keeps a local checkpoint and authentication session. Core cloud gameplay requires a connection.

Names, email and sign-in

In the current app, a newly entered nickname is saved on that device rather than uploaded as a new cloud profile name. Legacy profile names and account information may remain from earlier versions. Older versions can still send attempted profile text to infrastructure before server compatibility controls discard new unsupported changes.

New email linking, email sign-in/recovery codes and manual identity linking are temporarily paused in the app configuration and hosted service. Google and Apple sign-in are currently disabled in hosted Auth settings. Existing linked users and saved workshops are retained; the pause does not delete old account information. Keep an existing installation and session available: a new guest workshop is not a recovery method for an old workshop.

The game does not collect a parent PIN or birth date and does not represent a local access gate or an app-store purchase prompt as verified parental consent.

Optional purchases and store information

Apple handles purchases in the iPhone app and Google Play handles purchases in the Android app when the relevant products are available. ToyPop does not ask for full payment-card or bank-account details in its game purchase UI.

Opening native store features can initialize RevenueCat to fetch product prices, even before a purchase is made. ToyPop supplies the workshop identifier as the purchase-customer identifier. Store and purchase services can process device/platform information, product and transaction identifiers, receipts or purchase tokens, entitlement state, refunds and service-usage times. These support purchase verification, delivery, duplicate prevention, restoration and RevenueCat purchase analytics/reporting.

The app disables RevenueCat's automatic attribution-device-identifier collection option. That setting does not disable all technical or purchase data. Consumable resources are separate from eligible permanent-purchase restoration. Surprise Deal checkout remains paused.

Operations, diagnostics and updates

Cloud services receive normal connection information, including IP addresses and technical request data, to authenticate sessions, save progress, operate game services and protect against invalid game or purchase claims. Required economy/action records still exist.

Optional general gameplay analytics and Sentry crash reporting are disabled. RevenueCat purchase analytics and infrastructure logs are separate processing. The candidate app configuration disables EAS Update checks and downloads. Earlier private builds could use Expo update requests, including a randomized installation identifier and conditional launch-recovery diagnostics; their historical processing must be handled separately.

Service providers and recipients

• Supabase: cloud authentication, game database and server functions. Privacy information and data-processing terms.
• RevenueCat: native store product/purchase verification, entitlement reconciliation, purchase reporting and purchase-customer deletion requests. Privacy information and data-processing terms.
• Apple and Google Play: distribution, store accounts, checkout and store purchase records under their own policies. Apple privacy; Google privacy.
• Expo: build services and historical update-service processing for older private app configurations. Current candidate OTA updates are disabled. Expo privacy information.
• Support email and public help hosting: a support email is processed by the email services used by the sender and the publisher's Gmail inbox. Visiting public help pages also sends ordinary web connection requests to their hosting infrastructure.

These providers process the information needed to operate the game and its optional store features. Their own policies explain their independent services, including store accounts and payments.

Races, sharing and reminders

Online race participants can see a generated race alias, preset avatar, score and standing. A free-form nickname is not part of the current race-participant contract. A shared cabinet picture or visitor link contains chosen toy/cosmetic information; its current serializer excludes account credentials, account UUID, email and display name. Recipients and their chosen apps can retain or reshare that content. Opening a visitor link also sends a normal request and its cosmetic query information to the showcase host.

Optional local reminders use operating-system notification permission. No remote push-token registration is implemented in the reviewed app. Game audio uses playback; the app does not request microphone recording, location or contact access.

Requests and account deletion

A parent or guardian can contact the support inbox to ask about a child's game data or request review or deletion. Account access must be verified before disclosing or removing a workshop. Do not send passwords, sign-in/MFA/recovery codes, full payment-card details or identity documents. A player ID helps locate a record; it is not by itself proof of ownership or parental authority.

David Yerushalmi monitors davegd1994@gmail.com for ToyPop support and privacy requests.

The implemented in-app deletion path is Settings → Save & Recover Game → Delete Account. The external request page can be used without reinstalling the app. Support will explain the ownership or parental-authority information needed for the particular request. If ownership cannot be established, support may be unable to disclose or delete the workshop. Reinstalling the app is not required to send a request.

Verified account deletion removes the Auth account and associated cloud workshop records. In-app completion clears the current device's game checkpoint and local purchase identity. Other devices can retain offline copies. RevenueCat customer deletion is requested through its asynchronous provider process; accepting that request is not proof its queue has finished.

Transaction/refund references can remain with their former game-account link removed to prevent duplicate consumable grants and refund abuse. Detached race results preserve other players' standings. Completed deletion-status records keep a request-capability digest and completion/provider-stage information without the removed account ID or email. App stores keep their own purchase records. Account deletion does not request a store refund.

Retention and international processing

Active workshops and existing linked-account records are retained to provide the saved game. The publisher has selected 12 months of inactivity as the target for reviewing inactive workshops. Automatic inactivity deletion is not enabled. You can request deletion at any time instead of waiting for this review. Existing pre-release saves remain protected. New email linking is paused; historical data has not been purged. The data categories above can also appear in provider operational logs or backups and voluntary support correspondence.

ToyPop currently uses Supabase's Free plan. Its project backup page states that scheduled project backups are not included, and Supabase's published plan table lists one day of API/database log retention. This does not describe every provider security/support record or a separate local copy. A provider-plan change requires this notice to be reviewed. See Supabase plan and log-retention information.

Support correspondence is kept while needed to resolve and document the request. Account-detached transaction and refund references are retained for duplicate-payment and refund protection; those records do not retain the deleted game-account link. There is currently no fixed automatic expiry for these detached records. Provider processing can involve locations outside the player's country. ToyPop's active Supabase database project is configured in AWS region eu-west-2 (London). Supabase states that the database, Auth and database backups are region-hosted, while support, service metadata and other operational processing can occur elsewhere. See Supabase's data-location information. The database region does not mean every server-function request, support interaction or provider record is processed in that region.

Changes to this policy

We update this page when ToyPop's data practices change. The effective date above identifies the current notice. Contact the support inbox if you have questions about a child's data, retention or deletion.