Cookies and local storage policy

1. What browser storage means

Cookies are small values attached to web requests. Local storage is a browser database available to scripts on the same origin. The current static build uses local storage for functional state and quality-assurance events; it does not require cross-site advertising cookies.

2. Consent record

dbt_consent_v1 records “accepted” or “declined” so the choice bar does not repeatedly obscure the site. Declining leaves core local tools available because they operate only in your browser. You can revisit the choice by clearing site data.

3. Functional project records

dbt_fit_plan_v1 stores configurator answers; dbt_planning_signal_v1 stores the calculated planning range; dbt_capability_shortlist_v1 stores selected capabilities; and dbt_contact_draft_v1 stores draft contact fields. Each has a clear or reset control. Do not enter secrets or sensitive records.

4. Local event queue

dbt_event_queue_v1 retains up to 250 recent interaction events for functional QA, including page, click label, filter count and flow stage. It is not evidence of server delivery. Raw email addresses are excluded from event payloads.

5. Newsletter validation

The newsletter demo validates an address but does not save the raw email to the event queue or claim a subscription was sent. A future connected mailing provider would require an updated notice describing that provider and consent path.

6. Lifetimes and controls

Local-storage records generally remain until reset through the site or cleared in browser settings. Private-browsing modes may remove them earlier. Blocking all storage can prevent preferences, drafts and configurator state from persisting, while ordinary content remains available.

7. Changes and contact

If analytics or external embedded services are introduced, this policy and the consent interface should be updated before activation. Questions about site storage may be sent to [email protected].