BrimkyBrimky
Note legali Brimky

Policy e termini

Brimky è un servizio gestito di siti web, CMS e hosting fornito da Custom Software Solutions LLC. Le pagine seguenti regolano l'uso della nostra piattaforma.

Segnalare un abuso? Scrivi a [email protected] o usa il modulo. Per il copyright vedi la Policy DMCA.
Segnala abuso →
Mostrata la versione inglese

Stiamo preparando una versione in Italiano delle nostre pagine legali, revisionata da un legale. Per ora fa fede la versione inglese qui sotto.

In vigore dal 2026-05-15Ultimo aggiornamento 2026-05-15

Cookie Policy

This policy explains what cookies and similar technologies Brimky (operated by Custom Software Solutions LLC) sets when you use our website, dashboard, or admin tools.

1. What are cookies?

Cookies are small text files stored by your browser when you visit a website. They allow sites to remember sessions, preferences, and related state.

2. Cookies we set

Strictly necessary

These cookies make the site work and cannot be turned off via the Services. They are not used for tracking or advertising.

  • Customer session cookie — keeps you logged into the customer dashboard after using a magic link.
  • Admin session cookie — keeps admin staff logged into the admin panel.
  • CSRF / form cookies — protect against cross-site-request-forgery on form submissions.

Functional

  • Theme / preference cookies— remember UI choices you make during a session (e.g. the customisation wizard’s color schema preview).

Analytics

Customer-deployed sites use a first-party, no-third-party analytics pipeline that hashes visitor IPs daily and does not set tracking cookies.

The Brimkymarketing site (the templates catalog, landing page, and related public pages) also runs lightweight first-party analytics. No third parties are involved — the events are stored on our own servers and never sold or shared for advertising. Specifically, when you browse the marketing pages we record:

  • Page views (which page you opened, your locale).
  • Template interactions (which template detail you opened, which “Customize” button you clicked).
  • Outbound link clicks (which external URL you followed).
  • Help-chat opens (whether you opened the AI / human-team chat drawer).
  • The end-of-session signal (so we can measure session length).

These events do notstore your name, email, or any account identifier. To group events from the same browser we use two random opaque tokens kept in your browser’s localStorage (a long-lived visitor token) and sessionStorage(a per-tab session token). Both are first-party (no third-party domain is involved) and you can clear them at any time via your browser’s site-data controls.

We also store a coarse IP for spam triage: IPv4 addresses are masked to /24 (the last octet is zeroed) and IPv6 addresses are truncated to /64 before insertion, so the stored value cannot identify a specific household. We honor the legacy Do Not Track browser signal — if navigator.doNotTrackis “1” we do not record any of these events.

We do not use third-party ad cookies, retargeting pixels, session-replay tools, or cross-site identifiers on the Brimky website.

3. Cookies on customer-deployed sites

Cookies set by Client’s deployed website (e.g. analytics, chat widgets, embedded video) are Client’s responsibility. If Client uses tracking technologies that require visitor consent under EU / UK law, Client must provide an appropriate consent UI and disclose those cookies in their own privacy policy.

4. Controlling cookies

You can block or clear cookies in your browser settings. Blocking strictly-necessary cookies will sign you out and break authenticated flows.

5. Changes

If our cookie use changes (for example, if we add analytics), we will update this page. See also the Privacy Policy for broader detail on what we collect and why.