GoogleYouTube BAS Auto Bridge

Privacy policy · Last updated 12 November 2026

This policy covers the GoogleYouTube BAS Auto Bridge Chrome extension and its local handoff to the separately installed GoogleYouTube Loader desktop application. The publisher is the developer identified on the extension's Chrome Web Store listing. This is an independent project, not a Google or Bablosoft product.

Purpose and data accessed

When you start GoogleYouTube Loader, it creates a short-lived local request. The extension validates that request with the registered native host and reads cookies only for google.com, youtube.com and their subdomains in the selected Chrome profile. Cookie data includes names, values, domains or URLs, paths, expiry times and security attributes. Values may include authentication tokens, session identifiers, account-related identifiers and site preferences. These cookies can provide access to your signed-in account.

The extension does not read passwords, payment card details, email messages, page content or the browser history API. It does not operate in incognito mode. It has no background cookie synchronization; it reads cookies only for an active request from the local loader.

Where the data goes

The extension passes the data through Chrome Native Messaging to com.googleyoutube.basbridge on the same Windows computer. It has no analytics endpoint, advertising service or external collection server. The local helper temporarily protects the handoff with Windows DPAPI and passes the session to the local BAS browser. The BAS browser then uses those cookies in normal HTTPS requests to Google and YouTube for the requested session. Google and YouTube process those requests under their own policies. The developer does not receive a copy of the cookies from the extension.

Storage and retention

The extension does not store the cookie payload in extension storage or logs. The companion app keeps a short-lived encrypted handoff and deletes it after successful consumption; interrupted handoffs are cleaned up on a subsequent initialization. The BAS profile retains the transferred session until you remove that profile or the session expires or is revoked. Non-secret operational status and configuration files may remain locally.

On Windows, the companion app uses GoogleYouTube-data next to its executable and %LOCALAPPDATA%\GoogleYouTubeBASBridge. The saved BAS profile is GoogleYouTube-data\runtime-29.4.1\youtube-profile. Do not share a profile or cookie export containing your active session.

Permissions

Control and deletion

Stop the loader to stop the workflow. Run GoogleYouTube-Loader.exe --disconnect to remove its native-host registration and its configured extension policy, if any. You can then disable or remove the extension in Chrome. Removing the extension alone does not remove existing BAS profile data. To delete local session data, stop the loader and remove the saved youtube-profile folder; remove GoogleYouTube-data and %LOCALAPPDATA%\GoogleYouTubeBASBridge to remove the companion's local files. Existing data in your ordinary Chrome profile is separate.

The loader closes Chrome after it obtains the session; save unfinished work first. If configured with a published store ID, the loader may request automatic extension installation through a local Chrome policy. Whether Chrome applies that policy without prompts depends on the environment and is not guaranteed. Google may require account verification after session transfer.

Use and sharing commitments

Data is used only for the local session handoff described here and the user's requested BAS session. We do not sell cookie data, use it for advertising, creditworthiness or lending, or transfer it to a developer-operated remote service. Access to an account remains subject to the service's own authentication and session controls.

Contact

For privacy questions or bug reports, open an issue at the project support page. Do not include cookies, tokens, account credentials or private screenshots in a public issue.


Кратко по-русски

Расширение по запросу запущенного вами GoogleYouTube Loader читает cookies Google/YouTube и передаёт их приложению на том же ПК через Native Messaging. Среди этих данных есть авторизационные токены и идентификаторы. Само расширение не отправляет cookies разработчику, рекламным службам или аналитическим серверам. BAS использует полученную сессию для обычных запросов к Google/YouTube.

Временная передача зашифрована Windows DPAPI; рабочий профиль BAS сохраняет сессию. Для отключения локального соединения используйте --disconnect, затем при необходимости удалите расширение и папку youtube-profile. Не публикуйте cookies и не передавайте профиль другим людям. Дополнительное подтверждение аккаунта Google может потребоваться.