This is for people with an account: artists, their team members, and anyone managing an artist. If your details appear on somebody else's artist and you never signed up, you want Privacy for contacts instead. If you are just reading a page, you want Privacy for visitors.
Who we are
Stagent B.V., trading as TAP (The Artist Passport), registered in the Netherlands under Chamber of Commerce number 75826216, at Keizersgracht 520H, 1017 EK Amsterdam, The Netherlands. We decide what happens with the data described here, which makes us a controller.
For details you publish about other people, we and you are joint controllers. That division is set out in Shared responsibility with artists.
What we hold, and why we may
| What | Why | Our legal ground |
|---|---|---|
| Your email address | It is how you sign in. There are no passwords: we email you a link | Performing our agreement with you |
| Your name | So your team knows who you are, so you can appear as a contact if you choose, and so it can be shown on your passport | Performing our agreement with you |
| Your phone number, and whether it is verified | To confirm you are a real person before you can grant an app access to an artist, before you can ask for verification, and before you can ask us for a passport | Performing our agreement with you, and our legitimate interest in keeping the register free of fraud |
| Your avatar photograph | It is shown on your passport, and read by the applications you authorise | Performing our agreement with you |
| Your request for a passport, what the registrar decided and the reason, and the dates we issued or revoked it | So a passport can be read for what it is, and so a decision about yours can be explained later | Performing our agreement with you, and our legitimate interest in an accountable register |
| Everything on an artist: name, biography, images, logos, documents, links, contacts, the shop and the products read from a store the artist connects | It is the register. Publishing it is the service | Performing our agreement with you, and our legitimate interest in operating a public register artists and their counterparties can rely on |
| An artist's verification status, method, registrar and date | So a verification can be explained and withdrawn if it turns out to be wrong | Our legitimate interest in a verification that means something |
| The team name and invitation link from a Spotify team invite you send us, and when it arrived. We do not keep the mail itself | So a verification we granted can be explained later | Our legitimate interest in a verification that means something |
| Notes and decisions we record while operating the register, with who made them and when | So a decision about your account, an artist or your passport can be explained later, and support does not start from zero | Our legitimate interest in an accountable register |
| The name a connected app gives us for someone editing an artist through it, and when their access was last renewed | So an owner can see, on the Apps page, who currently holds access through an app they connected, and end it | Performing our agreement with the artist, and our legitimate interest in an accountable register |
| When you last used TAP, to the hour | So our team can tell an active account from a dormant one when helping you or keeping the register tidy | Our legitimate interest in operating and supporting the service |
| Which advert or which artist's page brought you here, when a cookie from the previous 30 days says so | So we can tell which placements and which artists bring the next ones; the artist sees its count, never who | Our legitimate interest in knowing what makes TAP spread; the cookie itself is covered by the cookie policy and its switch |
| When you look about to claim a handle, when you sign up, or when you claim one, and which advert brought you here if one did, while you allow it. Also your IP address, browser details and the page's origin; the pixel's separate automatic matching is explained in the cookie policy | So we can tell which of our adverts on ChatGPT bring people who go on to sign up or claim a handle | Your consent; the cookie itself is covered by the cookie policy and its switch |
| Which emails we sent you, and whether each arrived, was opened or was clicked | So we can tell a mail that never arrived from one that was ignored, and stop mailing an address that bounces or reports us as spam | Our legitimate interest in mail that reaches you |
| Server logs: page, time, browser, IP address | Keeping the service running and spotting abuse | Our legitimate interest in a service that works and is not attacked |
We do not profile you and we make no automated decisions about you. We run adverts on ChatGPT; a pixel you allow on our own pages measures whether they worked, telling OpenAI when you sign up or claim a handle. TAP does not supply your name or email address in those conversion events. The cookie policy explains the pixel's separate automatic matching feature and which pages exclude it.
What becomes public
Publishing an artist is a deliberate step, and until you publish it nothing is visible to anyone outside your team.
Once published, each page is in a state you set on that page. Your website, your links page and your music page are on or disabled. On, anyone can find the page: it is linked from your other pages and search engines may index it. Disabled, the links page and the music page stop answering and nothing points at them; a website that is disabled leaves the address answering with your name, avatar and channels, because a domain you connected points at it.
Your EPK has more states, because it is the page you send rather than the page people find. Anyone can find it: linked and indexed like a page that is on. Anyone with the link: the address still works for whoever has it, and we keep it out of search results, though the address is your handle, so a visitor who guesses it gets in. Only people you give access: the address answers with your name and avatar, and the page itself opens only for someone holding a link you handed out. You choose whether a visitor may ask for one, leaving their name, email address and a note for you to decide on, or whether the page is invitation only, in which case the form only sends a fresh link to an address you already gave one, and the link it replaces stops working. Disabled: the address stops answering, and links you handed out stop working.
The crawler controls sit beside those, on the artist's settings. Switch search engines off and the artist also leaves the sitemap we publish, so nothing of ours points a crawler at it. Both controls otherwise work by convention: we send the standard noindex signal and refuse the AI crawlers on our list by the name they present, so a crawler that misrepresents itself defeats them. Our robots file names no AI crawler itself, so the artist's switch is the only word on it.
Riders follow the EPK. They sit on the page, travel in the downloadable kit and open for everyone the EPK opens for; an EPK set to only people you give access keeps them, with everything else on it, behind a link you handed out.
Approved applications read artist data through our API on the terms in the API conditions, which is a separate path from what the public sees. An application that represents you, such as the booking platform that set your artist up, and a person editing the artist through app access that application handed them, can publish one of your pages, close it again, or hand out an access link on your behalf, so that a promoter it is already mailing gets a working link. Every owner is mailed the moment a page's visibility changes this way, or a person with that app access adds an outside address for the artist's activity by email, and every change is on your activity log under the name that made it. Every link handed out this way appears on your own access list with the name it gave.
Your own name and contact details only appear publicly if you switch that on yourself in the contacts section. It is off by default.
Your passport is not one of the public pages. You see it when you are signed in, and an application sees it only where you have authorised that application to read it.
Your account's email address, your account's phone number and the artist's internal number are never public. The address and number you give when you list yourself as a contact are separate fields, and those do show on the artist's pages.
Who else sees it
Everything is listed on Who receives register data: the public, approved applications, an assistant you connect, our service providers, and authorities where the law requires it.
An assistant you connect to your account, such as Claude or ChatGPT, reads and changes what you can for the artists you run, as you, each time you ask it to, until you remove it under Sign in with TAP on your account. Every change it makes is on the artist's activity as yours. What it keeps is up to its provider, under that provider's terms.
Two things worth repeating here. Approved applications are bound to a closed list of purposes and may not resell or copy the register. And Stagent, the booking platform, is the same company as us rather than a third party, which is why no contract sits between the two and why we hold ourselves to the same purpose limits internally.
Email from us
Sign-in links and notices about your artists are the service, so they always arrive. Setup tips and product updates are optional: switch either off on your account page or through the link at the foot of every such mail, and it stops the same moment. The activity of each artist you are on is optional too. It is on once you have signed in with your address; switch it off per artist on your account page, or with the link at the foot of each of those mails, which stops that artist alone.
Our mail provider tells us whether each mail arrived, and, when your mail client loads images, whether it was opened and whether a link in it was clicked. We use that to tell a mail that never reached you from one you chose to ignore, and to keep mail out of a mailbox that does not want it. An address that bounces stops receiving everything, sign-in links included, until you tell us it works again. An address that reports us as spam stops receiving the optional mail; sign-in links and notices about your artists still go, because you cannot use the service without them.
Verifying your phone
When you verify a number, the code is generated, sent and checked by Prelude. It never exists on our side; we only learn whether the check succeeded. We store the number and the fact that it is verified. Change the number and the verification falls away, because it proved possession of the old one.
Your passport
You can ask us for a passport once you are a member of at least one artist, your email address is confirmed, your phone number is verified, and you have added a photo of yourself. A registrar at TAP reads the request and either issues the passport or denies it, with a reason either way. While a request is still open you can withdraw it.
An issued passport shows your name, your photo, the date we issued it, and the artists you belong to with your role in each. Leaving every artist does not revoke it. A registrar can revoke a passport later, and you get the reason for that too.
An application you have authorised can read the passport through our API: your name, the address of your photo, and the artists you belong to with your role in each. Withdraw the authorisation from your account and it stops reading.
How long we keep it
While your account exists. Delete it from the account page and we hold everything for 7 days, so you can still stop it, then we remove your name, your email address, your phone number, your photo, your passport and your place on every artist. What the law makes us keep, we keep.
Your account row itself stays behind with none of that on it. Your activity log hangs on it, and a record of who did what has to outlive the person, so the row survives as an empty marker and the address you used is free to sign up again. The marker keeps which advert or which artist's page brought you here, a count that names nobody.
Take a copy first. The export on your account page holds everything personal we hold about you: your name, email address and phone number, your photo, your passport and the requests behind it, the artists you belong to with your role, which optional mail you switched off and when, the applications you authorised, your activity log, every mail we sent you and what happened to it, and when you last used TAP or which advert or artist's page brought you here. It leaves out a registrar's own internal notes about a decision on your account: ask for those under Your rights below and we send them, with anyone else's details taken out. It is there whenever you want it, not only when you are leaving.
An access link you hand out lives until you revoke it or it expires, and we keep the row after that: who held it, when they last opened something, and how often. That record is the reason to hand out a key rather than a secret address.
Two things outlive the account on purpose. An artist with other members carries on, minus you: your identity goes, the artist's profile stays, because it is not only yours. If you were its only owner it carries on with nobody at the wheel, and a registrar can seat a new one. And retired handles keep resolving so that links other people published do not break, which is the point of a register.
An artist is deleted the same way, by an owner, from the artist's settings, with the same 7 days and the same export. Afterwards the pages, the files, the team and the connections are gone, and what is left is an empty row holding the handle so nobody is ever given it again.
Your rights
Ask us for a copy of what we hold, correct it, delete it, restrict what we do with it, take it elsewhere in a machine-readable form, or object to anything we do on the basis of legitimate interest. The export and the delete button on your account page do the first and the third without asking anyone. For the rest, write to help@tap.fm and we will not ask you to justify the request.
You can complain to the Autoriteit Persoonsgegevens at autoriteitpersoonsgegevens.nl. Tell us first if you can; we would rather fix it.
Security and breaches
Traffic is encrypted, data is encrypted at rest, and access to production is limited to people who need it. No system is perfect. If something happens that puts your data at risk, we tell the regulator and we tell you, as the law requires and because you would want to know.
Changes
Material changes are announced by email before they take effect, not slipped into this page.