Skip to content

Security

The safest data is the data we never ask for

Your password and your card number never reach us. Here is what we do with everything else, and how to tell us if we got it wrong.

What reaches us

  • Your passwordNeverThere is no password of yours in our database
  • Your card numberNeverIt goes from your browser to the payment processor without passing through us
  • Your date of birth, ID, or bank detailsNever askedWe do not collect them, so we cannot lose them
  • Your files, site, and catalogOursEncrypted, and checked against who is asking on every request

Three of the four things people worry about never reach us at all.

What we do

Every claim, with the thing that makes it true

Each row prints what it rests on. If one of those stops being true, the row has to change with it.

Your account

Sign in with Google or with an email and password. Your password is never sent to Artistplus. It is set and checked by a specialist identity platform, so there is no password of yours in our database to lose, and no reset link of ours that could hand one over.

  • No password in our database
  • Expiring sessions

Payments

The card fields at checkout are hosted by our payment processor and submitted straight to it from your browser. That is not a policy we follow, it is something our code cannot do: the website has no server-side payment client at all. There is no card number of yours anywhere in our systems to steal.

  • Card fields never post to us
  • No card number on our servers

Your music, files, and site

Everything moves over HTTPS, on our site and on yours. Files at rest and the records describing them are encrypted where they are stored, and every artist site gets a certificate automatically, including a domain you brought with you.

  • TLS everywhere
  • Encrypted at rest
  • Automatic certificates

Nobody else can read your account

Every request works out who is asking before it does anything else, then checks that the record actually belongs to them. That is the first line of the function, not a filter tacked on at the end. Your public site serves published pages only, never your drafts.

  • Identity checked per request
  • Ownership checked per record
  • Drafts never public

The links you send out

A share link carries a token nobody can guess rather than a tidy number somebody can count up from. You can put a password on it, give it an expiry, or send a separate link per recipient, and every open and download is written to a log only you can read.

  • Unguessable tokens
  • Optional password and expiry
  • Access log per link

What our own team can do

Support access is not all or nothing. Staff hold named capabilities rather than one general key, looking at an account is read only by default, and anything that changes one is written to an audit log we keep.

  • Capability scoped roles
  • Read only by default
  • Audit log

Deleting is reversible for a while

Deleting a file moves it to trash rather than destroying it, and it stays recoverable for 3 to 30 days depending on your plan. The file itself stays where it was the whole time, so restoring gives you back a working file rather than a broken link. When the window does lapse, a copy is written to a separate backup store before the live one is cleared.

  • Trash with a retention window
  • Backup copy before purge

When something breaks

Errors page us the moment they happen, not the next morning when somebody remembers to open a dashboard. Service state is published on a status page you can read without an account, and we would rather say an unflattering thing quickly than a reassuring one late.

  • Alerting on every error
  • Public status page

Responsible disclosure

Found something? Tell us before you tell the internet

One form, one inbox, read by an engineer rather than a ticket queue. We answer every report within 3 business days.

Answered in 3 business days

By an engineer who can read the code, not an autoresponder.

Safe harbour

Report in good faith and we come after the bug, never the reporter.

Credit if you want it

Tick the box and your name goes on the fix when it ships.

We do not run a paid bug bounty and we do not hold a security certification. Reports are read by an engineer either way, and we would rather hear about a problem than not.
ToArtistplus securitysecurity@artistplus.io
Subject[SECURITY]High · Broken access control or IDOR
The finding
How bad do you think it is

Your read, not a verdict. We assess it ourselves and never hold an over-estimate against a report.

A URL, a page, or the area of the product. If it needs a specific plan or setup, say so.

The proof

In the order you did them. Never paste anybody else’s data, credentials, or session tokens: describe what you could reach, not what you took.

The consequence, not the mechanism. This is what decides how fast we move.

Optional. An unlisted video, a gist, a screenshot host, anything we can open.

You

Goes to security@artistplus.io. Answered within 3 business days.

Scope, process, and safe harbour

What is in scopeOur site, artist sites, share links, billing, and our mail
  • Anything on artistplus.io, on your dashboard, or on a website we publish for an artist.
  • The links we generate for sharing files, press kits, and file requests.
  • Account, billing, and access control, meaning anything that lets one account reach another.
  • Email we send, including anything that lets a stranger send mail that looks like ours.
What is out of scopeNo denial of service, no social engineering, no other artist’s data
  • Denial of service, load testing, or anything that degrades the service for artists.
  • Social engineering of our team, our members, or our suppliers, and physical attacks of any kind.
  • Scanner output with no working proof that it can actually be exploited.
  • Missing headers, cookie flags, or mail policy records with no demonstrated impact.
  • Anything that needs a rooted device, a hostile browser extension, or a machine already under attacker control.
  • Accessing, changing, or keeping data belonging to anybody other than you.
What happens after you send itAcknowledged in 3 business days, then reproduced, fixed, and credited
  • We acknowledge it within 3 business days, from a person, not an autoresponder.
  • We try to reproduce it, then come back and tell you whether we could and what we plan to do about it.
  • We fix it, tell you when the fix is live, and ask whether you want to be credited by name.
  • If we decide not to fix it, we tell you why rather than letting it go quiet.
Safe harbour, in fullStay inside these terms and we treat your research as authorised

Report in good faith and we will not pursue legal action against you, will not ask your internet provider who you are, and will not suspend the account you used. Work only on your own account or one we give you, stop as soon as you have proved the issue, do not access, change, or keep anybody else’s data, and give us a window to fix it before you write it up. If somebody else brings a claim about research that stayed inside these terms, we will say publicly that it was authorised.

Machine-readable contact details at /.well-known/security.txt. The companies that process data on our behalf are listed in the privacy policy.

Nothing here needs a card to check

The free plan is a real website with the same account protections as every paid one. Try it before you trust it with anything.