Privacy Policy

Effective Date: February 10, 2026  |  Last Updated: February 10, 2026

This Privacy Policy describes how Ag2Trust ("we," "us," or "our") collects, uses, and protects information when you use our platform, APIs, dashboard, and related services (collectively, the "Service"). It applies to our customers ("you" or "Customer"), their authorized users, and visitors to our website.

Ag2Trust is a business-to-business (B2B) AI agent orchestration platform. The Service is currently offered to customers in the United States. Our customers are businesses that deploy AI agents for their own end users. If you are an end user interacting with an agent powered by Ag2Trust, your relationship is with the business that deployed that agent, and their privacy policy governs that interaction.

Beta status: The Service is currently in beta. We have built and operate the privacy and security controls described in this policy in good faith, but they are provided on a best-effort basis. Automated protections such as PII redaction and content moderation may not catch every instance of sensitive or harmful content in every format. We are continuously improving these systems. Nothing in this policy should be read as a guarantee of absolute protection, and this policy should be read alongside our Terms of Service, which contains important disclaimers and limitations of liability.

1. Our Role: Processor vs. Controller

We wear two hats depending on the type of data:

• Data Controller for account data we collect directly from you (your name, email, billing information, and website usage data). We decide how and why this data is processed.
• Data Processor for customer content — the conversations, knowledge base documents, agent configurations, and any end-user data that flows through your agents. You (the Customer) are the data controller for this content, and we process it solely to provide the Service under your instructions.

LLM providers (such as OpenAI, Anthropic, or AWS Bedrock) act as subprocessors when they process prompts and generate responses on your behalf. Their data practices are governed by their own terms.

If you require a formal Data Processing Agreement (DPA) for your organization's compliance needs, please contact privacy@ag2trust.com.

2. Information We Collect

2.1 Account Information

When you register for the Service, we collect:

• Identity: First name, last name, email address
• Organization: Company name, organization contact email
• Authentication: We use Firebase Authentication to manage sign-in. We store your Firebase user identifier but do not store passwords directly — Firebase handles credential management
• Role and permissions: Your role within your organization (owner, admin, member, or viewer)

2.2 Billing Information

Payment processing is handled entirely by Stripe. We do not store credit card numbers or bank account details. We do store:

• Your Stripe customer identifier (to link your account to Stripe)
• Subscription tier and billing mode (metered or monthly)
• Usage records for billing purposes (agent-hours, token usage)
• Billing status (active, past due, canceled, etc.)

2.3 Customer Content

As part of providing the Service, we process content that you and your end users provide:

• Conversations: Messages between end users and your AI agents, including agent responses
• Knowledge base: Documents and text snippets you upload for agent context (PDFs, text files, etc.)
• Agent configuration: System prompts, tool settings, variable definitions, and agent type configurations
• Drafts: Staged content (emails, documents) created by agents before sending
• Feedback: Ratings and optional comments on agent responses

2.4 Credentials You Provide

To connect your agents to LLM providers, external tools, and integrations, you provide API keys and credentials. These are encrypted using per-customer KMS keys (AES-256-GCM envelope encryption) and are never stored in plaintext. See Section 8 for details.

2.5 Usage and Analytics Data

We collect usage information to operate and improve the Service:

• Platform usage: Agent runtime events (start, stop, error), token consumption, tool call counts, and API request metadata
• Website analytics: We use Google Analytics (GA4) within our application dashboard to understand usage patterns. Google Analytics collects de-identified data including pages visited, session duration, and general device/browser information. Google Analytics uses cookies to distinguish users — see Section 10
• Login activity: Timestamps of your most recent login

2.6 Audit Logs

We maintain two categories of audit logs for security and compliance:

• Agent audit logs: Records of agent inputs and outputs, with automatic PII redaction applied (see Section 6). Content is encrypted using your customer KMS key. Retention is configurable from 7 to 365 days depending on your tier.
• Compliance audit logs: Records of administrative and security-relevant actions (account changes, credential updates, policy modifications, API key management). These logs may include the IP address and user agent of the person who performed the action. They contain no conversation content and are retained for 7 years for legal and compliance purposes.

2.7 Waitlist and Inquiry Data

If you join our waitlist or submit an inquiry, we collect your name, email, company name, and use case description.

3. How We Use Your Information

We use the information we collect for the following purposes:

We do not use your customer content (conversations, knowledge base documents, agent prompts) to train models, for advertising, or for any purpose other than providing the Service to you.

4. How We Share Information

We do not sell your personal information. We share data only in these circumstances:

4.1 Subprocessors

We use the following third-party services to operate the platform:

4.2 LLM Providers (Customer-Configured)

When your agents process conversations, prompts and context are sent to the LLM provider you configured (e.g., OpenAI, Anthropic, AWS Bedrock). These providers act as subprocessors for your customer content. You choose which provider to use and provide your own API credentials. Each provider's data handling is governed by their own terms of service — once data leaves our platform and reaches a provider, we have no control over how that provider processes, stores, or retains it. We encourage you to review your chosen provider's privacy and data policies before configuring your agents.

4.3 Legal Requirements

We may disclose information if required by law, regulation, legal process, or governmental request. We will notify you of such requests when legally permitted.

4.4 Business Transfers

In the event of a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you before your information becomes subject to a different privacy policy.

5. Data Retention

We retain different types of data for different periods:

Automated cleanup jobs run daily to enforce these retention periods. When you delete your organization, all associated data (agents, conversations, documents, credentials, audit logs) is deleted. Compliance audit logs are retained for the legally required period after account closure.

