Privacy notice

The short version

• We collect what we need to run 50heads, pay heads and stop fraud: your email, your phone number, your answers, how you use the app, and payment and tax details when money moves.
• Tier 2 ID and face checks are done by Stripe. We keep only a yes or no and your age band; we ask Stripe to delete the photos when the check ends.
• Requesters never see who answered their question. Answers are anonymous to the requester, but 50heads itself holds your verification data.
• We don't sell data, track you across other apps or sites, or collect your location or contacts.
• We don't use your questions, the answers you buy or the reasons heads write to train AI models, and we don't sell them.
• If you connect 50heads to Slack, Microsoft Teams, Linear, Jira, Zapier, n8n, an AI assistant or the 50heads CLI, we keep only what it needs to work, and disconnecting or deleting your account removes our access. More under Apps and integrations below.
• You can get a copy of your data, correct it or delete it. Use the contact form.

The rest of this notice gives the detail.

Who we are

50heads Limited (company number 17486968), registered office 66 Paul Street, London, EC2A 4NA, United Kingdom, is the controller of your personal data. Contact our data protection lead through the contact form.

What we collect and why

We've assessed our legitimate interests against your rights. You can ask for a copy of that assessment.

Biometric data and the Tier 2 ID check

Tier 2 is optional. To reach it, you take a photo of your ID document and a short live selfie. The check is run by our identity provider, Stripe (Stripe, Inc. and Stripe Payments Europe Ltd), in a secure Stripe page that opens inside the app. Stripe compares your selfie with the photo on your ID and checks that the ID is genuine. The 50heads app and 50heads servers never receive, see or store your ID images, your selfie or any face data.

We ask for your explicit consent on a separate screen before the check starts.

What 50heads keeps: whether the check passed, your age band (for example 25–34), a reference number for the check and its date. Stripe tells us your date of birth once so we can work out your age band; we do not store it.

What Stripe keeps: when the check ends, we ask Stripe to delete your ID images, selfie and the details read from your ID. Stripe says this can take up to 4 days. Stripe keeps the biometric identifiers made from your selfie and ID photo for no longer than one year, only to detect fraud, such as one person opening several accounts, unless you withdraw consent first. Stripe may also use your images to improve its checks only if you agree to that on Stripe's own screen. See Stripe's privacy policy.

Where it is stored: Stripe processes and stores the check in Ireland and the United States. The result we keep is stored with our hosting provider in the EU and the US.

No other use: neither we nor Stripe use your face data for advertising, marketing or profiling, and we do not use it to train AI models. We share it with no one else.

Deleting it: when you delete your account, or withdraw consent in the app (You, then Privacy, data and appeals), we ask Stripe to delete the data from your checks and you move to Tier 1. You can also ask Stripe directly at privacy@stripe.com.

Face ID: the app can use Face ID or Touch ID to confirm it's you before you approve spending. That check happens entirely on your device; iOS tells the app only whether it succeeded, and no face data reaches the app or 50heads.

Automated decisions

We use automated checks to detect fraud, which can lower a head's tier or reject answers. Any head can ask for a person to review a decision through appeals.

AI and your data

We use AI on your data only to do things for you. That processing runs on Cloudflare Workers AI, our hosting provider, on our instructions. We use it to:

• summarize the written answers and reasons to a question, for the requester who asked it;
• translate written answers and reasons into the requester's language;
• review a question while it is being written, suggest clearer wording, and check it against our rules before heads see it;
• screen images uploaded with a question before they are stored or shown to heads.

We send the model only what the job needs: the words of the question, the written answers and the option each one picked, or the image. We don't send who a head is, their device, their country or their integrity-check results.

We don't use your questions, the answers you buy or the reasons heads write to train AI models, and we don't sell them. Heads' answers are never used to train models by us.

What the model produces is stored with the question, like the rest of the result. A summary groups the written answers but doesn't replace them: the requester can still read each one. A screening result can hold a question for a person at 50heads to look at, or refuse an image.

Separately, we use AI tools to help make our own advertising for 50heads. Those tools receive only our own descriptions and brand material, never personal data about heads or requesters.

More in AI and your data.

If you answer a question someone shared with you

