Chrome extension

川流字幕subruu Privacy Policy

Last updated: 2026-09-19

This policy covers the Subruu browser extension, subruu.com, member services and support. Privacy contact: plumyriver@kaikongtalk.com.

Captions, audio and video information

After you start captions, the extension processes audio from your chosen tab and reads the video URL, title, language, playback position and player information needed for synchronization. Audio and recognized/translated text are processed by Subruu's backend or the speech and translation services used by your selected engine. Encrypted recognition/translation results may be retained temporarily for retries and recovery; this service is not a promise that no text is stored.

Mirror-view video is processed in your browser and is not sent to our cloud for video storage. Prefetch and synchronized viewing request playlists or media segments from the original website. Stop ends new capture; requests already sent may finish processing, settlement or record updates.

Chat, replies and context search

When you use chat translation, reply translation or context search, relevant messages, visible author details, text you enter, prompts, video titles/URLs and necessary context are processed by the required translation, search or model services. Do not submit confidential material that you do not want those services to receive.

Shared captions and diagnostics

The shared subtitle cache stores video identifiers, original text, translations, timings and quality evidence for reuse by other viewers of the same video. In versions with Data & privacy settings, shared caching is optional and off by default. Enable it only when you intend to share the video's subtitles. Fresh captions remain available when off and may use more credits. Local session buffering is distinct from the shared cloud cache.

Service records include extension version, session identifiers, usage, latency, error codes and playback/caption timing events for operation, billing and troubleshooting. In versions with Data & privacy settings, the extension includes subtitle/chat excerpts and video details in diagnostics only when Share content for troubleshooting is enabled, which also permits support staff to review that content to troubleshoot captions. Turning off the corresponding choice stops that type of new content diagnostics or cache publication. Re-enabling cache takes effect when captions next start.

Older manually installed versions without these choices may automatically use shared caching and report limited text excerpts. You may stop using that version and contact us for deletion or version assistance. Changing settings or uninstalling does not automatically delete records already transmitted.

Accounts, credits, payments and rewards

Member sign-in processes a Firebase UID, email, display name, verification status and authentication credentials. Login state and preferences are stored in extension storage. Guest trials create an anonymous identifier and use HMAC hashes derived from an installation key and network IP to limit repeated claims. These abuse-prevention records do not store the original installation key or IP, but infrastructure security/access logs may contain connection information.

We retain credit balances, usage, passes, orders, payment status, support adjustments, login/check-in days and reward records to provide plans, prevent duplicate charges and resolve billing questions. Payment services such as ECPay handle checkout; we receive order and transaction results and do not collect full card numbers or security codes in the extension.

Referrals store referral codes, referring/referred account identifiers and necessary emails, reward progress, eligible purchased credits and reward ledger entries. Referral rewards do not reduce the referred member's purchased credits. Current member pages and campaign terms describe applicable rewards.

Support messages and attachments

Support messages, photos, videos and files you choose to send are retained for replies and problem resolution. Members access their own conversations; authorized support staff use a restricted support console. Do not send passwords, login tokens, full payment-card details or unnecessary identity documents.

Service providers and security

Depending on the feature, services include Google Cloud/Firebase for authentication, computing and storage; hosted model services on SaladCloud; and model/API processors such as OpenAI, ElevenLabs or XPluse. ECPay processes payments. Each processor should receive only the data required for its function. Audio or text may be processed internationally; retention also depends on the actual processing service's terms.

Cloud connections use HTTPS/WSS. Backend service credentials are kept on controlled servers or in Secret Manager. The extension uses authentication credentials or short-lived processing tickets as required. If you choose an engine running on your own computer, audio may be processed locally, while cloud translation and billing still send the information their features require.

Retention and deletion

Browser preferences and login data remain until sign-out, clearing extension data or uninstalling, as applicable. Session audio buffers support processing rather than an audio-history service. Temporary results expire according to retry/recovery windows and are removed by maintenance. Diagnostics are cleaned up according to troubleshooting and security needs. Shared captions remain for reuse until replaced, cleared or addressed through a verifiable request. Account, support and financial records are retained as needed to provide services, resolve disputes, prevent abuse and meet legal obligations.

For access, correction or deletion, email plumyriver@kaikongtalk.com or use website support. Members should provide their sign-in email; guest users can provide identifiers displayed by the extension, its version and approximate usage time. We may request reasonable identity verification but will not ask for your password. Specify whether the request concerns an account, support attachments, diagnostics or a particular video's cache. Records necessary for legal obligations, unsettled payments, disputes or fraud prevention may not be immediately removable.

Website analytics and cookies

With your permission, the website uses Google Analytics 4 for page views, scrolling, demo/tutorial interactions, downloads, registration/sign-in, checkout initiation and confirmed purchases. Analytics is optional; choosing Decline and continue does not affect accounts, captions or payments. Change your choice through Analytics cookie settings. The browser remembers the choice for up to 180 days.

