Cookies

Briesa sets a handful of cookies, each one there to make the product work or to remember how you left it. The website alone also carries Meta's pixel, which sets two advertising cookies so that a visit from a Meta ad can be counted; the product sets none. You can control cookies in your browser's settings, though signing in needs them.

A two-storey townhouse at dusk, its entry lit

Staying signed in

Essential12 hours

briesa.session

When 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. Briesa's staff use the same cookie to open the console, and must give an authenticator code first.

  • Essential1 hour

    Signing in or up

    briesa.pending

    Holds the email address you entered while the code is on its way to it, so the next step knows who it is asking.

  • Essential10 minutes

    Signing in through your group

    briesa.sso · briesa.oauth

    Holds 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

    Opening a portal

    briesa.portal

    Remembers that a vendor or landlord gave the right PIN for their portal, so they are not asked again during the same visit.

  • Preference30 days

    Passing the demo's gate

    briesa.demo

    Records only that you have passed the demo's gate, so the tour opens straight away next time. It holds nothing about you.

  • Preference1 year

    The team you chose

    briesa.team

    Remembers the team you last selected in the product, so it opens where you left it.

  • Preference1 year

    How you left the layout

    briesa.chrome · briesa.docs.sidebar · briesa.admin.nav

    Remembers whether a sidebar was open and how wide, so the page draws in that shape before anything moves. The last one is set only in Briesa's staff console.

  • Advertising90 days

    A visit from a Meta ad

    _fbp · _fbc

    Set by Meta's pixel on briesa.com, and only there: the first tells one browser's visits apart, the second is set when you arrive from a Meta ad and carries its click id, so Meta can report which ads brought people to the site. Meta's own policy governs what it does with them. Neither is set on the product's hosts, and a browser that blocks third-party trackers blocks both.

  • Not a cookieUntil cleared

    Stored in your browser instead

    briesa.theme

    Your 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.