Privacy
What CSS Radar handles.
CSS Radar audits public pages without an account. This page explains what leaves your browser, who can open a report, and when CSS Radar's temporary records expire.
Last updated August 3, 2026
When you start an audit
Your browser sends the submitted public URL to api.cssradar.com. The audit service opens that
URL in Chrome, inspects the rendered page and relevant HTML, CSS, and JavaScript, observes safe
interactions, and builds the report. It does not sign in or try to bypass access controls.
Do not submit private URLs, signed links, or URLs containing passwords, access tokens, or other secrets.
What is stored
- Audit status: the submitted URL, audit status, timestamps, and technical result references are stored in Google Cloud Firestore. This record is scheduled to expire 31 days after the audit finishes, fails, or is canceled.
- Report file: a completed report is stored as an HTML file in Google Cloud Storage. It is scheduled for automatic deletion after 30 days.
- Daily limit: CSS Radar derives a pseudonymous identifier from the visitor's IP address with a keyed hash. The raw IP address is not stored in the application's rate-limit record. That record is scheduled to expire within 48 hours.
The 30-day deletion rule covers the generated report file. Standard infrastructure logs kept by the service providers below are separate and follow each provider's own retention terms.
Who can open a report
Anyone with the report URL can open it without an account. CSS Radar does not list reports on the site or include them in its sitemap, but the link is not an access-control mechanism. Do not share it with people who should not see the report.
To request deletion before the automatic deadline, email hey@theosoti.com and include the report URL.
What cancellation does
Canceling asks the running audit to stop. If cancellation succeeds before publication, no report file is created. If the report has already finished, canceling does not delete it and the normal 30-day deletion schedule still applies.
Landing-page analytics
The public landing page loads Fairlytics to count visits and understand which pages are used. According to Fairlytics, its hosted service uses no cookies. It receives the current CSS Radar page URL, the referrer, and request data such as the IP address, browser, and operating system. Fairlytics says it uses the IP address to derive approximate location and a daily hashed visitor identifier, then discards the raw IP.
The URL typed into the audit form is not sent to Fairlytics as an analytics event, and generated reports do not load Fairlytics. Fairlytics stores its audience records separately. Its public documentation does not state a fixed retention period, so the 30-day report rule does not cover those analytics records.
Read Fairlytics' data explanation and terms.
Service providers and contact
- Netlify serves the public website.
- Google Cloud runs the audit service and stores temporary audit records and reports.
- Fairlytics provides the landing-page audience measurement described above.
CSS Radar is operated by Theo Soti. For a privacy question or an early report-deletion request, email hey@theosoti.com.