Legal

Cookie policy

Last updated: 15/11/2026

1. What cookies are

Cookies are small files stored in your browser when you visit a website, which let that website remember information about your visit.

This policy describes which cookies madebyprojects.com uses, or may use, what each one is for, and how you can give, refuse or withdraw your consent at any time.

2. Necessary cookies (always active)

These cookies are essential for the platform to work and do not require your consent, although they are detailed here for transparency. They do not depend on the choices you make in the banner or the preferences panel.

better-auth.session_token — keeps you signed in while you browse the platform. First-party. Lasts while your session is active.

madeby_cart_session — remembers the contents of your shopping cart, even before you sign in. First-party, httpOnly. It is a browsing-session cookie (deleted when you close your browser).

madeby_client_download_step_up — securely verifies your identity when downloading private documentation from the client portal. First-party, httpOnly. Lasts 20 minutes.

madeby_cookie_consent — remembers the cookie preferences you chose in the banner, so we don't ask you again on every visit. First-party. Lasts up to 180 days, or until you change your choice.

3. Analytics cookies (require your consent)

Madeby has built the integration with Google Tag Manager, intended to be able to manage Google Analytics (GA4) in the future and understand, in aggregate, how the site is used. The Google Tag Manager container only actually loads if, in addition to accepting this category (or advertising, see section 4), the specific environment you are visiting has it configured; on Madeby's public website (madebyprojects.com) it is not configured, so it never loads there. Even if it were to load in some test environment, it does not today contain any real Google Analytics measurement tag or any other provider's tag, so accepting this category never causes any analytics data to be sent or collected while that remains the case.

This integration uses Google's Consent Mode in its basic variant: the Google Tag Manager container does not load in your browser at all while there is no decision yet, nor if you reject both this category and advertising. It does not load in the background waiting for permission; it simply does not run until then. If you accept only the advertising category (section 4) without accepting this one, the container may still load for that other category, but the analytics signal stays denied either way: Google Analytics does not measure your visit and no analytics cookie is set unless you specifically accept this category.

If it is activated in the future, the associated cookies would be _ga, _ga_* and _gid, owned by Google Ireland Limited, and would only load if you accept this category in the banner or the preferences panel. You can review how Google manages them in its privacy policy: policies.google.com/privacy.

This policy will be updated before this tool is activated with any real provider configuration.

4. Advertising cookies (require your consent)

Madeby has built the integration with the Meta Ads pixel (Facebook/Instagram) to measure advertising campaigns. As of today this tool is NOT active in any environment: no real account has been configured, so no data is sent or collected even if you accept this category.

If it is activated in the future, the associated cookies would be _fbp and _fbc, owned by Meta Platforms Ireland Limited, and would only load if you accept this category in the banner or the preferences panel. You can review how Meta manages them in its privacy policy: facebook.com/privacy/policy.

If Google advertising tags (for example Google Ads) are added in the future inside the same Google Tag Manager mentioned in the previous section, they would follow the exact same rule: blocked until you accept this category, independently from analytics.

This policy will be updated before this tool is activated with any real provider configuration.

5. Third-party cookies during payment

When you complete a purchase, Madeby redirects you to Stripe's secure payment gateway, hosted on Stripe's own domain, not on madebyprojects.com.

During that process, Stripe may set its own cookies under its own privacy policy, unrelated to Madeby: stripe.com/privacy.

Madeby does not load any Stripe library or Stripe cookie within its own pages; Stripe's cookies, if any, only exist on Stripe's domain during checkout, and do not depend on this page's cookie banner.

6. Your choice: the banner and the preferences panel

The first time you visit madebyprojects.com, we show you a banner with three equally accessible options, all in the same visual style: accept all cookies, reject non-essential ones, or customise which categories you allow.

Analytics and advertising cookies would only be activated if you explicitly accept them. They are not pre-checked and are never activated before your decision.

You can change your mind at any time, including withdrawing consent you already gave, using the button below.

7. How to manage or delete cookies from your browser

Besides our preferences panel, you can block or delete any cookie from this site from your browser's settings.

Note that blocking necessary cookies may prevent you from signing in, keeping your cart between pages, or completing a protected download from the client portal.

8. Updates to this policy

This policy may be updated to reflect technical, legal or provider changes.

When there are relevant changes, in particular the actual activation of an analytics or advertising tool, a new update date will be published at the top of this document and, where applicable, we will ask for your consent again.

9. Contact

For any question about this cookie policy, you can write to us at alvaro@madebyprojects.com.