Data Privacy and Retention
Who controls each critical account and can another authorised person recover the service during an incident? Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion.
What You Will Be Able to Decide
- Explain data privacy and retention in product and business terms.
- Apply this decision: Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion.
- Recognise this material risk: the company keeps sensitive information it cannot justify, find, protect, or delete.
- Use this review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
A founder is clarifying who controls the product and how the company will respond when something goes wrong. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Who controls each critical account and can another authorised person recover the service during an incident? The course example is A small team's customer portal with contractors and external integrations; use it to decide what evidence would justify the choice before a builder implements it.
What Does Data Privacy and Retention Mean for Your Product?
A founder is clarifying who controls the product and how the company will respond when something goes wrong.
Use the illustrative service for this course (A small team's customer portal with contractors and external integrations) to make the choice concrete. Who controls each critical account and can another authorised person recover the service during an incident?
Technical term
Data Privacy and Retention
Data privacy governs appropriate collection and use of personal information; retention defines how long each category remains and why.
How Should a Founder Use Data Privacy and Retention?
For a small team's customer portal with contractors and external integrations, ask what would happen if the company keeps sensitive information it cannot justify, find, protect, or delete.
For this decision, the useful standard is that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Decision: Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion.
- Evidence to request: show that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Owner: name who will respond if the company keeps sensitive information it cannot justify, find, protect, or delete.
- Record the result in the security, ownership, and handover record.
- Practical review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
How Do You Choose an Approach to Data Privacy and Retention?
Who controls each critical account and can another authorised person recover the service during an incident? Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion.
The risk is that the company keeps sensitive information it cannot justify, find, protect, or delete. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Data Privacy and Retention?
What Warning Signs Should You Look For?
- The proposal does not address this risk: the company keeps sensitive information it cannot justify, find, protect, or delete.
- Nobody can show whether access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to data privacy and retention?
- How have we reduced or accepted this risk: the company keeps sensitive information it cannot justify, find, protect, or delete.
- Can you demonstrate that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Collect the minimum necessary data and document purpose, access, provider, location, retention, export, and deletion. Ask for evidence against the specific risk: the company keeps sensitive information it cannot justify, find, protect, or delete.