← Back to Magpie

Privacy

Last updated: 21 November 2026

The short version

  • You can use Magpie without an account. Those canvases stay in your browser on your device.
  • An account is optional. It needs your email address, and it lets you keep canvases in the cloud (in Paris) and receive documents from tools you connect over MCP.
  • Cloud canvases are stored as plain text unless you encrypt them with a passphrase. Encryption happens in your browser; we can't read or recover encrypted canvases.
  • Our analytics count events like “someone opened the app”. They never include your content, use no cookies, store nothing on your device and keep no IP addresses. The full list is below.
  • Magpie is free. We don't take payments, so we hold no payment details.
  • There is no in-app account deletion yet. Email hello@magpie.md and we'll delete your account.

Who we are

Magpie is a personal project run by Jonas Volny (Czech Republic). He decides how your data is used, which makes him the data controller under the EU's General Data Protection Regulation (GDPR). For anything about privacy, write to hello@magpie.md.

Local canvases stay on your device

Local canvases (the default, and the only kind without an account) are saved in your browser's storage (IndexedDB) on the device you're using, with their blocks, drawings, images and videos. Nothing from them is uploaded unless you put it into a cloud canvas yourself. We don't have a copy, so if you clear your browser data or lose the device, they're gone unless you exported them.

Magpie also saves preferences in your browser's local storage, such as light or dark theme, zoom speed, sidebar and navigator settings, and where you last scrolled on each canvas. These never leave your device.

Accounts

Accounts are optional. To sign in you enter your email address, and we email you a one-time code. There is no password. Sign-in is handled by Supabase Auth, in a database in Paris. The emails are sent through Brevo, a French email service.

For each account we store:

  • your email address;
  • when the account was created and when you last signed in;
  • your sign-in sessions, which Supabase Auth records with the IP address and browser they started from, and a short-lived security log of sign-in activity;
  • the last day you were active (just the date, updated at most once a day);
  • your cloud folders and canvases, and your MCP connection tokens (both described below).

While you're signed in, your browser keeps a sign-in cookie for magpie.md. It is needed to keep you signed in and is used for nothing else.

Cloud canvases: plain text unless you encrypt them

When you're signed in you can keep canvases in the cloud, so you can open them on other devices. They are stored in our Supabase database in Paris.

By default a cloud canvas is stored as plain text. That means it's technically readable by anyone with administrative access to the database: Magpie's founder and, in principle, Supabase. We don't look at your canvases unless you ask us to help with a problem or the law requires it.

You can encrypt a canvas with a passphrase. Your browser turns the passphrase into a key (PBKDF2 with SHA-256) and encrypts the canvas with AES-256-GCM before anything is uploaded, including images and videos stored inside it. The passphrase is kept only in the open tab's memory and is never sent to us. We store only the encrypted data, so we can't read the canvas, and if you forget the passphrase we can't recover it.

Encryption covers the canvas content, not its label. We can still see each cloud canvas's name, the name of its folder, and when it was created and last changed. Don't put secrets in canvas or folder names.

Coming soon, not live yet: new cloud canvases you create yourself will be encrypted by default. Canvases that connected tools write to, like the Inbox, will stay plain text and be clearly labelled. Until this ships, everything above applies: cloud canvases are plain text unless you encrypt them.

Offline copy on signed-in devices

So you can read your cloud canvases without a connection, a signed-in browser keeps a copy of them in its storage (IndexedDB), together with the list of your folders and canvases and your account email. Encrypted canvases stay encrypted in this copy and still need your passphrase.

When you sign out (“Disconnect” in the account menu), the copy is deleted from that browser. If you just close the tab, the copy stays so you can keep reading offline.

Pushing documents from connected tools

If you connect a tool to Magpie through MCP (the Model Context Protocol), for example a coding assistant, it can save documents to your cloud. By default they go to an Inbox canvas in a folder called Inbox; the tool can also add to another plain-text canvas, or create a new one, if you ask it to. To do this, it can also see the names of your cloud folders and canvases.

  • Pushed documents arrive and are stored as plain text, because our server writes them for you. You can encrypt that canvas later, but after that connected tools can no longer add to it. They can't write to encrypted canvases.
  • To connect a tool you create a token in Settings. We show it to you once and then store only a SHA-256 hash of it, plus the name you gave it, its first 10 characters (so you can tell tokens apart), and when it was created and last used. You can revoke a token at any time.
  • What you write to the tool, and what it writes before pushing it here, is handled by the company that provides that tool, under its own privacy policy. Magpie only receives what the tool sends to Magpie.

Analytics: what we measure

We want to know whether people find Magpie and keep using it, without knowing who they are. Inside the app, our analytics are built into Magpie itself: no third-party scripts, no ads and no trackers. The website pages use the same system. This section lists everything we collect.

1. Anonymous counts (everyone)

When something on the list below happens, your browser tells our server the event name and a few fixed details. Nothing is saved on your device for this: no cookies, no local storage, no device ID.

Like any website, our server sees your IP address and browser type (user agent) when your browser connects. For analytics it uses them only to work out your country and a daily visitor code: a SHA-256 hash of your IP address and user agent mixed with a random value (a “salt”) that we replace every day and then delete. The IP address and user agent themselves are not stored. Each day gets a new code, so we can't link your visits on different days, and once a day's salt is deleted nobody, including us, can work out an IP address from that day's codes. The code only lets us count unique visitors within one day.

