Cookie Policy

2. Storage We Use, At a Glance

Here’s everything QBRBuilder stores in your browser:

3. Essential Local Storage

When you make a choice in our cookie bar, we save exactly that choice in your browser’s local storage under the key qbrbuilder-cookie-consent. That’s the only reason it exists: so you’re not asked to make the same decision on every page load.

This entry never leaves your browser, is never sent to our servers, and isn’t shared with anyone. Because it’s strictly necessary for the bar to function, it doesn’t require your consent under GDPR or the ePrivacy Directive, and it’s set regardless of which option you choose.

We also keep your signed-in session in local storage — a key starting sb-, set by our authentication provider, Supabase — so you don’t have to log in on every visit. Like the consent key, this stays in your browser and is used only to authenticate you with our own servers; it’s equally strictly necessary and equally exempt from consent under GDPR/ePrivacy.

4. Functional Local Storage

If you’re signed in, we optionally cache a few small, non-essential things in your browser’s local storage purely for convenience: your Profile page’s name/title/company/timezone fields and avatar preview (under keys starting qbr_profile_settings_ and qbr_profile_avatar_), and whether you’ve already dismissed the Studio view-toggle explainer (qbr_studio_view_toggle_explainer_seen).

None of this is required for the Services to work — your actual profile data is always saved to our servers regardless of this setting, and the Profile page falls back to that server copy if this cache is empty or disabled. It exists only to make repeat visits marginally faster and to avoid re-showing a tooltip you’ve already dismissed, which is why it’s optional rather than essential.

We don’t write any of it until you turn Functional on in Section 7, and turning it off there clears whatever’s already stored, immediately.

5. Google Analytics

If, and only if, you turn Analytics on below, we use Google Analytics to understand basic site traffic — things like which pages are visited, how often, and from roughly which region or device type. Google’s own tag-loading script (gtag.js) loads on every visit and sends Google a single, cookieless signal recording your current consent choice — this is Google’s own required “Consent Mode” mechanism, and it carries no page views, no identifying data, and sets no cookie. No actual analytics tracking, no _ga or _ga_* cookie, and no page-view or visit data reaches Google until you turn Analytics on below. Google Analytics is the only analytics tool we use — we don’t run any other tracking, measurement, or tag-management tool on the Services.

Analytics data streams directly from your browser to Google’s servers. We don’t run our own analytics collector, and no analytics data is stored on our servers or on any QBRBuilder developer’s machine. The cookies Google Analytics sets (_ga, _ga_*) expire after up to 2 years. Google processes this data under its own Privacy Policy.

If Analytics is off, Google Analytics itself stays fully blocked: no _ga or _ga_* cookie is ever set, and no page-view or analytics data is ever sent. The only thing that still happens is the cookieless consent-signal ping described above — Google’s own mechanism for remembering that you’ve said no, which carries no personal or tracking data.

6. No Advertising or Marketing Cookies

QBRBuilder does not use advertising cookies, tracking pixels, or any third-party ad-tracking technology — no Meta/Facebook Pixel, no Google Tag Manager container, no retargeting or conversion tags of any kind. There is no “marketing” or “advertising” category in Section 2’s table because nothing in that category exists on the Services today.

This also means we do not “sell” or “share” personal information as those terms are defined under the California Consumer Privacy Act (CCPA), as amended by the CPRA, or under comparable laws in other US states. Google Analytics, described in Section 5, is used solely for first-party traffic measurement, not for cross-context behavioral advertising, and we receive no payment or other valuable consideration from Google or anyone else for the data it processes. See our Privacy Policy’s US State Privacy Rights section for the rights available to you if you’re a resident of California or another US state with a comprehensive privacy law.

Because the choices in Section 7 ask for your affirmative, opt-in consent before any non-essential storage is set — rather than only offering an opt-out afterward — they meet the EU’s GDPR/ePrivacy standard and, being strictly more protective, also satisfy the opt-out-based US state laws referenced above.

7. Manage Your Preferences

Essential storage is always on and has no toggle — it’s what lets the other two settings, and your sign-in, work at all. Turn Functional and Analytics on or off below, then save; your choice applies immediately and replaces whatever the bottom bar has recorded, since both read and write the same stored choice.

You can also clear this site’s local storage manually through your browser’s own settings, though doing so also signs you out.

8. Changes to This Policy

We may update this Cookie Policy from time to time, for example if we add or remove a tracking technology. If we make material changes, we’ll update the “Last updated” date above. Continuing to use the Services after a change takes effect means you accept the updated policy.

9. Contact Us

Questions about this Cookie Policy? Reach us at:

QBRBuilder
Email: contact@qbrbuilder.com