Skip to main content

Privacy Policy

Last updated: July 27, 2026

Information We Collect

BMH Guide does not require user registration. After optional consent, we collect limited usage data through analytics tools to improve the site experience. This may include:

  • Pages visited and time spent
  • Device type, browser, and operating system
  • Approximate geographic location (country/region level)
  • Referral source
  • Coarse pull-planner interactions such as selected mode, game shortcut, interface language, browser-language group, goal type, deadline range, whether a shortfall exists, use of the fictional quick-start example, approved validation-error category, and save/share actions
  • Coarse Play Signal interactions such as interface language, approved entry source, filters used, games followed or unfollowed, official-source openings, watchlist openings, and alert signup completion
  • Email address if you voluntarily join the launch list
  • Email address and selected games if you separately join Play Signal's preview waitlist
  • A game title if you voluntarily request a game that is not in the current Play Signal portfolio
  • Name, email address, subject, and message if you use the contact form
  • Anonymous NIGHTGLASS suggestion fields if you voluntarily use the in-game feedback form
  • Coarse NIGHTGLASS product events such as an anonymous game view, portrait-orientation block, renderer readiness, run start or broad result category, broad duration range, feedback opening or submission, approved entry source, interface language, and broad viewport class
  • Coarse Stack Attack events such as game readiness, run start, result category, score and elapsed-time ranges, retry, exit, approved entry source, broad viewport class, and portrait orientation prompts

Play Signal Watchlist, Analytics & Alerts

The Play Signal watchlist is stored on your device and does not require an account. If you accept optional analytics, we send a restricted set of anonymous events in the background to measure page visits, approved entry sources, filter use, games followed, official-source openings, and alert signup completion. We use a separate random identifier whose server-side value is stored only as a one-way hash. These events do not contain your email address, search text, IP address, browser user agent, or arbitrary game names.

The Play Signal preview waitlist requires its own explicit consent and is separate from the BMH launch list. Alert email delivery is not active during this demand-validation stage. If you join, we store your email address, selected games, interface language, approved entry source, referring page, available UTM fields, browser user agent, consent version, successful request count, and request timestamps in separate subscriber and request records. The request record is saved together with the subscriber update before the site confirms success. Unsubscribing from one list does not change the other. Any future Play Signal campaign must include its own suppression link.

If you use the optional “Missing a game?” form, we store only the title you submit, your interface language, the approved Play Signal entry source, and the submission time. This form does not require an email address, account, analytics consent, or anonymous identifier. The requesting IP address is processed only temporarily for an in-memory abuse limit and is not stored with the suggestion.

Anonymous event delivery is best-effort and runs after optional consent without blocking watchlist changes, filters, navigation, or page rendering. Email storage is contacted only when you submit the alert form.

Contact Messages

If you use the contact form, we store your name, email address, selected subject, message, page, browser user agent, submission time, and review status in a server-side database. We use this data only to review site feedback, corrections, and privacy requests.

To reduce automated abuse, the contact endpoint temporarily processes the requesting IP address for an in-memory rate limit. The IP address is not stored with the contact message.

NIGHTGLASS Game Suggestions

The optional in-game suggestion form stores the selected topic, optional one-to-five rating, suggestion text, interface language, broad game phase, approved site entry source, submission time, and review status in our server-side database. It does not ask for or store your name, email address, account, browser user agent, or device details with the suggestion. Suggestions are saved for product review and are not delivered through an email system.

To reduce automated abuse, the endpoint temporarily processes the requesting IP address for an in-memory rate limit. The IP address is not stored with the suggestion.

NIGHTGLASS Product Analytics

NIGHTGLASS remains fully playable without optional analytics. If you accept optional data use, the game sends a restricted set of first-party milestones to measure whether it was viewed, whether a portrait phone was asked to rotate, renderer readiness, run starts, broad victory or defeat categories, and feedback-form use. Load and play durations are sent only as broad ranges.

A random identifier is kept for the browser tab session and stored only as a one-way server-side hash. We do not attach your name, email address, IP address, browser user agent, exact score, exact play time, control inputs, or device fingerprint to these events.

Stack Attack Product Analytics

Stack Attack remains fully playable without optional analytics. If you accept optional data use, the game sends a restricted set of first-party events to measure whether it loaded, a run started or ended, someone retried or left, and whether a phone needed the portrait-orientation prompt. Score and elapsed time are sent only as broad ranges.

A random identifier is kept for the browser tab session and stored only as a one-way server-side hash. We do not attach your name, email address, IP address, browser user agent, exact score, exact play time, or game input history to these events. The requesting IP address is processed only temporarily for an in-memory abuse limit.

Pull-Planner Product Analytics

