Privacy Policy

1. Summary

The same policy is available inside the app in Armenian, Russian and English, on the Settings → Privacy Policy screen. This page is the English reference version.

2. Data at a glance

The table below summarizes every category of data the app handles, why it is handled and who processes it. Each row is described in full in the sections that follow.

Player names, scores, secret words and custom categories are never added to an update request, a purchase request or an ad request.

3. Data stored on the device

The app may store the following data locally:

• player names entered by users;
• scores;
• language, visual theme, timer, difficulty, haptics, and other game settings;
• custom category names, words, and word pairs;
• identifiers of recently used words or prompts to reduce repetition;
• an unfinished game and its current state;
• the state of the rewarded “PRO evening” trial: when it expires and when it was last started;
• the time an ad was last shown, so the interval between ads can be respected;
• a count of completed rounds and whether a store review has already been requested;
• markers of which one-time notices have already been shown: the version tag of the last “What’s new” dialog the user closed, whether the first-launch introduction was shown, and whether the “Two Words” explainer was shown;
• a simulated PRO status in development or Preview builds.

This local game data is used only to provide game features, restore settings, and resume play. It is not sent to a server operated by the developer. Users should avoid entering sensitive personal information in player names or custom categories.

Player names, scores, settings, custom categories and an unfinished game can be deleted with the full reset option in the app’s Settings. A few small technical values are kept so that a reset cannot be used to bypass them: the state of the rewarded “PRO evening” trial, the time an ad was last shown, the completed-round counter behind the review request, and the markers of the one-time notices. Uninstalling the app removes all app-controlled local data, subject to the device platform’s backup and restoration behavior.

4. App updates

Release builds may connect to Expo Application Services to check for and download compatible updates. Network requests necessarily expose ordinary technical information to the service provider, which may include an IP address, app version, platform or device technical information, and request logs. Player names, custom categories, and other local game content are not included in the app’s update request.

Expo’s privacy information is available at expo.dev/privacy.

5. Purchases and RevenueCat

For in-app purchases:

• Google Play processes the payment;
• RevenueCat retrieves the available product, validates the purchase, restores purchases, and determines whether the premium entitlement is active;
• RevenueCat may process an automatically generated anonymous App User ID, device type, operating system, purchase history, Google purchase token, product and transaction information, and entitlement status;
• the developer does not receive the user’s full payment-card details.

Purchase history is used to provide PRO access, restore a lifetime purchase, prevent entitlement errors, and understand purchase performance. The current app does not send a custom account ID, name, email address, advertising ID, player names, or custom game content to RevenueCat.

RevenueCat’s privacy information is available at revenuecat.com/privacy. Google explains its data practices at policies.google.com/privacy.

6. Advertising and Google AdMob

The free version may request an interstitial advertisement from Google AdMob after a completed game round. Ads are not requested during role reveal, discussion, voting, or other active gameplay. Ads are also not requested while PRO access is active. If an ad cannot be loaded, the game continues without blocking the user.

Before initializing advertising, the app uses Google’s User Messaging Platform to check applicable consent requirements and show a consent choice where required. If the resulting consent state does not permit an ad request, advertising remains disabled for that session. Where Google requires ongoing privacy options, the app provides an “Ad privacy choices” item in Settings so the user can review or change that choice.

The Google Mobile Ads SDK may automatically collect and share an IP address, which may be used to estimate approximate location; user interactions with the app or an ad; diagnostic and performance information; and advertising, app-set, device, or account-related identifiers. Google uses this information for advertising, ad measurement and analytics, and fraud prevention. Data is encrypted in transit. Depending on the user’s region, device settings, and consent choices, ads may be personalized or non-personalized.

In addition to the interstitial, the free version offers an optional rewarded video. It is never shown automatically: it starts only when the user chooses to watch it on the PRO screen or in a premium feature dialog, and watching it to the end unlocks a time-limited “PRO evening” trial of the PRO features other than ad removal. The rewarded format uses the same Google Mobile Ads SDK, the same consent state, and the same data practices described above, and it is not requested while PRO access is active.

The app does not add player names, scores, secret words, custom categories, or other local game content to an AdMob request. Android users can reset or delete their advertising ID in device settings. Google’s advertising privacy information and controls are available at policies.google.com/technologies/ads and myadcenter.google.com.

7. Sharing and sale of data

The developer does not sell personal data and does not use a separate behavioral analytics SDK.

Technical, advertising, and purchase-related data may be disclosed only to the relevant service providers—Google AdMob, Expo, Google Play, and RevenueCat—when needed to provide ads, measurement and fraud prevention, updates, purchases, entitlement validation, or restoration. These providers process data under their own terms and privacy policies.

Information may also be disclosed when required by law, to protect users, or to protect the app and developer from fraud or abuse.

8. Google Play review and sharing

After several completed rounds, the app may ask Google Play to display its own in-app review dialog. Google Play displays and processes the review. The app stores only a local counter and the fact that a review has been requested; it does not receive the review, its rating, or its text. The request is made at most once, and builds without the native review module skip it silently.

The results screen offers a “Share the game” button that opens the device share sheet with a fixed localized invitation text and a link to the app’s Google Play page. Player names, scores, secret words, and custom categories are not included. The user selects the recipient and the application that receives the message, and that application processes it under its own terms.

9. Email contact

When a user chooses to contact the developer, the app opens the user’s email application. The email address, message, and any information voluntarily included by the user are processed by the user’s email provider and the developer’s email provider. Users should not send sensitive information that is unnecessary for support.

10. Children

The app is not directed to children under 13. The game does not require an account and does not specifically request a child’s personal information. Parents and guardians should supervise younger users, use nicknames instead of full names, and avoid entering personal or sensitive information in custom categories.

If a parent or guardian believes that a child sent personal information to the developer by email, they may contact the developer to request its deletion.

11. Retention and deletion

Local game data remains on the device until the user performs a full reset or uninstalls the app.

Purchase records may be retained by Google Play and RevenueCat according to their legal obligations and retention policies. A user may contact armdevstack@gmail.com to request deletion of information controlled through RevenueCat. The developer may need an anonymous RevenueCat App User ID or purchase information sufficient to locate the record. Store transaction records that Google must retain may not be controlled by the developer.

12. Security

The app minimizes transmitted data and uses the standard security mechanisms provided by the device platform and service providers. Google Mobile Ads, RevenueCat, and Expo use encrypted network connections for their services. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

13. User rights

Depending on their location, users may have rights to request access, correction, deletion, restriction, or objection concerning personal data processed for the app. Requests can be sent to armdevstack@gmail.com. The developer may request limited information needed to verify and fulfill the request.

14. Changes to this policy

This policy may be updated when app features, service providers, or legal requirements change. The effective date at the top of the policy and inside the app will be updated when material changes are made.

15. Contact

• Narek Vardapetyan
• Email: armdevstack@gmail.com
• Application: Find the Spy (com.armdevstack.findthespy)