A 50heads customer can share one question, or a few in a row, with their own audience as a link. If you answer one, we keep your answer (the option, order or tap), a cookie on that link's address so the page knows you have answered, a scrambled network signal for 90 days so one person cannot answer many times, and, when the link has several questions, a random visit number that groups the answers one browser gave in one pass. We do not ask for or keep your name, email, phone number or account, and the person who asked never sees who answered. For your answer, we act as processor for the customer who asked, for their purpose; for the repeat check and the person-not-script check, we act as controller, on our legitimate interest in stopping abuse. The customer confirms to us that they were entitled to invite you. More in answering a question someone sent you.

Apps and integrations

You can use 50heads from other tools: Slack, Microsoft Teams, Linear and Jira, Zapier and n8n, and AI assistants, the 50heads command-line tool (CLI) and your own code through MCP, A2A or the API. Someone who manages a 50heads account connects each one. A question asked from any of them is an ordinary 50heads question on that account: it spends the account's credits, it is kept like any other question, and the people who answer never see which tool it came from or who in the workspace asked. The tool never sees who answered.

What each one sends us and what we keep:

In Slack we look up only the language of the person using 50heads, and keep it for up to 6 hours to avoid asking again. We don't ask any of these tools for access to other messages, channels or files, and from Linear and Jira we keep only 50heads commands. Slack, Microsoft, Linear, Atlassian, Zapier and n8n handle what you send through them under their own privacy terms.

Disconnecting. In 50heads, go to Settings, then Integrations and choose Disconnect; API keys are under Developers. On a team, the owner or an admin can do it. You can also remove the 50heads app from Slack, Linear or Jira, and we disconnect when they tell us. Removing the app from Microsoft Teams stops the bot there, but the organization stays connected to the 50heads account until it is disconnected in Settings, then Integrations.

What happens when you disconnect or uninstall. We revoke the access token with the tool where it has one, and delete our copy. We keep a record that the workspace or connection existed, its name and when it was disconnected, with the account's history, and questions already asked stay on the account like any other question. Disconnecting a Zapier, n8n, assistant, CLI or API connection revokes its keys and tokens and stops its webhooks.

If you delete your 50heads account, we disconnect every tool connected to your personal account, revoke its tokens and keys, stop its webhooks and delete the tokens we held. A tool connected to a team account belongs to the team, so it stays until the team's owner or an admin disconnects it, or the team is closed.

How we protect it

Everything between you, the tools above and 50heads travels over encrypted connections. Access tokens and signing secrets are encrypted when stored, and keys and refresh tokens are kept only as a one-way scramble. Each tool's request to us is checked against that tool's signature or credentials before we act on it. Only the people at 50heads who need it to run and support the service can reach personal data. Our hosting and other providers are listed on our subprocessors page.

Who we share it with

• Service providers that host, secure and run 50heads, process payments and payouts, check identities, and send email and text messages. They're listed on our subprocessors page and act only on our instructions.
• Tax authorities, where the law requires.
• Anyone the law requires, such as the police with a valid order.

Requesters see answers, tiers and integrity-check references, never who answered.

International transfers

Some providers are outside the UK and EU, mainly in the United States. We use the UK Extension to the EU–US Data Privacy Framework where the provider is certified, or the UK International Data Transfer Agreement or EU Standard Contractual Clauses, with a transfer risk assessment.

How long we keep it

We keep a second copy of stored files in the same hosting account. A deleted file can remain in that copy for up to 24 hours. This is not a promise of a recovery time.

Your rights

You can ask to access, correct, delete, restrict or move your data, object to processing based on legitimate interests, and withdraw consent. See your data rights. We reply within a month.

Children

50heads is for people aged 18 and over. If we find an account belongs to someone younger, we close it and delete their data.

Cookies

See our cookie policy. Without your consent, the website and portal set only the cookies they need to work, such as your language and currency choices and, in the portal, your sign-in. If you accept analytics cookies in the banner, we also use Google Analytics to count visits, on the basis of your consent; you can withdraw it at any time from Cookie settings at the foot of any page.

Complaints

Please tell us first. You can also complain to the Information Commissioner's Office at ico.org.uk, or to the data protection authority where you live.

Changes

We'll tell you about material changes in the app and by email before they take effect.

Version 0.12 (31 October 2026) names Stripe as the provider of the Tier 2 ID check, and says what 50heads and Stripe each keep, for how long and where. We ask Stripe to delete your ID images and selfie when the check ends. The biometric identifiers Stripe keeps to detect fraud are kept for no longer than one year.