6. PII Redaction

We operate a centralized PII (Personally Identifiable Information) redaction service that automatically detects and redacts sensitive data from audit logs. The types of information redacted include email addresses, phone numbers, Social Security numbers, credit card numbers, and IP addresses.

PII redaction is designed to reduce exposure of sensitive data in stored logs. However, it is not guaranteed to catch every instance of sensitive information in every format. You remain responsible for configuring your agents appropriately and instructing your end users not to share prohibited data types.

How the PII service behaves when unavailable:

• Inbound messages (end user to agent): Blocked with a service error. We will not process unredacted user input if the PII service is down.
• Outbound messages (agent to end user): Delivered without redaction. We prioritize availability of agent responses.
• Audit log writes: Blocked. We never write unredacted PII to audit logs. A placeholder is stored instead.

7. Content Moderation

We operate a toxicity detection service that scores agent responses for harmful content. This is an automated system designed to flag potentially harmful outputs before they reach end users.

Important limitation: If the toxicity service is unavailable, content passes through to end users without moderation. This is an intentional design decision — we prioritize availability of agent responses over blocking them when the moderation system is temporarily down. We monitor for service outages and work to restore moderation quickly, but during outages there is a window where unmoderated content may be delivered.

Content moderation is a supplementary safety measure, not a guarantee. You remain responsible for configuring your agents' system prompts and instructions to produce appropriate outputs for your use case.

8. Data Security

We implement technical and organizational measures to protect your data:

• Encryption at rest: Customer credentials and sensitive content are encrypted using per-customer AWS KMS keys with AES-256-GCM envelope encryption. Each customer has their own master key — there is no shared encryption key.
• Encryption in transit: All data in transit is protected with TLS 1.2 or higher, including internal service-to-service communication.
• Container isolation: Each agent runs in an isolated Docker container with non-root execution, a read-only application directory, and an isolated workspace.
• Network segmentation: Internal services (database, cache, audit) are on a private network not directly accessible from the internet.
• Access control: Role-based access control (RBAC) enforces permissions at every API endpoint. All database queries are scoped by customer to prevent cross-tenant data access.
• Audit logging: Security-relevant actions are logged to an append-only compliance audit log with 7-year retention.
• API key security: API keys are stored as irreversible bcrypt hashes. We cannot retrieve your API key after creation — only you have the original value.

For detailed technical information, see our Security Documentation.

To report a security vulnerability, contact security@ag2trust.com. We target a 2-business-day initial response.

9. Data Breach Notification

If we become aware of a security breach that results in unauthorized access to your personal information or customer content, we will:

• Notify affected customers by email without unreasonable delay. Our target is within 72 hours of confirming the breach, though actual timing may depend on the scope and complexity of the incident
• Describe the nature of the breach, the types of data involved, and the measures taken or proposed to address it
• Provide a point of contact for follow-up questions
• Notify relevant authorities as required by applicable law

As a data processor, we will assist you in meeting your own breach notification obligations to your end users or regulators. Our compliance audit logs provide a forensic record of system actions that can support breach investigation.

10. Cookies and Tracking

We use a limited number of cookies and similar technologies:

We do not use advertising cookies, retargeting pixels, or social media tracking scripts. Google Analytics data is not combined with data from other Google services to serve ads.

You can opt out of Google Analytics by installing the Google Analytics Opt-out Browser Add-on, or by configuring your browser to block third-party cookies.

11. Your Rights and Choices

Depending on your jurisdiction, you may have certain rights regarding your personal information:

• Access: Request a copy of the personal information we hold about you
• Correction: Update or correct inaccurate information through your account settings or by contacting us
• Deletion: Delete your organization and all associated data through the dashboard, or request deletion by contacting us
• Data export: Request an export of your data by contacting us before account deletion
• Opt out of analytics: Disable Google Analytics using the opt-out add-on linked above

For end users: If you are an end user of a business that uses Ag2Trust, please direct privacy requests to that business. They are the data controller for your information. We will assist our customers in responding to valid data subject requests.

California residents: Under the California Consumer Privacy Act (CCPA/CPRA), you have the right to know what personal information we collect and how it's used, to request deletion, and to not be discriminated against for exercising these rights. We do not sell personal information or share it for cross-context behavioral advertising. To exercise your rights, contact privacy@ag2trust.com.

12. Children's Privacy

The Service is a B2B platform intended for use by businesses. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us and we will delete it.

13. Third-Party Links and Services

The Service may contain links to third-party websites or integrate with third-party services (LLM providers, MCP servers, custom tool webhooks) that you configure. We are not responsible for the privacy practices of these third parties. We encourage you to review their privacy policies.

14. Where Your Data Is Processed

The Service is hosted on infrastructure located in the United States. Your data is processed and stored in the US. Our subprocessors (Firebase, Stripe, AWS KMS, Google Analytics) are US-based companies and may process data in the US or other jurisdictions in accordance with their own privacy policies. By using the Service, you acknowledge that your data will be processed in the United States.

15. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email or a notice on the dashboard at least 30 days before taking effect. The "Last Updated" date at the top of this page reflects the most recent revision. Continued use of the Service after changes take effect constitutes your acceptance of the updated policy.

16. Contact Us

If you have questions about this Privacy Policy or our data practices:

• Privacy: privacy@ag2trust.com
• Security: security@ag2trust.com
• General: hello@ag2trust.com

By using Ag2Trust, you acknowledge that you have read and understood this Privacy Policy. This policy should be read alongside our Terms of Service.