011. Current storage inventory
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 and bq-tool-favorites-v1: Activated only with consent. They keep tool slugs, open count, last-used time, or pinned tool IDs and contain no tool input or output.
bytequant:news-favorites:v1: Stores the IDs of up to 200 update cards you explicitly save on this device; it stores no title, article body, profile, or tool content.
bytequant:local-agent:v1 and bytequant:local-agent-conversation:v6:en: When you explicitly use Local Agent, these tab-scoped values hold the goal, plan, and up to twelve conversation summaries. They end with the tab session.
WebLLM model cache: Created only after you choose Enable local AI. It contains open-source model weights, tokenizer files, and WebAssembly—not chat content—and may use several hundred megabytes. Remove it by clearing ByteQuant site data in your browser.
bytequant-workspaces (IndexedDB): Stores only Workstation projects you explicitly save, as AES-GCM-256 ciphertext, plus a non-extractable device key. It remains until you delete projects or clear site data; the browser controls quota.
bytequant:workstation-active:v1, bytequant:workstation-handoff:v1, bytequant:workstation-agent-plan:v1, bytequant:workstation-agent-input:v1, and bytequant:tool-transfer:v1: Temporarily hold a project, Agent plan, prepared input, or bounded text you choose to pass in the same tab. Tool handoff expires after 20 minutes; other records end with the tab session.
022. Advertising and technologies we do not use
The current release uses no ByteQuant cross-device identity, fingerprinting, or analytics SDK. The Google AdSense advertising tag loads for publisher ca-pub-4158794981134847, and Google may use cookies or online identifiers when serving ads.
Tool input, files, passwords, and output are not sent to advertising systems. ByteQuant's on-device personalization choice is not advertising consent; where required, ad choices must be presented separately through a Google-certified CMP.
033. Giving, refusing, and withdrawing consent
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 and bq-tool-favorites-v1 immediately. Clearing browser site data removes every local record.
044. ePrivacy and GDPR approach
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.
055. Advertising consent and change management
Before a new purpose, provider, or storage technology is activated, the inventory, privacy notice, and consent interface must be updated. Local-personalization consent cannot be stretched to cover advertising purposes.
The AdSense ads.txt record matches the publisher ID in the site tag; only the AdSense dashboard can conclusively confirm account and site verification. For EEA, UK, and Swiss traffic, a Google-certified CMP integrated with IAB TCF must be published through the AdSense Privacy & Messaging area.
