AI, MCP, Service Account, and Automation Terms

Effective Date: June 30, 2026 Entity: Privatica, Inc. Mailing Address: 2810 N Church St STE 89170, Wilmington, DE 19802, United States Primary Site: https://thetam.app

These terms supplement the Terms of Service for use of TAM automation, MCP-compatible interfaces, service accounts, agents, tool execution, and AI-assisted functionality.

1. Responsibility for Automated Actions

You are responsible for actions taken through your users, service accounts, API tokens, MCP clients, automations, agents, and integrations.

You must configure least-privilege scopes and review actions before granting write access.

2. No Autonomous High-Risk Use Without Review

You must not rely on TAM automation or AI-assisted outputs as the sole basis for legal, financial, medical, employment, housing, insurance, credit, immigration, public-benefit, security-critical, safety-critical, or similarly high-impact decisions.

Human review is required where outputs may affect rights, safety, money, employment, compliance, or security.

3. Tool Calls and Audit Records

TAM may record:

• service account ID;

• principal ID;

• client ID;

• workspace/project identifiers;

• tool name;

• authorization decision;

• denial reason;

• input/output hashes;

• timestamps;

• completion status;

• audit events;

• related issue/wiki/GitHub resource references.

These records are used for security, accountability, support, troubleshooting, and compliance.

4. MCP Credentials

You must protect MCP credentials and service-account secrets. Do not commit secrets to repositories, share them in tickets, or expose them to browser clients.

If credentials are compromised, revoke them immediately and contact security@thetam.app.

5. Output Limitations

AI or agent-assisted outputs may be inaccurate, incomplete, outdated, unsafe, or unsuitable. You must validate outputs before acting on them.

6. Integration Boundaries

Connected tools may have their own permissions, limits, errors, and terms. TAM cannot guarantee third-party tool availability or correctness.

7. Suspension

We may suspend automation, MCP, service accounts, or integrations if they create security, legal, abuse, operational, or platform risk.