meldoc.io › Cookie Policy
Cookie Policy
Last updated: October 17, 2026
This policy covers meldoc.io, the Meldoc app at app.meldoc.io and public documentation at public.meldoc.io. It lists every cookie we set, what else we keep in your browser, and what Google Analytics receives.
Your choice
We ask before we use analytics cookies. The answer you give on one of our sites applies to all three, because they share one cookie on .meldoc.io. You can change it at any time:
- On meldoc.io, select Cookie settings at the bottom of any page.
- In the app, open your profile and use Analytics cookies under Privacy.
- On public documentation, select Cookie settings at the bottom of the page.
Turning analytics off deletes the analytics cookies straight away.
Cookies we set
Necessary
These make the sites work, so they are set without asking.
- cookie_consent — on meldoc.io, app.meldoc.io and public.meldoc.io. Remembers your cookie choice: whether analytics is allowed, and when you chose. It holds no identifier. Kept for a year; meldoc.io renews it each time you visit.
- mld.session — on api.meldoc.io, once you sign in to the app. Keeps you signed in; the pages' scripts cannot read it. Kept for 90 days from your last activity, and removed when you sign out.
- share_token_… — on public.meldoc.io, once you enter the password of a password-protected document. Lets you keep reading that document without entering the password again. One per document, kept for 24 hours.
Analytics, only with your consent
- _ga and _ga_9XF1RPEYSZ — set by Google Analytics on .meldoc.io once you accept. They hold a random identifier that tells visits apart. Google keeps them for up to two years; we delete them as soon as you decline or turn analytics off.
Meldoc uses no advertising or marketing cookies.
What Google Analytics receives
We use Google Analytics 4 to see which pages are read and which steps of getting started people complete.
- In the app and on public documentation, we send the shape of an address, not the address. A document page is reported as
/w/:workspaceSlug/documentation/:projectIdin the app and/:workspace/:project/:docon public documentation, so workspace, project and document names and document titles never reach Google. On meldoc.io, the page address is sent as it is. - The steps we record: in the app — sign-in completed, plan selected, workspace created, project created, GitHub App installed, repository connected and AI assistant connected. On meldoc.io and public documentation — clicks on the main buttons. We send no names, email addresses or document contents.
- Until you accept, nothing is sent to Google: the Google Analytics script is not even loaded, and if you decline or turn analytics off later, it stops.
- Like any request to a website, a request to Google carries your IP address and details of your browser. Google Analytics derives an approximate location (city) from the IP address and does not store the address itself.
- Google Analytics keeps event data for 2 months and data linked to the analytics identifier for 14 months.
Google Analytics is provided by Google Ireland Limited and Google LLC. See Google's Privacy Policy and how Google uses information from sites that use its services.
Other storage in your browser
Besides cookies, the app and public documentation keep a few things in your browser's local and session storage. They are used only by our own pages; nothing in them is sent to analytics or to anyone else.
- The app keeps your signed-in session (an access token and your profile) and your interface settings: colour mode, the layout of sidebars and panels, the last workspace you opened, onboarding cards you closed and an unfinished new project. Temporary state, such as a filter in the document tree, lives in session storage and ends with the tab. The app also caches its own files so it loads faster.
- Public documentation remembers the width of the sidebar and table of contents and which sections of the navigation are open. It also keeps two entries in local storage:
- color-mode — your colour theme. It is stored only if you pick a theme different from your system's; otherwise nothing is stored and the site follows your system.
- meldoc.recent — the documents you opened recently in this browser. For each one it keeps the workspace and project address, the project name, the document address and title, and when you opened it: the 20 most recent, newest first. It is used only for "Continue reading" on the home page of public.meldoc.io, is never written for a password-protected document, and is never sent to our servers or to analytics. Select clear history on public.meldoc.io to delete it, or clear the site's data in your browser.
- meldoc.io keeps nothing in your browser's local or session storage.
Signing out removes the session from the app. Clearing site data in your browser removes everything.
Other services
- Videos in public documentation show a preview image served through public.meldoc.io. The player itself loads only when you press play; from then on YouTube or Vimeo may set their own cookies under their own policies.
- Figma designs embedded in a document in interactive mode load from Figma when you open the document; Figma may set its own cookies under its own policy.
- Payments and sign-in with GitHub or Bitbucket happen on Stripe's, GitHub's or Bitbucket's own pages, under their cookie policies. We set no cookies for them.
Managing cookies in your browser
You can also delete or block cookies in your browser's settings. Blocking mld.session signs you out of the app; without cookie_consent, we ask for your choice again on your next visit.
Changes
We update this page whenever what we store changes. The date at the top says when it last did.
Contact us
Questions about cookies or your data: [email protected]. For anything else, see our contact page.