Party Picker
Privacy Policy

Binarytech provides Party Picker. Player names and game records stay on your device. Sections 1–5 describe Android advertising and purchases; the Apps in Toss section describes storage, advertising and usage metrics in that version. Each Apps in Toss feature described here applies when a version containing it becomes publicly available.

1. Scope and operator

This policy applies to Party Picker for Android, intended for people aged 13 and older. Binarytech is the operator and privacy contact: binarytech804@gmail.com. The app has no account registration, developer-operated game server, or separate analytics/crash-reporting SDK. Optional one-time ad removal is available through Google Play billing.

2. Information stored on your device

• Player names, preferences, the current game and results: stored in app-specific storage for gameplay, recovery and recent results. These are not sent to a developer server or included in advertising requests.
• Recent results: retained within the app's cleanup limits of 20 rounds or seven days. Preferences, names and an unfinished game may remain until reset.
• Age information: we do not request or store dates of birth, age groups or individual participants' ages.
• Advertising consent: Google UMP stores consent status and privacy choices locally and may send information needed to process consent to Google.
• Ad removal purchase: a signed Google Play receipt, containing the product ID, purchase token, time and applicable order identifiers, is stored locally to maintain ad removal offline. Player names and game records are not linked to purchase information.

3. Advertising and Google's data processing

The app uses Google Mobile Ads SDK and User Messaging Platform (UMP). Every ad request receives Google's CHILD age treatment. This does not determine a user's actual age or change the app's intended audience. Personalized ads, remarketing and requests to third-party ad vendors are restricted, and the Android Advertising Identifier (AAID) is not transmitted with this treatment. UMP separately receives an under-age-of-consent protection signal, which suppresses European advertising consent requests for the tagged users. Ads are requested only when the SDK reports they are eligible. Ad creatives are limited to a maximum G rating. Banners are hidden during gameplay.

When advertising is enabled, Google may collect and share the following for advertising, measurement, analytics and fraud prevention:

• IP address and approximate location inferred from it
• Product and ad interactions, such as app launches, ad taps and views
• Performance and diagnostic information, such as launch times and hangs
• App set ID and applicable device/account identifiers (excluding Android advertising ID under this app's protective configuration)

SDK data is encrypted in transit using TLS. We do not attach player names, round details or game results to ad requests. The advertising provider's own analytics and diagnostics are separate from the absence of a dedicated developer analytics SDK.

4. Third parties and international processing

Ad removal is a one-time purchase, not a subscription. Google Play manages payment methods and Play account information; the app does not receive card numbers. The app uses the Play Billing Library to query and acknowledge purchases and restore them with the same Play account. Receipt signatures are verified in the app, and receipts are not sent to a developer server. Verified ownership stops banner requests; ownership revocation reported by Play removes that entitlement. Payments, refunds and Google's transaction retention follow Google Play policies and applicable law.

Advertising and consent data is transmitted to Google's advertising services and may be processed by Google and its service providers on servers in the United States and other countries. Recipients, processing locations, retention periods and safeguards may vary with the service and consent choices. See Google's Privacy Policy and how Google uses information from partner services for processing, retention, international transfers and rights procedures. We do not determine or guarantee Google's server retention periods.

5. Choices, retention and deletion

• Reset local data in Settings resets player names, the current round and results. Advertising privacy preferences are managed separately by the SDK.
• Resetting game data does not cancel ad removal. Clear Android app storage or uninstall to delete the local receipt; it can be restored with the same Play account. Deleting app data does not delete Google Play order records or refund the purchase.
• Where required, use Advertising privacy options in Settings to review or change consent. This option appears only when the SDK requires it.
• Clear the app's storage in Android settings or uninstall to remove locally stored app data. Android settings also provide controls to reset or delete your advertising ID.
• The app is configured to exclude its data from Android cloud backup and device-to-device transfer. Manufacturer-specific backup behavior is described by the device provider.
• Resetting local game data does not delete data already processed by Google. Use Google's privacy tools and contact procedures to exercise rights relating to its data.

Storage, advertising, purchases and usage metrics in Apps in Toss

This section applies to Party Picker (party-picker) inside the Toss app. The Android-specific Google AdMob, UMP, Google Play purchase and Android backup settings above do not apply to this version. Support and rights procedures apply to both versions.

• Game storage: player names, settings, the current round and results are stored on your device through the Apps in Toss Storage SDK. Recent results are retained for up to 20 rounds or seven days. Reset data in Settings to remove saved names and game records. Data is not automatically shared with the installed Android app.
• Accounts and purchases: the mini-app does not use separate registration or Toss member-information integration. Toss manages its own account and service eligibility requirements. Versions containing ad removal offer a one-time, non-consumable purchase through Apps in Toss IAP. Toss and the app marketplace manage payment methods and orders; the mini-app does not receive card numbers. The product ID and delivery order identifier are recorded in Toss Storage. SDK pending, completed and refunded orders are queried to remove ads, recover undelivered purchases and restore with the same Toss account. Verified ownership stops banner and interstitial requests; a verified refund removes the entitlement. Order identifiers are not linked to player names, game records or analytics events, or sent to a developer server. Ad removal in the installed Google Play app is a separate product and entitlement.
• Banner and interstitial ads: the Apps in Toss SDK serves home-screen banners and an interstitial before results after every three completed rounds. The completion counter and last completed round identifier used to determine ad timing are stored locally and are not passed to the advertising API. Player names, game records and results are not passed to that API either. Toss and advertising providers may process device and advertising identifiers, usage and ad interactions for delivery, measurement and fraud prevention. We do not guarantee that the installed Android app's CHILD, G and UMP settings also apply to Toss advertising.
• Usage metrics: Apps in Toss Analytics measures app starts, game starts and completions, completion of three rounds during one app execution, actual interstitial impressions, and starting the next round after an ad. The SDK's automatically included anonymous identifier and fixed event names are sent to Toss. We do not attach player names, round identifiers, results, scores or saved game records to these events. The developer uses aggregated Toss console metrics to understand return visits and usage before and after ads.
• Retention, deletion and providers: resetting game data does not delete a Toss account or advertising and usage-metric data already processed, or cancel a purchase. Purchase delivery records are stored separately from game records; clearing the mini-app's storage removes the device copy. Clearing storage does not delete orders or refund payments, and purchases can be restored from order history with the same Toss account. Payments, refunds and transaction retention follow Toss and app-marketplace policies. See the Toss Privacy Policy and relevant in-app notices for data categories, retention, international processing, rights and advertising privacy choices. Where Google ads are served, Google's Privacy Policy also applies. The developer does not determine providers' retention periods.

6. Support and your rights

If you email support, your sender address and message are processed to respond and resolve your request. We delete them without undue delay once that purpose is fulfilled, except where retention is required by law or necessary to resolve a dispute, and then only for the necessary scope and period. Do not send passwords, player lists or sensitive information.

To request access, correction, deletion, restriction, consent withdrawal or other rights under applicable law regarding personal data we process, contact binarytech804@gmail.com. We may perform proportionate identity checks and will handle requests under applicable law. We cannot remotely retrieve game records that exist only on your device. If you believe the developer has collected personal information from someone under 13, please contact the same address.

7. Changes

We will update this page and its revision date when processing changes. Significant changes will be announced through the app or the public policy page.