Back
Nudge

Privacy Policy

Effective Date: July 12, 2026

Nudge ("Nudge," "we," "us," or "our") provides an asynchronous, turn-based multiplayer gaming platform accessible via web browser and as an installable Progressive Web App. This Privacy Policy explains what information we collect, how we use it, and the choices you have.

1. Information We Collect

Account information. When you create a Nudge account, we collect information depending on how you sign up:

  • Google Sign-In: your name, email address, and profile picture, as provided by Google.
  • Email & Password: the email address and password you provide (passwords are stored securely and are never visible to us in plain text).
  • Guest Play: a randomly generated identifier with no personal information required. Guest data may be more limited in what it can save or sync across devices.

Gameplay data. We store game state, moves, scores, and match history so that asynchronous games can be resumed across sessions and devices.

Device and usage information. We may collect browser type, device type, general usage patterns, and push notification subscription details (if you enable notifications) to operate and improve the service.

Cookies and similar technologies. We use cookies and similar technologies for authentication (keeping you signed in) and, where applicable, for advertising purposes described below.

2. How We Use Information

We use the information we collect to:

  • Operate core gameplay functionality, including matchmaking via shared links and turn notifications
  • Authenticate your account and maintain your session
  • Send push notifications related to your turn in a game (only if you opt in)
  • Maintain and improve the reliability and performance of the service
  • Display advertising, including through Google AdSense (see Section 4)

3. Third-Party Services

Nudge relies on the following third-party providers to operate:

  • Google — for OAuth authentication and, where enabled, advertising (Google AdSense)
  • Supabase — for database storage of accounts and gameplay data
  • Stripe — for processing token purchases. Stripe receives the payment and billing information you provide during checkout; Nudge does not receive or store your complete card number.
  • Vercel — for application hosting

These providers may process data on our behalf under their own privacy and security practices.

4. Purchases

When you buy virtual tokens, we retain transaction identifiers, the purchased package, amount, currency, fulfillment status, and refund or dispute state. We use this information to deliver tokens, prevent duplicate credits, handle refunds and disputes, and maintain the security of the in-app economy.

5. Advertising

Nudge may display advertisements served through Google AdSense. Google and its partners may use cookies to serve ads based on your prior visits to this or other websites. You can learn more about how Google uses data for advertising and manage your ad personalization settings at Google's Ads Settings page and How Google uses information from sites or apps that use our services.

6. Data Retention

We retain account and gameplay data for as long as your account is active. You may request deletion of your account and associated data at any time by contacting us (Section 8).

7. Children's Privacy

Nudge is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us so we can remove it.

8. Your Rights and Choices

You may:

  • Access or update your account information within the app
  • Request deletion of your account and data
  • Opt out of push notifications through your device or browser settings
  • Manage advertising cookie preferences through your browser or Google's Ads Settings

9. Contact Us

Questions about this Privacy Policy or your data can be directed to:

Email: nudgegaming.business@gmail.com

10. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by an updated effective date at the top of this page.