Privacy Policy | LingoCue

1. About This Policy

This Privacy Policy explains how LingoCue ("LingoCue", "we", "us", or "our") handles personal data when you visit lingocue.win, use the LingoCue staging service, create an account, or contact us.

Feature availability depends on the environment you use. Account testing, cloud media translation, and payments may be enabled separately. The media and payment disclosures below apply when you choose to use those features.

For privacy questions or deletion requests, contact support@lingocue.win.

2. Data We Collect

Account and profile data

When you create or use a LingoCue account, we may process:

your display name, email address, email-verification status, and profile image;
an internal user identifier and account creation/update timestamps;
your chosen authentication method and the identifier supplied by that authentication provider; and
a password hash when you choose email-and-password authentication. We do not store your plaintext password.

If you choose Sign in with Google, LingoCue requests only the basic OpenID Connect scopes openid, email, and profile. Google may provide:

your Google Account identifier;
your name;
your email address and whether Google has verified it; and
your Google profile image.

We use this information only to authenticate you, create or link your LingoCue account, protect the sign-in flow, and display your account profile. Google Sign-In does not give LingoCue your Google password. LingoCue does not request or access your Gmail messages, Google Drive files, contacts, calendar, photos, or other Google product content.

Where OAuth access or refresh tokens are stored, LingoCue is configured to encrypt them before they are written to the database. We do not use Google user data for advertising, credit decisions, or training general-purpose AI or machine-learning models.

Authentication and security data

To operate and protect the service, we process session identifiers, session expiry times, IP addresses, browser user-agent information, OAuth state and verification records, and password-reset or email-verification records.

Files and service content

Selecting or dropping a file on the homepage does not upload it. If you choose Google Sign-In with a file selected, we may temporarily save that selection in your browser to restore it after the sign-in redirect. This local copy is removed when restored or when sign-in is dismissed. It is eligible for recovery for ten minutes; expired copies are cleared the next time the site opens the local store. Clearing site data also removes these copies. If browser storage is unavailable, you may need to choose the file again after signing in.

We store profile images you upload. When you start cloud translation, we process your uploaded audio or video, its filename and duration, extracted speech, language and model choices, translation instructions and context, subtitles, and any generated captioned video. Uploaded media is stored and prepared on Cloudflare infrastructure. For speech recognition, extracted audio is divided into WAV segments and sent through OpenRouter to your selected Whisper Turbo or MAI-Transcribe 2 provider. The original video file is not sent to that provider. Transcript text, adjacent source text, prior translations, and translation instructions are sent through OpenRouter to the selected translation model provider.

New media tasks use direct translation with bounded repair calls; they do not run separate source-correction or rolling-summary model calls. Older saved tasks retain their original processing contracts, which may include correction or summary context.

We retain task identifiers, processing status, credit and provider-usage accounting, and temporary model results to support task recovery and prevent duplicate charges. Optional debug-payload storage, when enabled in your privacy settings, also retains prompts and model output for diagnosis. It is disabled by default.

Payment data

When payments are enabled, the selected payment processor receives checkout information such as your email, name, account reference, and selected product. We store processor customer and transaction references, subscription status, payment amounts, and credit grants, spending, refunds, and disputes. Payment card details are handled by the processor rather than stored in LingoCue's application database.

Communications

If you contact us, we process the name, email address, message, and related support correspondence that you provide.

Technical data

Cloudflare may process request metadata needed to deliver and secure the service, including IP address, request time, requested URL, response status, browser information, and security signals. The current staging build does not enable advertising trackers or third-party analytics scripts.

3. How We Use Data

We use personal data to:

create, authenticate, link, secure, and administer LingoCue accounts;
send required email verification, password-reset, and security messages;
maintain sessions and prevent fraud, abuse, and unauthorized access;
provide profile and account settings;
transcribe media, translate text, generate subtitle/video downloads, recover interrupted tasks, and account for model usage;
process payments, manage subscriptions and credits, and reconcile refunds and payment disputes;
respond to support requests;
diagnose failures and maintain service reliability; and
comply with applicable legal obligations and enforce our Terms of Service.

We do not sell or rent personal data. We do not use Google user data for personalized advertising, and we do not transfer Google user data to data brokers.

We disclose data only as needed for the purposes described in this policy:

