Plain-English data handling summary.

Last updated: June 9, 2026. This page is a public summary, not a substitute for a signed DPA, security questionnaire, procurement packet, or custom agreement.

Public website

The public website is primarily a company, product, pricing, trust, and routing product. It is not intended for submitting confidential operational data, passwords, access tokens, private keys, regulated data, or customer secrets.

Support email

Support inquiries may include contact information, organization names, user roles, screenshots, logs, billing context, or account details provided by the sender. Do not include secrets or regulated data in ordinary email unless specifically instructed through an appropriate secure channel.

TAHAI Operational Intelligence

Operational Intelligence is the flagship product for MSP operating context. Access should be assigned according to organization membership, role, work need, product entitlement, and the customer’s own governance requirements. Executive, finance, service, client, project, evidence, and trust views should be reviewed for appropriate visibility before sharing or exporting.

TAHAI PSA

TAHAI PSA is a live service-workflow product. Service tickets, approvals, project status, client questions, evidence, and workflow context may contain operationally sensitive information and should be handled according to least-access needs.

TAHAI IT Docs

TAHAI IT Docs is designed for IT documentation, operational records, client-facing approved materials, procedures, handoffs, and related account workflows. Access should be assigned according to least-access needs and the work a user is actually performing.

Owner and Staff users

Owner and Staff accounts are billable internal seats in IT Docs. Any user doing internal operational work must be Owner or Staff and must consume a billable internal seat. Equivalent operational access in OI or PSA should be assigned only to users who need it.

Client View users

Client View is read-only, allowance-based, and limited to approved client-facing material. Client View cannot create, edit, delete, invite users, manage members, access billing, access passwords or secrets, view internal docs or projects, toggle visibility, export organization data in bulk, run automation, or perform internal staff work.

Client View allowance

Core IT Docs includes 25 read-only Client View users per organization, or 5 Client View users per paid internal seat, whichever is higher. Larger client portal rollouts, approval workflows, evidence sharing, notifications, PSA-linked collaboration, or OI-connected client workflows may require a higher plan or separate product terms.

Customer responsibilities

Customers are responsible for assigning the right user roles, approving only appropriate client-facing material for external visibility, removing access when no longer needed, and avoiding submission of secrets through unsupported channels.

Formal procurement

Enterprise customers that require a formal DPA, security questionnaire, vendor review, or contract-specific data terms should email [email protected].