Privacy policy

Belong is an agent and automation service powered and operated by Belong Universe. In this policy, “we,” “us,” and “our” refer to Belong Universe as the operator of the service. This policy covers Belong account access, Console and Insights, and optional connected-service features available to your organization.

1. Account information and sign-in

When you sign in with Google, Belong requests basic identity information: your email address, account identifier, and profile information such as your name. We use this information to identify you, link an invited account, establish a session, and enforce organization access. Staff access may instead use an identity-aware access gateway. We retain identity, membership, session, and access-audit records to operate and protect these features.

Browser session cookies keep you signed in. Signing in with Google does not by itself give Belong access to your Gmail, Drive, Calendar, or Google Chat content. Connected-service access depends on the connections and permissions you authorize.

2. Google data we access through optional connections

You choose which connector to add and review the permissions requested. Depending on the enabled feature and granted permissions, the service may access:

• Gmail: messages, threads, headers and metadata, labels, drafts, and related mailbox state needed to search and read threads, create drafts, send email, and label or unlabel messages and threads as directed by you.
• Google Drive: files, metadata, permissions, and file content needed to search, read, download, copy, or create files as directed by you.
• Google Calendar: calendar lists, events, attendees, responses, availability, conference details, and related metadata needed to find, create, update, respond to, or delete events as directed by you.
• Google Chat: messages, conversation details, and related metadata needed to search conversations and messages, read messages, and send messages as directed by you.
• Authorization information: OAuth access and refresh tokens, granted scopes, token expiry information, and the connected account identifier.

3. How we use information

We use account and connected-service information to provide and protect user-facing Belong features: answer your requests, execute automations you request or configure, maintain task and conversation continuity, enforce access permissions, prevent abuse, investigate failures, and secure the service.

Depending on your instructions and permissions, this can include creating drafts, sending or labeling email, copying or creating files, managing calendar events, and sending Google Chat messages. Available tools depend on your organization and connected account permissions.

4. AI processing

When you ask the agent to work with connected content, relevant prompts, content, documents, and tool results may be sent to the selected AI model provider to interpret your request and produce the requested result or tool action. OAuth tokens are not included in model prompts.

Google user data is not used by Belong Universe to train general-purpose AI models, and we do not permit our service providers to use it for that purpose. We summarize or transform Google content as part of your requested workflow. We do not build advertising profiles, sell Google data, or use Google data to determine creditworthiness or lending eligibility.

5. Storage and protection

Server-side connector credentials are encrypted at rest and used by the service when calling the connected provider. Some native clients store authorization credentials locally on your device so they can refresh access. Credential storage and sign-out behavior therefore depend on the client or connection you use.

Prompts, relevant tool inputs and results, downloaded task files, conversation history, task events, and audit records may be retained to run, resume, display, troubleshoot, and secure your work. Disconnecting a service does not automatically delete content already retained in that history.

Access is controlled by tenant, user identity, organization permissions, and authorized service roles. Production access is restricted to authorized personnel and service components with a business need. Secrets are excluded from ordinary application and model logs. We use access controls, encryption, monitoring, and incident-response procedures to protect stored data.

6. Sharing and transfers

We share connected-service data when needed to provide the requested feature: with the connected provider to call its authorized API; with infrastructure, storage, monitoring, and AI model providers acting for us under contractual safeguards; with your organization as configured by that organization; for security or abuse investigations; or when required by law. Enabled email-delivery features may send recipient information, message content, and attachments to a delivery provider. Providers and processing locations depend on the feature, selected model, and deployment.

We do not sell Google user data, share it with data brokers, use it for advertising or retargeting, or disclose it for surveillance. Human access to Google user data is prohibited except with your affirmative permission for specific data, when necessary for security, when required by law, or for properly aggregated internal operations as permitted by Google's Limited Use requirements.

7. Google API Services User Data Policy and Limited Use

Belong's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only for prominent, user-facing features that you request or configure, plus the limited security and legal purposes allowed by that policy.

8. Your choices and deletion requests

• Choose which services to connect and review requested permissions.
• Review consequential tool actions when an approval is presented.
• Disconnect an optional connector to remove the credentials stored for that connector and stop future access through it.
• Revoke provider authorization separately through your Google Account connections. Disconnecting a server-side connector does not itself revoke Google's consent grant.

Native-client sign-out may also revoke its provider grant and remove local credentials. Follow the client confirmation and use Google Account settings to manage provider access independently.

To request deletion of account information or Google-derived content in retained conversations, tasks, files, or audit records, email tools@belonguniverse.ai from the associated account. We may retain narrowly required security, legal, or transaction records where applicable and will isolate them from normal product use. There is no single retention period for every feature and record type.

9. Changes and contact

We will update this policy before using Google user data for a materially different purpose and will request new consent when required. Questions, privacy requests, and complaints can be sent to tools@belonguniverse.ai.