Privacy Policy

Nightreign Seed Finder is designed to work without account creation. We collect limited information to run the app and improve it.

• Seed identification log: each time the site identifies a seed, one row is written to a database on our server. The row records the seed that was found, the marks that led to it (which map slots you set to which points of interest), the Nightlord, how many searches your browser has run, your timezone, whether you are on desktop or mobile, your viewport size, which map markers were enabled, how long the view was open, any ad credits spent, how many times your browser has been shown the adblock notice, whether the row came from the bug report flow, and the app version together with whether your browser passed the trust check. It also carries a random identifier for your browser. There are no accounts on this site, so that identifier is not tied to one, and the row holds no name and no email. The row does not record your IP address.
• Local storage preferences: your browser holds your display settings (pre-selected Nightlord, whether the Nightlord status card is pinned, minimalist mode, whether the sidebar is hidden, map text visibility, and how the event and gaol cards are shown), your map marker settings and the colours you chose for them, which notices and marker warnings you have already dismissed or acknowledged, the last path you marked so it can be attached to a bug report, your viewport size, and the state of your current ad credit session. It also holds the list of seeds you have identified, which is what the History page reads. That list is a seed number and a time for each identification, nothing else, and it never leaves your browser.
• Session storage: we store a temporary consent dismissal flag for the current session only.
• Cookies: consent cookies store your decision about privacy preferences. A separate cookie holds the random browser identifier described above, and two more count the searches you have run and the ad credits you have spent.
• Ad delivery signals: NitroPay and advertising partners may collect device identifiers, ad interaction data, and approximate location signals to serve and measure ads.
• Bug report submissions: if you choose to send a report, we collect the name, email, subject, message, and the page URL you were on, along with your browser user agent. We also record the IP address the report was sent from. The form accepts submissions from anyone, with no login, and the originating IP is the only thing that lets us contain abuse of it. The server then adds two internal flags of its own: one marks a submission as suspected spam, the other records whether the browser passed a trust check.

The seed identification log and the bug report form share one identifier. The random browser identifier sits on every seed identification row, and the same identifier is written on every bug report. A bug report also carries the name and email you type into the form. So sending a bug report attaches that name and email to the seed searches already logged from your browser, and to the ones logged after it. If you would rather not make that connection, email us instead of using the form.

The site measures anonymous usage data with Google Analytics to improve performance and usability.

• Google Analytics: collects aggregated usage metrics (pages visited, device and browser details, and interaction events).

Advertising on this site is operated and powered by NitroPay (Overwolf Ltd), which also provides the consent tool. NitroPay and its advertising partners may collect device identifiers, ad interaction data, and approximate location signals to deliver ads and measure performance. What NitroPay does with that data is set out in its own privacy policy.

The site uses Resend to send email. When you submit a bug report, your email address and the contents of the report pass through Resend so that a confirmation can reach you and a copy can reach the project inbox.

You can manage consent and opt-out choices in the Privacy Choices page or through your browser controls.

• Remember your preferences between visits.
• Provide map and gameplay tooling that depends on temporary session state.
• Respond to bug reports and user feedback you submit.
• See which maps and Nightlords people actually search, size the interface against the viewport sizes really in use, and investigate reports that a result was wrong.
• Measure site performance and usage trends to improve the product.

Preferences are stored locally in your browser. Seed identification rows are sent to our backend and kept in a hosted database. Bug report submissions are sent to the same backend so we can respond and fix issues. We do not sell personal information.

When ads are shown, NitroPay may use cookies or similar technologies to support consent choices and ad delivery.

• Clear local storage and cookies in your browser to remove saved preferences. Clearing cookies also clears the random browser identifier, so later seed identification rows carry a new one instead.
• Manage consent and opt-out requests on the Privacy Choices page.
• Block or delete advertising cookies through your browser settings.

We may update this policy as the site evolves. The date at the top reflects the latest revision.

If you are in the European Economic Area or United Kingdom, you can review and update your consent choices through the Privacy Choices page. When available in your region, the consent link will appear there.

California residents have the right to know what personal information is collected, request deletion of personal information, and opt out of the sale or sharing of personal information.

To opt out of the sale or sharing of personal information, visit the Privacy Choices page or the Do Not Sell page. If you are in a supported region, the opt-out link will appear below.

Those two pages cover advertising choices only. They do not reach the seed identification log or a bug report you have sent. For a request about either of those, write to the contact address at the bottom of this page.

If the link does not appear, email [email protected] with the request and it is processed the same way.

Email: [email protected]