Understand data retention

Purpose and scope

Identify which records are retained, why retention varies and how deletion or legal holds affect the lifecycle.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The product and record type.
• Contract, legal or operational retention need.
• Any deletion or export request.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For understand data retention, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• A mapped retention basis.
• A deletion or preservation action.
• A record of exceptions and authority.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.