Security that protects your income
Customers only subscribe to software they trust, and Affiliates only recommend products that make them look good. Every FormaBase product inherits the same layered protection, so Creators never have to build it, Affiliates never have to vouch for it alone, and customers can say yes with confidence.
Each layer stops a different kind of problem, so no single safeguard has to be perfect. Together they protect the customers you serve and the revenue they bring.
| Layer | How it works | What it protects | Status |
|---|---|---|---|
| Who gets in | Every Creator verifies their identity and signs the Creator Agreement before getting any access | You work alongside accountable, real people | In progress |
| Account security | Two-factor sign-in for every Creator and FormaBase team member | Your account, earnings and products | In progress |
| Blast radius | Each product can reach only its own data and nothing else | A problem in one product stays in that product | In progress |
| Customer data | Products receive only the customer details they need; card details stay with Stripe | Customer privacy, and the trust that keeps them subscribed | In progress |
| Code entry | Every change is reviewed before it reaches customers | Products that keep working, release after release | In progress |
| Automated screening | Automated checks for known vulnerabilities, leaked keys and suspicious code on every release | Customers, from anything harmful slipping in | Planned |
| Human approval | A person approves every first launch and anything the checks flag | The judgment that automation alone can miss | Planned |
| Runtime | Live monitoring, with the ability to pause one product instantly | Every other product, if one ever misbehaves | Planned |
Identity and access
In progressEvery Creator is a verified person. Before submitting a product, each Creator completes the same quick identity check with a dedicated verification provider. Customers and Affiliates know a real, accountable person stands behind every product. FormaBase keeps the result of the check, never a copy of your ID.
Affiliates verify once, when they set up payouts. You can start sharing links right away; the check happens only where it matters, before money moves.
Your account is protected. Two-factor sign-in guards Creator and FormaBase team accounts, and each Creator works only on their own product. Every administrative action is recorded, so there is always a clear record of who did what. When the team looks at Studio through a participant's eyes to help them, changes are turned off and the session is recorded too.
Keys stay locked away
In progressThe keys that move money and send messages live only inside the Core. A product holds just two credentials of its own, and they are set up for you. As a Creator there is nothing sensitive to store, manage or accidentally share.
Because FormaBase issues every product's credentials, it can replace them in one step if ever needed. And a release that accidentally contains a secret is caught before it ships, not after.
Reviewed releases
PlannedEvery release is checked automatically, and a person approves first launches and anything the checks flag. Updates get the same care as launches, so customers can rely on a product for years, and Affiliates can keep recommending it.
- Checks for known vulnerabilities in the building blocks a product uses
- Scanning for keys or passwords that should never ship
- Automated and AI-assisted review for anything hidden or out of place
- Products connect only to FormaBase and services approved for them
The Creator Agreement backs this up with clear commitments, so every Creator shares the same standard and the whole catalog earns the same trust.
Customers hand over their details and payment information because they trust the product. These protections keep that trust, on every product.
| Protection | What it means | Status |
|---|---|---|
| Encryption in transit | Every FormaBase page and product is served over an encrypted connection, always | Live |
| Browser security headers | Browsers are told to block common tricks, like disguising a page inside another site | Live |
| Payment details | Card numbers are handled by Stripe, a certified payments leader, and never stored by FormaBase | In progress |
| Encryption at rest | Stored data is kept with providers that encrypt it on disk | In progress |
| Data minimization | Each product sees only the customer details it needs to do its job | In progress |
| Money records | Earnings records are never edited or deleted; any correction is a new, visible entry | In progress |
For what personal information we collect and why, see the Privacy Policy.
Runtime protection
PlannedLive products will be watched for unusual behavior. If one product ever misbehaves, FormaBase can pause it in one step while every other product keeps running and earning.
Independent testing
PlannedBefore registration opens, FormaBase will commission an independent security firm to test the Core, and will repeat that testing as the platform grows. Outside experts checking the work is part of earning your trust.
Found something that looks like a security issue in FormaBase or a FormaBase product? We want to hear about it. Send a security report through the contact form, with enough detail for us to reproduce it. We will acknowledge your report, keep you updated, and thank you publicly if you would like.
Please act in good faith: give us reasonable time to fix the issue before disclosing it, avoid accessing or changing other people's data, and do not degrade the service. We will not pursue anyone who reports an issue this way. Our security contact is also published at /.well-known/security.txt.