Cookie policy
room.md keeps very little on your device. This page names all of it, and the list is generated from the code that does the storing.
What this covers
Cookies, local storage and session storage are three ways of keeping a small amount of information on the device you are reading this with. The law treats them alike, and so does this page: what matters is not the technique but that something is being kept on your machine, and why.
The categories in use
Two: strictly necessary, which runs so that the site works at all, and preferences, which is off until you switch it on.
There is no analytics category and no marketing category, because room.md runs neither. No advertising network, no tracking pixel, no traffic measurement, no profiling. If that ever changes, this page changes first and you are asked again.
Necessary and optional
Strictly necessary means the thing you asked for does not happen without it — you cannot sign in without a session, and we cannot remember that you refused without storing that refusal. Everything else is optional, which here means genuinely optional: refusing costs you some conveniences and nothing else. The site does not degrade, nothing is withheld, and you are not asked again on every page.
Choosing, and changing your mind
You are asked once, when you first arrive, and nothing optional runs before you answer — scrolling past the question is not an answer. Cookie settings sits at the foot of every page, and withdrawing is the same two clicks as agreeing was. Switching a category off deletes what it stored on this device rather than just stopping there.
Third parties
Two, and both only because signing in has to work. The first is Clerk, Inc., which handles sign-in and sets the session cookies. Those are strictly necessary — without them nobody can log in — and Clerk processes that data on its own infrastructure outside Moldova, under its own terms. The full list of everyone who processes data for room.md, and what they process, is in the privacy policy. The second is Cloudflare, Inc., which sits in front of Clerk and sets two cookies of its own on clerk.room.md to keep automated abuse off the sign-in service; they are named in the table above.
The database, the API and the scheduled tasks are in Amsterdam, and the files are in Cloudflare R2 buckets with EU jurisdiction. Signing in runs at Clerk and the Cloudflare edge in front of it, and the pages themselves are served by Vercel Inc. from its worldwide network. The privacy policy says who processes what, and on what safeguard.
The typefaces are served from room.md itself. They used to load from Google Fonts, which meant your IP address reaching a third party before you had been asked anything; they are local files now, so drawing this page contacts nobody.
Your browser
Your browser can block or delete any of this on its own, independently of what you choose here — usually under Privacy, Cookies, or Site data. Blocking the strictly necessary ones will stop sign-in from working, which is the honest answer rather than a warning meant to discourage you.
Asking us
Questions about this page, or about anything room.md holds about you: hello@room.md. This page is room.md's notice under Law No. 72/2025 on electronic communications and Law No. 195/2024 on personal data protection of the Republic of Moldova.