Privacy Policy

Fanpay runs Fanpay, a platform where creators publish what their promotion costs and brands book it at that price. This policy covers fanpay.app and everything served from it.

If you want to reach a human about anything on this page, hello@fanpay.app is read by someone who can act on it.

Only what a feature needs to work. Concretely, that is:

• Waitlist signups: your email address, which side you joined as (creator or brand), anything you typed in the optional note, and which page you signed up from. The note is free text — it is worth knowing that whatever you put there is what we store.
• Your account: your name, email address, whether that email is verified, and your profile picture if you signed in with Google.
• Your sessions: the IP address and browser user-agent of the device you signed in from, so you can see where you are signed in and end a session you don't recognise.
• Sign-in credentials: for Google, the account identifier Google gives us and the tokens that let us confirm it is you. For email links, a hashed copy of the link's token — never the link itself.

We do not ask for a date of birth, a phone number, or a physical address, because nothing we have built needs one.

Rate limiting is the clearest example, and it is worth spelling out because most sites do it the other way. To stop one person submitting the waitlist form a thousand times, we have to count requests per visitor. We do that by storing a SHA-256 hash of the route, your network address and a secret that never leaves our servers — not your address itself.

The practical difference: the stored value cannot be turned back into an IP address, and it is useless to anyone who obtains it. Deciding whether to accept an email address does not require us to keep a log of who visited, so we don't keep one.

There is also no advertising network on this site, no third-party analytics script, and no tracking pixel. We are not building a profile of you across other websites, and there is nothing embedded here that would let anyone else do it either.

Fanpay is designed to hold a brand's payment until a placement is approved, and to pay creators out on a cycle. None of that is built yet, and no payment data of any kind is collected today.

We have never handled a card number, a bank account or a tax identifier, and this page will say so until the day that changes. When it does, this section gets rewritten before the feature ships — including naming the payment processor, since they will hold that data rather than us.

Under data protection law we need a lawful basis for each thing we store. Ours are straightforward:

• Your account and session data: necessary to perform the contract — you asked for an account, and an account you cannot sign in to is not one.
• Waitlist signups: your consent, given when you submitted the form. You can withdraw it at any time by asking us to remove you.
• Rate-limiting hashes: our legitimate interest in keeping the service available and not paying to process automated abuse.

We do not sell your data. We do not share it for anyone else's advertising. The only third parties involved are the ones needed to run the service:

• Google, if you choose to sign in with Google. That exchange tells Google you signed in to Fanpay, and gives us your name, email and profile picture. Signing in with an email link avoids it entirely.
• Our hosting and database providers, who store the data on our behalf under contract and do not use it for their own purposes.
• An email provider, when there is one. At the time of writing no email service is connected, and sign-in links are delivered through our own servers only in development.

We will also disclose data if the law genuinely requires it — a court order, not a polite request.

Sessions expire on their own and expired rows are removed. Sign-in link tokens are consumed on first use and are useless afterwards. Rate-limiting rows are disposable — nothing reads a counting window once it has passed.

Waitlist signups are kept until the list has served its purpose or you ask to be removed, whichever comes first. Account data is kept while your account exists.

When you delete your account, the account and everything keyed to it goes with it. That is enforced in the database itself rather than by a script someone has to remember to run.

Depending on where you live you may have the right to access a copy of your data, correct it, delete it, restrict or object to how we use it, or take it elsewhere in a portable format. Where we rely on consent, you can withdraw it without giving a reason.

Email hello@fanpay.app and we will action it. We will not ask you to explain why, and we will not make you sign in to a dashboard to find a hidden switch.

If you think we have handled your data badly, you can complain to your local data protection authority. We would rather you told us first, but you are not obliged to.

Sessions are signed with a server-side secret, so a session cookie cannot be edited into someone else's. Sign-in link tokens are stored hashed, so a copy of the database does not hand anyone a way in. Traffic is served over HTTPS.

No system is perfect, and a policy that claims otherwise is not being honest with you. If we ever discover a breach affecting your data, we will tell you and the relevant authority within the timeframes the law sets.

Fanpay is not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has given us their data, tell us and we will remove it.

When this policy changes materially we will update the date at the top of the page, and — if you have an account — tell you directly rather than relying on you to re-read it.

Questions about any of it go to hello@fanpay.app.