Privacy Policy
What this is
AntibodyLinks Bridge is a private integration operated by AntibodyLinks ("we"). It connects AntibodyLinks' own engineering tools to one Google Drive account that we own. It has no public users and is not offered to anyone else.
Google data we access
The integration requests a single Google permission, the drive.file scope, which Google describes as "See, edit, create, and delete only the specific Google Drive files you use with this app" and classifies as non-sensitive. Under this scope, Google lets an app work only with files it creates and with existing files that the account owner opens with it or chooses to share with it (for example through a file picker). The rest of the Google Drive account stays out of its reach.
Our integration uses less than Google permits. It has no file picker and no "Open with" option. It works with the folders and files it creates itself, and with any folder the account owner has explicitly made available to it as a place to publish. It does not access Gmail, Contacts, Calendar or any other Google service. When a manual health report is run, it also reads the Google account's email address and total Drive storage usage, and uses them only in that report.
What the integration does
- It creates files in a private Drive folder containing AntibodyLinks engineering information: status summaries, progress reports, and records of the team's own software-development sessions.
- It reads messages that the team types into designated documents that the integration itself created in that folder, and it writes short acknowledgements back.
- It never changes sharing settings. Sharing is decided by the account owner directly in Google Drive. Because access to a file follows the folder it is in, the integration may move one of its own files into a folder that is not shared, for example to withdraw that file from the shared folder.
- It never permanently deletes files. Where older files are retired, they are moved to the Google Drive trash, from which the owner can restore them.
Whose information is involved
Only information belonging to the AntibodyLinks team. The integration is not used to collect information from customers, website visitors or the public. Before publication, development records are screened automatically and credentials such as passwords and access keys are redacted.
How Google user data is used and shared
Information is used only to keep the AntibodyLinks team informed about its own engineering work. The Drive folder is shared, read-only, with the team's own accounts. The team may read it through authorized AI providers connected to those accounts, including OpenAI through ChatGPT. When it does, the information the AI provider reads is processed by that provider under its own terms and privacy policy and the settings of the team's account with it; how that provider retains or uses the information is governed by those terms, not by this policy. We do not sell Google user data, use it for advertising, or transfer it to anyone else for their own purposes. We do not use Google user data to develop, improve or train generalized artificial-intelligence or machine-learning models.
AntibodyLinks Bridge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and security
The authorization that lets the integration reach Google Drive is stored only in the protected credential store of the computer that runs it. It is never written into code, logs or published files. Published files are held in Google Drive under Google's own security.
Retention
Files remain in the Drive folder until the account owner removes them, except that daily transcript folders are moved to the Drive trash after seven days.
Your choices
The account owner can withdraw the integration's access at any time at myaccount.google.com/permissions. After that, the integration can no longer read or create any files.
Changes
If this policy changes, the updated version will be posted on this page with a new effective date.