Privacy. What magpie collects, what it does with it, who else handles it, and what you can do about it. Last updated 12 October 2026.

magpie is run by Deus Labs Stockholm AB, a company in Sweden (“we” on this page). We decide how the data described here is used, which makes us its controller under the EU’s data protection law (GDPR).

Org. no. 559537-2219 · Luthens Gränd 6, 118 66 Stockholm, Sweden

Write to hello@getmagpie.me about anything on this page. There’s no separate data protection officer: the same people answer.

• magpie is a private library for things you save. No ads, no public profiles, no feed, and we don’t sell data to anyone.
• We keep your account details, your saves with copies of their pictures and videos, and what AI writes about them.
• AI services describe your saves and help you search. Each one, and what it gets, is listed below.
• If you sign in with Google, Google shares your name, email address and profile picture with magpie. magpie uses only your email address and Google account ID, and only to sign you in. It’s never used for ads, never sold, and never given to AI services.
• You can delete saves, unlink Google, sign out browsers and revoke device keys yourself, in Settings. For anything else, write to us.

• Your email address, and when your account was made and changed.
• Sessions. Each time you sign in, a session: a random token, when it started and ends, how you signed in, and your browser’s IP address and user agent (which browser and system). Settings lists your signed-in browsers so you can sign any of them out.
• Passkeys. The passkey’s public key and details about it (its name, kind, and whether it’s backed up). The private part stays on your device, and your fingerprint or face never reaches magpie.
• Device and AI-tool keys. When you connect magpie for Mac, the iPhone app, the browser extension or an AI tool (such as Claude Code or Cursor), magpie makes a key for it. We keep a fingerprint of the key (a hash, not the key), its last four characters, the device’s name (magpie for Mac sends your Mac’s name, such as “Anna’s MacBook”; the iPhone app and the extension send just “iPhone” or “Chrome extension”), and when it was made and last used. The key itself stays on the device: in the iPhone’s Keychain, or in the extension’s storage. AI-tool keys can search, read and add to your library, and can’t delete anything.
• Signing in with Google, covered in full in the next part.

magpie isn’t open for sign-up yet: you can only sign in to an account that already exists. To slow down people guessing, your connection’s IP address is held in the server’s memory to count sign-in tries, and forgotten when the server restarts, about once a day. It’s never written down.

What Google shares

When you choose Sign in with Google, Google asks you to share your basic profile with magpie: your name, email address (and whether Google has verified it), profile picture, and your Google account’s ID.

magpie asks for nothing more: only the openid, email and profile permissions. It gets no access to Gmail, Drive, Contacts, Calendar or anything else in your Google account, no offline access, and it never calls Google’s services on your behalf.

How magpie uses it

Only to sign you in. magpie checks that the email address Google sends is verified and belongs to a magpie account. If it does, your Google account is linked to that magpie account, and its ID is kept so magpie knows you next time. If no account has that email address, sign-in stops and nothing about you is kept. If you link Google from Settings while signed in, it’s linked to your account whatever its email address.

Your name and picture aren’t copied into your magpie profile or shown anywhere in magpie.

What’s stored, and where

With the link to your account, magpie’s sign-in system (Better Auth) stores what Google sent at your last sign-in: the sign-in token, which contains your name, email address and a link to your profile picture; a short-lived access token that stops working within about an hour; and the permissions you granted. They’re replaced each time you sign in with Google and aren’t used for anything else. Your session records that you signed in with Google. All of it is in our database, hosted by Supabase in Ireland, which only magpie’s servers can reach.

Who sees it

Nobody else. Data from Google is never sold, never used for advertising, never sent to AI services or used to train AI models, and never shared, except with the two providers that host magpie for us (Supabase for the database, Heroku for the servers). People at Deus Labs don’t read it unless you ask us to, it’s needed for security, or the law requires it.

Removing it

Unlink Google in Settings › Account, and the link and Google’s tokens are deleted at once (you’ll need another way to sign in first, such as a passkey). They’re also deleted with your account. You can take back magpie’s access from Google’s side at any time, at myaccount.google.com/permissions. That stops Google sharing anything new, but doesn’t delete what magpie already stored: unlinking does.

magpie’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• The link and where it came from (the site and the post’s id), the author’s name or handle, its title, the post’s words or a web page’s readable text, when it was posted and saved, and the collection, board or list it was in.
• Your handle on that site, where the browser extension sees it.
• Your own notes, and anything you change.
• What AI writes about it: a title, a summary, tags, a category, the people, brands and places it names, its colours, notes on its video, a cover, and a search fingerprint (made by a model magpie runs itself, so nothing is sent anywhere for it).
• Copies of its pictures and videos, and a screenshot of a web page, so the library still works if the original disappears. They’re kept in private storage and reached only through links that expire: within a week in magpie, and after an hour for AI tools.
• Your uploads (photos up to 20 MB, videos up to 50 MB, PDFs up to 30 MB) are stored exactly as you send them, including any details inside the file, such as where a photo was taken. Remove those before uploading if you don’t want them kept.
• Imports. From Raindrop, Pocket, Readwise Reader or mymind files: links, titles, notes, tags and dates. An Instagram data export is read on the server for dates and collections only, and the file isn’t kept.
• Ask and projects. The questions you ask and their answers; your projects’ names, briefs and notes; and the text of a page you link a project to.

