Privacy Policy
This policy describes FX Bridge Result Return, a personal local application under development, and its informational website. The return integration has not yet been enabled for unattended use.
Google data accessed and its purpose
The return component requests drive.file, which covers files the application creates or that you explicitly open or share with it through a supported picker. It is designed to check the selected return folder's identity and access, inspect relevant result-file metadata for duplicate prevention, and create new bridge-generated result files there. It does not request full-Drive access.
The separate queue reader uses its own read-only authorization to retrieve configured queue metadata and job contents. That authorization is not combined with the return credential. Approved queue instructions are passed to Codex for processing. A local launcher does not imply that model processing stays on the computer: instructions may be sent to the configured Codex service. This website does not publish queue contents.
Local storage and retention
The credential storage implementation uses Windows Credential Manager, with separate entries for the reader and return component. The reader has been authorized; return authorization and unattended result delivery are not yet enabled. Local bridge records retain job identifiers, processing states and result-file identifiers for duplicate prevention. Locally generated artifacts remain on the operator's computer unless explicitly returned or otherwise handled by the operator.
There is no implemented automatic deletion schedule for those local records or artifacts. Returned files remain in the selected Drive folder until the operator manages them. The intended return component does not delete existing Drive files.
Transfer and sharing
Authorization and authorized Drive requests communicate with Google. The result-return design sends generated result artifacts to the operator's selected Drive folder; it does not change file sharing permissions. Actual visibility depends on the folder's and files' Google Drive permissions. Credentials are not intended to be included in result artifacts or diagnostic output.
This website has no forms, application login, analytics scripts, external font requests or browser storage code. When hosted, the hosting provider may process ordinary request information, such as IP addresses, according to its own policies. No claim is made that hosting requests are never logged.
Revoking access and managing data
You can revoke application access through your Google Account's third-party connections settings. Revocation does not automatically remove previously created Drive files or local bridge records. Manage Drive files in Google Drive and local data on your computer. Removing duplicate-prevention records can invalidate the bridge's operational safety checks.
Questions and changes
For privacy questions, contact support@fxanalysisbridge.com. This policy must be reviewed when the application's data handling changes, before enabling the changed behavior.