Privacy Policy for Emerge
Emerge is a personal local-first software system used to develop, validate, and operate software-assisted capabilities for the account holder. This policy explains how Emerge accesses and uses Google user data.
Information Accessed
When authorized by the user, Emerge may access Gmail account data, including mailbox metadata, message content, drafts, labels, filters, and related account settings required for the Gmail capabilities being developed or used.
How Information Is Used
Emerge uses accessed data only for the following purposes:
- to read and interpret mailbox state for user-directed workflows
- to support message review, drafting, sending, and organization
- to develop, validate, and improve authorized Gmail capabilities
- to operate local or user-controlled email management workflows
Data Sharing
Emerge does not sell Google user data. Google user data is not shared with third parties except when necessary to operate infrastructure explicitly chosen and controlled by the developer or user.
Data Storage
Emerge is designed primarily for local-first operation. Depending on the workflow being used, authorized data may be processed or stored in local artifacts, local development environments, or user-controlled systems for capability validation, debugging, and operation.
Data Retention and Deletion
Authorized data is retained only as long as necessary to support the intended workflow, validation process, or user-requested operation. Users can revoke Google account access at any time through their Google account permissions settings.
Security
Emerge uses developer-controlled and user-controlled storage, credentials, and access boundaries. Sensitive credentials and tokens are kept outside source control and are intended to remain in local, access-controlled storage.
Contact
For questions about this policy or Emerge's Google API usage, contact the developer through the support email configured in Google Auth Platform.
Return to the project homepage: miaobinlien.com/projects/emerge