Local processing
RepoDraft
Privacy Policy
RepoDraft Privacy Policy
Last updated: May 24, 2026
This page explains how RepoDraft handles local repositories, local Git state, generated drafts, support contact, and user privacy choices.
Privacy
How RepoDraft handles local Git information
RepoDraft is designed around local repositories selected by the user. Core drafting uses local Git and project signals to prepare editable drafts on the Mac.
Local data
Information used for core drafting
To prepare drafts, RepoDraft may read or process local information from the repository you choose.- Selected local repository information
- Local file paths and extensions
- Git statuses
- Branch and changed-file count
- Changed areas and file kinds
- Diff stats where available
- Generated draft text
Use
Local information creates drafts.
RepoDraft uses local repository signals to summarize changes, prepare draft wording, support editing, and copy the selected draft text.Core boundaries
Core features do not send repository details.
Core features do not send source code, diffs, file paths, repository metadata, or generated drafts to Hazybyte Studio or a drafting service.Support contact
You choose what to send.
If you contact support, your email app sends the message. Remove private source code, raw diffs, file paths, private repository names, private client details, secrets, tokens, API keys, and credentials before sending. RepoDraft SupportApple services
Apple handles App Store services separately.
Apple may process information separately when you download or update the app, use App Store services, or choose to share diagnostics or analytics with Apple.No account
No app account is required.
RepoDraft does not require a Hazybyte Studio account for core drafting, and core drafting does not require a Git hosting login.Updates
Updates to this page
If this privacy information changes, this page will be updated with a new Last updated date.Choices
Your privacy choices
You can choose which local repository to open, avoid sending support details, redact support messages before sending, and use macOS or App Store privacy settings where applicable.