Google provides the optional Google Sign-In flow. Data exchanged with Google is governed by your Google Account choices and Google's privacy terms.
Cloudflare provides DNS, security, Workers hosting, D1 database, R2 object storage, Containers for media processing, and email-delivery infrastructure. Cloudflare processes data on our behalf to operate these services.
OpenRouter and the selected model providers receive extracted audio segments for speech recognition and text and context for translation. Their processing and retention depend on the provider and its terms; our temporary-result cleanup does not control copies held by those providers.
Stripe or Creem, according to the enabled checkout, processes payment and subscription information. Processor records are subject to that provider's retention practices.
Legal and safety recipients may receive data when disclosure is required by law or is reasonably necessary to protect users, LingoCue, or the public.

We do not include your Google access tokens or Google profile data in model prompts. If you use payments, your account name and email may be supplied to the selected processor for checkout, regardless of how you signed in.

We do not allow a service provider to use Google user data for its own advertising or to sell that data.

5. Storage, Security, and International Processing

LingoCue runs on Cloudflare infrastructure. Account, authentication, and application records are stored in Cloudflare D1, and uploaded profile images, media, and generated files may be stored in Cloudflare R2. Media-processing containers use temporary working storage. Required account emails are delivered through Cloudflare Email Sending.

We use HTTPS in transit, access controls, scoped service credentials, secure session cookies, and application-level encryption for stored OAuth access and refresh tokens. No system can guarantee absolute security, but we limit access to people and systems that need it to operate and protect the service.

Our service providers may process data in countries other than your own. Their processing is subject to their respective contractual and legal safeguards.

6. Retention

We retain data according to its purpose:

account and Google profile data are kept while your LingoCue account remains active and are removed from the active account database when the account is deleted, subject to the exceptions below;
normal web sessions are configured to expire after seven days, although a session may end sooner after sign-out, password reset, or revocation;
email-verification links expire after one hour;
security and service logs are retained only for the periods configured with our infrastructure provider and as needed to investigate reliability, security, or abuse incidents;
support correspondence is retained only while it is needed to resolve the request and maintain a reasonable record of the resolution; and
cloud media, processing checkpoints, subtitle files, and generated videos are scheduled for deletion when their task expires; the default task window is 24 hours from creation. Processing or cleanup outages can delay physical removal;
temporary model-result copies used for recovery expire after 24 hours and are removed by scheduled cleanup. This is separate from optional debug copies, which remain until removed or the account is deleted;
profile files and operational task and usage records remain while needed to operate your account and are removed during account deletion; and
after deletion, a limited financial archive retains transaction references, amounts, credit accounting, and a hash of the processor customer identifier. This archive excludes your email, raw application user identifier, media, prompts, and model output. Financial references can still be linked through processor records, so this is not a claim that the archive is anonymous.

Residual copies may remain temporarily in provider backups or security logs. We may also retain limited records when required by law, to resolve disputes, or to prevent fraud and abuse.

7. Your Choices and Deletion

You may:

use email-and-password authentication instead of Google Sign-In;
update your name or profile image in LingoCue account settings;
sign out to end the active browser session;
revoke LingoCue's Google access from your Google Account connections;
delete your LingoCue account from Settings > Security > Delete Account; and
contact support@lingocue.win to request access, correction, or deletion of associated data or stored files.

Revoking Google access stops future Google Sign-In authorization but does not by itself delete data already stored in your LingoCue account. Delete the LingoCue account or contact us if you also want that data removed.

Account deletion first freezes new work, stops media processing and subscriptions, removes owned files, and completes any pending usage settlement. If an external service or unfinished checkout prevents cleanup, deletion remains pending and can be retried. Account deletion does not issue a payment refund or erase records held independently by a payment processor.

We may need to verify your identity before fulfilling a data request. Your rights may vary by location and can be subject to lawful exceptions.

8. Cookies and Local Storage

LingoCue uses strictly necessary cookies for authentication, OAuth security, and session continuity. Theme preference may be stored locally in your browser. See our Cookie Policy for details. The current staging service does not use advertising cookies.

9. Children

LingoCue is not directed to children under 13, or a higher minimum age where required by local law. If you believe a child has provided personal data, contact us so that we can review and delete it where appropriate.

10. Changes to This Policy

We will update this policy when our data practices or service providers change. The date at the top shows the latest revision. Material changes will be communicated through the service or another appropriate channel before they take effect when required.

11. Contact

For questions, privacy requests, or complaints, email support@lingocue.win or use the contact page.