Privacy notice · Gmail internal pilot
How Hoop handles Google user data
Hoop uses Google account data only to provide the features you request. Signing in does not grant Gmail access. Gmail access begins only after you choose Connect Gmail, review the disclosure, and approve the Gmail read-only scope at Google.
Gmail task capture
Hoop examines qualifying Inbox and Sent messages to identify possible tasks. Deterministic filters exclude bulk, automated, no-reply, draft, spam, and other unlikely task sources before body or model processing where possible. Attachments, inline images, tracking content, and raw RFC 822 messages are not sent to the model.
Bounded normalized message text and limited prior-thread context may be processed by OpenAI through its API with response storage disabled. Gmail data is not used for ads, sold, transferred to data brokers, or used to train a generalized model by Hoop.
Storage, visibility, and deletion
Gmail source content and derived tasks are private to the connecting user. Normalized message content is retained for no more than seven days, then automatically redacted. Minimal exact evidence may remain with a derived task for as long as that task exists.
Disconnect Gmail stops new processing and deletes Hoop's encrypted refresh credential. Delete Gmail data additionally redacts retained content, removes Gmail evidence, and deletes tasks whose only source is Gmail. You can also revoke Hoop in Google Account security settings.
Google Workspace Limited Use
Hoop's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Human access is limited to security, legal, or explicit support cases where permitted and is auditable.
The internal pilot is limited to allowlisted test users. Public availability remains blocked until Google restricted-scope verification and the required security assessment are complete.