Legal

Cookies and local storage

Everything Brieflee keeps in your browser, item by item, and which of it you can switch off. Google Analytics only if you accept it; our ChatGPT and Google ads measurement and Google remarketing unless you switch them off, or in the EU, the EEA, the UK and Switzerland only if you accept them.

We use Google Analytics, and only if you say yes. It loads once you tick Analytics in the cookie banner, sets the two cookies listed below, and tells Google which pages were opened and which features were used. Decline and it does not load at all; turn it off later and we delete its cookies.

Our ChatGPT and Google ads measurement is on unless you switch it off, except in the EU, the EEA, the UK and Switzerland, where it runs only once you accept it. The OpenAI ads pixel runs on our public pages, our sign-in pages and briefleeone.com so that an advert we paid for inside ChatGPT can be matched to the sign-up, plan, waitlist entry or order it led to, and Google’s ads tag runs on the same pages of brieflee.ai so that an advert we paid for on Google can be matched to the account it led to, and so that Google can show our adverts again to people who have visited (remarketing). Where you are asked first and have not answered yet, Google’s tag runs with all of its consent settings off: it sets and reads no cookie, and Google uses what it sends only to estimate how many visits led to sign-ups. Switch Advertising off, or choose Reject all, and both stop and their cookies are removed. There is no session recorder, and nothing about you is sold.

One third party does run code in your browser, and we would rather name it than let you find it in the page source. Cloudflare protects this site from automated abuse, and its bot detection injects a small script on every page load which reports to Cloudflare whether the browser looks automated. It is a security measure rather than an analytics one: it does not identify you, does not track you between sites, and we receive nothing from it. It is listed in our sub-processor list.

A few cookies, and a lot that is not cookies

Brieflee itself sets no HTTP cookies. It uses your browser’s local storage, which is the same idea by a different mechanism: a small amount of data kept by your browser, on your device, readable only by brieflee.ai and never attached to requests to anyone else. This page calls that storage rather than cookies because that is what it is.

Three exceptions set real cookies: Google Analytics (_ga and _ga_…), only once you have accepted it, and the two ads measurements, unless you switch Advertising off or, in the EU, the EEA, the UK and Switzerland, until you accept them: the OpenAI ads pixel (__oppref and __obref), on our public pages, sign-in pages and briefleeone.com, and Google’s ads tag (_gcl_…), on the same pages of brieflee.ai, which may also set Google’s own cookies on Google’s domains for remarketing. They are there so that an advert we paid for can be matched to what it led to. Every kind is listed below, item by item.

What we store