For each event we store: the event name, its details from the table below, when it happened, the country and the daily visitor code.

EventWhenDetails sent
lp_viewA website page loads: home, about, privacy or MCP setupPage path; the website you came from (its domain only); campaign tags in the link (utm_source, utm_medium, utm_campaign)
lp_cta_clickYou click one of the main buttons on the website, such as the one that opens the appWhere the button is (for example top or bottom of the page)
app_openThe app loadsWhether it runs as an installed app, whether you're signed in, phone or computer
block_createdYou add a blockHow: paste, type, import or drop
board_createdYou create a canvasLocal or cloud
feature_usedYou use a feature (at most once per feature each time you open the app)Which feature: drawing, mermaid, code, image, embed, fullscreen, folder, search, export or import
cloud_connectedYou sign in with an email codeNone
encryption_enabledYou encrypt a canvasNone
mcp_token_createdYou create an MCP connection tokenNone
mcp_pushA connected tool pushes a document (recorded by our server)Whether it created a new canvas
pwa_installYou install Magpie as an appNone
feedback_sentYou send feedback from the app (once the form exists)None (the feedback itself is covered separately)

Events never contain your content, canvas or block names, IDs, your email address or account ID.

We rely on our legitimate interest in understanding, in aggregate, how Magpie is used. Because events carry no name, account or lasting identifier, we can't find your events among the others or delete them individually. How to opt out is explained under your right to object.

2. Opt-in usage stats (not available yet)

We plan to add a setting that is off unless you turn it on. If you turn it on, your device remembers the week you started using Magpie and which days you used it, and once a day sends us: that install week, how many of the last 7 days you used Magpie, and the app version. This tells us whether people come back. Turning it off stops it and clears what was saved on your device. We'll update this page when it ships.

3. Account statistics (signed-in users)

For accounts, we count from our own database how many accounts sign up and stay active (using the “last active day” above), how many cloud canvases exist and how many documents connected tools push. We look at these as totals, not to watch individual people.

Features that contact other websites

  • Embeds. When you add a web page as an embed, our server fetches that address once to check that it can be embedded. The page then loads directly from that website in your browser, and that website sees your visit as usual.
  • Images linked in markdown. An image written as a web link in your text loads from the website that hosts it.
  • Dictation. The microphone button uses your browser's built-in speech recognition. Some browsers send the audio to their maker for recognition (Chrome, for example, sends it to Google). Magpie doesn't receive the audio, only the text your browser returns.

Companies that process data for us

CompanyWhat it does for MagpieWhere your data isCompany based in
Supabase (Supabase Pte. Ltd.)Database and sign-in: accounts, cloud canvases, MCP tokens, analytics eventsParis, France (on Amazon Web Services). Supabase's support staff and some of its own providers are outside the EU.Singapore
Brevo (Brevo SAS)Sends the sign-in code emailsEuropean Union (France and Belgium)France
Vercel (Vercel Inc.)Hosts the website and runs our server code, including analytics and the MCP endpointAll our server code, including the part that keeps you signed in, runs in Vercel's Paris region. Static files (page code, styles and images, with no personal data) are cached and served from the Vercel location closest to you.United States

Each of them processes data only to provide its service to us. For data that may leave the EU: Vercel is certified under the EU-U.S. Data Privacy Framework, and the data processing terms of Vercel and Supabase include the EU's Standard Contractual Clauses.

We don't sell your data and we don't share it with advertisers.

How long we keep it

DataKept for
Local canvasesOn your device until you delete them or clear your browser data. We have no copy.
Account (email, sign-in records, last active day)Until you ask us to delete your account
Cloud canvasesUntil you delete them, or your account
Offline copy of cloud canvasesUntil you sign out in that browser, or clear its data
MCP connection tokens (hash, name, first 10 characters, dates)Until your account is deleted. Revoked tokens stay marked as revoked and stop working immediately.
The daily analytics saltReplaced every day; the old one is deleted
Individual analytics events30 days, then deleted
Daily totals (for example, “120 app opens on 3 March”)Kept. They contain no visitor codes and can't be linked to anyone.

Our providers also keep short-lived technical logs (which can include IP addresses) for security and debugging, and database backups, for limited periods they set. Deleted data can remain in those backups until they expire.

Your rights, and how to delete your account

You can ask us for a copy of your data, to correct it, to delete it, to restrict how we use it, to move it elsewhere, or object to how we use it. Write to hello@magpie.md from the email address of your account. We'll answer within one month.

Deleting your account. There isn't a button for this yet. Email hello@magpie.md from your account address and we'll delete your account, your cloud canvases and your MCP tokens, and confirm when it's done.

Some things you can already do yourself in the app:

  • delete a single cloud canvas or folder from the sidebar;
  • delete all your cloud folders and canvases at once (“Delete all cloud folders and canvases” in the account menu);
  • revoke MCP connection tokens in Settings;
  • sign out, which removes the offline copy from that browser;
  • export any canvas to a file from the sidebar.

These don't delete the account itself or your email address; for that, email us.

Your right to object. You can object to any processing we base on legitimate interest. For analytics: a content blocker that blocks Magpie's analytics requests (to magpie.md/api/a) stops them, and Magpie works the same. For account statistics: email hello@magpie.md and we'll leave your account out of them.

If you're unhappy with how we handle your data, you can also complain to the data protection authority in the EU country where you live or work.

Changes to this page

When we change what we collect or who processes it, we update this page first and change the date at the top.

Back to Magpie