Privacy Policy
Last updated: 2026-09-06
This Privacy Policy explains how CSS to Tailwind (“we,” “us,” or “the site”) handles information when you use csstotailwind.com. Related pages: Terms of Use and Disclaimer.
Short version
CSS→Tailwind conversion runs in your browser. Your pasted CSS is not uploaded to a conversion API for mapping. The site does load third-party analytics scripts for traffic measurement. Contact-form fields are sent only when a form endpoint is configured.
Who we are
CSS to Tailwind is a free, static developer utility and documentation site. We provide a converter, related tools, and guides. We do not require an account to convert CSS.
Browser-side conversion
When you use the converter or most secondary tools, input is processed locally in your browser after page assets load. We do not operate a conversion server that receives your CSS snippets for mapping.
- Pasted CSS / tool input is not uploaded for conversion.
- We cannot recover snippets you paste into the editors.
- You can typically keep using conversion features after the page has loaded even if the network drops (asset caching and browser support permitting).
Local storage and cookies we control
The default converter does not write your CSS input to localStorage or to a remote conversion store. We do not use first-party cookies for accounts or login (there are no accounts).
Your browser may still keep normal technical data (cache, session history). Clearing site data removes locally stored preferences if any tool later adds them.
Analytics and third-party scripts
This site currently loads:
- Google Analytics (gtag.js) — to measure page views and basic usage. Google may set cookies and process data such as IP address, device/browser information, and pages visited under Google’s policies.
- Ahrefs Analytics — for site traffic and SEO-related measurement.
These scripts are for site analytics. They are separate from CSS conversion: analytics requests do not include the CSS you paste into the converter. For how Google processes data, see Google’s privacy documentation. You can also use browser controls, extensions, or Google’s ad settings where available to limit ads/analytics cookies.
Hosting and server logs
The static site is served by a host (for example Vercel or similar). Hosts typically keep standard access logs (IP address, URL, timestamp, user-agent) for security, reliability, and traffic. Log retention follows the host’s policies.
Contact form
If you submit the contact form, fields such as name, email, subject, and message are validated in the browser. Delivery happens only when a form endpoint (for example Formspree or a similar provider) is configured. That provider then processes the submission under its own privacy policy. Do not send passwords or highly sensitive secrets through the form.
Clipboard
Copy actions use the browser Clipboard API or a local fallback. This site does not transmit clipboard contents to our servers as part of conversion.
Children’s privacy
The Service is aimed at developers and is not directed at children under 13 (or the equivalent minimum age in your region). We do not knowingly collect personal information from children.
Your choices
- Stop using the site or clear site data in your browser.
- Block or limit third-party scripts/cookies with browser settings or extensions.
- Avoid submitting the contact form if you do not want those fields processed by a form provider.
Because conversion input is not stored by us, there is usually no conversion snippet on our servers to access or delete. For analytics or form-provider data, use the controls offered by those providers or contact us via the form about a specific submission when delivery is enabled.
Changes to this policy
We may update this Privacy Policy by posting a new version on this page with an updated “Last updated” date. Continued use after changes means you accept the revised policy.
Contact
Privacy questions: use the contact form. For who runs the site, see About.