Privacy.

Mixtaped is owned and operated by Verstack For Marketing and PR L.L.C S.O.C, a limited liability company registered in Dubai, United Arab Emirates (commercial license no. 1516468), Office 101B-06, Mohammed Bin Al Zubair building, Al Garhoud, Dubai, UAE. For your data, Verstack is the controller.

Your email address — for the 6-digit sign-in code. There are no passwords. If you continue with Apple instead, Apple gives us an email address — your own, or a private relay address if you choose to hide yours — and an identifier for your Apple account; we never see your Apple password. On the website, Apple also passes on the name on your Apple account the first time you continue with it; it is kept with your sign-in record, and nothing in Mixtaped shows or uses it. The iPhone app doesn't ask for it. Occasional announcements about Mixtaped are opt-in: you receive none unless you switch them on in settings on the website, and every one carries a link that switches them off again. Sign-in codes cannot be turned off, because they are how you get in. Your handle and profile (display name, bio, avatar). Your library — shelves, entries, notes, tags, dates, and photos you upload. Who you follow, and who follows you. A view count per profile and per shelf. Your settings — theme, motion and email preferences. Your appearance choices: how your library is laid out and, on a paid plan, the accent colour and typeface you pick for your account and any background image you upload for a shelf or for the library itself. Those images are stored files, like the rest of your photos, and the same caveat below applies to them. If you subscribe, your plan status (which plan, its state, when it renews) and the identifiers of whichever shop sold it — a Stripe customer and subscription reference on the web, or the Apple transaction references from the App Store.

We don't run ads, we don't sell or share your data with data brokers, and we don't track you across the web. To see how mixtaped.app is used, the website counts visits with Umami, a privacy-focused analytics service that keeps its data in Frankfurt, Germany: no cookies, nothing kept in your browser, and no IP address stored. For each page view it receives the page's address (never anything after a "?"), the site you came from, your browser, operating system, device type, screen size, language and country, and it tells visits apart with a scrambled code made from your connection and browser that cannot be turned back into either. It counts mixtaped.app only, never the iPhone app, and if your browser sends "Do Not Track" it counts nothing at all. Apart from Umami's, there is no script on any page here that we didn't write ourselves, except three that come with something you open: opening a place on the website opens its live map, and when that map is Mapbox's, Mapbox's map code reports that map load to Mapbox; opening a film plays its trailer from YouTube; and pressing play on a saved link's video or song loads that service's own player (all three below, under third parties). Our own count is the view count named above: opening someone's profile or shelf adds one to a single number on that page's row, and that is the whole record. No visitor id, no cookie and no IP address is stored with it, and a view of your own pages is never counted. So that a refresh doesn't inflate anyone's number, our server remembers for 30 minutes that a view of that page was just counted from your connection or your account. It keeps only a scrambled code for that, in memory and never on disk, and a restart forgets it. Your browser also keeps a list of what this tab has already counted; it is thrown away when the tab closes.

