Privacy Policy

1. Text you translate

Your input, selected tone and our instructions are sent through our server to the DeepSeek API to generate a response. Our application does not save your input or generated text in its database or your account history. Credit activity records do not include translation content. Do not submit passwords, payment details, confidential information or personal information you are not authorized to share.

DeepSeek processes API requests as a separate provider under its applicable terms and policies. Our decision not to store translation text does not mean that every provider has the same retention practices.

2. Google sign-in and account data

When you sign in with Google, we store your Google account identifier, verified email and display name to identify your account and link your credits, orders and activity. We do not receive or store your Google password. A signed HttpOnly session cookie normally keeps you signed in for up to 30 days. Temporary sign-in security cookies expire after 10 minutes or are cleared when the callback completes.

Google sign-in handles authentication separately from AI generation. Translation requests are sent to DeepSeek as described above. Google Analytics, when configured, is described in the hosting and analytics section below.

Signing out removes the session cookie from the current browser. It does not delete your account or transaction records.

3. Free allowance and credit records

We use a signed, HttpOnly visitor cookie with a normal lifetime of one year to recognize this browser for the five-use free trial. Server-side records keep a hash of the random visitor identifier, usage timestamps and reservation status. Signing in links eligible anonymous usage to your Google account and preserves the remaining allowance; it does not grant another five uses. A browser-account association keeps the allowance from resetting at sign-out. A separate keyed hash of the Cloudflare-provided IP is used only for an hourly abuse limit, not as the visitor identity. The application does not store the raw IP in these usage tables. Clearing or blocking cookies can affect visitor recognition, and we cannot identify a person reliably across unrelated anonymous browsers.

We store credit balances and records of purchases, generation reservations, completed usage, canceled reservations and refund adjustments to show account activity and reconcile credits.

4. Payments

Waffo provides hosted checkout. We send your email, the product, price and order identifier to create checkout. We store order amounts, currency, credit quantities, provider payment and refund references, status and timestamps. Our application does not collect or store full card numbers or card security codes. Information entered at checkout is processed by Waffo and its payment partners under their applicable notices.

5. Hosting, analytics and browser storage

Cloudflare hosts the website and API; Neon PostgreSQL stores account and transaction records. Infrastructure providers may process network and diagnostic information, including IP addresses, to deliver and protect their services. Providers may process information outside your country.

When configured, Google Analytics and Microsoft Clarity measure visits and interactions using cookies or similar technologies. The information can include device, network and browsing identifiers and should not be assumed to be fully anonymous. Translation panels and account information are marked for masking in Clarity. We do not intentionally send translation content as analytics event data.

Browser session storage remembers a checkout retry identifier. Local storage temporarily remembers a pending order identifier to follow payment confirmation across pages or tabs. Blocking or clearing cookies and storage can affect sign-in, analytics or checkout recovery, but does not erase server-side account or transaction records.

6. Retention and requests

Account, credit and transaction information is retained as needed to operate the service, reconcile payments, handle disputes and meet applicable recordkeeping obligations. You may contact us to request access, correction or deletion of information associated with your account. We may need to verify your identity, and some transaction records may need to be retained where applicable requirements allow or require it.

7. Contact and updates

For privacy questions or account-data requests, contact the support email below. Do not send passwords or card details. The revision date on this page will be updated when this policy changes.

Provider privacy information