Compliance themes
Removing a module: keep or toss the data
ADR-0005: when a customer unticks an element, its data is kept by default: archived, read-only and restored if the element is added again. Tossing is a separate, explicit choice that needs the element id typed, a verified backup first and, for books and personal data, an export, a retention check and a Spanish acknowledgement. There is no delete-all. Built as tested code in the core, Logistics, packaging and the launcher model; no screen. Deleted data is not securely erased.
Built in the repository (checked files or tested library code; not a product you can run yet)
What to plan for
- Secure erase not provided
- Whole-element granularity only
- Kept archives accumulate
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Role templates EMP-0006
- Inactive/terminated employee archive EMP-0014
- Product active/archived INV-0013
- Data retention settings SEC-0036
- True removal: a build holds nothing for elements outside its spec SEC-0042
- Hiding by flag does not count as removal SEC-0043
- Document archive 5+ years PE-0063
- Yape/Plin tax record keeping PE-0112
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.