Bridge API Client

Account & data

Privacy policy

What information we use, why we use it and the choices available to you.

Effective date: 31 October 2026 · Operator: Serdar Murat Çelik

Google and GitHub sign-in identify your account. API request content is separate from sign-in information and is processed to provide the API functionality you choose.

1. Scope

This policy covers the Bridge API Client desktop application, its managed account features and this public website. The application helps users compose API requests, inspect responses and view account usage. Access to managed features requires administrator approval.

2. Information we handle

  • Account identity: the account identifier, email address and basic profile information supplied by Google or GitHub, such as your name and profile image when provided. We do not receive your Google or GitHub password.
  • Access and device information: account status, assigned permissions, registered installation identifiers, device/platform/version information, sign-in sessions and application API key metadata.
  • Usage and security records: request identifiers, selected service/model, request timing, usage counts, allowance reservations, completeness status and administrative changes. Records may identify the account, device or key associated with a request.
  • Request content: text, files or other information you intentionally include in a supported API request, and the response returned by the selected service. Only request formats supported by your application version are available.
  • Website and support information: hosting services may process IP addresses and ordinary request/security metadata. If you contact us, we receive the information you include in your message.

3. How we use information

We use information to authenticate accounts, manage approval and permissions, deliver requested API features, display usage, enforce allowances, protect accounts, investigate failures or abuse, and respond to support or privacy requests. We do not sell account information or use Google account data for advertising.

This public website contains no advertising, analytics scripts, embedded trackers or sign-in form. The application uses essential session and credential storage for authentication; signing out ends the application's local session.

4. Google account data

Google sign-in requests basic identity scopes: OpenID, email and profile. We use the returned information only to identify your account, support sign-in and manage application access. We do not request access to Gmail messages, Google Drive files, contacts or calendars.

Google account information is not used to develop, improve or train generalized artificial intelligence or machine-learning models. It is not sent to API providers as request content. Text or other content that you independently enter into an API request is handled separately, as described below.

Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including applicable Limited Use requirements.

5. Processing and sharing

Authentication, hosting and infrastructure providers process information needed to run the application. Google or GitHub handles its own sign-in process. Authorized administrators can access account, device, usage and audit information necessary to operate the service.

When you submit an API request, its content is transmitted through the application's service infrastructure to the API service used to fulfil that request. Those providers may process or retain content under their own terms and privacy policies. Avoid submitting sensitive information unless you understand and accept the relevant service's data handling.

We may disclose information where required by law or where necessary to protect accounts, investigate abuse or defend legal rights. Service providers may process data in countries other than your own.

6. Storage, retention and protection

The central account and usage records do not retain API request or response bodies by default. Conversations and operational history may remain on your device, depending on the application features you use. External API providers apply their own retention rules.

Account records are kept while needed to provide and administer access. Usage, allowance and audit records currently have no automatic expiry: they may be retained after access ends to preserve accounting, prevent duplicate charges and support security investigations. Deleting local history, reinstalling the application or revoking a key does not erase these records or reset usage.

You may request deletion or restriction of account information. We will review the request and explain which records can be removed and which must be retained for accounting, security or legal reasons. Revoking Google access does not itself erase information already held by the application.

We use encrypted network connections, access controls and operating-system credential storage for supported desktop platforms. These measures reduce risk but cannot guarantee absolute security.

7. Your choices

  • Sign out of the application and ask your administrator to revoke device access or application API keys.
  • Review or revoke Google access in your Google Account connections, or GitHub access in your GitHub application settings.
  • Contact us to request access to, correction of, or deletion of account information, or to ask about retained records.
  • Do not include secrets or sensitive personal information in support messages unless necessary and agreed in advance.

8. Contact and changes

Bridge API Client is operated by Serdar Murat Çelik. For account or privacy requests, contact s.muratcelik@gmail.com. We may ask for reasonable evidence that you control the account before acting on a request.

We will publish policy updates on this page with a revised effective date. Material new uses of Google account data will require appropriate notice and consent before they begin.