Sleek Translator Privacy Policy

Updated: 6 October 2026. This policy applies to Sleek Translator at sleektranslator.com.

Google sign-in

Google sign-in is optional and unlocks an account-based demo allowance. Through Firebase Authentication we receive your Google account identifier, email address and verification status, display name, and profile photo when provided by Google. Firebase stores your authentication profile and account timestamps. The app uses your identity to sign you in, verify eligibility, enforce translation limits across devices, and display your account email. Name and photo may be present in the authentication profile but are not needed to translate text.

We request basic sign-in information only (openid, email, profile). We do not access Gmail, Google Drive, contacts, calendars, or other Google Workspace content. We do not send your Google account profile to translation models, sell it, use it for advertising, or use it to train AI models.

Translation text and results

When using demo mode, your source text and translation settings pass through our server and are sent to Google Gemini to generate a translation. The response is returned to your browser. The demo quota database does not store source text or translations. Google processes these requests under its Gemini API terms; on its unpaid service, submitted text and responses may be used to improve Google products. Do not submit confidential or sensitive information unless the relevant provider's terms meet your needs.

When using your own API key, the published website sends requests directly from your browser to the AI provider you select. That provider receives the text, settings, and key needed to authenticate the request and applies its own processing and retention policies.

Local chat history and API keys

Chat history is stored in IndexedDB in your browser. Preferences and drafts use browser storage. Signing in does not upload or synchronize chat history between devices. You can clear a conversation's history, delete a conversation, or remove site data in your browser.

Your personal provider keys are kept in page memory or stored in your browser depending on the Store keys setting. The website does not upload them to the quota database. You can remove saved keys in settings. Firebase also stores browser sign-in credentials to keep you signed in; signing out clears the app's active sign-in session.

Usage limits and abuse prevention

Our server verifies Firebase sign-in tokens and reads account creation and revocation information. Firestore stores hashed account or network identifiers, daily and monthly character/request counters, reservation identifiers, and timestamps. Network addresses are processed to apply guest and network limits; quota identifiers are generated using a keyed hash rather than storing plain IP addresses. Cloudflare Turnstile processes technical browser and network information to check whether requests are legitimate. Cookies, incognito mode, or a different device do not reset account allowances.

Analytics and hosting

Google Analytics 4 collects technical and usage information such as page views, device/browser information, cookies or similar identifiers, and approximate location. Google processes network information when receiving analytics requests. We do not deliberately include translation text, API keys, account email, or Google profile details in analytics events. Advertising personalization and Google Signals are disabled in our tag configuration.

Vercel hosts the website and API and processes request metadata such as network addresses, request times, paths, and error information for delivery, operations, and security. We do not intentionally log translation request bodies or personal API keys.

Who receives data

Google/Firebase provides authentication and quota storage; Google Gemini processes demo translations; Google Analytics measures website usage; Vercel hosts the service; Cloudflare provides abuse protection. Your chosen AI provider processes requests made with your personal key. Data is shared for these functions, not for selling Google account information or targeted advertising. Provider infrastructure may process data outside your country.

Read the Google Privacy Policy, Gemini API terms, Cloudflare Privacy Policy, and Vercel Privacy Policy.

Protection, retention, and deletion

Requests to the published service use HTTPS. Database rules deny direct browser access to quota records; access is through the authenticated server. Server credentials are stored as deployment secrets. These protections reduce risk but cannot guarantee that every browser, device, or third-party service is free of vulnerabilities.

Local history, preferences, and saved keys remain until you clear them. Firebase authentication profiles remain until account deletion. Quota and abuse-prevention records currently have no automatic expiry and remain until operational cleanup or a deletion request; resetting a counter does not automatically delete historical records. Providers retain their own operational data under their respective policies.

You can revoke Google access in Google account connections. Revoking access or signing out does not by itself delete local chat history or server quota records. To request deletion of your Firebase account and associated account quota records, contact the operator using the contact link below and identify the account email. We may ask you to verify ownership before deletion. Third-party logs and backups are subject to the provider's deletion and retention procedures.

Contact and changes

For questions or account/data deletion requests, contact support@sleektranslator.com. Changes to data handling will be reflected on this page with an updated date.