Privacy Policy — Blert Lost Ticks

Last updated 25 August 2026

Blert Lost Ticks does not collect, store, transmit, or sell any user data. It has no analytics, no telemetry, no accounts, and no servers of its own.

What the extension does

The extension runs only on pages under https://blert.io/. There it reads the raid, session, and personal-best data that blert.io already serves to your browser, computes lost-tick counts and personal-best percentile badges from it, and displays the results in the page.

Data collection

None. Every calculation happens locally in your browser. Nothing is sent to the developer or to any third party, and the extension contacts no server other than blert.io itself.

Network requests

The extension calls blert.io's own public API endpoints on the site you are already visiting, in order to read the data it displays:

These are the same requests blert.io makes itself. No request is made to any other host.

Local storage

To avoid refetching the same figures repeatedly, the extension caches computed percentile values in your browser's localStorage under the blert-pbp: prefix, on the blert.io origin, for twelve hours. This data stays on your device, is never transmitted anywhere, and is removed when you clear your browser's site data.

Permissions

The extension requests no Chrome permissions at all. Its manifest declares a single content-script match for https://blert.io/* and nothing else. It has no background service worker and executes no remote code — all of its code ships inside the extension package.

Changes

If this policy ever changes, the updated version will be posted at this URL with a new date above.

Contact

Questions about this policy can be sent to contact@olm.pet, or raised as an issue on the project's repository.