Privacy Policy
This Privacy Policy explains how Busby Adams Equity LLC ("Busby Adams," "we," "us," or "our") collects, uses, stores, discloses, and protects information when you use the Busby Adams AI platform, including its website, AI agents, modules, Google sign-in, Google Workspace integrations, and related services (collectively, the "Service").
The Service can connect to Google services only after an authorized user grants the requested permissions. The Google data available to an AI agent depends on the scopes approved for that agent and the tools enabled by the platform administrator.
1. Information We Collect
Account and identity information
When you sign in with Google, we may receive your Google subject identifier, name, email address, profile information, hosted-domain indicator, and confirmation that your email address was verified. We use this information to authenticate you, associate you with the correct customer website instance, determine your account category and permissions, and display your identity in the Service.
Google user data
If you authorize an AI agent to use Google Workspace capabilities, the Service may access data from the Google services selected for that agent. Depending on the configuration and permissions you approve, this may include Gmail messages and labels, Google Drive files and folders, Google Calendar events, and Google Chat messages. Some configurations may permit creating or changing content, such as creating Drive files or folders, modifying email labels, or creating or updating calendar events.
The Service requests Google permissions by service. The current platform can be configured to request scopes that allow Gmail modification and label management, Google Drive access, Google Calendar access, and Google Chat message access. An individual customer instance or agent may enable fewer services or deny specific tools even when a broader Google scope has been granted.
Conversations and AI content
We collect prompts, messages, AI responses, tool requests and results, session identifiers, project identifiers, and related metadata needed to provide conversations and agent-assisted workflows.
Memories, tasks, and module records
The Service may store long-term memories derived from eligible user statements, durable tasks, schedules, triggers, project records, solution artifacts, workflow status, and other records created through enabled modules. The Service is designed not to save passwords, access tokens, or other authentication secrets as long-term AI memories.
Technical and security information
We may collect request identifiers, timestamps, IP and proxy information present in server logs, browser and device information, authentication events, errors, service health information, and audit information used to operate and secure the Service.
2. How We Use Information
We use information to:
- authenticate users and maintain secure sessions;
- provide AI chat, agent, module, task, memory, and workflow functionality;
- execute user-requested actions through authorized tools;
- retrieve relevant Google content and present it to the requesting user or authorized AI agent;
- create or update Google content when the user requests an action and the applicable tool is enabled;
- maintain conversation context, user preferences, project context, and durable work products;
- operate, monitor, troubleshoot, protect, and improve the Service;
- enforce permissions, customer-instance boundaries, acceptable-use requirements, and security controls; and
- meet legal, regulatory, and contractual obligations.
3. AI Processing
Information you submit, information retrieved by authorized tools, and relevant stored context may be included in prompts sent to the AI model or delegated AI service selected by the customer instance. AI-generated output can be inaccurate and may reflect information supplied to it. Users should review output before relying on it or using it to take consequential action.
The platform may use locally hosted models and may also use separately configured external AI providers for bounded delegated work. When an external provider is enabled, information necessary to complete the delegated request may be transmitted to that provider under the customer instance's configuration and the provider's terms.
4. How We Share Information
We may disclose information:
- to service providers and subprocessors that host, secure, maintain, or support the Service;
- to Google when necessary to authenticate users, exchange OAuth credentials, or call Google APIs and Google Workspace MCP services;
- to configured AI model, source-control, search, storage, or integration providers when a user or authorized agent uses that capability;
- to the customer organization that operates the applicable website instance and its authorized administrators;
- when directed or authorized by the user;
- to protect rights, security, property, users, or the Service; or
- when required by law, legal process, or a valid governmental request.
We do not sell Google user data. We do not use Google user data for advertising. We do not permit humans to read Google user data except when the user has affirmatively shared it, when necessary for security or support with appropriate safeguards, when required by law, or when the data has been aggregated or anonymized for permitted internal operations.
5. Google API Services User Data
Our use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google access tokens and refresh tokens are used only to provide the authorized Google integration. Refresh tokens are encrypted at rest by the Service. Tokens are not displayed to AI models or users and are not stored in source code.
6. Legal Bases
Where applicable law requires a legal basis, we process information as necessary to provide the Service and perform our agreement with the user or customer, based on consent for optional integrations, for our legitimate interests in operating and securing the Service, and to comply with legal obligations.
7. Data Retention
We retain information for as long as reasonably necessary to provide the Service, maintain security and audit records, satisfy customer configuration, and meet legal obligations. Retention periods may differ by customer website instance, account category, module, and record type.
- Guest sessions may be deleted when the session is completed.
- Authenticated guest sessions may be retained for a limited period configured by the customer instance.
- Authenticated workspace-user data may be retained until deleted or until a configured retention policy applies.
- OAuth credentials remain until revoked, replaced, deleted, or made unusable.
- Project artifacts and module records may be retained as business records until an authorized user or administrator deletes or retires them.
Backups may retain deleted information for a limited period until overwritten under normal backup rotation.
8. Security
We use administrative, technical, and organizational safeguards appropriate to the Service, including encrypted HTTPS connections, secure cookies, encrypted OAuth refresh tokens, restricted secrets, container and network segmentation, least-privilege access controls, internal service credentials, and server-side authorization. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
9. Your Choices and Rights
Depending on your location and relationship with the customer organization, you may have rights to request access, correction, deletion, restriction, portability, or objection. You may also:
- sign out of the Service;
- delete eligible memories through Memory Management;
- ask an administrator to correct or disable your customer-instance account;
- revoke the application's Google access from your Google Account security settings; and
- contact us to request deletion of OAuth credentials and associated personal information, subject to retention obligations.
Revoking Google access prevents future Google API access but may not automatically delete information already stored in project records, conversations, audit logs, or backups. Contact us if you also want stored information reviewed for deletion.
10. Customer Website Instances
The Service supports separately configured customer website instances. The customer operating an instance determines its branding, enabled modules, authorized agents, user assignments, integrations, and certain retention settings. A customer-specific privacy policy should be published with each instance. If your account is provided by an organization, that organization may have additional policies governing your use of the Service.
11. Children's Privacy
The Service is intended for business and authorized adult use and is not directed to children under 13. We do not knowingly collect personal information from children under 13 through the Service.
12. International Processing
Information may be processed in the United States and in other locations where configured service providers operate. Those locations may have data-protection laws different from those in your jurisdiction.
13. Changes to This Policy
We may update this Privacy Policy to reflect changes to the Service, integrations, law, or data practices. We will update the effective date and provide additional notice when required.
14. Contact Us
For privacy questions, Google data deletion requests, or requests concerning your information, contact:
Busby Adams Equity LLC
Email: michael@busby-adams.com
Website: https://aidev.busby-adams.com/