watermark
remover
← Back to workspace

Legal

Privacy
Policy.

Last updated: August 21, 2026

This policy explains how Watermark Remover handles information when you use the workspace at claude-text-watermark-remover.com.

What we process

We process the text you submit to provide the selected cleanup, rewrite, or humanization result. The application also creates a browser visitor identifier so guests can use the daily free allowance without creating an account.

If you sign in with Google, we receive the basic account information provided through that sign-in flow, such as your name, email address, and Google account subject identifier.

Do not submit passwords, API keys, confidential client material, health information, or other sensitive personal information that you are not authorized to send to the processing providers described below.

Anonymous service analytics

We record hourly totals for page views and workspace actions: starting, completing, or failing a processing run, and requesting a text download. Each counter may include the page path, broad device category, referring website host, and restricted campaign tags.

This analytics collector does not set or read analytics cookies, local storage, a visitor identifier, an account identifier, IP address, browser user-agent, submitted text, or a per-person event history. The counters are not joined to accounts or the visitor identifier used for the guest allowance.

How we use information

We use submitted text to provide the selected processing result, operate the service, apply usage and abuse limits, investigate misuse, and maintain the service. We use the visitor identifier to count daily usage. The API stores an HMAC-derived value for this purpose rather than the raw visitor identifier.

We use anonymous aggregate analytics to understand page traffic, referral and campaign performance, workspace completion rates, and technical failures. We retain signed-in account identifiers, email addresses, and display names to administer accounts, report account totals, and apply administrator-issued Pro gifts.

Processing providers

When selected, Character cleanup is performed by the configured watermarks-remover service operated within our hosting environment. Humanize is performed locally in the FastAPI container by the TextHumanize package. When you select Semantic rewrite, the text produced by the preceding selected tool is sent to OpenAI through its Responses API. OpenAI processes that text under its applicable business terms and privacy commitments.

The application requests that OpenAI does not store Responses API application state by setting store=false. OpenAI states that its default abuse-monitoring logs may still contain prompts and responses and may be retained for up to 30 days, unless different approved data-retention controls apply to our OpenAI organization or longer retention is legally or operationally required.

Payments

Pro subscriptions use Stripe-hosted Checkout and Stripe's customer portal. Stripe processes payment card information under its own privacy policy. We store the Stripe customer identifier, subscription identifier, price identifier, subscription status, and webhook processing metadata needed to apply your plan; we do not store payment card details.

Storage and retention

The current service has no account history or text-library feature. Submitted text is sent to the processing services for the requested operation and is not intentionally stored as a user document in an application database. Masked access logs, backups, and security records may retain limited technical information for operational and security purposes.

Aggregate analytics counters are retained for 90 days. Signed-in account records and Pro-gift records are stored while needed to operate the account and subscription service. Usage counters are stored in Redis and expire on a daily or short rate-limit schedule. Billing status is stored in PostgreSQL while it is needed to administer an account. Stripe event identifiers used for replay protection are retained for approximately 90 days. Browser visitor identifiers may remain in an httpOnly cookie for up to one year unless you clear browser data.

Sharing

We use hosting and routing providers, OpenAI for Semantic rewrite, Google for sign-in, and Stripe for subscriptions and payment administration. Character cleanup and Humanize run within our hosting environment. Submitted text is shared only with the services required by the tools you select.

We do not sell submitted text or personal information.

Your choices

You can select Character cleanup, Humanize, or both without sending text to OpenAI; choose not to submit text; clear browser cookies to remove the local visitor identifier; manage a subscription through the Stripe customer portal; and contact us to request access, correction, or deletion of personal information where applicable.

Security

We use access controls, server-side secrets, encrypted HTTPS connections, private service networking, rate limits, and restricted service privileges appropriate to the current service. No internet service can represent absolute security.

Changes and contact

We may update this policy as the service changes. The updated date above indicates the latest revision. For privacy questions, contact [email protected].