Analytics code loads only after permission. We remove URL query parameters, unrecognized fragments and referrer paths. Emails, account UIDs, form contents, audio, captions, login credentials and original order numbers are not sent as analytics event parameters; purchase identifiers use a one-way hash. Google Analytics may process cookies, device/browser information and approximate region. Google Signals and advertising personalization are disabled. Analytics is not the billing ledger.

Limited Use

Subruu's use and transfer of user data received through Chrome extension permissions comply with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide or improve the clearly described caption, viewing and related features. We do not sell data, build personalized advertising profiles from captions or browsing data, or provide it to data brokers.

Transfers are limited to permitted circumstances, including processing needed for the described features, uses you explicitly authorize, legal obligations and necessary security handling. People do not routinely read user content. Access is limited to your consent for specific content or material you submit to support, necessary security/legal handling, or policy-permitted anonymous aggregates.

Campaign attribution within Subruu

With your separate opt-in, we associate registered campaign and creative codes with your signed-in account to measure first successful bilingual subtitles and verified purchases. Attribution lasts 30 days; direct visits do not overwrite campaigns, and existing users are not counted again as first activations. Backend payment receipts are deduplicated even when you do not return after payment. This feature does not collect raw search terms, advertising click identifiers, viewing URLs, audio or caption content, or send account identifiers or these internal conversions to Google Ads. You can withdraw this choice in analytics cookie settings. While signed in, withdrawal removes your account attribution data; failed requests are retried on your next sign-in. Account, subtitle and payment functions remain available.Campaign and conversion details are retained for up to 180 days; first-activation deduplication state is retained until account deletion.

Optional Google Ads measurement

The October 17, 2026 notice also covers extension-reported installations, only for new ad journeys created after explicit acceptance. On first installation the extension saves only the time and version locally. A random measurement ID is generated only after explicit consent. It reports to our backend only when an official setup page is opened within seven days with consent and a matching store-opening journey. Updates, development builds and existing users are not backfilled. The backend keeps only a hash of the random ID and the version/time; the source lasts at most thirty days and installation records are removed on withdrawal or expiry. Google receives only the ad identifier, time and deduplication ID, not the version or a device fingerprint. This is a lifecycle observation, not a Chrome Store-signed receipt or a unique-person count.

This separate option is unchecked by default. With your additional consent, the website and backend store Google ad click identifiers (GCLID/GBRAID/WBRAID), which can be associated with your account after sign-in. The updated choice covers Chrome Web Store openings, new members' first extension connections, first successful subtitles and genuine purchases. Store openings can be reported before sign-in; they are not proof of installation, and an extension connection is not subtitle success. We send only the click identifier, event type/time, deduplication identifier and, for purchases, value/currency to Google Ads. We do not send viewing platforms or URLs, audio, captions, email, account UID or credentials. Remarketing and ad personalization remain disabled.

The store-opening and first-connection events added on October 15, 2026 apply only to new ad-source journeys created after an explicit acceptance of the updated notice. Earlier consent is not expanded automatically, and existing journeys or historical records are not backfilled for these events. You can decline or withdraw in Analytics cookie settings.

Click identifiers are kept for up to 30 days, delivery/deduplication records for up to 180 days, and first-activation deduplication until account deletion. Withdraw through Analytics cookie settings without losing access to captions, accounts or payment. Withdrawal immediately removes local click identifiers and, after an authenticated connection, removes backend identifiers and stops unsent events. Offline withdrawal is retried. Stopping delivery does not automatically recall data already sent to Google, which remains subject to Google's policies. Blocking, refusal, cross-device use and views without clicks can cause undercounting. Advertising reports are not accounting records.

Managing your choices

Choose “Accept analytics and ad measurement” to allow website analytics, Subruu attribution and Google Ads measurement together, or use “Customize” to choose individually. “Decline and continue” declines all optional purposes. Silence, closing the notice or continuing to browse does not grant consent. Existing refusals are preserved when this interface updates.

After you consent to ad measurement, a random journey identifier connects the ad landing, store or download clicks, registration page, official extension detection and account connection. After sign-in it can be linked to the member and server-verified first subtitle success. Opening the store is not an installation; detecting the extension does not prove a new installation. Anonymous journeys last up to 30 days. Withdrawal stops measurement and clears active data; anti-replay withdrawal records last up to 180 days. Refusal, blocking, device changes or not returning to the site may leave gaps.

Before you make a choice, the ad source already in the URL may pass between public pages on this website through their URLs for up to 20 minutes. This does not write tracking cookies or browser web storage, or send tracking events. This feature does not add it to external sites, the Chrome Web Store, payment links or private account pages. Recording starts only after consent; refusal or expiry clears the source. URLs may still appear in browser history and ordinary web access logs; do not share URLs containing ad identifiers.