Privacy Policy

WHAT INFORMATION WE COLLECT

We collect information you provide and information generated when you use the hosted Service:

• Account information — name, email, organization, and authentication identifiers when you sign up or sign in.
• Integration information and credentials — connected workspace, channel, and user identifiers; integration settings; and access tokens, signing secrets, or provider credentials you authorize the Service to store.
• Session metadata — operational metadata about agent runs surfaced in the console, such as agent and channel identifiers, status, timestamps, token counts, tool-call names, and cost. This is used for observability.
• Agent content — messages, relevant conversation history, shared files, prompts, tool results, workspace files, and memory that your configured agents process. Where this content is handled and stored is described below.
• Billing information — if you subscribe to a paid plan, payment details are collected and processed by our payment processor; we do not store full card numbers.
• Usage and device data — log data, IP address, browser type, and interactions with the website and console.
• Communications — messages you send us for support or inquiries.

WHERE CREDENTIALS AND AGENT CONTENT ARE PROCESSED

Integrations configured through the hosted Service store their credentials encrypted in the control plane. The Service supplies the credentials needed by the daemon or relay responsible for that integration. Credentials configured only on your own daemon remain under your control.

The daemon processes conversations and runs agents. It may retain session transcripts, tool results, workspace files, and runtime state. With your own daemon, that storage is on infrastructure you operate. With Cloud execution, it is on infrastructure operated for the Service. Relevant content is sent to the model providers and tools configured for the agent.

The control plane stores configuration, operational metadata, and encrypted credentials. Authorized console and API operations can retrieve conversation or workspace content from the daemon without persisting those transcripts or workspace contents in the control-plane database. Memory and organization knowledge configured for control-plane storage are stored there.

For integrations that use a relay, inbound content passes through the relay to the responsible daemon without being persisted by the relay.

SLACK DATA AND AI PROVIDERS

When you connect Slack, agents can process messages, conversation history, files, and other Slack content available through the permissions granted to the app. This content can be included in prompts and tool results sent to the selected model provider and retained in agent transcripts or configured memory.

AgentConnect does not use Slack data to train its own AI models. Model providers and connected tools have their own processing, retention, and location policies, which depend on the provider, account, and settings your organization selects. Do not configure providers or tools to use Slack data for model training.

AI-generated responses may be inaccurate or incomplete. Review outputs and proposed actions before relying on them, especially for consequential decisions.

GOOGLE USER DATA

This section covers the data AgentConnect receives from Google when you sign in with Google or use the AgentConnect app in Google Chat.

What we access:

• Google sign-in — your name, email address, profile picture, and Google account ID. We use them to create your AgentConnect account, sign you in, and match your account to your Google Chat identity.
• Google Chat — the messages you send the AgentConnect app, in a direct message or by @mentioning it in a space; the sender's Google Chat user ID, display name, and email address; the space's ID, name, and type; and your Google Workspace customer and domain IDs. With its own app credentials, the app also reads the spaces it has been added to and the membership of the person who connects a Workspace, and posts and edits its own messages. It does not read other messages in a space.

How we use it: to deliver each message to the agent of the AgentConnect organization your Workspace is connected to, and to post the agent's answer back; to connect a Workspace to one organization and confirm that the person connecting it belongs to that Workspace; and to show a direct message in the console only to the person who sent it. To produce an answer, the agent sends the message to the model provider your organization chose.

Storage and retention: the hosted control plane stores the identifiers above — user, space, customer, and domain IDs — and not message contents. Message contents are kept in the conversation's session on the daemon that runs the agent: your own, or the one AgentConnect Cloud runs for your organization. They are retained as your plan and configuration determine, and deleted with the session, the agent, or the organization.

Removing the Google Chat integration from your organization's AgentConnect agent disconnects your Workspace. You can also uninstall the app in Google Chat, and ask us to delete your data at [email protected].

We do not sell Google user data, use it for advertising, or use it to develop, improve, or train generalized AI or machine learning models. AgentConnect's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

HOW WE USE INFORMATION

We use the information we collect to:

• Provide, operate, secure, and improve the hosted Service.
• Authenticate you and maintain your account.
• Display observability, usage, and billing information in the console.
• Communicate with you about the Service, including security and administrative notices.
• Detect, prevent, and respond to fraud, abuse, and security incidents.
• Comply with legal obligations.

LEGAL BASES (EEA/UK)

Where the GDPR or UK GDPR applies, we process personal information on the bases of performance of a contract (providing the Service), our legitimate interests (securing and improving the Service), your consent (where required, such as certain cookies), and compliance with legal obligations.

WHEN AND WITH WHOM WE SHARE INFORMATION

We do not sell your personal information. We share it only:

• With service providers who process data on our behalf (for example, cloud hosting, analytics, and payment processing) under appropriate confidentiality obligations.
• With third-party platforms and model providers that you choose to connect, to the extent needed to operate your integrations.
• When required by law, or to protect the rights, safety, and security of AgentConnect, our users, or the public.
• In connection with a merger, acquisition, or sale of assets, subject to this policy.

COOKIES AND ANALYTICS

We use cookies and similar technologies to keep you signed in, remember preferences, and understand how the website and console are used. You can control cookies through your browser settings; disabling some cookies may affect functionality.

DATA RETENTION

We retain personal information for as long as your account is active or as needed to provide the Service, and thereafter as required to comply with legal obligations, resolve disputes, and enforce our agreements. Operational session metadata is retained according to your plan and configuration.

Session transcripts, runtime state, workspace files, and managed memory follow the retention and deletion settings of the component that stores them. Removing a session does not necessarily remove separately retained workspace files or memory. Uninstalling the Slack app or disconnecting an integration does not by itself erase previously stored content.

For access, transfer, or deletion requests involving data held by the hosted Service, contact [email protected]. Include the relevant account or workspace so we can identify the data and verify the request. For data held on your own infrastructure or by a connected provider, contact the operator or provider responsible for that copy.

HOW WE KEEP INFORMATION SAFE

We use technical and organizational measures designed to protect information, including encryption in transit, encryption of stored integration credentials, and access controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. You are responsible for securing infrastructure you operate and for the access you grant to agents, integrations, and model providers.

YOUR PRIVACY RIGHTS

Depending on where you live, you may have the right to access, correct, delete, or port your personal information, and to object to or restrict certain processing. Residents of the EEA, UK, and California (among others) may have specific rights, including the right not to be discriminated against for exercising them.

To exercise these rights, contact us at [email protected]. You can also review and update much of your account information directly in the console.

INTERNATIONAL TRANSFERS

We may process and store information in countries other than where you live. Where required, we use appropriate safeguards, such as standard contractual clauses, for cross-border transfers.

CHILDREN

The Service is not directed to children under 18, and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.

CHANGES TO THIS POLICY

We may update this Privacy Policy from time to time. When we make material changes we will update the "Last updated" date above and, where appropriate, provide additional notice.

CONTACT

Questions or requests regarding this policy? Contact us at [email protected].