Cookies

mado uses no analytics, advertising or tracking cookies anywhere. What it does store is listed below, surface by surface. Everything here is either needed for something you asked for (signing in, opening a protected demo) or a preference you set yourself, so there is no consent banner.

Embedded demos, share-page player and help hubs: nothing

The demo player, the embed script and the in-app help script set no cookies and write nothing to localStorage, sessionStorage or IndexedDB. A viewer session is a random id held in memory for one page load. This is why a company can embed a mado demo or help hub without adding it to its own cookie notice. How viewers are counted without cookies is explained in our Privacy Policy.

Our website (mado.show)

• mado-themeLocal storageRemembers light or dark theme, only if you use the theme switch.Lasts: Until you clear it
• mado_unlockCookieSet only after you enter the right password for a password-protected demo, so you are not asked again. Sent only to that demo’s page.Lasts: 1 hour

Studio (studio.mado.show)

In production the sign-in cookie names start with __Secure-, which tells the browser to send them only over HTTPS.

• better-auth.session_tokenCookieKeeps you signed in.Lasts: 30 days
• better-auth.session_dataCookieA short-lived copy of your session so pages load faster.Lasts: 5 minutes
• Sign-in stateCookieProtects a Google sign-in while it is in progress.Lasts: Minutes, until sign-in finishes
• mado_themeCookieRemembers your Appearance setting, only if you change it.Lasts: 1 year
• Editor hintsLocal storageRemembers which tips and banners you have dismissed in the editor.Lasts: Until you clear it

The Chrome extension

The optional capture extension is not a website, but it keeps data in your browser, so we list it. It sets no cookies, in its own pages or in the pages it captures, and loads no analytics or advertising code. It keeps, in the extension’s own storage:

• Settings and flagsExtension storage (local)Your choices (mode, camera, microphone, blur, bubble corner, click mode), whether you granted microphone and camera access, and which tips you have dismissed.Lasts: Until you remove the extension
• Capture in progressExtension storage (session) and IndexedDBScreenshots, clicked elements, typed text with passwords, card numbers and codes masked, scan outlines and the state of a Helper run, until you finish or cancel. Studio uploads it with your own session and the extension then deletes its copy.Lasts: Until you finish or cancel; session state also ends when the browser closes
• Learn while I workExtension storage (local) and IndexedDBOnly for a site you switched it on for: text outlines and addresses of the screens you visit there, kept until you send or delete them.Lasts: Until you send, delete or turn it off and choose to delete

Removing the extension deletes all of this.

Checkout

When you buy a paid plan, you pay on a Stripe or Link page. Stripe and Link set their own cookies there, under their own cookie policies. We do not load any Stripe script on our own pages.

Removing them

You can clear or block all of the above in your browser settings. Blocking the Studio sign-in cookie means you cannot stay signed in.