Your library is private: there are no public profiles, no feed and no sharing links. Saves from social sites contain other people’s names, handles, faces and words; magpie keeps them only as part of your private library. If something of yours is in someone’s library and you want it removed, write to hello@getmagpie.me.

• Browser extension. When you sync a site, it reads the saved, liked or bookmarked lists of your own account on sites you’re signed in to in that browser (Instagram, X, TikTok, Reddit, Pinterest, Cosmos, YouTube, Dribbble and Behance), and sends those posts and your handle on the site to magpie. Your passwords and those sites’ cookies stay in your browser and aren’t sent to magpie. It syncs on a schedule only if you turn that on. Once you’ve synced a site by hand, it also catches a post the moment you save it there; you can turn that off per site. Its right-click menu and Save button send the page, link or picture you choose, with its title. It reads Chrome’s bookmarks only from folders you tick. Its settings stay in the browser.
• magpie for Mac can read the bookmarks of Safari, Chrome, Arc, Brave, Firefox and other browsers on your Mac, and sends only the folders you tick.
• The iPhone app and share sheets send what you share or pick. The app reads the clipboard only when you tap Paste, to find a link, and reads nothing else on your phone.
• Site icons. Saved links show the site’s icon, which your browser or the iPhone app loads from Google’s icon service. Google sees your IP address, the saved site’s domain and that the request came from magpie, and may link that to your Google account if you’re signed in to Google in that browser.
• Fetching. To make a save, magpie’s own machines visit the link (and the site’s public embed services) to get its words, pictures and video. The site sees a visit from magpie, not from you.

• To run magpie for you: sign you in, keep your saves, sync them, and show them on your devices and to AI tools you connect.
• To describe your saves with AI, make them searchable, file them into projects and answer your questions.
• To keep magpie and your account secure: sessions, sign-in limits, and finding and fixing faults.
• To answer you when you write to us.

No ads, no selling or renting data, and no profiling for anyone else. We don’t train AI models on your data. Requests through OpenRouter are sent with its settings for providers that keep no copy and don’t train on it. Anthropic and TypeSafe handle what they get under their own terms. AI output is labelled as written by AI, and none of it makes decisions with legal or similar effects on you.

magpie’s code can count how it’s used (such as what its AI costs, or how many words a search had, never the words or your saves) with PostHog in the EU. It is switched off today; this page will say so before it’s turned on.

AI tools you connect (such as Claude Code or Cursor) get what you ask them to read from your library. What they do with it is between you and that tool’s provider.

• SupabaseHosts the database: your account, sign-in records, saves and everything magpie writes about them.EU (Ireland)
• Heroku (Salesforce)Runs magpie’s website and the server the apps and AI tools talk to. Everything you send passes through it.EU
• Cloudflare R2Stores the copies of pictures and videos, page screenshots, covers and your uploads.Western Europe (not an EU-only guarantee)
• Anthropic (Claude)Describes and tags saves from their pictures, words and video notes; answers your Ask questions; writes project briefs; picks covers; suggests categories.United States
• OpenRouterPasses requests on to the three models below. Every request asks to be sent only to hosts that keep nothing and don’t train on it.United States
• Google Gemini, run by Google Cloud through OpenRouterWatches short videos (a minute or less) to describe them, and takes a second look at search results and filing decisions the quick check isn’t sure of.United States
• Whisper (OpenAI’s speech model), run by Groq or DeepInfra through OpenRouterWrites down what’s said in the first five minutes of a longer video.United States
• Claude Haiku, run by Google Cloud or Amazon Bedrock through OpenRouterWrites notes on a longer video from six of its frames and that transcript.United States
• TypeSafe (Jev)Quick judgements: what a search means, which results fit it, and which project or category a save belongs in. Gets your search words and the text of saves, never pictures.United States (San Francisco)
• Cloudflare Email RoutingForwards email sent to hello@getmagpie.me.United States company; its network handles the mail

Your search words leave magpie: they go to TypeSafe, and for some results to Google’s Gemini. Questions you ask in Ask go to Anthropic. We pass each provider only what its job needs.

The database is in Ireland (Supabase), and magpie’s servers run in the EU (Heroku). Pictures and videos are stored by Cloudflare R2 in Western Europe; its settings don’t guarantee they stay inside the EU.

Some of the work (fetching links, reading videos and asking AI to describe saves) runs on a computer Deus Labs operates in Sweden. Most working copies it makes are deleted when the job is done; the rest are cleared out by hand.

