Cookie Policy
Last updated: August 8, 2026
1. What Cookies Are
Cookies are small text files placed on your device when you visit a website. We and our partners also use similar technologies such as web beacons, pixels, and local storage. Together we call these “cookies.”
2. Types of Cookies We Use
- Strictly necessary — required for the Site to function (security, load balancing, basic preferences). These cannot be switched off.
- Performance / analytics — help us understand how visitors use the Site (e.g., Google Analytics) so we can improve content.
- Functional — remember choices you make (such as preferences) to provide a better experience.
- Advertising / targeting — set by us or advertising partners to deliver and measure relevant ads and may build a profile of your interests. These may involve a “sale” or “share” under state privacy laws.
3. The Cookies We Set
These are the first-party cookies MoneyBricks sets itself. Every one of them is set by us, readable only by us, and never sold or shared with an advertising network.
| Cookie | What it does | How long it lasts |
|---|---|---|
mb_ref | Records the share code from a “?ref=” referral link so the member who referred you gets credit if you sign up. It identifies them, not you. The first referral link you follow wins; a later one never overwrites it. | 30 days, or until you sign up — whichever comes first |
sb-… | Keeps you signed in to your account and lets us refresh your session. Set only after you sign in. | Your session; refreshed while you stay signed in |
mb_team | Holds the pass for a team report you were given a link to. Set only when you open one. | 2 hours |
mb_hq | Holds the sign-in for our own internal operations page. Set only for us. | 8 hours |
We also keep a small amount of information in your browser’s local storage rather than in a cookie — your cookie choices themselves, and by default your BrickScore and reading progress, which stay on your device unless you choose to sync them to an account. See the Privacy Policy for what that covers.
4. Bot Protection on Our Forms
When you submit a form — the waitlist, the contact form, sign-in, or saving a BrickScore — an invisible challenge from Cloudflare Turnstile checks that the submission comes from a person rather than a script. Cloudflare receives your IP address and basic browser signals to make that check, and may store a short-lived token in your browser. This is strictly necessary security: it runs only on submission, it sets no advertising cookie, it builds no profile of you, and nothing it collects is sold or shared with an advertising network. It is listed among the recipients of device and usage data in the Privacy Policy.
5. Managing Cookies
When required, we display a consent banner before any analytics or advertising cookie loads, and you can change your choices at any time via “Your Privacy Choices” in the footer. Two things it does not cover: the cookies that keep you signed in, which the Site cannot work without, and mb_ref, which is written when you arrive on a referral link and so is already set by the time the banner appears. You can clear it — along with anything else here — through your browser settings, and doing so only means the member who referred you goes uncredited. You can also opt out of certain advertising cookies via industry tools such as the Digital Advertising Alliance (optout.aboutads.info) and Network Advertising Initiative (optout.networkadvertising.org). Blocking some cookies may affect how the Site works.
6. Global Privacy Control
We honor the Global Privacy Control (GPC) signal as an opt-out of sale/sharing and targeted advertising where required by law.
7. Changes
We may update this Cookie Policy as our practices or the law change; the “Last updated” date reflects the latest version.