Card numbers never touch your page.
Follow one $10 tip from a fan’s phone to a creator’s bank, and see exactly what each stop can read. Then the rules that protect the money once it’s there.
What the fan sees
The fan types their card into a field served by our card vault, inside Lina’s page. The page itself never holds the number.
- Card number
- 4242 4242 4242 4242
- Expiry · CVC
- 08/29 · 314
- mei@studio.nl
- Amount
- $10.00 tip
Six rules for the money.
The controls that matter most to creators and fans, in plain words. The full list is in our SOC 2 report.
- Cards never touch Kudo
Card numbers go straight to a PCI DSS Level 1 vault. We store a token and the last four digits.
- 48 hours on new bank details
A new payout account waits two days before it can receive money, and we email you at both ends.
- Passkeys and two-step codes
Required before any change to payouts. Passkeys are the default for new accounts.
- Encrypted everywhere
TLS 1.3 in transit, AES-256 at rest, keys rotated every 90 days and held in a hardware module.
- Data stays in the EU
Creator and fan data is stored in Frankfurt and Dublin. Backups are encrypted and kept for 35 days.
- Least access, logged
Staff reach production through short-lived, approved sessions. Every one is recorded and reviewed weekly.
Checked by people who aren’t us.
Audits and certifications, renewed every year. Ask for a report and we’ll send it the same week.
- SOC 2 Type II
Audited yearly. Report available under NDA.
- PCI DSS
SAQ A. Card data is handled by our Level 1 processor.
- GDPR
EU data residency, DPA on request, DPO in Lisbon.
- ISO 27001
Certified since 2025, renewed in September.
Responsible disclosure
Found something? We pay for it.
We reply within one working day, keep you posted until it’s fixed, credit you if you want, and never take legal action over good-faith research.
- 1Test only against your own pages and accounts. Create as many as you like.
- 2Don’t access, change or keep data that isn’t yours. Stop and tell us if you do by accident.
- 3Give us 90 days to fix it before you write about it. We usually need far fewer.
| Severity | For example | Reward |
|---|---|---|
| Critical | Moving money or reading card data you shouldn’t | $5,000 – $15,000 |
| High | Taking over another creator’s page or payouts | $1,500 – $5,000 |
| Medium | Reading another fan’s email or private note | $400 – $1,500 |
| Low | Smaller issues with a real impact | $100 – $400 |
Out of scope: reports from automated scanners without a working example, missing headers with no impact, and social engineering of our team.
Questions from your security team? We’ll answer them.
Studio customers get our SOC 2 report, a DPA and a call with Wiktor, who runs security at Kudo.