NameWhat it doesCategoryKept for
de.auth.tokenYour sign-in token. Without it you are signed out on every page load.EssentialUntil you sign out
de.auth.userA cached copy of your own profile, so the app paints instantly instead of flashing empty.EssentialUntil you sign out
de.auth.lastactiveWhen this browser was last used, for the inactivity sign-out. Shared between tabs so one idle tab cannot sign out the one you are working in.EssentialUntil you sign out
de.social.state, de.social.recentOne-time values tying a social sign-in back to the browser that started it. They are what stop someone mailing you a callback link that swaps your session for theirs. The first lives in the tab that pressed the button; the second is shared by every window of this browser, because the sign-in can come back in a different one.EssentialThe sign-in attempt; never accepted after ten minutes. What an abandoned attempt leaves is cleared at the next sign-in, or when the tab closes.
de.desktop.signinA one-time secret for a Google or Microsoft sign-in that the Brieflee app for Mac sent to your web browser. Only the app window holding it can finish that sign-in, so a link handed to another program signs nobody in. Written only inside that app.EssentialThe sign-in attempt; never accepted after ten minutes. Removed when the sign-in finishes or you press Cancel; what an abandoned attempt leaves is replaced at the next one.
de.consent.v1This decision. Storing it is what stops us asking on every page.EssentialUntil you change it
de.tab.*, de.ai.*The meeting panel's open tab and its AI conversation. Teams reloads the panel every time you switch tab during a call, and these are what survive it.EssentialThe meeting
de.setupdone.*That you dismissed the setup step for a meeting. The server cannot tell “not started” from “already dismissed” until the first transcript arrives.EssentialThe meeting
de.shell.tour.v1.<user>, de_guide_seen_v1That you have seen the product tour. Without it the tour reopens on every visit, including over a live call.Essential1 year
de.notif.seen.v1Which notifications you have read. Without it every notification is permanently unread.Essential1 year
de.sample.onThat you turned on “Explore sample data”. Cleared when the tab closes, so a demo never outlives the session.EssentialThe browser tab
de.desktop.update.quietThat you dismissed the update notice in the Brieflee app for Windows, and for which version, so it does not come back on every page while the app stays open. Written only inside that app; the next version is announced again.EssentialUntil you quit the app
de.chunk-reloadedA one-shot guard that stops a failed script load turning into a reload loop after a deploy.EssentialMinutes
de.support.sessionThe chat you started with the assistant on this site, so moving to another page does not make you retype your details to carry on. Written only once you have filled in that form, and deleted by “Start a new chat”.EssentialUntil you start a new chat
de.calendar.viewWhich calendar view you last had open. Decline and the calendar opens on its default.Preference1 year
de.hint.*Which one-off hints you have dismissed. Decline and a dismissed hint can come back next visit.Preference1 year
_gaGoogle Analytics' own cookie. It lets Google tell that two visits came from the same browser, so a return visit is not counted as a new person.Analytics2 years, or until you turn Analytics off
_ga_<property>The second half of the same thing: which visit you are on, for the Brieflee property specifically.Analytics2 years, or until you turn Analytics off
__opprefOpenAI's click reference: which of its adverts inside ChatGPT brought you here, so the sign-up, waitlist entry or order it led to can be matched to it. Set by OpenAI's pixel on our public pages, the sign-in pages and briefleeone.com unless you switch Advertising off (in the EU, the EEA, the UK and Switzerland, only once you accept it): never inside the app and never in a meeting.Advertising30 days, or until you switch Advertising off
__obrefA random reference OpenAI's pixel keeps for this browser, so two of its reports from the same browser can be told apart from two browsers. Same pages and the same rule as __oppref.Advertising365 days, or until you switch Advertising off
_gcl_aw, _gcl_gbGoogle's click reference: which of its adverts brought you here, so the account it led to can be matched to it. Set by Google's ads tag on our public pages and sign-in pages unless you switch Advertising off (in the EU, the EEA, the UK and Switzerland, only once you accept it): never inside the app and never in a meeting.Advertising90 days, or until you switch Advertising off
_gcl_auA random reference Google's ads tag keeps for this browser, so a sign-up can be matched to an advert clicked earlier in the same browser. Same pages and the same rule as _gcl_aw.Advertising90 days, or until you switch Advertising off
doubleclick.net, google.comGoogle's own cookies on its own domains, which its ads tag may set or read when it counts a visit for remarketing. They belong to Google, not to brieflee.ai, so we can neither read nor delete them: your browser can clear them, and adssettings.google.com controls the adverts Google shows you. Same pages and the same rule as _gcl_aw.AdvertisingAs Google sets them

Why most of it cannot be switched off

Everything marked Essential is there because the product does not work without it: you would be signed out constantly, the meeting panel would lose your conversation every time Teams reloaded it, and the guided tour would reopen over a live call. Under the ePrivacy rules, storage strictly necessary for a service you asked for does not require consent, and we have kept that list to what genuinely earns the description rather than filing conveniences under it.

The two Preference items are the opposite: switch them off and nothing breaks. The calendar opens on its default view, and a hint you dismissed can reappear. That is the whole cost. The two Analytics items cost you nothing at all: they are for us, not for you, which is exactly why they are off until you say otherwise.

Changing your mind

Use Cookie settings in the footer of any page. Withdrawing is one click, exactly as giving it was, and it does not merely stop future writes: anything already stored under Preferences is deleted at that moment.

What Google Analytics is told, and what it is not

Before any address is sent, the search terms are removed and every identifier is replaced with a placeholder. Google is told that someone opened /post-meeting/:id, never which meeting; /ai, never the question you typed there; and of a shared report only that one was opened, never the link. It receives no audio, no transcript, no summary, and no meeting, client or project name.

It never runs inside the meeting panel in Teams, Google Meet or Zoom, where the page on screen is somebody’s live call. And this page changed in the same release as the script: when the category appeared in the banner everyone was asked again, rather than carried over on a decision made about something else.