GitHub OAuth access
MakeMyReadme uses GitHub OAuth so you can select repositories available to your GitHub account. Access is used to inspect repository context and prepare README output.
How MakeMyReadme handles GitHub repository access.
MakeMyReadme is built for real GitHub repositories, including private client repositories. This page explains what the product needs access to and how the review flow works.
Private repositories
Private repos can be used when your GitHub account grants access. The app should only read the repository context needed to estimate input, generate the README, and create the requested Pull Request.
What is sent for generation
The generation step can include repository metadata, file names, package or framework signals, scripts, selected source snippets, and prompts needed to draft the README.
What is stored
MakeMyReadme may store account metadata, repository metadata, generated README output, job status, usage estimates, checkout status, and OAuth tokens required for the GitHub workflow.
Review before merge
The generated README is designed to be reviewed before it is merged. A README Pull Request is a review step, not a hidden automatic rewrite of your repository.
Removing access
You can revoke GitHub access from your GitHub account settings at any time. For deletion questions, contact contact@bewide.ai.
Important note about secrets
Do not paste secret values into MakeMyReadme. README generation can mention environment variable names and setup steps, but real API keys, database URLs, Stripe secrets, and private credentials should stay outside documentation.