This privacy policy explains how the weTubeBox browser extension handles data when you use it with the WeTubeBox website, API, and Telegram bot. The extension is a companion to the WeTubeBox service at https://wetube.eu.cc.
Data You Choose To Send

The extension sends data to WeTubeBox only when you use an extension action, such as a popup command or a right-click context-menu command. Depending on the action, the extension may send:

The page URL, link URL, image URL, or video page URL you selected for processing.
A requested processing quality when one is supplied by the extension flow.
A file ID when you choose actions such as upload to Google Drive or send to Telegram for an already processed file.
Authentication requests needed to fetch or refresh the extension token.


Account And Authentication Data

weTubeBox accounts are linked through Telegram. The extension does not ask for, collect, or store a username or password. When you are already signed in on the WeTubeBox website, the extension can request a short-lived bearer token from the WeTubeBox API. The website session cookie is used by the browser only for that token request.

The extension stores the bearer token in browser.storage.local. The server currently issues the token for 120 minutes. The extension clears the token on logout and when the API reports that the token is invalid or expired. Lightweight account details such as user ID, display name, and Telegram username may be stored locally so the popup can show connection status.
Local Extension Storage

The extension may store the following data locally in Firefox extension storage:

authToken: the short-lived API token and its expiration time.
userInfo: lightweight user information returned by WeTubeBox.
pendingUrl: a URL queued before authentication is completed.
lastResult: the most recent processing result shown in the popup.
tasks: recent task history shown in the in-page task panel, capped by the extension at 50 tasks.


This local data stays in the browser until it is replaced, cleared by an extension action, removed by logout where applicable, or deleted by the user through browser controls.
Server-Side Processing Data

When you submit a URL, the WeTubeBox server processes that URL and may store request and file records for your account. These records can include the submitted source URL, request status, requested quality, timestamps, processing time, file name, title, source site, file size, MIME type, extension, duration, resolution, channel or uploader metadata, generated download/watch links, Google Drive links, Telegram file IDs, and internal server file paths.

WeTubeBox uses this data to process downloads, show task results, prevent duplicate processing, enforce quotas and rate limits, provide account history, deliver files, debug failures, and protect the service from abuse.
Telegram And Google Drive

WeTubeBox uses Telegram for account linking and file delivery. The service may store Telegram identifiers such as chat ID, Telegram username, language, message IDs, and Telegram file IDs when needed to authenticate your account or send files to your Telegram chat.

Google Drive integration is optional and is handled by the WeTubeBox service, not directly by the browser extension. If you connect Google Drive, WeTubeBox may store encrypted Google refresh tokens, Drive folder IDs, Drive file IDs, and Drive links so it can upload files you request. The extension triggers Drive upload only when you choose that action for an available file.
Data Sharing

WeTubeBox does not sell extension data and does not use it for personalized advertising. Data is shared only as needed to provide the requested service:

With the WeTubeBox API and backend systems to authenticate, process URLs, store files, and return results.
With the source website or remote server for the URL you selected, because WeTubeBox must access that URL to process or download it.
With Telegram when you authenticate through the bot or ask WeTubeBox to send a file to Telegram.
With Google Drive when you have connected Drive and ask WeTubeBox to upload a file there.
With infrastructure providers used to host, secure, log, and operate the WeTubeBox service.


Retention

The extension token is short-lived and currently expires after 120 minutes. Local extension task history is capped at 50 tasks and can be cleared from the extension UI or browser controls.

Server-side file retention depends on the user's WeTubeBox quota plan. 7 days for the free plan, 30 days for the VIP plan, and unlimited retention for the unlimited plan. Users can delete files from the WeTubeBox dashboard. Files deleted by a user are soft-deleted first and are scheduled for physical purge after the configured purge window (10 days). Some metadata of requested file may remain for account history, security, abuse prevention, support, and audit purposes.
Your Choices

You can avoid sending a URL by not using the weTubeBox context-menu or popup processing actions.
You can log out from the extension to clear extension authentication data.
You can clear recent task history from the popup or remove extension data through Firefox settings.
You can manage and delete stored files from the WeTubeBox dashboard.
You can choose not to connect Google Drive, and Drive upload will not be used unless you request it.


Security

The extension requires HTTPS API URLs. Authentication tokens are stored only in Firefox extension local storage, not in page localStorage or sessionStorage. API requests use bearer tokens, and the service clears or rejects expired tokens. Google Drive refresh tokens stored by the backend are encrypted by the Laravel application.
Contact

For privacy or support questions, you can contact us via email wetubebox [at] gmail.com or use the WeTubeBox website at https://wetube.eu.cc or the WeTubeBox Telegram bot at https://t.me/weTubeBoxBot?start.
Changes To This Policy

This policy may be updated when the extension or WeTubeBox service changes. The effective date above identifies the current version.