This Cookie Policy explains what cookies and similar technologies (such as local storage) BrioMon Technologies LLC ("BrioMon", "we", "us") uses on briomon.com and its related applications, why we use them, and the choices available to you. It should be read together with our Privacy Policy.
What This Policy Covers
This Cookie Policy explains what cookies and similar technologies (such as local storage) BrioMon Technologies LLC ("BrioMon", "we", "us") uses on briomon.com and its related applications, why we use them, and the choices available to you. It should be read together with our Privacy Policy.
What Are Cookies?
Cookies are small text files placed on your device when you visit a website. They allow a site to recognize your device, remember information about your visit (such as whether you're logged in), and function correctly across page loads. "Similar technologies" includes browser local storage and session storage, which some parts of BrioMon also use for the same purposes described below.
The Short Answer
BrioMon does not use cookies for advertising, cross-site tracking, or behavioral profiling, and no cookie is set at all until you create an account or log in. The only cookies we set ourselves are strictly necessary for the site to function -- keeping you signed in and managing session security. We do not currently use any analytics, marketing, or advertising cookies of our own.
Cookies We Set Directly
The table below lists every cookie BrioMon's own code sets on your browser, and only after you sign up or log in -- nothing is set while browsing the public marketing pages.
| Cookie | Set by | Purpose | Duration |
|---|---|---|---|
| sb-<project-ref>-auth-token (and numbered parts, e.g. .0, .1) | BrioMon (via Supabase Auth) | Keeps you signed in; stores your authentication session so you aren't asked to log in on every page. | Set by Supabase Auth session settings -- confirm the exact value under Supabase Dashboard → Authentication → Sessions. |
| bm_session_activity | BrioMon | Tracks how recently you were active so an idle session can be signed out automatically -- 2 hours of inactivity for customer accounts, 12 hours for staff accounts, with a 30-day absolute limit regardless of activity. | 30 days (or sooner, per the inactivity rule) |
Every cookie in this table is Strictly Necessary -- BrioMon does not set any Functional, Analytics, or Marketing cookies of its own.
Third-Party Services
Some features on BrioMon rely on vetted third-party infrastructure providers who may set their own cookies or local storage tokens. We don't control these directly, and they only load on the specific pages or actions described below -- not sitewide.
5.1 Payment Checkout & Merchants of Record (2Checkout & Paddle)
When purchasing an individual subscription, MCMP certification, or corporate seat plan, payment processing is handled externally via our Merchant of Record (MoR) partners:
- 2Checkout / 2Monetize (Verifone): Serves as the primary Merchant of Record for individual subscriptions and one-time MCMP purchases.
- Paddle: Serves as the primary Merchant of Record for corporate annual invoicing.
When you launch checkout, you interact with secure, embedded, or hosted payment environments operated by 2Checkout or Paddle. These processors deploy strictly necessary cookies and local storage tokens solely on their domains to manage session state, calculate localized tax (VAT/GST/Sales Tax), and enforce PCI-DSS Level 1 fraud prevention. BrioMon never processes, stores, or sees full payment card details or banking credentials on its servers.
5.2 Cloudflare Stream (Video Playback)
MCMP course videos, exam media, and MCMD/Sanctuary guided-practice videos are played through an embedded Cloudflare Stream player, loaded only on the pages where that content actually plays. Cloudflare may set cookies scoped to its own domain in connection with video delivery. See Cloudflare's cookie policy for details.
5.3 Google (Sign-In)
If you choose "Continue with Google" to sign in, you're redirected to Google's own sign-in flow, which is subject to Google's cookie and privacy policies. BrioMon does not receive or set any cookies as part of that redirect beyond the authentication cookies described in Section 4 once you're signed back in on our site.
Consent & Your Choices
Because every cookie BrioMon sets directly is strictly necessary -- there is no functioning account or session without them -- many privacy frameworks (including the EU/UK ePrivacy rules) do not require a consent banner or opt-out mechanism for these specific cookies. That said, requirements differ by jurisdiction, and this section is exactly what a reviewing attorney should confirm against each region BrioMon actually operates in.
You always have the following controls, regardless of jurisdiction:
- Browser settings: every major browser lets you view, delete, or block cookies, and to be notified before a cookie is set. Blocking BrioMon's necessary cookies will prevent you from staying logged in.
- Account deletion: removing your account removes the need for these cookies going forward.
If BrioMon adds analytics, marketing, or advertising cookies in the future, this policy -- and the consent mechanism offered to visitors -- will need to be updated accordingly. In most jurisdictions, that would require an opt-in banner before any such cookie is set, not just a notice.
Changes to This Policy
We'll update this page whenever the cookies or third-party services described above change. The "Last Updated" date at the top reflects the most recent revision.
Contact
Contact BrioMon
BrioMon Technologies LLC
1603 Capitol Avenue, Suite 413
Cheyenne, WY 82001, USA
Questions about this policy: privacy@briomon.com
General enquiries: connect@briomon.com
Website: briomon.com