1. Necessary storage
The current application sets the first-party pb_auth cookie for sign-in. It is marked HttpOnly and SameSite=Lax, and Secure in production. Its expiry follows the configured authentication token. The final notice must state the actual configured duration after production verification.
The editor stores preferences such as panel width and selected views in local storage so your workspace can remember them. These values normally remain until overwritten or cleared in your browser. The basket itself is stored with your account in the database. Necessary storage is used only for the service it supports.
2. Optional tracking
We do not treat continued browsing as consent to advertising tracking. Any optional analytics, advertising pixel or third-party tracking must stay disabled until the required informed consent is obtained. Rejecting it must not prevent normal shopping or design use.
A privacy-conscious first-party measurement still needs an appropriate legal assessment. The presence of view counters in the source code is not proof that every analytics implementation is exempt from consent. The deployed website must be checked before this notice is finalised.
3. External services and choices
A hosted payment or identity-verification page may use the provider's necessary storage under its own notice. External images and services may receive connection information even without placing a cookie. The Privacy notice and final provider register explain relevant recipients.
You can clear browser storage or block cookies through your browser. Doing so may sign you out or reset preferences. If optional tracking is introduced, a persistent cookie-settings control must let you withdraw consent as easily as you gave it. Questions can be sent to [support email to be confirmed].
Before this draft can be published
- Run a production browser inventory
- Confirm authentication expiry
- Prevent optional scripts before consent
- Provide withdrawal of consent if tracking is introduced