Scope of this notice
The notice concerns the Casino Ledger editorial application, including its country selector, public articles, local calculator and configured partner-navigation route. It does not describe the internal systems of a casino, wallet, bank, regulator or browser vendor. Each of those services has its own responsibilities and information. A link from this site does not make another organisation part of the same account or privacy arrangement.
The description is based on the prototype's implementation reviewed for this version. A future published service needs its actual domain, publisher and infrastructure documented. No private workspace account address is substituted for a dedicated public contact. Where a production detail is unknown, it remains identified as pending instead of being filled with a plausible company name, retention period or legal basis that has not been established.
Publisher identity and production contact are pending
Casino Ledger is the editorial project name. It is not a substitute for the legal identity of the entity responsible for a production website. That identity, jurisdiction and dedicated contact must be established before the public launch. This page does not invent a registered company, office, data-protection officer or historical operating record. The local preview should not be mistaken for a completed corporate disclosure.
The contact page explains how to prepare a correction without sending sensitive account information. It does not currently provide an inbox or upload process. Do not guess an address on a proposed domain or use a personal account found elsewhere in the workspace. A production contact must be deliberately assigned and verified for the service it represents.
The implemented browser-state inventory
The country selector uses a first-party cookie named edition to remember a supported reading country. The promotion-frequency controller can use a sessionStorage flag named cl-promotion-seen to avoid repeating promotional panels within the relevant tab session. The arithmetic calculator uses the values entered in its page form to update an on-page output. These are distinct functions and should not be described as one advertising profile.
The current application does not create a reader account, persistent visitor identifier or server-side browsing-history table. It does not contain a newsletter subscription or a document-upload form. This inventory describes application code, not every activity of a future network provider. Normal website delivery still involves requests and connection information, which are discussed separately below.
What the edition cookie contains
The cookie stores a supported two-letter country code selected through the country form. It does not contain a name, email address, bank reference, casino balance or precise location. Its purpose is to choose a reading edition when the reader returns to the site's entry address. A value identifying an edition should not be interpreted as verified residence or permission to use an external operator.
The selector accepts only configured choices rather than an arbitrary destination address. Selecting a country replaces the stored reading choice with that supported code. The application does not build a history of every earlier selection from this cookie. It uses the current value as a preference. A separate physical-country rule can still govern a partner route, so the reading choice and outbound eligibility remain different decisions.
How long the reading preference is configured to last
The selector response configures edition with a maximum age of thirty days. The value is set when a supported choice is submitted. Browser controls, private modes and user deletion can affect actual storage. The cookie's configured lifetime does not guarantee that every browser will retain it for exactly thirty days or that every future visit will behave identically after storage has been cleared.
The preference is stored by the browser for this site rather than in a Casino Ledger user-account database. Clearing the site's cookie removes that stored choice in the relevant browser profile. It does not erase data held by an unrelated partner site. Different devices or browser profiles can therefore have different reading preferences without the application linking them into a cross-device identity.
What happens when the country form is submitted
The form sends the selected country code to this site's country endpoint. A supported choice sets the reading-preference cookie and directs the browser to the corresponding public edition. The form is not a casino registration, identity check or payment instruction. It does not ask for an address, date of birth or account credentials. Its meaning is limited to navigation and reading context.
An invalid or unsupported value is not used as an arbitrary external redirect. The application returns an error rather than accepting a visitor-supplied destination. This describes the selector's implemented behaviour, not a guarantee about every future form added to the project. Any new field or submission purpose would need its own review and an updated explanation rather than silently inheriting this narrow notice.
How an automatic reading suggestion is chosen
At the entry address, the router first considers a valid saved reading preference. Without one, it can use a supported country code supplied by a trusted hosting source. If that is unavailable, the implementation can consider a browser language preference that explicitly matches a supported regional language. If no supported choice is established, the reader can use the directory and manual selector. The process chooses an edition, not an identity.
The language hint is not treated as physical-country verification for an offer. A browser can request a regional language while its reader is elsewhere. A saved choice can likewise reflect what someone wants to read rather than where they live. The interface therefore keeps manual navigation available and does not claim that an automatic suggestion proves age, residence or operator eligibility.
Country information is coarse and source-limited
The production adapter is designed to use a coarse country code from the trusted hosting environment. The local server's production mode accepts its designated verified-country input only through the configured trusted-proxy relationship. Ordinary public request headers are not intended to become self-asserted physical-location proof. The local preview can simulate a country for testing, which is different from a production location assessment.
The application does not request the browser's precise geolocation permission. It does not need GPS coordinates to choose a reading edition. A country code can still be wrong for a reader's circumstances, which is why the selector is useful. The code should not be described as an identity, residential-address or legal-eligibility check.
Browser language is a reading hint
A normal browser request can include preferred languages. The entry router can use an explicit supported regional-language match as a fallback reading suggestion. It does not use that signal to create an advertising audience or claim that the reader physically occupies the matching country. A language preference can reflect learning, travel, family use or a general browser setting rather than location.
Changing an edition does not require changing the browser's language configuration. The manual country form provides a direct reading choice. If a suggestion is inappropriate, select another edition or open its public address. This action should be understood as navigation, not as a method to bypass restrictions applied by a partner service.
Public article addresses identify the content being read
A public locale path identifies its article. The application does not classify a visitor as Googlebot and serve a different article body to disguise it from a person. A manual edition change opens another public address. Country-dependent offer presentation is a separate part of the page and does not make the reading preference a hidden personal-content profile.
This distinction matters for privacy as well as clarity. A reader can share the public article address without sharing a private account token. The application does not insert a persistent reader identifier into article links. A future change that introduced personal accounts, private recommendations or visitor-specific article histories would need a separate inventory and explanation rather than being described as the existing edition function.
Reading preference and offer-country checks are distinct
A saved edition can affect which information is convenient to read. It does not override a verified physical-country restriction on a configured outbound offer. The offer route uses its own allowed-offer and country checks. A missing or unsupported country can result in an information response instead of an external redirect. This is a technical routing decision, not a certification that a service is authorised or appropriate for a person.
The application does not use country selection to collect proof of residence or casino account eligibility. It also does not treat an affiliate configuration as legal approval. Those questions require current service and jurisdictional information. The privacy point is that an editorial choice is not expanded into a verified personal profile or a record of the reader's gambling activity.
The promotion-frequency flag limits repetition
The browser-side controller can store cl-promotion-seen in sessionStorage after a promotional panel is displayed. Its purpose is to reduce repeated panels within that tab session. The value is a simple flag rather than a name, device fingerprint, account identifier or list of clicks. The controller uses it to decide whether to show another panel, not to send a reader to an advertising audience.
The presentation also allows a displayed panel to be dismissed. Dismissal is an interface action. The current application does not transmit that action to an analytics endpoint or store it in a server-side click table. This describes the implemented controller; it does not promise how a future analytics system would behave if one were added later.
Session storage is different from the edition cookie
The frequency flag is kept in browser sessionStorage, which is associated with the site's page session rather than a thirty-day cookie. Reloading a page can preserve the session value. Browser session and restoration behaviour can matter, so this notice does not promise an exact wall-clock deletion time for every browser setting. MDN's storage documentation explains the general browser mechanism separately from this site's particular flag.
The application does not use the flag to join sessions across devices or identify a casino customer. If browser storage is unavailable, the code handles the storage access without making the article depend on a tracking service. Clearing site data can remove the flag, which may affect repetition control. It does not remove an external site's account history or cancel a partner registration.
Display triggers are local interface observations
The promotional controller observes conditions such as whether the main call to action has left the viewport, elapsed page time and scrolling. It can choose between a compact bottom format and a slide-in format. Those observations are used by the local display logic. The current script does not send a stream of scrolling, timing or dismissal events to a server or advertising platform.
An interface observation still has a specific purpose and should be described accurately. It would be misleading to say the page has no interaction logic at all. It would also be misleading to describe that logic as a recorded behavioural profile when no such application record is created. A future measurement system would need its own disclosed events, recipients and retention information.
Calculator values stay in the page's arithmetic function
The wagering calculator reads the deposit, bonus, multiplier and base fields and updates the displayed product. Its form handler prevents ordinary submission. The script does not send those values to an operator, analytics endpoint or Casino Ledger account database. The numbers are hypothetical arithmetic inputs; the form is not a deposit instruction or an assessment of the reader's finances.
Do not enter private account credentials or personal documents into a calculator field. The calculator needs only the numeric inputs relevant to its two formulas. It does not read a casino account, verify a promotion or predict outcomes. The privacy description follows that narrow function rather than inventing a financial-analysis profile that the application does not implement.
There is no Casino Ledger player account
The prototype does not offer player registration, balances, deposits, withdrawals or a login area. It does not need a reader's casino password or payment authorisation to provide an article. A partner site reached after a deliberate link can offer its own account process, but that is a different service with different information and responsibilities.
Do not confuse an editorial country preference with a registered account. The cookie stores a reading code, not a username or identity decision. No history of games played, losses, winnings or operator balances is created by the current editorial application. This statement concerns the application and does not describe data an external operator may already hold about its own customers.
There is no document-upload channel in this prototype
The current site does not provide a form for bank statements, identity documents, payment receipts or private account screenshots. Articles explain how to organise those records for the relevant institution; they do not ask readers to give Casino Ledger copies. A future upload feature would introduce a different processing purpose, security question and retention requirement and cannot be assumed to exist under this notice.
If preparing a correction, identify the public statement and a public primary source instead of attaching a private account file. If an account-specific investigation is needed, use the responsible service's protected channel. A payment guide can be read without surrendering private evidence to the editorial publisher.
No advertising-audience or fingerprinting integration is implemented
The application does not send IP addresses, user agents or visitor events to Meta CAPI, Google Ads audiences, analytics pixels or fingerprinting services. It does not implement covert audience capture before a redirect. The browser script contains no analytics network calls. This is an implementation statement about this prototype, not an assurance that every site linked from an article follows the same approach.
An external link can lead to a service with its own marketing or analytics systems. Read its notice before providing information or creating an account. A commercial relationship does not make those external practices invisible or automatically covered by this page. If Casino Ledger later adds a measurement tool, the actual data, recipient and purpose need to be identified rather than described using this current absence statement.
No application click-log database is implemented
The current editorial application does not maintain a click-log table or stored visit history. It does not append the reader's movements to a persistent account record. Local browser state is limited to the described preference and frequency functions. This should not be widened into a claim that no network information is ever processed during page delivery or that future infrastructure cannot create logs.
A server receives requests in order to respond, and a hosting or network provider may have its own operational systems. The assigned virtual server runs Nginx and Node; site access logging is disabled, while operational error and service logs can still be generated. The infrastructure provider’s separate policies have not been supplied. Therefore this notice does not invent a zero-day infrastructure retention period or claim that every possible upstream log has been disabled. Those details require production evidence.
Page delivery necessarily differs from stored profiling
A browser requests pages and assets from a server or local preview process. Connection and request information can be involved in delivering those responses even when the application does not create a visitor database. It is inaccurate to equate no click logging with no processing of any request information. This notice distinguishes the application's stored state from the normal delivery path and the assigned production server’s operational settings.
The production server serves casinoguidemap.com through Nginx and HTTPS, with the application bound to loopback behind that proxy. Country lookup uses a local DB-IP file rather than sending each visitor address to an external lookup API. Provider-level retention and the actual hosting jurisdiction have not been established here. No international-transfer safeguard, provider-wide logging policy or backup deletion period is inferred merely from installing the application.
Server-side destination configuration is not a reader profile
The partner route uses known offer identifiers and server-side destination configuration. It does not accept an arbitrary external destination supplied through a public redirect parameter. The configuration can contain affiliate campaign parameters, but that is not the same thing as storing a reader's name, balance or private account reference. This page does not publish private configuration material as an ordinary report.
A fixed partner parameter can still be meaningful to the destination's commercial tracking. The absence of a local click database does not establish the destination's attribution behaviour. The appropriate boundary is that this application controls its route and local state, while the external service must explain its own processing. A future change adding per-visitor identifiers would require a new assessment and disclosure.
External navigation has its own browser request context
The local server and production adapter set a strict-origin-when-cross-origin referrer policy. Browser behaviour and the nature of the destination determine the actual request context. This notice does not claim that an external site receives no information at all. The partner sees its own requested address and parameters, and network delivery involves its own connection information.
Do not include private account details in a public article address or a link shared with others. Casino Ledger's ordinary article paths do not require a personal account token. If a future form or campaign adds query data, its purpose and recipients would need review. The current policy header is one technical measure and should not be presented as complete anonymity.
Official-source links are separate navigations too
Articles can link to regulators, consumer-information bodies and technical documentation. Opening such a link takes the reader to another service, which may have its own cookies and infrastructure. A source citation does not mean that the external body receives article corrections or private account complaints through Casino Ledger. Use the destination's actual instructions for any separate enquiry.
A public source link is useful evidence for a scoped statement, not an endorsement of all external processing. The application does not need to copy a reader's bank statement to a regulator just because the regulator is cited. Keep reading, account investigation and formal reporting as separate actions with the appropriate recipient for each.
Images and page code are served as site assets
The prototype's own images, styles and browser code are stored as site assets. Reading an article does not require a third-party casino iframe or an advertising pixel embedded in place of an illustration. A photograph or logo used in the page is not itself an external account session. A later addition of remote media would need its own review rather than silently inheriting this statement.
Images support explanation and navigation; they do not establish game activity, a winning session or a reader's interests in a stored profile. The application does not ask a reader to identify themselves to view those assets. Normal asset requests still form part of page delivery, so the broader infrastructure qualifications in this notice remain relevant.
Browser controls can change stored preferences
A browser can provide controls for cookies and site storage. Clearing this site's data can remove the reading preference and frequency flag in that browser profile. The next entry visit may then use another available reading hint or show the directory. This effect concerns local site state and should not be described as deletion of a casino account or data held by an unrelated organisation.
Browser interfaces vary, so this page does not give an unverified sequence of menu labels for every product. Consult the browser's current help for site-data controls. Blocking storage can affect remembered choices or panel-frequency behaviour while the public article addresses remain navigable. The application does not require a persistent personal account to read the content.
Private browsing is not a promise of network anonymity
Private modes can affect local browser storage, but they do not turn an external navigation into no request at all. A destination still needs to receive a request to deliver a page. This notice therefore does not suggest that private browsing makes a reader anonymous to every service or changes local authorisation. Its relevance here is limited to how a browser may retain the preference and session state.
A reader can use public article addresses without registering. If storage is cleared or not retained, choose an edition again when needed. Do not use a private mode as a claimed workaround for operator eligibility or assume it removes information already held by an external account. The application makes no such promise.
Rights information needs an identified responsible entity
Privacy rights depend on applicable law and the actual processing arrangement. The European Commission provides general information about GDPR rights and the information individuals should receive. This page does not decide the framework for an unidentified future publisher or invent a completed rights-request procedure. The responsible production entity and public contact must be assigned before the notice can explain that actual route.
Do not send identity documents to a guessed email address to request deletion of a simple browser preference. The preference can be managed through the browser's site-data controls. Questions about an external casino account must go to that service through its proper process. A general description of rights is not a promise that Casino Ledger holds a hidden player database that can be exported or erased.
Retention claims are limited to what is implemented
The configured edition-cookie maximum age is thirty days. The promotion flag uses browser session storage rather than a server-side retention schedule. The application does not implement stored click or account histories. Those statements do not establish the independent retention of the assigned infrastructure provider, a browser vendor or a partner service. Each unknown infrastructure arrangement must be identified from evidence before a production promise is made.
This notice also does not invent backup deletion intervals or security-log periods for systems that have not been assigned. A credible inventory distinguishes no such application record from an unreviewed external arrangement. The application’s selected settings are documented here; the infrastructure provider’s own purposes and relevant storage information still require actual evidence rather than a generic retention number copied from another website.
What would require this notice to change
New analytics, advertising audiences, remote media, account registration, newsletter forms, uploads or persistent click identifiers would change the processing inventory. They should be reviewed and explained before being described as part of the existing small preference system. A new production host also requires actual provider and retention information. The current absence of a feature is not advance consent to add it silently.
A notice revision should identify the behaviour and date actually reviewed. It should not use a fresh date to imply that every external partner policy was independently checked. Where a feature is removed, distinguish the current application from any records a separate service may still hold. Clear updates preserve the limits of each claim rather than presenting privacy as a permanent badge.
Example: choosing an edition while elsewhere
Consider a hypothetical reader who is physically in one supported country but wants to read the Irish edition. The reader can choose Ireland through the form and open the public Irish article. The stored value expresses that reading choice, not a declaration that the person has moved or obtained permission to use an Irish operator. At the entry address, a valid saved choice can take priority for reading. The production offer check remains tied to its trusted country input rather than being overridden by that preference.
The application does not need the reader’s name, travel itinerary or precise coordinates to perform this navigation. It also does not create an account history saying that the person gambles in Ireland. If another person later uses the same browser, the saved preference can still be present. They can select another edition or manage site data. This example explains why the same short code has a narrow purpose even though it refers to a country. The code is useful for navigation precisely because it is not treated as proof of personal eligibility.
Preparing a factual observation about an unexpected request
If a reader notices a request or browser behaviour that seems inconsistent with this notice, a useful observation identifies the public page, approximate time, action taken and destination involved. Distinguish a request made while loading the article from a new navigation after deliberately opening a source or partner. Those are different events. Also distinguish the site’s own code from browser extensions or other software that can affect a browsing session. This notice does not claim to control an extension or a separate application.
Do not publish a raw network export containing cookies, authorisation headers, full account addresses or private query values merely to demonstrate the observation. A narrowly described public destination and action can be enough to prepare a report, while sensitive evidence should remain private until an appropriate secure route exists. The prototype currently has no upload inbox. A future verified publisher contact must explain how to receive any evidence it actually needs. An observation should not be sent to a guessed domain address or an unrelated casino support channel.
The same distinction applies when checking the calculator. Reading an on-page output is different from submitting a transaction, and opening an external article is different from a hidden background request. A clear report should describe what happened without assuming its cause. If later investigation identifies an application change, the processing inventory and notice need updating. If the event belongs to an external navigation or browser software, the responsible service’s information is relevant instead. The aim is an accurate connection between behaviour and responsibility rather than a blanket claim that every browser request came from this project.
Read the site without supplying private account evidence
Choose an edition, read the article and use the calculator with hypothetical or relevant numeric inputs. Open conditions and sources when needed. No player account or identity upload is required for those tasks. Keep bank statements, casino credentials and verification files with the institutions responsible for the actual account issue. An article about a payment does not require the editorial publisher to receive the payment record.
Before following an external link, recognise that the destination is a separate service. Review its information before giving personal data or creating an account. If a privacy issue concerns this prototype, use the factual scope described here and the pending-contact status on the contact page. This notice explains the current implementation honestly while leaving production identity and infrastructure decisions visibly unfinished.
How the local country lookup is implemented
The assigned production server uses Nginx and a local DB-IP Country Lite database to derive a coarse country code from the incoming network connection. The database is downloaded as a file; an individual visitor address is not sent to DB-IP for an API lookup. The current staged database release is October 2026. Its free edition has reduced coverage and accuracy, so a country result is a navigation hint rather than verified residence or personal identity.
Nginx replaces the incoming X-Verified-Country header with the result of its own lookup before forwarding the request to the application on the same server. The application accepts this header only from its configured loopback proxy. A country string supplied by a remote browser is not trusted. The root address opens a supported local edition first; direct article addresses retain their text, title and heading for every reader and crawler.
Country detection does not create a visitor profile or a list of past journeys. This application stores no click logs and has no advertising audience integration. Nginx access logging is disabled for this virtual host. Operational error and service logs can still be created to diagnose failures; they should not contain passwords, payment records or document uploads. Infrastructure and network providers can process connection metadata independently of the editorial application.
The DB-IP dataset is distributed under Creative Commons Attribution 4.0. Pages using the country result include a concise attribution link. The country selector remains available because network geolocation can be wrong, especially for shared networks and travelling readers. Selecting another public edition does not alter the verified country used by a configured outgoing offer, and it does not establish eligibility to use an external gambling service.
Sources and method
Quick answer
What does the edition cookie store?
It stores a supported country code chosen as a reading preference. It does not contain a name, email, bank reference, casino balance or precise location. The selector configures a thirty-day maximum age in the browser. The value helps choose an edition and does not verify residence, age or eligibility for an external account.
Does Casino Ledger create an advertising profile from my country?
The current application does not create a persistent visitor profile or send country and interaction data to advertising audiences. It uses the described coarse signals and browser preference for edition routing. Normal page delivery still involves requests, and future hosting arrangements remain to be documented. No profiling claim is made about external sites reached after a deliberate navigation.
Why is there a sessionStorage flag?
The cl-promotion-seen flag helps avoid repeated promotional panels within the relevant tab session. It is a simple local flag rather than a personal identifier or list of clicks. Browser session and restoration settings can affect its lifetime. The current script does not send panel observations or dismissals to a server analytics endpoint.
Are calculator values submitted to a casino?
No such submission is implemented. The page reads its numeric fields and updates an arithmetic output, while the form handler prevents ordinary submission. It does not log in to a casino, assess finances or predict results. Do not enter credentials or private documents into the fields; only the calculator's stated numeric inputs are needed.
Does the site store click logs?
No application click-log database or stored browsing-history table is implemented. This differs from claiming that no request information is ever processed. A server must receive requests to deliver pages, and the future host's operational systems are not assigned or documented yet. The notice therefore does not invent an infrastructure-wide zero-retention guarantee.
Can I remove the remembered country?
Browser site-data controls can remove this site's preference in the relevant profile, after which the entry page may use another available hint or the directory. Selecting another supported edition replaces the choice. Clearing local state does not delete data held by a partner website or cancel an external account. Consult the browser's current help for its actual controls.
Does a partner link have the same privacy notice?
No. A deliberate partner navigation reaches a separate service whose own processing and policies apply. The current route does not silently embed a registration page, but the destination receives its normal navigation request and configured parameters. This notice does not promise that an external casino uses no cookies, attribution or marketing systems.
Where can I send a privacy request?
The production publisher identity and dedicated public contact are not yet assigned. This prototype does not invent an inbox or request-handling policy. Do not send identity documents to a guessed address. The browser can manage its local preference, while an external account request belongs with that service's proper process. A completed production notice must identify the actual responsible entity and route.