Parleroo Privacy Policy

What Parleroo needs to work

Parleroo helps learners understand and practice language from supported streaming services.

First, the important part:

• We don’t sell your data. Not now. Not ever.
• We don’t use what you do in Parleroo to target you with ads or marketing messages. Not now. Not ever.

We built Parleroo for people who want to give their screen time a little more meaning — to enjoy a good show and come away knowing a little more of a language than they did before.

We did it because we believe culture travels one word at a time.

That’s what your data is for: making Parleroo work for you. Nothing else.

Here’s what that means in practice:

• When you use a learning feature, Parleroo uses the subtitle, the words you interact with, and the account or settings information needed to make that feature work.
• Sometimes subtitle text needs to be processed by Parleroo or by one of the services that helps a feature work — for example, when you ask for a translation.
• Your show history is deliberately small: we keep the show title and only the words you interacted with, not the subtitles they appeared in.
• We use a few outside services to make Parleroo work: Google for sign-in, Resend for sign-in emails, OpenAI for language and practice features, and Render to host Parleroo and its database. If you choose to open Forvo or Wiktionary, the word you selected is passed to that site.

Some things happen entirely in your browser; others need Parleroo’s servers. That includes things such as signing you in, translating language, creating practice material, and keeping the service running reliably.

Parleroo does not sell your data or use it for personalized advertising.

Parleroo is the publisher and privacy contact. Questions or requests can be sent to privacy@parleroo.com.

Information we handle

Depending on the features you use, Parleroo handles:

• Account information such as your email address, display name, avatar, public account identifier, and sign-in provider.
• Website and extension authentication information, including signed sessions and extension credentials.
• Settings such as learning languages, voice-command phrases, shortcuts, playback choices, subtitle choices, speech rate, and voice preferences.
• Supported streaming-service page information needed to provide the feature, including subtitle text, selected words, context, and supported video metadata.
• Learning activity such as words encountered, help/pronunciation activity, practice progress, language choices, show references, and aggregate statistics.
• Practice information that you type or submit, including sentences, notes, recognized speech transcripts, and generated practice material.
• Diagnostic information such as request IDs, error evidence, and trace data when diagnostics are explicitly sent or are needed to maintain security and reliability.

The current product does not collect payment, financial, health, or precise location data. Parleroo does not operate a general browsing-history collector. The extension reads supported streaming-service pages for the features that operate there. Forvo is opened as a user-requested reference page and is not read or modified by the extension. It does not collect unrelated browsing activity for advertising or profiling.

Raw microphone audio is not stored by Parleroo in the current implementation. The browser’s speech-recognition service may process microphone input under the browser’s own policies; Parleroo receives the recognition results used by its features.

Show-history data minimization

Parleroo does not turn viewing on a supported streaming service into a stored subtitle transcript. Subtitle text may be held temporarily in the extension or sent to the Parleroo server and its configured language-service provider when a feature needs it. Durable show history is based on qualifying word-level learning activity and show metadata, not the full subtitle.

For example, if you watch a show without any qualifying word activity, it does not appear in your show history. If one word is the only word that becomes part of your learning activity for that show, the history records that word-level activity and the relevant show metadata, not the complete subtitle in which the word appeared. A failed request or explicitly uploaded diagnostic trace may contain text needed to investigate that request; this is a limited diagnostic path, not a subtitle-history transcript.

How we use information

We use information to authenticate users and protect account access, synchronize settings between the website and extension, read supported subtitle context and provide translation, explanation, pronunciation, and practice features, record learning activity and present statistics and personalized practice, send passwordless sign-in email when requested, maintain and secure the service, debug and improve reliability, and investigate abuse, security issues, or a support request.

Parleroo does not sell user data and does not use user data for personalized, retargeted, or interest-based advertising.

Local and server-side processing

The extension stores settings and temporary runtime state in browser storage. Its refresh credential is stored in extension IndexedDB and its short-lived access credential is stored in extension session storage. The server stores only a hash of the refresh credential. Signing out revokes the extension refresh session and clears local extension credentials.

The extension stores your privacy-consent choice locally in Chrome storage for that browser installation. The consent record contains an acceptance time and version markers; it is not synchronized to another browser profile or sent to Parleroo.

Email sign-in links expire after 15 minutes. Extension handoff records expire after five minutes. Extension access credentials expire after one hour, and refresh sessions expire after 30 days without a successful rotation. Website sessions last up to 30 days, subject to account access expiry.

Parleroo’s server stores account, settings, learning, practice, authentication, and operational records needed to provide the service. Subtitle and translation inputs are sent to the Parleroo server when you request a feature that needs them. The server sends the minimum required context to its configured language-service provider and returns the result.

External sharing and providers

Parleroo shares information only when needed to provide the features described above, operate the service, protect it, or respond to a user request. Current providers and integrations are:

• Google provides the Google sign-in experience and identity information.
• Resend delivers passwordless sign-in emails.
• OpenAI processes the minimum required server-side translation, explanation, word-detail, and practice prompts. These prompts can include selected words, subtitles, context, and language choices. Parleroo does not make additional claims here about OpenAI retention or model training beyond the active provider terms and account configuration.
• Render hosts the Parleroo application and production PostgreSQL environment.
• Supported streaming services provide the pages on which the subtitle learning feature operates. Parleroo reads supported page content in your browser; each service continues to process its own account and viewing activity under its policies.
• Forvo and Wiktionary receive browser requests when you choose to open their pronunciation or dictionary pages. The selected word can appear in the requested URL.

The browser may also provide speech recognition and speech synthesis. That processing is controlled by the browser and its providers, not by Parleroo; their own policies apply.

Parleroo does not make user data available for routine human review. Authorized operators may access limited information when necessary for security, abuse prevention, legal obligations, service operation, or user-requested support.

Retention and deletion requests

Parleroo does not currently have one universal retention period or an automatic purge for every account, learning, and diagnostic record. We retain information only for as long as it is needed to provide, secure, maintain, or improve the service, subject to legitimate security or legal needs.

You can sign out, reset learning statistics through the existing settings features, or request access, correction, or deletion by emailing privacy@parleroo.com. Parleroo currently handles account deletion requests manually. We may ask you to verify control of the account, but will not ask you to send a password or authentication token by email. We will review account, authentication, settings, learning, practice, and related diagnostic records. Some security or legal records may require separate review before they can be removed.

Deleting server-side data cannot erase copies already present in browser storage. Sign out and uninstall or clear the extension if you also want to remove local extension data.

Authentication and security

Parleroo uses HTTPS for production website and API communication, signed website sessions, short-lived extension access credentials, rotating refresh credentials, and server-side hashing of refresh credentials. Diagnostic error evidence redacts credential-shaped fields before durable persistence.

No internet transmission or storage system can be guaranteed completely secure. If you believe there is a security issue, contact privacy@parleroo.com.

Chrome Web Store Limited Use

Parleroo’s use of information received from Google APIs, including information made available through Chrome extension permissions, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Parleroo limits data use to the disclosed subtitle-learning purpose and related authentication, security, support, and reliability operations. Parleroo does not sell user data or use data for personalized advertising.

Before the extension reads supported-page content, loads extension settings, or sends extension data, it presents the complete in-product disclosure and requires affirmative, informed consent. Closing or deferring that disclosure keeps the extension inactive. This policy does not replace the product disclosure.

Changes to this policy

We may update this policy when the service, integrations, or legal requirements change. We will update the date above and publish the current version at this address.