Clear information about your data.

Lanternleafgames.com is a static website. Lanternleaf Games does not ask you to create an account, collect information through a public web form, add advertising trackers, or deliberately set application cookies.

The site uses Cloudflare Web Analytics to measure aggregate page views and browser performance. The lightweight beacon does not use cookies and, according to Cloudflare, does not collect or use visitors' personal data or track individual visitors across Cloudflare customers' sites. Lanternleaf Games uses the resulting aggregate statistics to understand which public pages are useful and whether they load reliably; it does not build visitor profiles or maintain a separate website visitor database.

Cloudflare delivers and protects the site. It may process an IP address, the requested URL, connection and browser information, and security signals needed to route requests and prevent abuse. Cloudflare may also set a strictly necessary security cookie when an enabled protection requires one. This supports Lanternleaf Games' legitimate interests in keeping the website available and secure; Lanternleaf Games does not build a visitor profile or maintain a separate website visitor database.

Cloudflare describes its handling of end-user traffic in its Web Analytics documentation, Privacy Policy, and cookie documentation.

Bug reports can be submitted voluntarily from inside Mosslight Meadow. Lanternleaf Games determines why and how those reports are handled and is the data controller. Privacy requests can be sent to [email protected].

A submitted report contains the category and description you provide; random submission and report references; client and server timestamps; processing status and expiry time; the game version, revision and release channel; and whether the reporter was opened from Settings or a paused game. Optional technical details contain build, display and renderer information, diagnostics, and the current meadow state. A gameplay-only PNG screenshot is optional when reporting from a paused game. Screenshot dimensions, file size, and integrity hashes are also stored.

Reports are designed not to include an email address, Steam ID, Steam name, save data, Windows user path, continuous monitoring, audio, or video recording. The service rejects obvious email addresses, numeric Steam IDs, and Windows user-profile paths. Please do not type other personal or account information into the description.

• Purpose: receive voluntary reports, investigate and fix Mosslight Meadow problems, and protect the reporting service from abuse.
• Legal basis: Lanternleaf Games' legitimate interests in maintaining and improving the game and keeping the reporting service secure.
• Optional: sending a report is not required to play the game or use any purchased feature.
• No profiling: reports are not used for advertising, automated decisions, or player profiling.

When an eligible completed run is submitted to Online Records, Mosslight Meadow sends a compressed replay proof to the private Lanternleaf verification service. Lanternleaf Games determines why and how these records are handled and is the data controller. The service authenticates the current Steam session, reconstructs the run using the exact rules for that game build, and only then asks Steam to keep the best verified score.

The r128 authorization design has passed a controlled end-to-end test but is not yet enabled in production. Under that design, a wander begun without online authorization stays in Local Records only and creates no trusted proof or uploadable queue entry. Only a trail authorized before it starts can submit to Online Records or retry its protected submission after a later connection loss.

A trusted-run record contains the numeric Steam account identifier returned by Steam; random run and private receipt references; game version, revision, release channel, simulation and verifier versions; the meadow seed; recorded movement, actions, choices, day transitions, checkpoints and compact state hashes; final run state and score; timestamps, processing status, integrity hashes, and the Steam publication result. An online-authorized run may also contain its one-use authorization grant reference and server simulation nonce. The Steam authentication ticket is used for authentication and is not stored in the database, proof storage, or processing queue.

Trusted-run records do not contain a bug-report description, screenshot, save file, email address, Steam display name, raw IP address, or user-agent. The connecting address is used only to derive a short-lived, service-specific abuse-rate-limit key; neither the address nor that derived key is written to the trusted-run database or proof object.

• Purpose: provide Online Records, verify competitive runs, prevent duplicate or forged submissions, publish only matching results, and audit leaderboard integrity.
• Legal basis: providing the Steam-connected leaderboard feature you use and Lanternleaf Games' legitimate interests in fair competition and service security.
• No invasive scanning: verification replays the submitted game record; it does not install a kernel driver, scan unrelated files, record audio or video, or run as a separate permanent background service.
• No advertising: trusted-run data is not used for advertising, unrelated profiling, or automated decisions outside leaderboard verification.

Cloudflare provides encrypted network delivery, rate limiting, the verification application, a private database, private proof-object storage, and an asynchronous processing queue as a service provider. Replay proofs and receipt records are not publicly listed or downloadable. Public status pages show service availability only; they do not expose players, proofs, tickets, receipts, or leaderboard jobs.

• Recipients: authorised Lanternleaf Games administrators, Cloudflare acting as a service provider, and Valve/Steam receiving the verified score and compact run-detail fields for the Trusted leaderboard.
• Publication: Steam displays leaderboard information according to its own account, community, and privacy settings. Lanternleaf Games publishes only after an exact replay match.
• Retention: the 90-day bug-report expiry does not apply to trusted runs. Proofs and their audit trail are retained while the associated leaderboard version is active and as reasonably needed to investigate score disputes, prevent replay reuse, and protect leaderboard integrity. They are reviewed when a leaderboard or verifier version is retired.
• Rights: requests for access, correction, deletion, restriction, or objection can be sent to [email protected]. Include the relevant Steam profile or account identifier and approximate run time when possible so the correct record can be located.
• International processing: Cloudflare's and Valve's applicable data-processing terms and transfer safeguards apply where processing occurs outside the EEA.

Reports are sent over HTTPS to the Lanternleaf Games support service. Cloudflare provides network delivery, security and rate limiting, the report application, and private database and image storage as a service provider. Cloudflare may process connection information such as an IP address or client user-agent as needed to deliver and protect the request; Lanternleaf Games does not store those values in the bug-report record.

Before the report body is read, a one-way, service-specific digest derived from the connecting IP address is used for a one-minute abuse rate limit. The raw IP address and user-agent are not written to the report database or screenshot storage. Minimal operational logs may contain a report reference, result code, and whether a screenshot was attached, but not the report description, technical details, diagnostics, or screenshot itself.

• Recipients: authorised Lanternleaf Games administrators and Cloudflare acting as a service provider.
• Screenshot access: private; screenshots are not published, listed, or served from a public URL.
• Retention: reports and screenshots expire 90 days after server receipt. Automatic cleanup runs daily, so final removal may complete within roughly 24 hours after expiry.
• International processing: where Cloudflare processes data outside the EEA, its applicable data-processing terms and transfer safeguards apply. See the Cloudflare Data Processing Addendum.

Before sending, you can remove the screenshot, turn off technical details, close the reporter without sending, or save a local copy instead. After a successful submission, the game displays a report reference.

You may request access, correction, deletion or restriction of personal data in a report, and you may object to processing based on legitimate interests. Contact [email protected] and include the report reference when possible. Because reports intentionally contain no account or email identifier, the reference is the most reliable way to locate the correct report.

You may also lodge a complaint with the data-protection supervisory authority in the EEA country where you live or work, or where you believe a data-protection infringement occurred. The European Commission provides an overview of your data-protection rights, and the European Data Protection Board lists the national supervisory authorities.

Links to Steam, the Lanternleaf Games support service, and the leaderboard verification status page open services with their own technical operation and policies. This page describes lanternleafgames.com and the Mosslight Meadow support and Online Records flows; it does not replace the policies of Steam or Cloudflare.

Legal provider details, editorial responsibility, and terms for using Lanternleaf Games materials are available in the Impressum.