Last updated 21 August 2026
Cookie Policy
Bricklark sets three cookies. All three exist to keep you signed in. We do not use cookies for analytics, advertising or tracking you across other sites.
What we set
| Whose data | What we hold | Why |
|---|---|---|
| bricklark_token | Signed session token for a business owner or staff member. Expires after 7 days. | Keeps you signed in to the dashboard |
| bricklark_worker_token | Signed session token for a field worker. Expires after 30 days. | Keeps a worker signed in to the worker portal |
| bricklark_portal | Signed session token for a client. Expires after 30 days. | Keeps a client signed in to their portal |
All three are HTTP-only, meaning JavaScript on the page cannot read them, and are sent only over an encrypted connection in production. Each expires on the schedule above, or immediately when you sign out. Crews and clients get a longer session than office staff deliberately: a worker on a site should not be signed out mid-job.
Why there is no cookie banner
Consent banners exist for cookies that are not strictly necessary — analytics, advertising, profiling. Bricklark sets none of those. A cookie that only keeps you signed in is exempt, so asking you to approve it would be theatre rather than a choice.
If we ever add analytics, we will ask first and this page will say so.
Turning them off
Your browser can block or delete cookies. Because ours carry your session, blocking them means you cannot stay signed in — the product will not work.
Third parties
Some services we rely on may set their own cookies when you interact with them directly — notably Stripe during a payment, for fraud prevention. Those are governed by their policies. The services listed in our Privacy Policy are the full set we use.