Privacy
Last updated: June 2026
Overview
shieldcn is a free, open-source badge service. We collect minimal, anonymous analytics to understand how the site is used and anonymous diagnostic data to keep the service reliable. We do not store personal information, set cookies, or sell your data. We rely on a small number of privacy-respecting subprocessors (listed below), and configure each so that no identifying data is retained.
Analytics
We use OpenPanel, an open-source analytics tool, to collect anonymous usage data such as page views, referrer URLs, and browser type. Analytics requests are proxied through our own domain — no third-party scripts or cookies are involved. OpenPanel processes your IP address transiently to derive coarse, non-identifying information (such as country and device type) and does not store the raw IP.
Error monitoring
We use Sentry to capture errors and performance diagnostics so we can fix issues quickly. Sentry only receives data when something goes wrong — there is no per-visit tracking. Error reports include technical details such as the request path, a stack trace, and browser or runtime version. We explicitly disable Sentry's collection of personal data, so error events do not store IP addresses, cookies, or request bodies. No cookies are set.
No cookies
shieldcn does not set any cookies. We do not use fingerprinting or any other cross-session tracking mechanism.
Badge requests
When a badge is embedded in a README or docs page, your browser makes an image request to our server. We log standard HTTP request data (URL path, referrer, timestamp) for caching and rate limiting. Your IP address is processed transiently to serve the request and apply rate limits, but is not stored or used to identify you.
Token pool
Users who donate a GitHub token via the token pool authorize a read-only OAuth scope with zero permissions. Tokens are encrypted at rest and used solely to make GitHub API requests for badge data. You can revoke access at any time from your GitHub settings.
Subprocessors
We share data with the following third-party services, each chosen for its privacy-respecting design:
Opt out
To opt out of analytics, visit any page with ?no-track appended to the URL (e.g. shieldcn.dev/?no-track). This sets a localStorage flag that permanently disables the analytics script in that browser.
Contact
Questions? Open an issue on GitHub or reach out at github@fwdtojustin.com.