Privacy Policy

The short version

• There are no accounts and no sign-up. We don't ask for your name, email or password.
• Your README draft is saved only in your own browser. It is never uploaded to our servers.
• When you enter a GitHub username, we look up that account's public GitHub data to fill in the tools. We don't store it in a database.
• We use Google Analytics to count visits and, if enabled, Google AdSense to show ads. Both use cookies, which you can accept or reject.

Who runs this site

MakeReadme (makereadme.prabathoff.workers.dev) is an independent project run by Prabath in Sri Lanka. For any privacy question, email prabathoff@gmail.com.

Data stored in your browser

These are kept in your browser's local storage. They never leave your device, and clearing your site data removes them:

• profile-readme-draft: your README editor content, so your work survives a page reload.
• pf-theme: whether you chose light or dark mode.
• mr-consent: your cookie choice (accept or reject).

GitHub usernames and public profile data

When you import a profile, make a share card, or use GitHub Wrapped, the developer persona or the roast tool, the username you type is sent to our server. The server then requests that account's public information from the GitHub API: name, avatar, bio, location, follower count, public repositories, languages, stars and public contribution activity.

We use this only to generate the result you asked for. It isn't saved to a database or used to build profiles. Responses may be cached for up to an hour to keep the site fast and stay within GitHub's rate limits. Result pages such as /roast/username are public links that anyone with the URL can open; they only show information that is already public on GitHub.

Hosting and server logs

The site is hosted on Vercel. Like most web hosts, Vercel processes technical data such as your IP address, browser type and the pages requested, in order to deliver the site, keep it secure and diagnose errors. See Vercel's privacy policy.

Cookies, analytics and advertising

Google Analytics

We use Google Analytics 4 to understand how many people visit, which pages and tools they use, roughly where they are (country or city) and what devices they use. Google Analytics uses cookies and similar technologies. We also send a few anonymous events, such as "README downloaded", to learn which features are useful. We don't send names, emails or the contents of your README to Google.

Google AdSense

We may show ads served by Google AdSense. When ads are shown:

• Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website and other websites.
• Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet.
• You can opt out of personalised advertising in Google's Ads Settings, or opt out of some third-party vendors' use of cookies for personalised advertising at www.aboutads.info.

Learn more in How Google uses information from sites or apps that use its services.

Your choices

• Use the cookie banner, or Cookie settings in the footer, to accept or reject analytics and advertising cookies. Visitors in the European Economic Area, the UK and Switzerland have these cookies off until they accept.
• You can also install the Google Analytics opt-out browser add-on, or block cookies in your browser settings.

Affiliate links

Some "next steps" recommendations (for example domain registrars, hosting providers and online courses) may be affiliate links. If you buy through one, we may earn a commission at no extra cost to you. These partners may use cookies to attribute the referral, under their own privacy policies. We only recommend services that are relevant to developers, and affiliate links never change what the tools do.

Third-party images and links

README previews and the READMEs you generate load images from third-party services, such as img.shields.io (badges), capsule-render (banners), streak-stats, github-trophies, skillicons.dev, readme-typing-svg and komarev.com (view counter). When your browser, or GitHub, loads these images, those services receive normal request data such as an IP address. Links to Ko-fi, Buy Me a Coffee, X, LinkedIn and other sites are covered by those sites' own policies.

Children

This site is not directed at children under 13, and we don't knowingly collect personal information from them.

Your rights

Depending on where you live, you may have the right to access, correct or delete personal data, or to object to its processing. Because we don't keep accounts or a user database, most data we could hold is analytics data held by Google. You can manage it with the options above. For anything else, contact us and we'll respond within 30 days.

Changes to this policy

If we change how data is handled, we'll update this page and the "Last updated" date at the top.

Contact

Questions about privacy: prabathoff@gmail.com.