Privacy Policy

1. Information We Collect

Information you provide

We collect information you provide directly, including contact requests, account registration details, support messages, onboarding answers, signup access requests, tenant settings, policy configuration, approval decisions, redaction settings, and other information submitted through the website or portal.

Website contact information

When you contact botYguard through the website, we collect details needed to respond, such as request category, name, work email, organization, role, organization type, organization size, website, expected agent scale, procurement stage, workflow or use case, current stack, and whether you asked to receive a copy of the request.

Account and portal information

The portal may process account email, password hashes or OAuth identity information, tenant memberships, browser session information, authentication events, security events, and administrative activity.

Product and integration information

botYguard processes product data needed to govern agents, including agent profiles, policies, approvals, audit logs, usage events, tool-call events, chat or thread messages, redaction placeholders, provider credentials, secrets, Google Workspace connection email and scopes, encrypted Google refresh-token metadata, Discord installation and channel metadata, and integration configuration.

Technical information

We may collect technical information such as IP address, browser or device details, request identifiers, timestamps, logs, error information, performance information, usage events, security signals, and analytics information from Cloudflare Web Analytics.

2. How We Use Information

• Provide, secure, operate, maintain, troubleshoot, and improve botYguard.
• Authenticate users, manage sessions, maintain tenant membership, and enforce role-based access.
• Evaluate policy, approval, redaction, secret, credential, and integration rules before agent actions run.
• Operate configured workflows for Google Workspace, Discord, model providers, hosted agents, and MCP-connected agents.
• Send contact, transactional, verification, support, security, and operational messages.
• Detect, investigate, and prevent fraud, abuse, unauthorized access, policy violations, security incidents, and service misuse.
• Maintain audit evidence, support compliance reviews, debug failures, and report usage or operational analytics.
• Comply with legal obligations, enforce terms and policies, and protect the rights, safety, and security of botYguard, users, and third parties.

3. How We Share Information

We share information with service providers and connected systems only as needed to provide, secure, support, and improve botYguard. The public website uses Cloudflare for hosting, email-related services, and Web Analytics.

If you configure integrations, botYguard may exchange information with identity providers, Google Workspace, Discord, model providers, MCP clients, hosted runtime providers, or other connected systems to perform the requested and policy-authorized workflow.

We may also disclose information if required by law, to protect rights and safety, to investigate abuse or security incidents, or in connection with a merger, acquisition, financing, reorganization, or similar transaction. We do not sell personal information.

4. Retention

We retain information for as long as reasonably necessary for the purposes described in this policy, including to provide botYguard, maintain accounts and tenant configuration, operate integrations, preserve security and auditability, troubleshoot issues, enforce terms and policies, comply with legal obligations, resolve disputes, and protect against fraud, abuse, or unauthorized use.

Retention periods may vary based on the type of information, sensitivity, customer configuration, operational need, legal requirements, security risk, backup cycles, and whether the information is needed for audit, compliance, investigation, or dispute-resolution purposes.

5. Security

botYguard is designed around tenant boundaries, scoped permissions, policy enforcement, approvals, audit trails, and secret protection. Provider credentials, agent secrets, and Google refresh tokens are stored encrypted where the service persists them. Browser sessions use secure cookies and CSRF protection. Redaction controls can reduce the private context exposed to agents and model providers.

No system is perfectly secure. You are responsible for keeping your account, users, integrations, credentials, provider accounts, connected agents, and workflows configured appropriately for your use case.

6. Your Controls and Choices

Tenant administrators can manage users, policies, integrations, provider credentials, agent access, secret bindings, redaction settings, approvals, and relevant workflow configuration in the portal. You may also be able to revoke integration access through the connected provider.

You can contact us about privacy questions, account-related requests, or data concerns at info@botyguard.ai. We may need to verify your request and may retain information where necessary for security, audit, legal, or operational reasons.

7. Children

botYguard is intended for business and organizational use. It is not directed to children, and children should not create accounts or use the service.

8. Changes to This Policy

We may update this Privacy Policy as botYguard, our integrations, our security practices, or applicable requirements change. The effective date above shows when this version became effective.