LanternLoop · privacy

Privacy Policy

This draft explains how the LanternLoop website handles information when you browse the site, read its co-op game guidance, use its cookie choices, or explore the planned app service. It is written for clarity and must be completed with the publisher’s verified details before publication.

Publisher details to complete: No operator name or direct contact route was supplied for this site. The site owner must add the responsible publisher’s name and a verified contact method before this policy is published.

01 / What is involved

Information and purposes

LanternLoop is an informational service intended to help adults discover and plan relaxed indie co-op game nights. The website does not currently ask visitors to create an account, submit a profile, or enter contact details through this page. Do not send personal information to the site unless a future feature clearly explains why it is needed.

Technical request data: When your browser requests this page and its resources, the relevant service providers may receive technical connection information such as the request, browser, device, network and time details normally transmitted with a web request. This site does not use that request to identify you for an unrelated purpose.
Cookie-consent preference: The site stores a choice of “accepted” or “rejected” in the browser’s local storage under the LanternLoop consent key. This lets the site remember whether the cookie banner should be shown again and records the preference locally.
Future account information: No account collection is described in the supplied site. If LanternLoop later adds accounts, profiles, saved game lists or planning features, the owner must update this policy before collecting those details, including the fields collected, purposes, legal basis where required, retention and user controls.

02 / Where information goes

Storage, retention and sharing

Consent preference retention: The saved consent choice remains in the browser’s local storage until it is changed through the site’s cookie settings, removed by the visitor, or cleared by browser or device controls. No longer server-side retention period for this preference has been supplied.
Necessary typography request: The selected web typography is delivered through Google Fonts. Its stylesheet originates from fonts.googleapis.com and its font files originate from fonts.gstatic.com. These resources load with the page before a visitor makes a cookie choice, so the browser sends a technical connection request and associated connection data to Google. This request serves the site’s presentation and typography; it is not described as optional analytics, and cookie consent does not control this necessary presentation request. This policy does not add claims about Google’s retention or transfer practices beyond the documented request and origins.
Other recipients and transfers: The site may disclose technical request information to the providers needed to deliver the page and its resources. No additional analytics, advertising, account, payment or game-library recipient has been supplied. The owner must verify and add any further recipients, international transfers, retention periods or processor arrangements before publication.
Security: The owner should maintain reasonable technical and organisational safeguards appropriate to the information actually processed. No separate security specification or incident contact was supplied for this draft.

03 / Your controls

Choices, rights and updates

You can choose “Accept” or “Reject” in the cookie-consent notice. You can revisit that choice through the site’s cookie settings control. You can also clear local storage or site data in your browser; doing so may cause the notice to appear again. The necessary Google Fonts request described above occurs before that choice and is not switched off by rejecting optional cookies.

Depending on where you live and what information is processed, you may have rights such as asking for access, correction, deletion, restriction, portability, or objection, and you may withdraw consent where processing relies on consent. The practical scope of a request depends on the data involved and applicable law. No direct contact route was supplied, so the owner must add a verified route for rights requests before publication.

The owner may revise this policy when the site, app or data practices change. The updated version should be posted on this page with a clear indication of what changed. No effective date has been supplied and none is stated here.

04 / Before this goes live

Contact and publication note

For privacy questions, requests or concerns, use the publisher contact details that the site owner must provide here before publication. No verified email address, postal address, phone number, operator identity, data protection contact or regulator route was supplied, so this draft intentionally does not invent one.

This is a generated plain-language draft, not a claim that LanternLoop complies with every applicable privacy law. The owner should review it against the actual hosting, font delivery, app, account and consent implementation, then add the missing publisher and contact details.