• Your account and email addressAs long as you have the account. Deleting it is done by email for now, within a month of asking.
• Sessions (with IP address and browser)Until you sign out of that browser, and never more than 90 days.
• Your linked Google account, with Google’s tokensUntil you unlink it in Settings › Account, or your account is deleted. The tokens are replaced each time you sign in with Google.
• PasskeysUntil you delete them in Settings.
• Device and AI-tool keysUntil you revoke them. A revoked key’s name and dates stay with your account.
• Saves, their copies and what AI wroteUntil you delete them.
• Deleted savesA copy for 30 days, so they can be brought back, then erased with their pictures and videos. Where each one came from (the site and its post id) is kept, so a sync doesn’t add it again.
• Unsaved Ask questionsOne day.
• Database backupsmagpie doesn’t make its own backups yet. When it does, each is kept for 30 days.
• Working copies made while processingMost are deleted when the job is done, and a clean-up removes picture copies left over after two days. Some older working folders are still being cleared out by hand.
• Server logsKept by our hosting providers for a short time. magpie doesn’t copy them anywhere.
• WaitlistUntil the email saying magpie is open has gone out, or until you ask us to remove you.
• Connection addresses for counting triesIn memory until the server restarts (about once a day), never written down.

You have the right to:

• get a copy of the personal data we hold about you (access)
• have it corrected (rectification)
• have it deleted (erasure)
• get it in a format you can take elsewhere (portability)
• have us limit what we do with it while something is sorted out (restriction)
• object to what we do on the basis of our legitimate interests (objection)
• withdraw consent at any time, where we rely on it

Much of it you can do yourself: edit or delete saves, download a save’s details, unlink Google, delete passkeys, sign out browsers and revoke keys in Settings. For a copy of everything, deleting your account, or anything else, write to hello@getmagpie.me. We answer within a month, and may ask you to confirm it’s you.

If you think we’ve got it wrong, you can complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY) at imy.se, or to the authority where you live. We’d like to hear from you first.

• Contract: your account, signing in (Google included), keeping, syncing and describing your saves, and the AI processing that makes magpie work.
• Legitimate interests: security (sessions, sign-in limits, logs), keeping other people’s posts as part of your private library, and answering people who write to us.
• Consent: the waitlist email, and the access you turn on yourself, such as scheduled syncs and bookmark folders. You can withdraw it at any time.
• Legal obligation: where the law requires us to keep or hand over something.

You need an email address and a way to sign in to have an account; without them magpie can’t work. Everything else you choose to give.

The landing page and this one set no cookies. Signed in, magpie uses these, all needed for it to work:

• magpie_sessionKeeps you signed in.Until you sign out, at most 90 days
• magpie.session_dataA short-lived copy of your sign-in, so pages don’t ask the database each time.1 minute
• magpie.stateSet while you sign in with Google or link it, to check that Google’s answer belongs to the sign-in you started.5 minutes
• Passkey checkSet by Better Auth while a passkey is being checked or added.A few minutes
• magpie.prefs, magpie-sidebar, magpie-indexRemember how you left the library (size, layout, sidebar width and folds), so it opens that way.1 year
• magpie.setup, magpie.setup-atRemember that setup is done, and where you were in it.1 year; 1 day

No advertising, analytics or tracking cookies. Some view settings are also kept in your browser’s local storage, which stays on your device.

The waitlist stores your email address and when you left it. Nothing else: no name, and nothing about you from anywhere else.

It’s used for one email, the day magpie opens. It isn’t shared or sold. To be taken off, write to hello@getmagpie.me.

The landing page has no analytics, ads or trackers. Its fonts and pictures come from this site. To slow down scripts, your IP address is held in the server’s memory to count tries and forgotten within a day, never stored with your email.

• Everything travels encrypted (HTTPS).
• The database can only be reached by magpie’s servers, never directly from a browser or app.
• Pictures and videos are private, reached through links that expire.
• Keys are stored only as fingerprints, and passkeys only as public keys. The sign-in cookie can’t be read by scripts on the page.
• Sign-in tries are limited, and AI-tool keys can’t delete anything.

No system is perfectly safe. If a breach puts your data at risk, we’ll tell you and IMY as the law requires.

magpie isn’t directed to children under 13. In EU countries that set a higher age for agreeing to online services on your own (up to 16), you need to be that age. If you think a child has given us their data, write to us and we’ll delete it.

Anthropic, OpenRouter and the providers it reaches, TypeSafe and Google’s icon service are in the United States, and Supabase, Heroku and Cloudflare are US companies. Where data goes outside the EEA, we rely on the EU–US Data Privacy Framework where the provider is certified under it, or on the European Commission’s standard contractual clauses in the provider’s data processing terms.

One exception today: magpie’s Claude requests run on an Anthropic account that doesn’t yet have a data processing agreement. Before magpie opens to anyone beyond the people testing it, they move to Anthropic’s commercial terms, which include one. Write to us for details.

We’ll update this page when what magpie does with data changes, and change the date at the top. If a change matters, we’ll tell you before it takes effect.

Anything about your data, or to have it deleted: hello@getmagpie.me.

Deus Labs Stockholm AB, Sweden · Org. no. 559537-2219 · Luthens Gränd 6, 118 66 Stockholm, Sweden