Retention basics
Drafts and release metadata are retained to preserve audit history and enable regeneration.
Retention continues even if you stop generating new drafts.
Control access
You control access by uninstalling the GitHub App or revoking repos.
Removing access stops new data from being collected.
Deletion requests
Contact support with the org name and repo list you want removed.
We confirm completion once the deletion is processed.
After deletion
Deleted data cannot be restored, so export any notes you need first.
Reinstalling later will rebuild drafts from GitHub history.
Review and introspect
Retention choices shape auditability.
- Do you need a retention policy for release notes in your org?
- Have you documented who can request deletions?
- Are you comfortable with how deletion impacts audit history?