Privacy Policy

Text processed by the detector

The detector performs the Unicode analysis and cleaning in your browser. To enforce the free and paid usage limits, the application server receives the submitted text for the individual authorization request, checks its character count, and does not store or analyze the text. The clean result remains in the page until you close or refresh it.

Uploaded files and images

Supported text files, DOCX files, and PDF text layers are read in your browser and converted into text for the detector. Images are processed in your browser with OCR to extract visible text; the original image is not uploaded to our server or stored by this application. OCR cannot recover invisible Unicode characters that are not represented in the image pixels. When you click Detect after importing a file or image, the extracted text is included in the same one-time quota authorization request described above and is not stored by the application.

Daily usage records

To enforce the free limit, the application server stores a small daily usage record keyed to an anonymous browser fingerprint or your signed-in account. The record contains a count and date, not the text you pasted. Anonymous visitors receive three checks per day with a 1,000-character limit; signed-in Free accounts receive 10 checks per day with a 3,000-character limit.

Technical request data

Our hosting provider may process ordinary technical request data needed to deliver the website, such as an IP address, browser information, request time, requested URL, and security or error records. These records are handled by the hosting and infrastructure providers under their applicable terms and are not used by the detector to read the text in your browser textarea.

Cookies, analytics, and advertising

Google Analytics 4 and Microsoft Clarity measure page visits and help us understand how visitors use the site. These services may process technical and interaction data such as browser and device details, page URLs, and click or scroll activity. The detector text fields, imported file names, highlighted source text, and cleaned-text output are marked for Clarity masking. The detector does not send pasted or imported text to Google Analytics 4. See Google's Privacy Policy and Microsoft's Privacy Statement for how they process data.

Clipboard access

The Copy Clean Text button only attempts to write the clean result to your clipboard after you activate it. The site does not read your clipboard in the background.

Support messages

If you email support@hiddencharacterdetector.app, we receive the information you choose to include, such as your email address, message, browser details, or a description of a problem. Do not send passwords, payment details, or private text unless support specifically asks for a safe, minimal example.

Accounts, orders, and paid features

When you sign in with Google or GitHub, we process the account identity information supplied by that provider, such as your email address, provider identifier, display name, and profile information made available by the provider. When you purchase a plan, Waffo handles checkout and we store the account identity, order status, product, payment-provider reference, subscription state, and entitlement information needed to provide credits and subscriptions. We do not receive or store your full payment-card number. The pasted text used by the detector is not sent to Waffo.

Access and correction requests

You may ask what personal data we hold about your account or ask us to correct inaccurate account information by emailing support@hiddencharacterdetector.app. Send the request from the email associated with your account when possible, identify the information you want to access or correct, and include an order number if the request concerns a purchase. We may verify your identity before disclosing or changing account data, and we will not ask you to send a password or full payment-card number.

Deletion and account closure

You may ask us to delete your account and associated application data by contacting support@hiddencharacterdetector.app. The current account-deletion process requires an authenticated account, confirmation of the account email address, and the confirmation phrase DELETE. We may ask for those confirmations to prevent an unauthorized deletion request.

If the account has an active recurring subscription, it must be canceled before deletion can finish. The application attempts to cancel active subscriptions; if a cancellation cannot be completed, the account is not deleted and support will explain the next step. After a successful deletion, the application removes the account access, login tickets, API keys, credits, detector and extension usage records, subscription records, and orders associated with the account, and disassociates applicable feedback records.

Retention after deletion

Some limited records may remain where necessary for security, fraud prevention, legal compliance, dispute handling, or payment-provider requirements. In particular, the application may retain an irreversible identity fingerprint and account-revocation record so deleted credentials cannot immediately reopen the deleted account and previously issued sessions can be invalidated. Waffo and other infrastructure providers may retain transaction or technical records under their own policies and legal obligations. These retained records are not used to restore the deleted account.

Your choices

You can stop using the tool, edit or clear text in your browser, clear local browser storage, cancel a subscription from the account area, avoid submitting sensitive text, and contact us with privacy questions or data requests. We may need enough information to understand and respond to a request, but we will not ask for your password.