Skip to content

Cookies & device storage

What this application uses

The reviewed application does not include browser advertising pixels, session replay or visitor analytics scripts. It uses the cookies and device storage below to sign you in, protect forms, remember chosen interface settings and recover work. Server-side reporting integrations do not themselves install website tracking cookies.

These cookies are needed for the account functions you request. They are HttpOnly and SameSite=Lax; Secure is enabled for HTTPS production configuration.

Device storage

BuildQuote uses bq- and bq: keys for editing recovery, site sketches, offline clock events, AI conversation drafts and interface preferences. buildquote-active-identity helps prevent one account from inheriting another account’s drafts. Local storage persists until removed; session storage normally ends with the tab. Data is not kept safe by a cookie banner alone: use your own device or sign out when finished.

Sign-out and account changes clear BuildQuote draft keys. Browser settings can clear storage, but doing so can permanently discard unsynced sketches or clock events. Save or sync work first. Clearing device storage does not remove business records already saved on the server.

Maps, address search and optional tracking

Map providers receive your IP address and tile requests when a map loads. Address search sends what you type to the configured address provider, as explained beside the search box. External links and Stripe checkout have their own notices.

No “accept all” banner is needed merely to claim consent where there are no optional trackers. If visitor analytics, advertising, embedded media or other non-essential storage is added, it must be inventoried and assessed first. Where consent is required, block it before choice; provide equally accessible accept/reject controls, granular settings and an easy withdrawal route. Do not treat scrolling, silence or a pre-ticked box as consent.