Privacy Policy

What stays on your device

Everything you put into a tool — JSON, JWT tokens, passwords, files you upload to hash, QR code contents, contact details, anything. The tool’s logic runs entirely as JavaScript in your browser. You can verify this in your browser’s DevTools (open Network tab and use any tool — you won’t see your data leave).

Some tools save your settings (selected tab, color choices, etc.) in localStorage on your device so the page picks up where you left off. That data also never leaves your browser.

What is collected

The site uses Google Analytics (via Firebase) to count how many people visit each tool. The events recorded are page-view pings — which URL you opened, the browser type, and approximate country. The events do not contain any of the content you put into the tools.

Analytics helps decide which tools to prioritize next. If you block analytics with a content blocker, every tool still works normally.

Feedback and tool suggestions

Two surfaces on the site let you intentionally send us a message: the “Was this helpful?” widget at the bottom of every tool, and the Suggest a tool form. When you submit either one, the text you typed gets written to a Cloud Firestore database (Google Cloud) along with the slug of the tool you were on and a server timestamp.

We don’t log your IP, user agent, or anything beyond what you typed. Email on the suggestion form is optional and used only to let you know when the tool you requested ships — never resold, never added to a marketing list.

Please don’t paste confidential information (production data, internal docs, secrets) into the feedback or suggestion forms. Treat them as you would a public GitHub issue.

Legal basis:we process the submissions you send on the basis of your explicit consent — pressing “Send suggestion” or a thumbs button is the consent.

Retention: suggestions and feedback are kept indefinitely by default, since they inform the long-running tool roadmap. You can ask for your submission to be deleted at any time using the contact route below.

Your rights and how to reach us

snaptxt is operated by Hanuman Singh. For any privacy-related request — questions, data access, deletion, or to lodge a concern — write to privacy@snaptxt.app.

You have the following rights regarding any personal data we hold about you (which, for snaptxt, would only be the contents of a feedback or suggestion submission you sent us):

• Access — ask for a copy of what we have.
• Correction— ask us to fix something that’s wrong.
• Deletion — ask us to remove your submission.
• Portability— ask for your data in a machine-readable format (we’ll send JSON).
• Withdraw consent— applies to any future processing; we can’t un-collect what was already submitted, but we can delete it.

To exercise any of these, email the address above with the approximate date and content of your submission so we can find it. We’ll respond within 30 days. There’s no verification overhead because we don’t collect identifying information — your description of the submission is enough.

If you’re in the EU and unhappy with how we handle a request, you have the right to lodge a complaint with your local data-protection authority. For users in India, the same right applies under the Digital Personal Data Protection Act.

Where your data is processed

All of the Google services listed in the next section (Firestore, Analytics, Performance Monitoring, App Check) run on Google Cloud’s global infrastructure. Submissions and analytics events may be processed in data centers outside your home country, including in the United States. Google operates under standard contractual clauses for EU data transfers; full details are in Google’s privacy policy.

Bot protection on the suggestion form

The /suggest-a-tool/form runs Google reCAPTCHA v3 via Firebase App Check to deter bot submissions. reCAPTCHA evaluates browser signals — mouse movement, timing, interaction patterns — and returns a score that Firebase uses to decide whether to accept the write. The check is invisible; you don’t see a CAPTCHA challenge. Standard Google Privacy Policy applies to those reCAPTCHA signals.

Cookies

No tracking cookies. Google Analytics uses a first-party cookie for session deduplication; no third-party advertising cookies are set. Google reCAPTCHA may set its own first-party cookies on pages where it runs (currently the suggestion form).

Third-party services

The site is hosted on Firebase Hosting (Google). Page requests therefore hit Google’s servers — that’s how any website on Firebase works. Static assets are served from Google’s CDN. No content you enter into a tool is sent with those requests.

Beyond Hosting, the site uses these Google services: Firebase Analytics (page-view counts), Firebase Performance Monitoring (page load timings), Cloud Firestore (storage for the feedback and suggestion submissions described above), and Firebase App Check / reCAPTCHA v3 (bot protection on the suggestion form).

Changes to this policy

snaptxt is actively developed — new tools ship, new third-party services get added, the data we receive can shift over time. We’ll keep this page current. Specifically:

• The “Last updated” date at the bottom is bumped on every change, even small wording fixes.
• Material changes— anything that affects what we collect, who we share it with, or how it’s used — are highlighted at the top of this page for at least 30 days after the change.
• We don’t collect contact details proactively, so we can’t email you about updates. If you submitted an email through the suggestion form and a change directly affects suggestion handling, we’ll send a one-off note.
• Continued use of snaptxt after an update means you accept the revised policy. If you don’t agree with a change, stop using the site — there’s no account to delete or data to remove, since nothing you put into a tool was ever sent anywhere.

Contact

Privacy questions go to privacy@snaptxt.app. For anything else, the general inbox is hello@snaptxt.app.