The Brennick website (this site) sets no cookie and stores nothing in your browser. The app sets a small number of cookies when you sign in or choose a setting, every one of them needed for the thing you asked for. There is no advertising cookie, no analytics cookie and no tracking of any kind, so there is no consent banner: there is nothing to consent to.
The website sets no cookies
The pages under brennick.ai, this one included, set no cookie and write nothing to local storage. Page views are counted by a privacy-preserving analytics service whose script uses no cookie, no local storage and no fingerprint of your browser or address; it counts a page view and nothing about you.
The contact form and the pricing page load nothing until you act: the bot-protection check appears only once you start typing in the form, and the plan buttons only link to the sign-up page.
Cookies the app sets
Signing in, using the client portal or choosing a setting sets the cookies below. Each is set by Brennick or by one of the services that run part of the product, and each is listed with what it is for and how long it lasts.
Every cookie on this page is strictly necessary for something you asked for: signing in, staying signed in, finishing a step you started, or keeping a setting you chose. None is used for advertising, analytics or tracking.
Staff sign-in (the firm dashboard)
The staff sign-in service sets these on the sign-in pages and the firm dashboard. They hold your session and nothing else; the service’s documentation says they store no personally identifiable information by default.
__session
- Set by
- The staff sign-in service
- Purpose
- Your signed-in session for the firm dashboard, as a short-lived token the app checks on every request.
- Lasts
- 60 seconds, refreshed while you use the app; gone when you sign out.
- Where
- The app’s own domain, on the sign-in pages and the dashboard.
__client_uat
- Set by
- The staff sign-in service
- Purpose
- A marker of when your sign-in state last changed, so the app knows whether to refresh the session.
- Lasts
- Until you sign out or your browser clears it; the service states no fixed length.
- Where
- The app’s own domain.
__client
- Set by
- The staff sign-in service
- Purpose
- The service’s own long-lived client token, which keeps you signed in between visits.
- Lasts
- As long as your browser keeps it; the service states no fixed length.
- Where
- The sign-in service’s own address, not the app’s pages. It cannot be read by Brennick’s code.
Client portal sign-in
Brennick sets these when a client of a law firm signs in to the portal. Both are locked to the portal’s address and cannot be read by any script.
__Host-brennick_portal
- Set by
- Brennick
- Purpose
- Your portal session: a signed token the server checks on every portal request.
- Lasts
- One hour, renewed while you use the portal; removed when you sign out.
- Where
- The client portal.
__Host-brennick_portal_rt
- Set by
- Brennick
- Purpose
- Renews your portal session without asking you to sign in again.
- Lasts
- 30 days; removed when you sign out.
- Where
- The client portal.
Settings you choose
Set only when you pick the setting. Each holds one word.
brennick_theme
- Set by
- Brennick
- Purpose
- Your screen theme: dark, light or match device, so the first paint is right.
- Lasts
- One year.
- Where
- The app, the client portal and the intake page.
brennick_density
- Set by
- Brennick
- Purpose
- Your table density in the firm dashboard: comfortable or compact.
- Lasts
- One year.
- Where
- The firm dashboard.
Finishing a step you started
Short-lived cookies that carry one step of a flow to the next. None holds anything about you beyond the step.
brennick_awaiting_provisioning
- Set by
- Brennick
- Purpose
- Set when you return from the card step, so the dashboard waits for your firm to be created instead of showing the pricing page again.
- Lasts
- Two minutes.
- Where
- The firm dashboard, once, after checkout.
brennick_intake_firm
- Set by
- Brennick
- Purpose
- After you send an intake, the portal sign-in page can name the firm you contacted. It holds the firm’s public web address name only.
- Lasts
- 90 days.
- Where
- A law firm’s intake page, then the portal sign-in page.
brennick_oauth_<service>
- Set by
- Brennick
- Purpose
- Protects the connection of a calendar or practice-management account to the firm: a signed state that the return from that service must match.
- Lasts
- Ten minutes, and only on the connection address.
- Where
- The firm dashboard, while a firm admin connects a service.
Services with their own pages
Two parts of the product run on another service’s own pages or frame. Any cookie they set is on that service’s address, under that service’s cookie policy; none is set on Brennick’s pages.
Bot-protection check
- Set by
- The bot-protection service
- Purpose
- Tells people from automated abuse on a law firm’s intake page and the contact form. It runs in a frame from the service’s own address and, by its privacy terms, collects only the signals strictly necessary to detect bots; it never receives what you type.
- Lasts
- Per the service’s cookie policy.
- Where
- The service’s own frame on the intake page and the contact form.
Checkout and billing
- Set by
- The payment processor
- Purpose
- Paying for a plan and managing the card happen on the payment processor’s own pages; its fraud-prevention cookies are set there. No payment script loads on Brennick’s pages.
- Lasts
- Per the processor’s cookie settings page (its two fraud-prevention cookies: one year and 30 minutes).
- Where
- The processor’s checkout and billing pages.
Local storage
Brennick’s own code writes nothing to local storage or session storage, on the website or in the app. The staff sign-in service’s script, which runs on the sign-in pages and the firm dashboard, keeps its own working state under its own documentation.
How to control cookies
Your browser lets you see, block and delete cookies for any site. Blocking the sign-in cookies signs you out of the app and the client portal; everything on the website keeps working. The theme and table-density cookies are set only when you choose a setting, and deleting them returns the app to its defaults.
The Privacy Policy explains Do Not Track and Global Privacy Control signals: Brennick does no cross-site tracking and sells or shares no personal information, so there is nothing for either signal to stop.