Data access
ReleaseMind reads release metadata, tags, and PR context required for drafting.
Access is scoped to the repositories you select and the permissions required for drafting.
We do not request access to unrelated repos.
Data we store
We store draft content, release metadata, and the minimum identifiers needed to map PRs to tags.
This data powers regeneration and audit history.
Access controls
GitHub App permissions limit access to selected repositories.
Access can be revoked at any time from GitHub settings.
Operational security
We monitor for abnormal access and rotate credentials when needed.
If you suspect a security issue, contact support immediately.
Review and introspect
Security starts with least-privilege access.
- Is repository access scoped to only what you ship?
- Do you have a security contact for ReleaseMind incidents?
- Are you comfortable with the data stored for drafts and history?