Account and data information

Data processed by the service

Third-party sign-in creates your account. The service stores provider account identifiers, display names, email addresses and session records. Sessions may include browser information and IP addresses. Email addresses are not used to merge different accounts automatically.

After a host connects, the service processes its identifier, contact times, execution permissions, task inputs, status, results and usage records. Task text and files may pass through the cloud; submit only content you wish to share with the service. Host credentials are verified by digest. The authentication component encrypts OAuth access and refresh tokens. Identity records, including identity tokens, are kept in an access-controlled database.

Files are temporary transfers

New native imports and exports expire by default 24 hours after becoming available, with shorter lifetimes supported by the API. Older upload tickets retain their original lifetime; existing permanent objects are legacy data. Expiry blocks new access. A bounded recovery window for accepted tasks can delay physical cleanup. Failed cleanup is retried. Access expiry does not mean physical deletion is complete.

File expiry does not automatically delete task text results, accounts or billing history. Do not use Bridge as long-term file backup.

Providers and controls

The service runs on Cloudflare. Google or GitHub handles the sign-in method you choose; your AI client processes inputs and outputs under its own rules. Third-party sign-in does not authorize engineering repositories. The website does not request Google Drive permissions.

Signing out revokes that web session. Host pausing and client authorization are managed separately. The individual operator handles account and data requests. Automatic deletion of all historical records and fixed processing deadlines are not promised.

Operation: Bridge · independently operated. Support and account data requests: dashideyizhizuo@gmail.com.