This Privacy Policy explains what personal data Readme Widgets collects when you use the website at readmewidgets.dev and its mirrors, the widgets it generates, the dashboard and the VS Code extension (the “Service”), how we use and share it, and the rights you have. It is written to meet the EU and UK General Data Protection Regulation (GDPR), U.S. federal law including the Children’s Online Privacy Protection Act (COPPA), and U.S. state privacy laws such as the California Consumer Privacy Act (CCPA).
In short: we collect only what the widgets you turn on need, we don’t sell or rent your data, we don’t use advertising or analytics trackers, and you can disconnect services or delete everything at any time.
1. Who We Are
The Service is operated by CJ Artz, who is the “controller” of your personal data under the GDPR and the “business” under U.S. state privacy laws. You can reach us about anything in this policy at [email protected].
2. Information We Collect
Information you give us or connect
- GitHub sign-in: your GitHub username, display name, avatar and email address. We don’t receive your GitHub password.
- Spotify: the developer credentials you create and enter, and a refresh token, used to read what you’re playing and your top tracks and artists.
- Steam: your Steam ID and the API key you enter, used to read the game you’re playing and your most played games.
- VS Code extension: while it’s connected, the name and language of the file you have open, the URL of its Git repository, whether you’re idle, and from that, how long you code in each language each day. It doesn’t send your code. The extension is open source, so you can check exactly what it sends in its source code on GitHub.
- Widget settings and content: the options you save, such as themes, banner and typing text, and the city you choose for the weather widget.
- Private repositories (optional): see section 5.
- Messages: anything you send us, such as a privacy request.
Information we get from public sources
- Public GitHub data for the GitHub cards: stars, commits, pull requests, issues, reviews, followers, public repositories and the languages in them, and details of repositories you choose to show.
Information collected automatically
- Server and security logs: IP address, browser or client type, the page or image requested, and the time, used to run and protect the Service.
- Profile view counter: when GitHub loads your views widget, a short, one-way hash of the requesting address is kept for 15 seconds so one visit isn’t counted many times. Only the total count is stored.
- Cookies: only those needed to keep you signed in and secure; see section 7.
We don’t collect sensitive personal data (such as health, biometric or precise location data) and ask you not to put any in widget text.
3. How We Use It and Our Legal Bases
We use personal data only for these purposes, each with a legal basis under the GDPR:
| Purpose | Legal basis (GDPR article 6) |
|---|---|
| Creating your account, signing you in, and drawing the widgets you set up | Performance of our contract with you (the Terms) |
| Reading data from Spotify, Steam, VS Code and GitHub for the widgets you turn on | Performance of our contract with you |
| Reading private repository languages, if you connect them | Your consent, which you can withdraw at any time by disconnecting |
| Caching data so widgets load quickly and survive outages | Our legitimate interest in a fast, reliable service |
| Keeping logs, preventing abuse and securing the Service | Our legitimate interest in protecting the Service and its users |
| Answering your messages and requests | Performance of our contract, or our legitimate interest in responding |
| Complying with law and responding to lawful requests | Compliance with a legal obligation |
We don’t use your data for advertising, sell it, build marketing profiles, or make decisions about you based solely on automated processing that have legal or similarly significant effects.
4. What Your Widgets Make Public
Widgets are images anyone with the link can view, and you usually place them on public pages. Whatever a widget shows, such as the song you’re playing, the file and repository open in VS Code, the games you play, your weather city, your coding time or GitHub statistics, becomes visible to anyone who sees it. Choose what to show in the dashboard, and only embed widgets with information you’re comfortable making public. Copies may persist in caches (including GitHub’s image proxy), screenshots and archives we don’t control.
Embedding isn’t what makes a widget public. Every widget you set up has its own link, such as readmewidgets.dev/your-username/spotify, that follows a predictable pattern. Anyone who visits that link can see the widget, even if you never added it to a README or website. To stop a widget from showing information, disconnect the service it uses (or turn off what it shows) in the dashboard, or delete your account.
5. Optional Private Repository Access
If you choose to connect private repositories for the Top Languages card, GitHub gives us an access token for your repositories. GitHub describes this access as read and write, because it offers no read-only option for private repositories to apps like this one.
- We use it only to read how much code of each language is in the repositories you own.
- We never write, change or delete anything in your repositories or account.
- We never store or display your code, private repository names or other contents. Only per-language totals are kept, and they appear only on your languages card.
- The token is stored encrypted and used only to update your languages card.
- You can withdraw consent at any time by disconnecting in the Top Languages editor, which deletes the token and removes the authorization from your GitHub account, or by revoking it in your GitHub settings.
This is optional and not recommended for accounts holding sensitive private code. See the Terms of Service.
We don’t sell your personal data, and we don’t “share” it for cross-context behavioral advertising as those terms are defined under California law. We disclose it only:
- To service providers that run the Service for us under obligations to protect it: our server hosting provider and Cloudflare, which routes and protects traffic to the site.
- To the services you connect, when we request your data from them: GitHub, Spotify and Steam receive requests made with the access you granted.
- To services that help draw widgets: Open-Meteo receives the coordinates of the city you choose for the weather widget, and Google Fonts receives the text of your typing widget to load its font. Neither receives your name or account details.
- For legal reasons, when required by law or a valid legal process, or to protect the rights, safety or property of our users, the public or us.
- In a business transfer, such as a merger or sale of the Service, with notice to you and this policy continuing to apply.
- With your direction, such as when you embed a widget publicly.
We use only cookies that are strictly necessary for the Service:
| Cookie | Purpose | Duration |
|---|---|---|
| Session cookie | Keeps you signed in to the dashboard | Until you sign out, up to 30 days |
| CSRF and callback cookies | Protect sign-in from forgery and return you to the right page | Session |
| gh_private_state | Protects the private repository connection from forgery | 10 minutes |
We don’t use analytics, advertising or tracking cookies, so no consent banner is needed, and we treat Global Privacy Control signals as an opt-out of any sale or sharing, which we don’t do anyway. Widget images don’t set cookies.
8. How Long We Keep It
We keep personal data only as long as needed for the purposes above:
| Data | How long |
|---|---|
| Account, settings and connected credentials | Until you delete them or your account |
| VS Code current file status | 10 minutes after the last update |
| VS Code coding time | About 13 months, then deleted automatically |
| Cached widget data (GitHub, Spotify, Steam, weather) | Minutes to a few hours, with a last good copy kept up to 7 days |
| Private repository language totals | Up to 7 days after they were read, or until you disconnect |
| Profile view counter address hash | 15 seconds |
| Server and security logs | A limited period, normally no more than 30 days, unless needed to investigate abuse |
When you delete your account, we delete your account record, settings, connected credentials and tokens, and coding time, and revoke private repository access at GitHub. Cached copies expire within the periods above, and backups, if any, are overwritten in the normal course.
9. Security
We protect personal data with measures appropriate to the risk, including encryption in transit (HTTPS), encryption of private repository tokens at rest, access limited to what each part of the Service needs, and keeping software up to date. No method of transmission or storage is completely secure, so we can’t guarantee absolute security. If a breach affects your personal data, we will notify you and the authorities as the law requires.
10. International Transfers
Our servers are located in the United States, and the services we work with may process data in other countries. If you’re in the European Economic Area, the United Kingdom or Switzerland, your data is transferred to countries that may not have the same level of data protection. Where required, we rely on adequacy decisions (such as the EU-U.S. Data Privacy Framework for certified providers) or the European Commission’s Standard Contractual Clauses and their UK and Swiss equivalents. Transfers needed to perform our contract with you, such as fetching your data from a service you connected, may also rely on that necessity.
11. Your Rights in the EEA, UK and Switzerland
If the GDPR or UK GDPR applies to you, you have the right to:
- Access the personal data we hold about you and get a copy;
- Rectify inaccurate or incomplete data;
- Erase your data (you can delete your account in the dashboard);
- Restrict how we process it in certain cases;
- Data portability: receive data you gave us in a structured, machine-readable format;
- Object to processing based on our legitimate interests;
- Withdraw consent at any time, such as by disconnecting private repositories, without affecting processing before you withdrew; and
- Complain to your local data protection authority, or in the UK to the Information Commissioner’s Office. We’d appreciate the chance to address your concern first.
Send requests to [email protected]. We’ll answer within one month, which may be extended by two more months for complex requests, and may need to confirm your identity, usually by asking you to sign in with the GitHub account concerned. Requests are free unless they are manifestly unfounded or excessive.
12. Your Rights in the United States
Depending on your state (including California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon and others with consumer privacy laws), you may have the right to:
- know what personal data we collect, use and disclose, and get a copy of it;
- correct inaccurate personal data;
- delete personal data we collected from you;
- opt out of the sale of personal data, sharing for cross-context behavioral advertising, targeted advertising and profiling. We do none of these;
- limit the use of sensitive personal information. We don’t collect any for inferring characteristics about you; and
- not be discriminated against for exercising these rights.
In the past 12 months we have collected these categories of personal information, as described in section 2: identifiers (such as username, email and IP address); internet or other electronic network activity (such as logs and VS Code activity); and, if you provide them, account credentials for connected services. We collected them for the purposes in section 3 and disclosed them only as described in section 6. We have not sold or shared personal information.
To make a request, email [email protected]. You may use an authorized agent, in which case we may ask for proof of their authority and to verify your identity. If we deny your request, you may appeal by replying to our decision, and if your appeal is denied, you may contact your state attorney general. California residents may also ask about disclosures to third parties for direct marketing under California’s “Shine the Light” law; we make none.
13. Children’s Privacy
The Service is not directed to children under 13, and we don’t knowingly collect personal data from them. In the EEA, UK and Switzerland, people under 16 (or the lower age their country sets for consent to online services) may use the Service only with a parent or guardian’s consent. If you believe a child has given us personal data, contact [email protected], and we will delete it and the account.
14. Changes to This Policy
We may update this policy as the Service changes or the law requires. We’ll update the “Last updated” date above and, for material changes, notify you in the dashboard or by other reasonable means before they take effect. Where the law requires your consent to a change, we’ll ask for it.
15. Contact Us
For questions, requests or complaints about privacy, contact CJ Artz at [email protected].
