AI Trust Summary

This AI Trust Summary is plain-English customer-facing copy that can be used on a trust page, sales deck, or security questionnaire. It does not replace the legal terms.

Your data is yours

Customer Data belongs to the customer. Boo does not sell Customer Data and does not use Customer Data to train generative AI models unless the customer expressly approves. Boo also asks third-party model providers not to train on Customer Data unless the customer expressly approves.

Boo uses the access you give it

Boo works through tokens, API keys, service accounts, connected accounts, scopes, and permissions. If the credential does not have access, Boo does not have access. Customers decide what Boo is allowed to access and do.

Boo learns privately inside your workspace

Boo can remember your processes, decisions, corrections, workflows, schemas, naming conventions, and preferences so it gets better for your company over time. That customer-specific memory is Customer Data, and the skills you build in Boo belong to you, not to Boo.

Boo can still improve as a product

Boo can improve general skills and product quality without copying one customer's private data into another customer's workspace. The general methods Boo learns are non-identifying and do not contain Customer Data, in the same way an office software vendor can ship generic templates without owning your documents.

Boo protects customer data

Boo uses safeguards designed to protect Customer Data, including encryption, access controls, least privilege, logging, monitoring, incident response, and vendor management. Boo limits employee access to Customer Data to personnel with a business need.

Boo routes work intelligently

Boo may choose among different models, tools, and infrastructure based on quality, cost, speed, safety, availability, and task fit. The goal is to complete the task well while avoiding unnecessary expenses.

Boo may use the public web

Boo may use public web information when the task requires current or external information. Public web information may be inaccurate, outdated, or subject to third-party rights, and should be verified before important use.

Boo can make mistakes

Boo is powerful, but it is still AI. Outputs can be wrong. Customers should review new workflows and important outputs, especially before external, regulated, financial, legal, security, or customer-impacting use.

Boo does what you ask, with the access you give it

Boo can take action inside the systems customers connect as required by the tasks and their subtasks. Customers should grant access carefully, maintain backups where appropriate, and review important workflows and outputs before they are used externally or for irreversible, regulated, financial, legal, security, or customer-impacting actions.

You stay in control of AI rules

You decide where and how to use Boo. For decisions or content that fall under AI laws such as the EU AI Act or state automated decision laws, you remain responsible for the required notices, human oversight, and assessments, and we provide information to help.

Boo includes usage controls

Boo is usage-based, and customers can manage usage through credits, payment settings, and supported spending controls. Boo may pause or limit usage when credits run out, payment fails, or usage creates risk.