Brindle Cookie Policy

Last updated 27 July 2025

1. About this policy

This Cookie Policy explains how Brindle ("we", "us", "our") uses cookies and similar technologies on the Brindle website and application (the "Site"). It also explains your choices about these technologies.

2. What are cookies?

Cookies are small text files placed on your device to store data that can be retrieved by a web server in the domain that placed the cookie. Cookies may be session cookies (expire when you close your browser) or persistent cookies (remain until they expire or you delete them). We may also use similar technologies such as localStorage and pixels.

3. How we use cookies

We use cookies to:

  • Ensure the Site works securely and as expected (strictly necessary)
  • Authenticate users and maintain sessions
  • Prevent fraud and abuse (e.g., reCAPTCHA)
  • Measure and improve performance and user experience (analytics; only if enabled and consented)
  • Remember some preferences (where applicable)

4. Types of cookies we use

A) Strictly necessary (cannot be switched off)

Purpose: Core functionality, security, load-balancing, session continuity. Examples (names vary by implementation) include Supabase auth/session cookies (access/refresh tokens or SSR session cookies) and app routing/session indicators. Legal basis: our legitimate interests in running a secure, functional service.

B) Performance & analytics (optional; enabled only with your consent)

Provider: PostHog. Purpose: understand usage and improve features (pageviews, events, funnels, performance). Examples: ph_* or similar PostHog cookies used to distinguish users and sessions. Legal basis: your consent (not set unless/until you consent).

C) Security & fraud prevention

Provider: Google reCAPTCHA (used on forms such as contact/ebook). Purpose: detect and prevent automated abuse/bot traffic. Google reCAPTCHA may set cookies like NID, 1P_JAR or other identifiers to provide its service. Legal basis: our legitimate interests in protecting the Site and users.

D) Functionality (only if/when introduced)

Purpose: remember user selections and preferences (e.g., UI, locale). Status: not widely used today; may be added later to improve UX. Legal basis: your consent or our legitimate interests, depending on use.

5. Third-party cookies we may use

  • Google reCAPTCHA (security; required to submit certain forms)
  • PostHog (analytics; set only if analytics is enabled and you consent)

Note: Providers may change over time; we’ll update this policy as needed.

6. Do we keep cookies?

Strictly necessary & security cookies: yes, these are set and kept as required for the Site to work (e.g., Supabase auth/session, reCAPTCHA on protected forms). Analytics cookies: only if analytics is enabled in our environment and you’ve consented. If disabled or you decline consent, these are not set. We anticipate continuing to use necessary cookies; analytics may be enabled/expanded in future based on consent.

7. Cookie retention

  • Session cookies: removed when you close your browser
  • Persistent cookies: retained until their set expiration or you delete them via your browser (typical ranges: days to 13 months)

8. Your choices

Where required by law, we will ask for consent before setting non-essential cookies. You can withdraw consent at any time via cookie settings (when available) or by clearing cookies in your browser. Most browsers let you block or delete cookies; blocking necessary cookies may affect Site functionality. The Site may not respond to Do Not Track (DNT) signals—use the cookie settings and browser controls described above.

9. Changes to this policy

We may update this policy from time to time. Any changes will be posted on this page with an updated “Last updated” date.

10. Contact us

If you have questions about our use of cookies or this policy, please contact us at info@brindleai.com.