Privacy.

1. Browser-local tools

The session ledger stores records in your browser using localStorage. Entries can include the date, stake, balances, paid lives, kills, deaths, Survival exits, hours, and notes that you provide. The site’s static front-end code does not transmit those ledger entries to BR1 Almanac. Clearing site data removes them; exporting a CSV creates a file on your device.

A service worker may cache pages and assets on your device for speed and limited offline access. You can remove that cache through your browser’s site-data controls.

2. Advertising, cookies, and similar technologies

The production site is configured to use Google AdSense Auto Ads. Third-party vendors, including Google, may place or read cookies on your browser or use web beacons, IP addresses, and similar identifiers to deliver, limit, personalize, and measure advertising. Reserved banner containers remain hidden unless separately configured.

Google may use advertising cookies to serve ads based on your prior visits to this site or other sites. You can review or change Google advertising personalization through My Ad Center. Other advertising partners may provide their own controls and privacy notices.

3. Consent and regional privacy choices

Where law or advertising-platform policy requires it, the publisher must configure an appropriate consent or privacy-choice message before certain advertising technologies are used. Visitors in the EEA, the United Kingdom, and Switzerland may be shown the consent flow provided through Google’s certified consent-management platform before personalized advertising is enabled.

Browser settings, privacy extensions, global privacy signals, and ad-platform controls may limit cookies or personalization. Blocking storage or scripts can also prevent some ads, site caching, or local tools from functioning as designed.

4. Hosting and technical logs

The hosting provider, security services, and internet infrastructure may automatically process ordinary request data such as IP address, user agent, requested URL, referrer, timestamp, approximate region, and security events. Their retention and use are governed by the selected providers’ policies and account configuration.

5. Direct sponsorships and outbound links

Direct-sold banners are labeled as advertising and use sponsored outbound links. A campaign landing page may receive ordinary request information when you click, including your IP address, browser details, timestamp, and referring page. BR1 Almanac does not control an advertiser’s collection, security, or privacy practices.

Links to BR1, publishers, government agencies, advertisers, and other third parties lead to services with their own terms and privacy policies. Downloading the PDF, DOCX, or an exported CSV creates a local file under your browser and device settings.

6. Sensitive information and minors

Do not enter wallet seed phrases, private keys, passwords, government identifiers, payment-card data, or other sensitive information into any ledger note or site field. BR1 Almanac has no wallet-connect or payment function.

The publication discusses a game whose paid-play terms may require adult eligibility. The site is not designed to collect personal information from children.

7. Changes and contact

This policy should be reviewed whenever analytics, advertising partners, consent tools, forms, accounts, payments, or other data-processing features change. The effective date above identifies the version packaged with this release. A dedicated BR1 Almanac contact method will be published here before direct inquiries are accepted; unrelated brands and social accounts are not authorized to receive information on its behalf.