Operational data
The service records structured request logs needed for security, reliability, abuse prevention, and incident diagnosis. Client network addresses are represented by a deployment-specific salted fingerprint rather than written to application logs in raw form.
Performance measurement
The production interface sends same-origin Core Web Vitals such as LCP, INP, and CLS together with the page path, navigation type, anonymous metric identifier, and quality rating. This measurement does not include query strings, account identifiers, advertising identifiers, or market selections.
Optional analytics
BTC Regime uses Google Analytics 4 only after a visitor chooses Accept analytics
. Google Analytics is not loaded before that choice, and rejecting analytics does not limit the service. After consent, Google Analytics cookies may be used to process aggregate interaction, device, referrer, and recognized campaign information. The BTC Regime integration does not intentionally send arbitrary application query strings. Visitors can change or withdraw their choice throughCookie settings
in the footer. Changing the preference to rejected stops future tracking and removes BTC Regime Google Analytics cookies. Google's own processing is governed by its terms and privacy information.
External services
The browser connects to Coinbase Exchange for live BTC-USD ticker updates. Following a link to Unlime, Coinbase, Bitstamp, or another external site subjects that visit to the destination's own privacy policy.
Retention and contact
Operational and performance records are retained only for the period needed to monitor and secure the service, according to the production operator's infrastructure policy. Privacy requests can be submitted through unlime.it.
Effective and last reviewed: 2 September 2026.