Privacy Policy
How CSR.plus handles your data — and why your private keys stay on your device.
Data processed in your browser
All certificate generation, decoding and cryptographic computations in the browser tools are performed on your device. The one exception is /api/generate, which generates the key pair on our server to return it to your script over TLS; that key is not persisted, but it does transit our infrastructure.
Information we collect
- No accounts: CSR.plus does not require registration and does not collect names, emails or payment information.
- Google Analytics: We use Google Analytics to understand aggregate usage (pages visited, approximate location, device type). This data is collected by Google under its own privacy policy and cannot be used to identify you personally.
- Affiliate links: Some outbound links, such as the SSL Monitor link and the Namecheap links on our SSL price comparison page, are affiliate links. If you click them and make a purchase, we may earn a commission at no extra cost to you.
- Server logs: Standard web server logs (IP address, user agent, requested URL) are retained temporarily for security and operational purposes.
Cookies
We use essential cookies for preferences such as theme and language. Google Analytics sets its own cookies (such as _ga) to measure usage. Advertising partners may set advertising or tracking cookies when you interact with ads or sponsored content.
Who is responsible for your data
CSR.plus is operated by an individual developer under the name CSR.plus — there is no registered company behind it. For the purposes of the GDPR and comparable laws, the data controller is the CSR.plus operator, reachable at [email protected]. We do not have a Data Protection Officer; privacy requests go to the same address and are answered within 30 days.
What our server-side tools receive
Most tools run entirely in your browser. A few need the network: /check, /bulk, /ssl-check, /dns-propagation, /acme-preflight, /revocation, /caa, /ct and every /api endpoint receive the domain name you submit, plus your IP address and user agent. Domain names are queried live and are not written to a database. Request logs (IP, user agent, path, timestamp, status) are kept for 30 days for abuse prevention and troubleshooting, then deleted. API-generated key pairs are held in memory only and are never written to disk.
Cookies and consent
Strictly necessary cookies keep your theme and language preference; they need no consent. Analytics (Google Analytics 4) runs only after you accept it in the consent banner, and we use it in aggregate form to understand which tools are used. Advertising and affiliate partners may set their own cookies when you click a partner link; those clicks are also counted in our aggregate click statistics. You can change or withdraw consent at any time from the cookie settings link in the footer, and withdrawing it stops analytics immediately.
How long we keep data
- Server request logs: 30 days, then deleted.
- Analytics events: 14 months (GA4 retention setting), aggregated and never linked to an identity.
- Affiliate click counters: aggregated totals only, no personal data.
- Tool inputs (PEM, CSR, keys): never stored server-side; browser tools keep them in memory until you close the tab.
Your rights under GDPR
If you are in the EEA, the UK or Switzerland you may request access to your personal data, correction of inaccurate data, erasure, restriction of processing and portability, and you may object to processing based on legitimate interests. Write to [email protected] and we will respond within 30 days. You also have the right to lodge a complaint with your local supervisory authority.
International transfers
Our servers are located in the United States, so data you submit to the server-side tools is processed there. Analytics and other providers may process data in the United States under standard contractual clauses. We do not sell personal data.
Last updated
This policy was last updated on 2026-11-08. Material changes are announced on this page; the date above always reflects the current version.
Contact
For any privacy-related questions, contact [email protected].