Privacy Policy

1. The Adversary app

Adversary is a mobile memory game. The app does not require an account, and NBP Apps does not currently operate a cloud profile for scores, board history, or gameplay choices. Game state needed to run a round is processed on the device. The app sends selected product, gameplay, and purchase events to the services described below, but it does not upload complete boards or score history. If online accounts, cloud saves, or multiplayer features are added, this policy will be updated before those features launch.

2. Purchases and RevenueCat

Adversary may offer optional in-app purchases. The Apple App Store or Google Play handles billing for a purchase made through its store, and RevenueCat provides purchase validation, entitlement status, and transaction information. RevenueCat may process an anonymous app user identifier, device and app information, purchase receipts or tokens, transaction details, and last-seen app activity. NBP Apps does not receive your complete payment-card details. Read RevenueCat’s Privacy Policy.

3. Advertising and Google AdMob

The free Starter level may display a native advertisement from Google AdMob in the revealed Danger-card position. Customers with an active Adversary+ lifetime entitlement do not receive these ads. Adversary uses the Google Mobile Ads SDK to request and display ads and Google’s User Messaging Platform to present privacy choices where required.

Personalized ad selection is disabled. Google’s publisher first-party identifier is also disabled.

Adversary requests permission through Apple’s App Tracking Transparency framework before Google Mobile Ads may access the Identifier for Advertisers (IDFA). If permission is granted, Google may use the IDFA for advertising attribution and measurement across apps and websites owned by other companies. If permission is denied or restricted, the IDFA is unavailable and Adversary continues using contextual or non-personalized ads. The user’s choice does not affect access to the game.

Before Apple’s permission prompt, Adversary may display an explanatory message supplied through Google’s User Messaging Platform. Google privacy-consent choices and Apple’s App Tracking Transparency permission are separate choices.

Google may process an IP address (which can be used to estimate approximate location), app- or developer-scoped device identifiers, device and app technical information, advertisements shown and interactions with them, product-interaction data, and crash, diagnostic, and performance information. Google may use this information to request and display ads, measure performance, limit repeated ads, detect fraud and invalid traffic, and provide analytics. Google’s bundled iOS privacy manifest identifies Device ID as data used for tracking under Apple’s App Store definition.

When Google requires an ongoing privacy-choice entry point, it is available in Adversary under Settings > Privacy Choices. Tapping an advertisement may open a third-party destination governed by that advertiser’s own privacy practices. For more information, read the Google Privacy Policy, How Google uses information from sites or apps that use its services, and How Google uses data for advertising.

4. Product analytics and Layers

Adversary uses the Layers SDK for product analytics and purchase measurement. Layers advertising consent is disabled, and no Conversions API (CAPI) destination is connected. In the current configuration, Layers is not used to send Adversary data to an advertising platform.

Layers automatically processes app and session events together with install and device identifiers, including an install identifier and, on Apple devices, the Identifier for Vendors (IDFV), plus device or app details such as device model, operating-system and app versions, locale, time zone, and screen size. A source IP address is necessarily received when the app connects to Layers; Layers states that it uses the address to derive an approximate country or region at ingestion and then drops the address.

The events Adversary deliberately sends describe when a game starts or finishes; a per-round random identifier; the selected difficulty and entry point; the outcome, qualifying final score, best-score status, and Danger-related result; when sharing is started or completed, including the share format and activity type when available; when a paywall is viewed or a purchase is started; and a successful purchase’s product identifier, purchase amount, currency, and transaction identifier. Adversary also sends whether the lifetime unlock is active. The app does not send your launch-list email, name, or an Adversary account ID to Layers.

Layers processes these records for NBP Apps so we can understand product use, activation, retention, gameplay, and purchase performance. Layers states that SDK event records are kept for its product-analytics retention period. Read Layers’ Privacy Policy and data-protection documentation.

5. Feedback email

