ByteQuant tools require no HTTP cookies. This page explains the localStorage keys in use, why they exist, and how you can control them.
bq-consent-v1: Keeps your privacy choice, policy version, and decision time for 180 days. This record is essential to remember the choice and avoid asking on every visit.
bq-theme: Remembers the light or dark theme you request. It is treated as essential storage because it delivers an explicit service preference.
bq-tool-usage-v1: Activated only with consent. It keeps tool slug, open count, and last-used time for up to 180 days and contains no tool input or output.
The current release uses no HTTP cookie, cross-device identifier, fingerprint, pixel, analytics SDK, advertising identifier, or third-party tracking tag.
Advertising placeholders are visual layout elements only. They make no request to AdSense or another ad network, and the source contains no publisher identifier.
Optional local personalization is off by default and never pre-ticked. 'Essential only' appears on the same layer as acceptance, and refusing does not reduce tool functionality.
Use the footer's 'Privacy choices' control at any time. Withdrawing consent deletes bq-tool-usage-v1 immediately. Clearing browser site data removes every local record.
Article 5(3) of the ePrivacy Directive generally requires consent, after clear and comprehensive information, before storing or reading information on a device; an exception may apply where storage is strictly necessary for an explicitly requested service.
Under GDPR, consent must be freely given, specific, informed, and expressed by a clear affirmative action. Withdrawal must be as easy as giving consent. National ePrivacy implementation rules must also be assessed.
Before a new purpose, provider, or storage technology is activated, the inventory, privacy notice, and consent interface must be updated. Consent for local personalization cannot be stretched to cover a new purpose.
If Google AdSense is enabled for the EEA, UK, or Switzerland, no ad tag should load until a Google-certified CMP integrated with IAB TCF is configured. An ads.txt record should be added only after a verified publisher identifier exists.