Google User Data Transparency
Privacy Policy
1. Who operates this application
Dot Attention Bridge is a privately operated application used by its owner for personal market research and workflow automation. It is not offered to the public. Contact the application support address shown below for questions about this policy.
2. What Google data may be accessed
Subject to the permissions approved by the owner, the integration can access Google Drive files and associated metadata, such as file names, IDs, timestamps, and contents. The files involved may include research summaries, market data, chart images, task snapshots, and results generated by the owner's tools.
The integration may use the drive.file scope for files it creates or opens through the application and, where required to access pre-existing Drive resources, the broader Google Drive scope. Actual access depends on the OAuth consent granted.
3. Why and how the data is used
Data is accessed solely to carry out the owner's selected workflows: locating and retrieving research files, preparing data snapshots, transmitting relevant research materials to configured automation tools, and creating or updating output files in Google Drive.
4. Where data may be processed and shared
Depending on the workflow, selected files and associated metadata may pass through or be processed by the owner's local computer, personally configured cloud server, Google Drive, and automation or AI services explicitly configured by the owner (including the connected personal assistant workflow). The operators of those services may process submitted data according to their applicable policies.
Google user data is not sold, distributed for advertising, or shared with unrelated data brokers. Data transfers are limited to services needed to perform the owner's authorized workflow.
5. Storage and retention
OAuth credentials are stored in the owner's configured credential storage. Copies of research files, operational logs, and generated artifacts may remain in local, cloud, or Google Drive storage, subject to the owner's system configuration and cleanup practices. No universal automatic deletion period is promised. The owner controls removal of locally stored and Drive-hosted research data to the extent permitted by the systems in use.
6. Access control and revocation
Only accounts deliberately authorized by the owner are intended to use the integration. The owner can revoke Google access using Google Account security settings, disable connected automation workflows, and delete stored output files or credentials in the configured environments. Revoking Google access stops future authorized Drive API operations but may not automatically erase previously created local or cloud copies.
7. Security
The integration is intended to keep OAuth secrets out of its public website and to use HTTPS for web links. As with any locally operated or self-managed service, security depends on the owner's configuration, credential protection, and software maintenance.
8. Changes to this policy
Changes to the integration's data access, processing, or storage practices should be reflected in an updated version of this policy. The effective date at the top will be revised as needed.
9. Contact
For questions about this policy, contact lingfengzhang03@gmail.com.