Sending a feedback email from the app’s Settings screen is optional. If you choose Send an Email, Adversary opens an email composer addressed to NBP Apps. The draft may include the app version, build number, device model, operating-system version, and locale to help us understand your feedback. You can edit or remove this information before sending, and nothing is sent unless you send the email. NBP Apps receives the message and any content or attachments you choose to include.

6. Launch-list emails

When you join the launch list on this website, we collect the email address you submit and an optional signup source showing where the form appeared. We use that address for Adversary launch news and closely related beta availability updates. Joining the list does not create an account or guarantee beta or early access.

7. Website tracking and cookies

On the /app-store landing page, we also collect first-party counts of visible page visits and taps on the Download button to understand how the page performs. Records contain the event type, server timestamp, landing path, and, when present, the utm_source, utm_medium, utm_campaign, and utm_content campaign labels and the referring website’s hostname. We discard referrer paths and query strings and do not collect Facebook click IDs. Random identifiers link events from a single page load and prevent duplicate records; they are not saved in cookies or browser storage and do not identify you across visits.

These records are stored in Cloudflare D1 and viewed through a private dashboard. This feature does not store IP addresses, names, email addresses, advertising identifiers, or device fingerprints, and does not send these events to Meta. Counts measure page visits and button taps, not confirmed app installations. We retain the records to compare landing-page performance over time until they are removed when no longer needed. Privacy requests can be sent to nbpapps@gmail.com.

The website uses Cloudflare Web Analytics to measure page views, navigation, and website performance. Its browser beacon processes current-page performance information and page URLs. According to Cloudflare, the beacon does not store or access cookies, local storage, session storage, or IndexedDB. Cloudflare receives a source IP address as part of normal request handling, then discards it at the nearest data center rather than storing it in its core analytics databases or logs. See Cloudflare’s RUM beacon documentation. The website does not use advertising cookies or session recording. Basic request information may also be processed temporarily to prevent spam and automated submissions, but it is not intentionally stored with the waitlist record. Waitlist information is stored using Cloudflare D1.

8. Sharing and sale of information

Information may be processed by Apple, Google Play, RevenueCat, Layers, Google AdMob and participating advertising partners, Cloudflare Web Analytics, Cloudflare D1, and providers that operate the app or website, or disclosed when required by law. We do not sell launch-list email addresses; advertising-related “sale” or “sharing” choices, where applicable, are presented through Google’s privacy choices.

When App Tracking Transparency permission is granted, Google and participating advertising partners may process the IDFA for cross-app advertising measurement and attribution. When permission is denied, the app does not provide them with the IDFA.

9. Retention, deletion, and choices

Waitlist information is retained only as long as needed for launch and beta updates. Feedback emails are retained as needed to respond to the message, address reported issues, or improve the app. To remove an email address or make a privacy request, write to nbpapps@gmail.com. App-related information handled by Apple, Google Play, RevenueCat, or Layers may also be subject to their retention rules and privacy-request processes. NBP Apps will coordinate applicable Layers access or deletion requests.

Google controls retention for information it processes for AdMob under its own policies. Advertising choices can be changed through Settings > Privacy Choices when that entry point is required and available. Privacy requests can be sent to nbpapps@gmail.com, and Google may also handle requests about data it processes under its own privacy policy.

Tracking permission can be reviewed or changed in iOS under Settings → Privacy & Security → Tracking. Google consent and privacy choices can be reopened from Adversary’s Settings → Privacy Choices when that option is required and available.

10. Children’s privacy

Adversary is not directed to children under 13, and we do not knowingly collect their personal information. A parent or guardian who believes a child submitted information can contact us to request its deletion.

11. Security and international processing

We use reasonable safeguards to protect information under our control, but no online service can guarantee absolute security. Providers may process information in countries other than your own, subject to their safeguards and applicable law.

12. Changes to this policy

We may update this Privacy Policy as Adversary, its monetization, or its services change. Updates will appear here with a revised last-updated date.

13. Questions and privacy requests

Send privacy questions or requests to nbpapps@gmail.com.