If the app crashes in your browser, a short technical crash report (the error text, the page address, and your browser's user-agent string — never your library) is sent to our own server logs so we can fix it. The iPhone app sends one too when it cannot read an answer from our database, or the database or storage reports a fault: the kind of failure, which part of the database it was asking, and the app's version — with no account attached, and never anything from your library.

Most of what we hold runs the service you signed up for: your account, your library, the sign-in codes, and a plan if you buy one. Some of it keeps Mixtaped safe and working, which is our legitimate interest — the rate limits, the crash reports and server logs, and acting on reports of abuse. Announcement emails go out only with your consent: you switch them on, and switching them off withdraws it.

There are two ways to pay for a plan, and they involve two different companies.

On the web, payment is processed by Stripe. Your card details go to Stripe directly and never touch our servers. We give Stripe your email address and your Mixtaped user id so the payment can find its way back to your account, and we receive a customer reference and the state of your subscription.

In the iPhone app, a plan is an Apple in-app purchase. Apple takes the payment; we never see your card or your Apple ID. Apple's servers send us signed notifications about the transaction — the product, the dates, the status — carrying the Mixtaped user id the app attached at purchase so we credit the right account. If a purchase arrives without one, we park it for a human to match rather than guessing.

Stripe's and Apple's own privacy policies govern what each of them holds.

Every shelf has a visibility: public (on your profile), unlisted (off your profile, readable by anyone who has the address), or private (only you).

Private is not a hidden button. The rule lives one layer deeper than the app: the database itself checks who is asking before it hands over a single row, and to anyone who isn't you a private shelf simply does not come back. So a bug in a page, a link someone shares, or a request made straight to the database without going through Mixtaped at all still gets nothing.

Unlisted is not a secret, and we'd rather say so than let you assume otherwise. There is no random token in the link: the address is your handle plus the shelf's name, so someone could guess it. What unlisted does buy is that the shelf is off your profile and out of every list the database will hand out — it can only be resolved one exact address at a time, and a run of wrong guesses gets rate limited. Treat unlisted as unadvertised, not as protected; anything that must not be seen belongs on a private shelf.

Photos are the second honest caveat. Every photo you upload — including one on a private shelf — is stored in public object storage under a long random filename. Anyone holding that exact URL can open the file without signing in, and the storage layer does not check who they are; what keeps it unseen is that the app never shows a private shelf's photo URLs to anyone else. Deleting your account deletes the files. Until that changes, skip truly sensitive photos.

Your profile has its own visibility — "Search-indexed", "Linked only", "Hidden", or "Private" — and only a search-indexed profile is offered to search engines. The default is "Linked only".

Your data sits in a Supabase Postgres database and Supabase object storage, in Frankfurt, Germany. The app runs on Railway, in the Netherlands, which also holds our server logs, and requests reach it through Cloudflare, so Cloudflare sees the traffic on its way in. Email — sign-in codes and confirmations of account changes, billing notices for a plan bought on the web, the announcements you switched on, and alerts to us when someone files a report — is delivered by Resend, which is given the address each email goes to and what it says. These providers process data on our behalf and nothing more.

Some of the companies named on this page — Cloudflare, Resend, Stripe, Mapbox and Apple — are in the United States or handle data there, so what they handle for us can leave Europe. Those transfers happen under the safeguards those providers offer.

When you search for something to add, the words you typed go to our server, and our server asks the matching index — so the index sees us rather than you. Which index depends on what you're adding: TMDb (films), Deezer (music), Apple's iTunes Search (track previews and album track listings), Open Library (books), Steam and, where it is configured, RAWG (games), OpenStreetMap's Nominatim (places), and Wikipedia (topics, and games Steam never sold). Map thumbnails for places are fetched from Geoapify. This is the same for both apps: the iPhone app searches through our server too.

Pasting a link works the same way. The address goes to our server, and our server opens that page itself to read its title, description, picture and icon — so the site you linked sees a visit from our server, not from you. On any shelf but a Links shelf, a YouTube link is read through YouTube instead, and a Google Maps link through Google Maps and Nominatim.

Your device does talk to some of them directly, because pictures and sound have to come from somewhere: cover art from TMDb, Deezer, Apple, Open Library, Steam and Wikipedia, the 30-second previews from Apple, a saved link's picture and icon from wherever that page keeps them, and your own uploads from Supabase storage. Anyone who looks at your shelves loads them the same way. Those servers see the request a browser or phone makes — its IP address and browser details — exactly as they would for any image on the web. When you open a place on the website, your browser loads its live map from Mapbox in the US, which sees your IP address and browser details, and its map code keeps a random ID in your browser's storage — or, when Mapbox's map isn't available, from OpenFreeMap in Hungary, through Cloudflare, which sees the same request, sets no cookies and keeps no IP addresses in its access logs. In the iPhone app a place's map is drawn by Apple Maps, so Apple sees the request for that part of the map.

Opening a film plays its trailer, muted and without controls, behind the film's title, when the film has one and you haven't asked for less motion. The trailer comes from YouTube's privacy-enhanced youtube-nocookie.com address, so YouTube sees your IP address and browser details as soon as the film is open, not only when you press anything.

A saved link to YouTube, Vimeo, Spotify, SoundCloud or Apple Music can be played in place. The player itself isn't loaded until you press play; then your browser or phone loads the service's own player — YouTube's from its privacy-enhanced youtube-nocookie.com address — and that service sees your IP address and browser details, under its own privacy policy and cookie rules. The link's picture and icon are another matter: like any saved link's, they come from the service's own servers and load whenever the entry is shown, so that service sees the same details then too.

Continuing with Apple happens on Apple's own screen, and Apple tells us only what is listed above, under what we store.

None of those indexes, and no site you link to, receives your email address, your handle, or anything from your library beyond the words or the link you asked about. Stripe and Apple do receive identifiers, as described under payments.

One feature would send text to a language model: drafting a shelf from a sentence you type, which would go to Anthropic (Claude) to come back as a suggested shelf. It is switched off in both apps today, and nothing else in Mixtaped sends your writing to a model. If we turn it on, this page changes with it.

No tracking cookies. Your browser's local storage holds your session token (so you stay signed in — unless you untick "Keep me signed in", which scopes it to the tab), your light/dark theme choice, the handle you last signed in as, and, during signup, your not-yet-saved handle and picks. It also keeps a few memories that save you repeats: that you've seen the tour and the latest announcement, your plan as last read so the page doesn't flicker, when the upgrade note last showed, and a draft of an entry you started and haven't saved. If a place opens on Mapbox's live map, Mapbox's map code adds its random ID there, and it stays until you clear it. Alongside all that, for the life of the tab only, sits the list of profiles and shelves this tab has already counted a view for. On iPhone the equivalent session lives in the device keychain, and the same kind of interface memories sit in the app's own storage. A player you press play on is that service's own page and follows its own cookie rules; on iPhone it keeps nothing once it closes.

Your account and your library stay for as long as you keep the account. Deleting it removes your profile, shelves, entries, follows and uploaded files at once; if a file cannot be removed at that moment, we're told, so a person can remove it by hand.

Deleting something smaller — an entry, a shelf, a photo — takes it out of the database at once, but the photo file itself stays in storage, reachable only by its exact link, until we clear out the photos nothing uses any more or you delete your account.

The database is backed up once a day and each backup is kept for seven days, so something you delete can survive in a backup for up to a week. Photos are not in those backups.

A few things outlive an account. Stripe keeps its own record of your payments, as billing records must be kept by law; deleting the account cancels a web subscription but does not erase that record. Reports other people filed about your pages stay, so a person can still review them. Lines in our server logs can name an account by its id; deleting the account does not remove them. And if a purchase ever needed a person to sort it out, our record of that purchase — the shop's references, not your library — stays as a billing record.

Export — "Your data" in settings downloads your whole library as JSON; on iPhone it hands you the file to save or share. Delete — "Delete library" in settings permanently removes your account, profile, shelves, entries, and uploaded files. It's immediate and irreversible, and a subscription bought on the web is cancelled with it.

Deleting cannot cancel an Apple subscription — nothing outside Apple can. If you subscribed on iPhone, cancel in your Apple ID subscription settings first, otherwise Apple keeps billing for an account that is gone.

You can ask us for a copy of what we hold about you, ask us to correct it or delete it, take it with you to another service, object to how we use it, and withdraw a consent you gave. Most of that you can do yourself: edit your library and profile (a new handle is a note to us), export it, switch announcements off in website settings or from the link in any of them, and delete your account. For anything else, write to hello@mixtaped.app and a person will answer.

If you think we've handled your data wrongly, you can complain to the data-protection authority where you live or work. We'd be glad of the chance to put it right first.

Questions, worries, or requests: hello@mixtaped.app.

This page covers what we hold and who can see it. The other half of the deal — what you agree to by using Mixtaped — is on the terms page.