BiliFlow · Updated: 1 November 2026
How BiliFlow handles your data.
BiliFlow downloads selected Bilibili media and processes video and audio on your device. Speech recognition and supported translation models run locally. It still uses the network to contact Bilibili and its media servers, verify paid access and rewards, download optional AI model data, use online caption translation when you separately approve it, and send usage events when you choose to share them.
What is stored in this browser
- Downloads: selected video metadata, title, original page URL, part, output format, timestamps, progress, status and the Chrome download ID. Optional history keeps up to 100 finished entries. Turn it off or clear it in Settings/History. You can delete a finished entry or select and delete multiple finished entries. Deleted entries disappear immediately from the interface; outstanding settlement records remain hidden until quota/reward recovery finishes, then are removed. Saved media files are kept. Active jobs and outstanding quota/reward settlements remain until recovery finishes. Clearing history does not delete downloaded files.
- Preferences and limits: language, bubble position/visibility, reward sound preference and the last daily reward display, daily allowance and job reservations. Operational counters are separate from browsing history. A cached minimum/latest release version supports update notices and prevents new saves when a published update is required. BiliFlow checks its release-status service when the workspace requests status, at Chrome startup and approximately every six hours while Chrome is running; scheduling and network availability can delay checks. A version reported by Chrome as an available update is also stored locally. These functional checks do not require optional usage analytics, but the service receives ordinary connection metadata. Chrome manages actual Store updates; the extension does not force a reload during a download. The most recent selected page source is remembered per tab for up to one hour in browser session storage (up to 20 tabs) so the popup shows the video you chose. Successful source-format discovery is cached for ten seconds in the extension worker; starting a download resolves fresh source information.
- Temporary media: downloads use this extension's private browser file storage (OPFS). A failed job can retain partial tracks for a validated retry while history is enabled. Completed processing and cancellations remove their temporary tracks; clearing finished history or turning it off prunes finished checkpoints. Orphaned/old partial tracks are pruned after seven days when recovery runs. Cleanup requires the browser/extension to run; saved Downloads files are separate.
- Subtitles and models: selected media is decoded locally. If you enable saved progress, up to five subtitle checkpoints contain transcript text, timing, language and a file hash in this browser's IndexedDB; checkpoints do not contain the media file. Clear saved progress in Subtitle Studio. Verified model files stay in a browser cache until you remove downloaded models. Unfinished model-weight downloads can stay in private browser file storage for a validated retry; completion removes the partial copy. Remove downloaded models also attempts to remove these partial files. Other open Studio tabs can be downloading the same models; close them before removing all model data.
- Access: a license key, cached verification/access state, signed receipts where enabled, and a random reward identifier are stored locally. Legacy ExtensionPay customers can have provider credentials/user state in browser storage; existing Chrome Sync data may remain during migration. This storage is not a password manager or end-to-end encrypted vault.
Chrome and your operating system manage the saved files and browser profile. Anyone who can access that profile may be able to read its local data. Uninstalling the extension does not remove files already saved to your Downloads folder.
Optional messages and local preferences
BiliFlow can show an optional analytics invitation once per extension version when you open its workspace. Installing or updating alone does not enable usage analytics. Enable confirms the disclosed collection; Not now leaves it off, and closing the card preserves your existing choice. Settings remains available. A later version may invite you again without changing your preference automatically.
After a newly confirmed video save, a visible BiliFlow interface may offer a neutral, optional review link. Free can receive a reminder after each new confirmed save; ordinary dismissal or opening the review link does not mark a review as posted. Choosing Don't ask for 24 hours pauses reminders for that period. Simultaneous completions may be combined into one pending reminder so cards do not stack. For PRO, choosing Remind me after 24 hours defers the reminder; opening the review link stops further automatic PRO review reminders without asserting that a review was posted. A permanent do-not-ask choice persists across updates. Existing suppression choices remain respected. A separate Free allowance reminder can offer plan information at low or exhausted availability, at most once per UTC day; actual checkout requires your own action. Existing source and processing limits still apply.
Functional local preferences store the last invitation version, review cooldown/suppression choices, bounded completed-job IDs to prevent duplicate messages, the allowance-reminder date and a temporary active-message claim. These are independent of optional usage analytics. Clearing download history or disabling analytics does not reset these message preferences. They are not uploaded as prompt-impression telemetry.
Active new-purchase installation policy: the 1/3/5 browser-installation cap applies only to eligible purchases on or after 1 November 2026 at 00:00 UTC, under the active policy and compatible activation flow in publicly available version 1.0.10 or later. Earlier purchases are exempt from this new cap. Purchase verification and expiry checks still apply. Functional installation references and slot/recovery records support this policy; they are not hardware fingerprints or optional usage analytics. See the terms and service release status for the active policy.
Optional usage analytics
Analytics is off until you explicitly enable it in the optional invitation or Settings. With consent, BiliFlow sends allowlisted feature/error events, a random installation ID, event/time IDs, extension version and limited values such as output format, quality tier, plan tier and processing device. Events can include opening upgrade options, choosing a checkout plan or voluntarily opening the review link; limited enum values describe the selected plan and upgrade reason. These are interaction signals, not verified purchases or posted reviews. Existing general analytics consent does not automatically enable the newly disclosed upgrade, checkout, review-link and license-verification event categories; these remain paused until you confirm the updated disclosure by saving Settings with analytics enabled. Accepted terminal activity can trigger a non-blocking delivery attempt in addition to scheduled retries. IDs are pseudonymous, not a claim of complete anonymity. The installation ID is separate from the reward identifier.
Analytics does not include video URLs, BVIDs, video titles, media, subtitle text, account cookies, license keys or payment details. Turning analytics off stops new event collection, clears the local event queue and requests deletion of previously received installation events. If offline, deletion retries later; Settings can report that it is pending. Turning it on again creates a new analytics identifier. Opt-in analytics does not represent every installation or measure exact uninstall/cohort churn.
Network services and paid access
| Service | Data/purpose |
|---|---|
| Bilibili and media CDNs | Video identity and selected source requests for metadata, formats, captions and downloads. Your browser may use your existing Bilibili session for source access. BiliFlow's analytics/license service does not receive your Bilibili cookies. Platform login/VIP/region restrictions still apply. |
| BiliFlow backend on Vercel | License verification, random reward identifier, daily claim/reservation/job IDs, operational balances and opted-in analytics. HTTPS requests expose normal connection metadata to the host. IP-derived HMAC buckets are used for bounded abuse rate limits, not one-claim-per-IP entitlements. |
| Gumroad / existing ExtensionPay access | Purchase and access verification with the relevant provider. A submitted Gumroad license key is forwarded to Gumroad to verify the product, plan and paid access. The provider handles checkout/payment details under its own policy. BiliFlow stores a salted license hash and verification status on its backend; it does not collect your card number. |
| Hugging Face model hosting | Only when using optional local AI: requests for pinned tokenizer/configuration/model-weight files. The host sees normal connection metadata such as IP address and requested model files. Your media and captions are not uploaded. Executable inference code is packaged with the extension. |
Optional online subtitle translation
Chinese-to-English, English-to-Hindi and Chinese-to-Hindi translation use downloaded local models. Other language pairs use Google's online translation service only after you check the separate online-translation permission in Subtitle Studio and start translation. The checkbox is off by default and approval resets when the Studio page is reopened; accepting model downloads or usage analytics does not approve online translation.
For an approved online translation, selected caption text and source/target language codes are sent to translate.googleapis.com over HTTPS. Caption text is included in the request URL, so the provider can receive it in normal request records along with connection metadata such as your IP address. The extension omits browser credentials on these requests. Media files, Bilibili cookies, license keys and local download history are not attached to the translation request. This text is not sent to BiliFlow's analytics service. Avoid online translation for private or sensitive captions you do not want to share; keep the permission unchecked to use only local routes. Turning the permission off prevents further requests; it cannot retract requests already sent. Google controls its own processing and retention, and deleting BiliFlow history or analytics does not delete provider records. Availability and accuracy are not guaranteed.
These services have their own policies: Gumroad, ExtensionPay, Hugging Face, Vercel, Google and Bilibili.
Retention and deletion
The daily data-retention job removes raw analytics events received more than 30 days ago, installation-scoped daily aggregates older than 90 days, and IP-HMAC rate buckets older than one day. Deletion tombstones remain for 90 days to prevent queued events from being re-uploaded. A record can remain until the next successful cleanup; failed scheduling can delay removal. Hosting/provider logs follow their own retention settings and policies.
Reward balances, claims, settlement records and license verification records support earned access, cooldowns and replay protection. They are operational records and are not cleared by the analytics switch or local history button. No automatic expiry is currently claimed for the full reward ledger. Contact support for a request concerning operational records; deleting them can remove earned access or require re-verification. Purchased media files remain under your control.
Permissions
Downloads saves and checks output files; storage keeps the local state above; activeTab identifies the selected page; offscreen enables background local processing; alarms retry queued analytics/deletion/recovery and schedule published-version checks; declarativeNetRequest applies narrowly scoped media request headers. Supported-site access permits video metadata/CDN requests and the optional bubble. Existing payment-service access supports legacy provider verification.
Limited use and security
BiliFlow's use and transfer of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. BiliFlow uses accessed data to provide and improve its download, subtitle, access and reliability features. It does not sell user data or use video/history content for advertising. Remote requests use HTTPS. Signed access receipts, when enabled, use server signatures; legacy access verification can instead use the existing provider/backend verification path. Private signing keys are not distributed with the extension. These measures do not guarantee that a device, browser profile or third-party service can never be compromised.
Contact and changes
BiliFlow is operated by Suhaib in India under the independent software brand Elnavix Labs / Elnavix. Elnavix Labs is not an incorporated company. For product support, privacy questions or deletion requests, email founder@elnavix.online. See the BiliFlow support page for the information that helps us investigate a problem. Material changes will be described with the matching release and this policy's updated date.
License installations, help and feedback
License activation can send a random browser-installation identifier and your license key to BiliFlow for provider verification. The backend uses a non-plaintext purchase/license reference, verified plan, active/released installation state and first/last verification timestamps for access control and same-computer recovery. These functional checks are separate from optional usage analytics; turning analytics off does not disable licensing. No hardware fingerprint is used. Another Chrome profile or reinstall can be a different installation. New slot assignment requires explicit activation confirmation. Device transfers are unavailable; owner-verified recovery is limited to the same buyer and same computer. Installation references alone cannot prove hardware identity.
Active installation records and the non-plaintext license mapping support purchased access and same-computer recovery. Minimal current and superseded installation mappings remain while needed to support the purchase and prevent a superseded installation claiming another slot. Detailed recovery request and registration/denial audit records are removed after 90 days by the protected retention task. Feedback and any optional name/email are kept for up to90 days. Retention-task operation must be verified at rollout. Requests for access/correction/deletion go to founder@elnavix.online and are reviewed to preserve legitimate purchase recovery; no fixed response deadline is promised.
Automated troubleshooting runs locally from a packaged FAQ; no LLM or third-party AI service receives your questions. The header Support link opens Telegram at @BliFlowSupport_bot. Nothing is messaged automatically. Telegram and the bot operator handle information you choose to send under their respective practices; we do not automatically copy feedback, keys or download history to Telegram. Do not send passwords, license keys, card information or signed media URLs.
Human replies are usually handled08:00–22:00 IST (02:30–16:30 UTC); response and resolution times vary. Automated help is available anytime. The uninstall survey is voluntary; only a submitted response requires written feedback. Name/email remain optional and are self-reported, not verified identity. See Telegram privacy information.