What should I plan for with “True removal of unselected elements”, with a focus on a removed element's data is a separate choice?

A package holds nothing for elements outside its spec: no code, assets, migrations or data tables, and hiding by a flag does not count. A packaging command proves the absence of files, menu entries, permissions and database tables for a profile, and the core tests check the database side. Plan for: a removed element's data is a separate choice; proven per profile, not for every possible spec; installer behaviour not tested. It exists only as a file in the repository, not as a product feature.

Go to the related page

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 Security and privacy

• What should owners check about “Security model and threat model”, in particular regarding external review not done?
• Why does “No hidden doors” matter for a small business, especially around applies to the code that exists?
• Which edge cases come up around “Staging discipline”, thinking about rollout tooling not built?
• See it in context with the whole topic
• Search all answers