Security & Compliance
We aim for SOC 2 alignment. Stripe handles payment-card data and Didit handles age and identity checks where those workflows are enabled.
Fraud Prevention
Where payments are enabled, Stripe tooling and ALS dispute records support transaction review.
VAT Compliance
Tax and receipt handling runs only in enabled payment flows and follows the applicable launch configuration.
Copyright Compliance
Published notice, takedown, and counter-notification routes support copyright reports.
AML/KYC
Didit handles age and identity checks where an enabled workflow requires them; Stripe Connect separately handles payout-account checks.
What does the platform keep a record of?
Security on a licensing platform is mostly about evidence — being able to show who agreed to what, and when. The records below exist so that either side of a deal can answer that question later.
- Licence records. Each issued licence keeps the agreed scope, parties, and purchase date so permitted use is provable later.
- Commission orders and approvals. Briefs, proposals, milestones, and sign-offs stay attached to the project, including the record of who approved each stage.
- Identity checks where required. Didit performs age and identity checks where an enabled workflow requires them; Stripe Connect separately verifies payout-account holders.
- Dispute and takedown trails. Copyright reports follow the published notice, takedown, and counter-notification routes, and disputes keep an evidence record.
All payment data is processed by Stripe, a PCI DSS Level 1 certified service provider.

