Privacy Policy

We process the text you submit to provide the cleaning result. The submitted text and cleaned output are not saved in our application database. Request records store word, character, byte, and model-token counts; processing type and status; provider-reported cost and request identifiers; credit activity; errors; and processing times so we can operate and analyze the service.

Text is sent to the configured model provider to perform the rewrite. If the external watermarks-remover service is enabled, text is also sent to that service for deterministic Unicode cleaning. Their processing is governed by the deployment and provider agreements configured by the operator.

When you sign in, we receive the profile information needed for authentication, such as your email address, name, profile image, provider identifier, and session details. Magic-link emails are delivered through the configured email provider.

We use this information to secure your account, show your balance, prevent abuse, and provide support.

Stripe hosts checkout and processes payment details. Simple Unmark does not receive or store your complete card number. We store the Stripe Checkout session identifier, pack, amount, currency, credit quantity, account identifier, and purchase status to fulfill and reconcile purchases.

For guests, we set a signed, essential browser cookie containing a random identifier. The cookie is not available to browser scripts and is used to count free cleans and prevent concurrent abuse. It expires after 30 days.

We use the open-source FingerprintJS library to derive a browser identifier and a coarser device-similarity identifier from browser and device characteristics. The server also derives a request signature from browser headers and, when supplied by a trusted reverse proxy, a TLS fingerprint. Before storage, every identifier is transformed with a server-secret HMAC; raw fingerprint components and raw identifiers are not stored in cleaning request records.

We separately derive a one-way keyed hash from a shortened network prefix (IPv4 /24 or IPv6 /64) to apply shared-network rate limits. We do not store the raw IP address in cleaning request records. Fingerprint matches may be associated with signed-in accounts to identify possible duplicate promotional usage for manual review. These pseudonymous identifiers and request records are retained as needed to operate and protect the service.

When our trusted proxy or CDN supplies it, we process a two-letter country code derived from the request network location. We store this code on account and cleaning records for service analysis, abuse prevention, and operational context. It is country-level information, not precise location data.

Application errors, registrations, purchases, and completed cleanings may generate operational notifications through Telegram. These notifications can include an account email or pseudonymous guest identifier, account or request ID, country code, usage counts, credit and token totals, provider cost, duration, and error details. They do not include submitted text or cleaned output.

We retain account, usage, and purchase records for as long as needed to operate the service, meet legal obligations, resolve disputes, and prevent abuse. No system is perfectly secure, but access should be limited and secrets kept in server-side environment variables.

Depending on your location, you may have rights to access, correct, export, restrict, or delete personal data. Contact [email protected]. We may need to verify your identity and retain legally required transaction records.

Service providers may process information in countries other than your own. Appropriate contractual and legal safeguards should be used where required. We may update this policy as the service evolves; the date above shows the current version.