Last updated: September 2026. This notice describes how the Halo integration accesses and handles Google account data.
Halo only accesses data that its owner, Edward Luo, explicitly authorizes through Google's OAuth consent screen. This may include:
No data from other Google services is accessed unless explicitly granted.
Data is used only to answer the owner's own requests: summarizing email, preparing meetings, locating documents, drafting replies, and similar personal-assistant tasks. Halo has no advertising, analytics, or commercial use of this data, and the integration is not shared with any third party as a service.
When an AI assistant performs a task, the text it processes — which may include parts of email or documents — is sent to the assistant's model provider under that provider's own terms and privacy policy. The owner's assistants may run on the owner's machines or on servers the owner controls through services he uses. The Google OAuth credentials themselves are stored only in local credential files on the owner's machines and are never committed to source control or shared.
Halo does not maintain its own copy of the owner's mail or documents. Short-lived task logs on the owner's machines may contain snippets of processed content and are cleaned up by the owner. Google remains the system of record for all Google account data.
Review or revoke this integration at any time at Google Account → Connections. Deleting the local credential file at ~/.config/google-workspace/ additionally removes the stored tokens.
Questions: degrluo@gmail.com.