Library
Resources
Open, practical material. Use it even if you do not work with us.
§01
How to write a brief in 30 minutes
A good brief answers five questions: who the user is, which single task they solve, what data you collect, which integrations are mandatory, and what success looks like three months after launch.
Tip: describe data as a table of "field — why — who sees it — how long we keep it". It becomes the backbone of your privacy policy.
§02
Minimum application security checklist
- Passwords are hashed with a modern algorithm (Argon2id or bcrypt).
- Every request uses HTTPS, no mixed content.
- Server-side permission checks for every data request.
- No secrets stored in the repository.
- Dependencies are scanned automatically.
- There is a procedure for deleting an account and its data.
- Backup restore has been tested at least once.
An interactive version is in the Readiness calibrator.
§03
App Store and Google Play review: how to prepare
The reviewer sees your app for the first time with no context. Give them a test account with populated data, a short guide to key features, and explain every permission. Make sure data declarations match the SDKs you include — analytics and advertising SDKs often collect more than expected.
§04
Glossary for non-technical founders
| Term | In plain words |
|---|---|
| Threat model | A list of what could go wrong and what we do about it |
| CI | Automatic code checks on every change |
| Rollback | Returning to the previous working version |
| 2FA | A second sign-in factor, such as an app code |