Security and privacy
Security model and threat model
A written security model exists in the repository: assets, attackers, eight rules (true removal, signed everything, local authority for offline use only, online features decided by the host, no hidden doors, staging discipline, break-in tests, an honest limit) and a table of what is built and what is not. A full threat model, an external security review and the host design are planned.
Designed in a document, no code yet
What to plan for
- External review not done
- Host not built
- A person who holds the code can attack the code
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- True removal: a build holds nothing for elements outside its spec SEC-0042
- Hiding by flag does not count as removal SEC-0043
- Absence test per profile: files SEC-0044
- Absence test per profile: commands and menus refuse SEC-0045
- Absence test per profile: database schema lacks removed tables SEC-0046
- Signed everything: builds, updates, entitlements, catalog and price documents SEC-0047
- Signature is mandatory, no skip path SEC-0048
- No demo or default keys in any build SEC-0049
- No default network binding SEC-0050
- No runtime CDN or remote asset loads SEC-0051
- No founder or hidden auto-boot SEC-0052
- Offline guard enforces the no-hidden-doors rules SEC-0053
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.