Briesa sets a handful of cookies, each one there to make the product work or to remember how you left it. None is for advertising and none follows you to other sites. You can control cookies in your browser's settings, though signing in needs them.
Essential12 hours
briesa.sessionWhen you sign in, Briesa sets one session cookie. It is signed, it cannot be read by any script on the page, and it belongs to the one address that issued it, so it never follows you across the platform's hosts. It carries its own expiry inside the signature, so a copy kept past its time stops working.
Essential10 minutes
briesa.ssoHolds the details of a single sign-on attempt while you are away at your group's identity provider, so the answer that comes back can be matched to the request that went out.
Essential12 hours
briesa.portalRemembers that a vendor or landlord gave the right PIN for their portal, so they are not asked again during the same visit.
Preference30 days
briesa.demoRecords only that you have passed the demo's gate, so the tour opens straight away next time. It holds nothing about you.
Preference1 year
briesa.teamRemembers the team you last selected in the product, so it opens where you left it.
Preference1 year
briesa.chrome · briesa.docs.sidebarRemembers whether the sidebar was open and how wide, so the page draws in that shape before anything moves.
Staff only4 hours
briesa.admin.session · briesa.admin.navSet only for Briesa staff signing in to the console, never for an agency or its people.
Not a cookieUntil cleared
briesa.themeYour light or dark theme, and everything you do in the demo, stay in your browser's own storage. None of it is sent to Briesa.