Privacy Policy
Last updated: August 7, 2026
Summary
QSTools is designed so tool inputs (tokens, passwords you generate, JSON, etc.) are processed in your browser. We do not need accounts for the MVP. This policy explains what may still be collected around hosting, ads, and analytics.
Tool processing
Decode, generate, and format features run client-side. Your tool payloads are not intentionally uploaded to QSTools servers for processing. You should still avoid pasting production secrets on shared or untrusted devices, because browser extensions or local malware can read page content.
Hosting and logs
Like most websites, our host/CDN may process standard request metadata (IP address, user agent, URL, approximate timing) for delivery, security, and abuse prevention. Retention depends on the provider configuration.
Advertising
We may show third-party ads (for example Google AdSense). Ad partners can use cookies or similar technologies to measure and, where allowed, personalize ads. Their policies apply to that processing. If we later enable personalized ads for visitors in the EU/EEA/UK, we may add a consent (CMP) flow.
Analytics and product analytics
We may enable optional analytics via environment configuration. Depending on what is turned on, this can include:
- Aggregate traffic tools such as Plausible, Umami, and/or Cloudflare Web Analytics (typically page views and basic referral data, without building advertising profiles from QSTools tool payloads).
- Microsoft Clarity (if enabled): heatmaps and session recordings to understand UI friction. Clarity may collect device/browser signals and interaction data. Sensitive tool fields (for example JWT/secret inputs and generated passwords) are marked for masking where possible, but you should still avoid pasting production secrets on shared devices.
Contact
Privacy questions: email [email protected] (Cloudflare Email Routing). We may update this policy; the “Last updated” date will change when we do.