Back to the board

Privacy

What mbrd does with your things, which is nothing at all - and this is the long way of saying so.

no account no server of ours no tracking last changed 7 October 2026

  1. There is no account and no server that holds your work. On the web, mbrd runs in your browser and keeps your boards in your browser's storage on your own computer; saving a board writes a .mbrd file wherever you choose to put it. In the desktop and Android apps every board is a file in a folder of your own, Documents/mbrd unless you chose another, and the app keeps a few earlier copies of each beside them, in a hidden .autosave folder, in case a save goes wrong. On the web the browser keeps a few earlier copies of a board you are working on, in the same storage as the board. We collect nothing at all - no analytics, no tracking pixels, no cookies, no fingerprinting, no error reporting. Report a problem only copies some details to your clipboard and opens the issues page; what you paste there is up to you.

    The other half of that promise is that we have no backup of anything. On the web, clearing your browser's data for this site deletes your boards, and Safari deletes a site's storage by itself when you have not visited it for seven days, so save anything you would be sorry to lose to a file.

  2. This is every place mbrd reaches, and what each one sees.

    Our host. The website is served by Cloudflare as static files, and it sees the traffic that reaches it the way every web server does; we have added no logging of our own on top. An open tab also asks it for a newer version of the app every quarter of an hour and when you come back to the tab. The desktop and Android apps instead ask GitHub, about once a day, whether a newer release is out, and download it from GitHub when you press Update. Turning off Check for updates automatically stops the daily question; the app then asks only when you press Check for updates. Those requests carry nothing about your boards.

    YouTube and Spotify. A card for a YouTube video or a Spotify track asks nothing of anyone until you press play. Pressing play loads their player, the YouTube one from its no-cookie host, and they then see the request the way they would if you opened it in a tab. At that moment the card also asks the service for its title, and Spotify for its cover, if it has none yet, and keeps them so it never asks again.

    jsDelivr. Making a preview for a video your browser cannot read downloads a converter from this public code mirror, once you ask for it. The converter comes to the video, never the other way round.

    Google Drive, only once you connect it. Share link uploads the board to your own Drive, as a file in your account, and gives you a link to it. Save to cloud keeps a board there and uploads it again after each change, so it can open on another computer. Signing in happens on Google's own page. None of it passes through anything of ours - we run no server and have nowhere to put it - so what leaves your computer goes from you to Google and nowhere else, under whatever terms you already have with them. A share link works for anyone who has it and needs no account, so it is as private as the people you send it to. The files stay in your Drive until you delete them there, and the permission mbrd asks for reaches only the files mbrd itself made.

    If you never play a YouTube or Spotify card and never connect Drive, nothing about your boards leaves your machine.

  3. There is no account to create and nothing is gathered, so a child's data is treated no differently from anybody else's - neither is collected. If any of this ever stops being true, this page changes first and the date at the top changes with it. mbrd is free software, and its source is public, so you do not have to take our word for any of it. Questions go to the project's issues page.