Drunk Monk Play free

Legal

Privacy Policy

How Drunk Monk handles data when you play our browser and mobile games, including ads, cookies, consent choices, diagnostics, and your rights.

Effective date: 2026-04-18
App: Drunk Monk (browser game; hex path multiplayer and related modes)

Important: This document is a draft for internal and early-adopter use. Before a broad public launch, paid features, or significant traffic from regulated regions, have it reviewed by a qualified attorney and update it to match your actual deployment, vendors, and data practices.

Who we are

“Drunk Monk” refers to the game experience operated by the project maintainer(s) who control the deployed website and associated Supabase project. The production site is drunkmonkstudios.com; contact the operator at support@drunkmonkstudios.com.

What this policy covers

This policy describes how the app handles information when you open the site, play games (local or online), sign in (if enabled), and use feedback or bug-report features.

Information we collect

Data minimization (custom questions)

For Snap Judgments, custom question lines you type may be stored in the custom_questions table so we can improve mechanics and moderation. Those rows are deleted automatically after 30 days (scheduled database job). We do not use them for marketing lists.

No names or emails for anonymous play

Anonymous multiplayer does not require an account. We do not ask for your real name or email to play in the browser. If you choose to sign in with Supabase Auth, the authentication provider stores account fields according to your project settings (see below).

Advertising and third-party cookies

The site shows ads through Google AdSense. The AdSense script loads on every page, but ad units only request ads after you consent:

  • European Economic Area, United Kingdom, and Switzerland: Google's consent message asks for your choices. Google serves personalized, non-personalized, or limited ads based on those choices.
  • Everywhere else: the in-app cookie banner asks. If you accept, ad units request ads. If you reject, no ad units load.

Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads based on your visits to this site and other sites on the Internet. You can opt out of personalized advertising in Google Ads Settings, or opt out of some third-party vendors' cookies at aboutads.info. Learn more in How Google uses information from sites that use its services.

Satire and characters

Snap Judgments uses exaggerated character traits and prompts for gameplay and satire. They are fiction for the match and do not represent the views of the people who build or operate Drunk Monk.

You provide directly

  • Account data (optional): If you create an account with Supabase Auth (email/password or other methods your project enables), the authentication provider stores credentials and profile fields according to your Supabase project settings.
  • Gameplay and lobby text: Display names, room titles for public lobbies, Snap Judgments labels you enter, and similar fields are stored in match state in the database so other players can see them.
  • Reports and feedback: When you submit a bug report, feedback, crash, or performance report, we store the text you enter plus structured diagnostic payloads (see below).

We collect automatically

  • Technical diagnostics in reports: The app may include environment metadata such as page URL, user agent, language, screen and viewport size, timezone, coarse device class, network online flag, whether cookies are enabled, localStorage availability, reduced-motion preference, and similar browser-reported values. Game-related diagnostics may include board summaries, path animation samples, and other non-secret game state excerpts to reproduce issues.
  • Identifiers: A browser-local client id may be stored in sessionStorage / localStorage for anonymous sessions. Reports can include a room id / slug and, when signed in, identifiers that link the report to your account as configured in the app.
  • Replay data (bug reports): Large replay payloads may be uploaded as gzip JSON to private cloud storage associated with your Supabase project. Only designated report administrators can read those objects, subject to database and storage policies.

What we do not intentionally collect

We do not market the game to children under 13 and do not knowingly solicit personal information from children. Parents or guardians who believe a child submitted data should contact the operator so records can be removed where feasible.

Why we use this information

  • To run multiplayer matches and show public lobby listings.
  • To authenticate users where sign-in is enabled.
  • To diagnose bugs, improve performance, and respond to feedback.
  • To protect the service (abuse investigation) where permitted by law.

Depending on jurisdiction, we rely on performance of a contract (providing the game), legitimate interests (security and improvement), and/or consent where required (for example, non-essential cookies or marketing — currently not described as in use). Customize this section with counsel if you target those regions.

How long we keep data

Default targets are documented in docs/SECURITY_AND_RETENTION.md (project repository). In short: match rows and reports should be retained only as long as needed for operations and triage, then deleted or aggregated according to your operational schedule.

Custom Snap Judgments questions: retained no longer than 30 days (automatic deletion).

Who receives data (subprocessors)

The app is designed to work with:

  • Supabase (database, authentication, realtime synchronization, file storage for replay attachments, and related APIs).
  • Cloudflare (or your chosen static host / CDN / edge worker) for serving the web application.
  • Firebase (Google) for the native iOS and Android apps: Analytics, Performance Monitoring, and Crashlytics when configured.

Your deployed instance may use additional vendors (analytics, error tracking). List them explicitly if you add them; update this policy when you do.

Native iOS app (Snap Judgments)

When the optional Firebase configuration file (GoogleService-Info.plist) is present, the iOS app may send:

  • Analytics events (for example match started, feedback category/rating toggles) via Firebase Analytics.
  • Performance traces (timed operations such as match start and inbox refresh) via Firebase Performance Monitoring.
  • Crash and non-fatal error reports via Firebase Crashlytics.

Players can disable this collection in Settings → Diagnostics → Share analytics & crash reports. Feedback message text is delivered by email (or the device Mail composer) to the operator support address and is not attached to Analytics events. Ad personalization signals are disabled by default in the app configuration.

The iOS app also shows interstitial ads through Google AdMob. To serve ads and measure their delivery, Google may receive device identifiers, approximate location derived from your IP address, ad interactions, and diagnostic data. The app does not ask for App Tracking Transparency permission and does not track you across other companies' apps or websites. See How Google uses information from sites or apps that use its services.

Online play in the iOS app stores your display name, room code, and game moves in Supabase so both players can see the match. Custom packs (photos, Live Photos, and questions you create in the Studio) stay on your device and are not uploaded. Camera and photo library access is used only when you choose to add pictures to a custom pack.

Native Android app (Snap Judgments)

When the Firebase configuration file (google-services.json) is present, the Android app sends the same categories as the iOS app: analytics events, performance traces, and crash and non-fatal error reports. Players can turn this off with Share analytics & crash reports in the app's settings. Feedback message text is not attached to Analytics events. The Android app shows AdMob interstitials under the same conditions as the iOS app.

Update App Store Connect privacy nutrition labels and the Google Play Data safety form to match the Firebase products you enable.

International transfers

If players connect from outside the country where your Supabase project region is located, data may be processed across borders. Add SCCs / UK IDTA references if counsel advises for EU/UK traffic.

Security

We use industry-standard practices appropriate to a small project, including TLS in transit, database row-level security for sensitive tables, and restricted access to administrative routes. No method of transmission or storage is 100% secure.

Your choices and rights

Depending on your location, you may have rights to access, correct, delete, or export personal data, and to object to certain processing. To exercise rights, contact the operator at support@drunkmonkstudios.com. You may also delete local browser data (cookies, local storage) for the site; that may reset anonymous identifiers.

Changes

We may update this policy from time to time. Material changes should be reflected by updating the effective date and, where appropriate, an in-app notice.

Contact

Email support@drunkmonkstudios.com.