Data boundaries of this build

1. No account or transaction flow

This build installs no account system, payment processing, behavioural analytics or advertising trackers. The correction tool has no submission endpoint. The local JavaScript does not send field contents to a remote service, and no external API is used to filter the archive or calculate a download.

The cookie banner stores only your Accept or Decline choice in localStorage under bopliostorycrats.consent. Both options keep tracking off. This entry is not an account identifier or play history and is not uploaded by the application. See Cookies: build inventory for its scope and how to change or clear it.

2. Local correction drafts

Draft text is held in page memory, not website-managed persistent storage. The tool asks for a reference, topic, optional source URL and message, not an identity or email address. Do not include sensitive personal details.

Copying places text on your device’s clipboard; downloading creates a file under your control. Browser features, clipboard history, extensions or device backups may retain those copies independently of this website. Reset cannot remove an exported file or clipboard copy.

3. Search, filters and downloads

Archive filter selections remain in page memory and are not saved as visitor preferences. The homepage date search navigates to the archive with a query in the URL. That query can appear in your browser history and in hosting request logs. Use it for draw dates, not personal information.

CSV exports are prepared in the browser from the visible supplied records. No account is needed and the tool does not upload the export. Text exports are also prepared locally.

Lucky Number Reveal reads the supplied homepage records locally. Its revealed numbers and visit counter remain in page memory; the activity sends no play events to a server and saves no play history.

4. Independently operated destinations

Source and support links leave this website when followed. Those destinations have their own operators, notices and technical practices. Their resources are not embedded in these pages; no third-party fonts, images or scripts are loaded by this build.

5. Technical delivery

Serving a page can involve technical request information such as an IP address, requested URL, timestamp and browser details. The precise logging, security mechanisms and handling depend on the deployed hosting configuration. This page makes no blanket promise that no personal data is ever processed or that every kind of processing relies on consent.

6. Controls and scope

You can read every result without JavaScript, leave the local tools unused, reset their fields and choose whether to follow external links or save files. The Cookies page describes the build’s storage choices. Cookie settings in each page’s footer lets you review or change the saved banner choice; clearing this site’s browser storage removes it.

The local feedback-draft tool can help prepare a note about the website, but it is not a delivered privacy request or a rights-request channel. This implementation notice is not a certification of legal completeness for every deployment or jurisdiction.