Taxes, regions and compliance / Compliance themes
Which edge cases come up around “Removing a module: keep or toss the data”, considering secure erase not provided?
Built in the repository (checked files or tested library code; not a product you can run yet) C0217
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. Plan for: secure erase not provided; whole-element granularity only; kept archives accumulate. It exists only as a file in the repository, not as a product feature.
How to read this
The tag above says how real the answer is. Answers describe the plan in the repository and design documents. No app is released. Where an answer touches tax or law, treat it as a theme to verify with a qualified local adviser.
More in Compliance themes
- What should I plan for with “Trade and export rules”, especially around customs codes?
- What should I plan for with “Legal hold”, in particular regarding holds are local?
- What should I plan for with “Personal-data requests offline”, especially around tax data cannot simply be erased?
- See it in context with the whole topic
- Search all answers