If you accept optional analytics, we send a small set of first-party pull-planner events to our server-side Neon database in addition to Google Analytics. These events tell us whether someone opened a planner, which approved site section led them there, started changing planner inputs, opened the fictional quick-start example, encountered an approved required-field error, selected a game shortcut, generated a result, saved a local plan, or used a share action.

We attach a random anonymous browser identifier and store only its one-way server-side hash. We do not store an IP address, browser user agent, exact resource or pity values, plan names, reward labels, free text, or shared-plan parameters with these events. The endpoint accepts only approved planner routes, games, languages, and coarse result categories.

Event delivery runs in the background and is best-effort. A failed or slow analytics request does not block planner calculation, local saving, sharing, navigation, or any other site feature.

Launch List Emails

If you join the launch list, we store your email address, signup page, signup source, referring page, available UTM campaign fields, browser user agent, consent version, successful request count, and first and latest subscription-request timestamps in a server-side database. Each successful request receives a database request record before the site confirms success. We use this list for verified code alerts and major official update notes only.

To reduce automated abuse, the signup endpoint temporarily processes the requesting IP address for a short in-memory rate-limit window. The IP address is not added to the launch-list database.

We may securely import launch-list records into Zoho Campaigns to deliver and measure those emails. Every marketing campaign includes an unsubscribe link. We also maintain an individual suppression link for launch-list records. Unsubscribing stops future campaign exports and emails; you can also ask us to delete the source record through the contact page.

Cookies & Local Storage

We use cookies and browser local storage for the following purposes:

  • Analytics cookies — Google Analytics for traffic analysis, loaded only after you accept optional data use
  • Advertising cookies — Google AdSense and its advertising partners may place or read cookies, use web beacons, device identifiers, and IP addresses to deliver, limit, personalize, and measure ads when advertising is enabled
  • Local storage — Saving your pull-planner drafts, selected game context, named plans for each mode, gacha simulator progress, Play Signal language and watchlist choices, optional-data choice, and local watchlist entries. Stack Attack also stores your best score on the device. After optional analytics consent, local or session storage also holds separate random anonymous planner, Play Signal, NIGHTGLASS, and Stack Attack identifiers. Pull-planner plan names and exact resource values remain on your device unless you deliberately copy a sanitized share link.

Pull-planner analytics never include exact currency, tickets, probability inputs, income-event labels, plan names, or shared-plan parameters. Page-view addresses are recorded without query strings or URL fragments. Shared assumptions are placed after the URL fragment marker so browsers do not send them with the page request.

Third-Party Services

We may use the following third-party services that have their own privacy policies:

  • Google Analytics — website traffic analysis
  • Google AdSense — advertising delivery, frequency control, measurement, fraud prevention, and consent management
  • Vercel — hosting and performance analytics
  • Neon — server-side storage for consented anonymous planner, Play Signal, NIGHTGLASS, and Stack Attack events; voluntary launch-list and separate Play Signal alert emails; NIGHTGLASS suggestions; and contact messages
  • Zoho Campaigns — delivery, suppression, and measurement of launch-list emails

Advertising & Consent

When advertising is enabled, Google and its advertising partners may use cookies, web beacons, device identifiers, or IP addresses to serve and measure personalized or non-personalized ads, prevent fraud, and limit how often an ad appears. Google may combine this information with activity from other sites or apps according to its own policies.

Where required, including in the European Economic Area, the United Kingdom, and Switzerland, advertising choices are collected through a Google-certified consent management platform. You can review or change those choices through the privacy message shown on the site.

Learn more about how Google uses information from sites that use its services in Google's partner sites policy.

Data Retention

Google Analytics data is retained for up to 26 months. Raw first-party planner and Play Signal events and daily anonymous-user deduplication records are retained for up to 90 days. Daily aggregate event and unique-user counts, which do not contain the browser identifier, may be retained for longer-term product trends. Local storage data persists on your device until you clear your browser data or use the reset function within our tools. Launch-list email records are kept until they are no longer needed or you ask us to remove them. Play Signal alert records follow the same rule but remain logically and operationally separate. Contact messages are retained while they are needed for review or follow-up, then deleted when no longer necessary. NIGHTGLASS suggestions are retained while they are useful for product review, then archived or deleted when no longer needed.

Your optional analytics choice is stored locally in your browser. You can reopen Privacy settings from the control at the bottom of the site and change the choice at any time. Advertising consent, where required, is stored and managed separately by the certified consent platform.

Your Rights

You can clear all locally stored data at any time by clearing your browser’s storage or using the reset buttons provided in our tools. You can decline or later change optional analytics through the site's Privacy settings control. Advertising choices, where required, can be changed through the certified consent message. Unsubscribe from each campaign list using the corresponding link included in every message. BMH and Play Signal suppressions are separate. To request deletion of a source email record or removal of a contact message, submit a request from the contact page.

Changes to This Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated revision date.

Contact

If you have any questions about this privacy policy, please contact us via our contact page.