Back to Meticulous Community

Cookie Policy

Last Updated: September 8, 2026


1. What Are Cookies?

Cookies are small text files that are placed on your device (computer, phone, or tablet) when you visit a website. They are widely used to make websites work, work more efficiently, and provide information to the website owner.

We also use similar technologies such as local storage (localStorage), which stores data in your browser.


2. How We Use Cookies

Meticulous Community uses a minimal number of cookies, all of which are necessary for the platform to function or to improve your experience. We do not use any advertising, analytics, or tracking cookies.


3. Cookies We Use

3.1 Strictly Necessary Cookies

These cookies are essential for the Service to function. They cannot be switched off. You can set your browser to block them, but parts of the Service will not work.

Cookie NamePurposeDurationSet By
Supabase auth cookies (sb-*)Authentication — keeps you logged in and maintains your sessionSession (expires when you close your browser or your session expires)Supabase (our database and authentication provider)

Lawful basis: These cookies are strictly necessary for the performance of the service you have requested (Article 6(1)(b) GDPR). No consent is required, per Article 5(3) of the ePrivacy Directive.

3.2 Functional Cookies

These cookies enable enhanced functionality and personalization. They are not strictly necessary but improve your experience.

Cookie NamePurposeDurationSet By
Admin role cache (admin users only)Caches your admin permissions to avoid checking on every page load1 hourMeticulous Community (HMAC-signed for security)

Lawful basis: Our legitimate interest in providing a smooth experience for our administrators (Article 6(1)(f) GDPR). Regular users never receive this cookie.

Why there is usually no cookie banner: None of the cookies above require consent. The one cookie that does — the share attribution cookie in Section 3.3 — is asked about, on the page you arrive at, only where the law requires it.


3.3 Share Attribution Cookies

When you arrive through a link someone shared — a brew, a recipe, a coffee, a roaster, a profile, or a widget embedded on a roaster's website or email — we may remember which share brought you, so that the person or roaster who shared gets credit if you later sign up or visit our shop. See the Privacy Policy, Section 4.4.

Cookie NamePurposeDurationSet By
mc_refHolds a random share token, the time you arrived, and three labels: who shared (a roaster's name or "member"), how (link, QR code, embed), and what (brew, recipe, coffee, roaster, profile). Contains no personal data. Readable by our shop at meticuloushome.com so a later visit there can credit the share.30 daysMeticulous Community
mc_consentRemembers your answer to the attribution prompt (allowed or declined) so we do not ask again.12 months (or the browser session while the question is pending)Meticulous Community

Lawful basis: Your consent (Article 6(1)(a) GDPR) in the EU, EEA, UK, and Switzerland, where we set mc_ref only after you choose Allow on the prompt. Elsewhere, our legitimate interest in understanding how people find the community (Article 6(1)(f) GDPR); you can clear the cookie at any time (Section 7).


4. Local Storage

We also use your browser's localStorage for the following:

KeyPurposeWhen Set
__DEBUG_LOGGING__Enables verbose logging in the browser console for troubleshooting. Only active if you manually enable it.Only when you explicitly set it (developer feature)

Note: This is not set automatically. It is a developer/debugging tool that you can enable by opening your browser console and running: localStorage.setItem('__DEBUG_LOGGING__', 'true').

We additionally use your browser's IndexedDB and a service worker cache to store your own data on your own device (recently viewed pages, your shots) so the app works offline and loads faster. This data never leaves your device and is cleared when you clear your browser storage.


5. Third-Party Cookies

We do not use any third-party cookies. Specifically:

The only third-party involvement is Supabase (our database provider), which sets authentication cookies on our behalf as a data processor.


6. Cookies We Do NOT Use

For clarity, the following types of cookies are not used by Meticulous Community:

TypeStatus
Advertising / targeting cookiesNot used
Third-party analytics cookies (Google Analytics, Mixpanel, etc.)Not used — our one first-party attribution cookie is described in Section 3.3
Social media tracking pixelsNot used
Cross-site tracking cookiesNot used
Performance monitoring cookies (Hotjar, FullStory, etc.)Not used
A/B testing cookiesNot used
Email marketing cookiesNot used

A note on product analytics: We measure how the product is used (pages viewed, features used, performance) to improve it — see our Privacy Policy, Section 4.3. This measurement is cookieless: it does not set any cookies or use cross-site tracking, which is why no consent banner is required. If that ever changes, we will ask for your consent before setting any analytics cookie.


7. Managing Cookies

7.1 When You See a Consent Prompt

Almost everything we set is strictly necessary or minimally functional (see Section 3), so there is no site-wide cookie banner. The one exception is the share attribution cookie (Section 3.3): if you arrive through a shared link from the EU, EEA, UK, or Switzerland, a short prompt on that page asks whether we may remember who shared it with you. Choosing No thanks sets nothing but a record of your answer. You can change your mind at any time by clearing the mc_consent and mc_ref cookies in your browser (Section 7.3).

7.2 Browser Settings

You can also control cookies through your browser settings. Most browsers allow you to:

Note: If you block strictly necessary cookies (Supabase auth), you will not be able to log in to the Service.

7.3 How to Manage Cookies in Common Browsers


8. Updates to This Policy

We may update this Cookie Policy from time to time. When we add new cookies or change how we use existing ones, we will:


9. Contact Us

If you have questions about our use of cookies, contact us at:


10. Related Policies


This Cookie Policy was last reviewed on July 13, 2026.