Trust Center

Careful with your data. Honest about the rest.

The controls behind ChatPlotDB and Relay: how your data is separated, protected and accessed, what we do not promise yet, and where every claim on this page is written down in full.

Encrypted

database credentials at rest, never sent back to the browser

Read-only

every query ChatPlotDB runs on your database

Per-org

separation of connections, chats, dashboards and Relay sites

TLS

for all traffic to the hosted service

How we keep that promise

Your data stays yours

Your data is used only to run the Services for you. We do not build models of our own and do not train any model on your data.

Credentials locked away

Database passwords are encrypted before they are stored, and no endpoint hands one back — not to you, and not to anyone who reaches your account.

Roles per product

Inside an organization each member has a role for ChatPlotDB and for Relay, so a Relay teammate never sees your databases, and admins control who can change what.

A guarded crawler

Relay reads only public pages, follows robots.txt, and refuses private and internal network addresses, so it cannot be pointed at infrastructure behind your firewall.

Honest about the gaps

We hold no certification yet, have not had a third-party penetration test, and do not promise an uptime target or backups. The Security page lists every gap.

Your choice of models

The Privacy Policy names every AI provider a request can reach. For full control, an enterprise deployment runs the models inside your own AWS account.

Amazon Bedrock

The same models,inside your own account

On the managed service, model calls go to each vendor's API. On an enterprise deployment they don't leave your cloud: ChatPlotDB runs in your AWS account and serves those same foundation models through Amazon Bedrock, in the region you choose.

[ 01 ]

Your account, your region

The agent runs inside your own AWS account and VPC, and Bedrock serves the models from the region you pick, so your prompts, your schema and your rows stay inside the boundary you already govern.

[ 02 ]

No third-party model API

Nothing is sent to Anthropic, OpenAI or anyone else, and nothing is used to train a shared or public model. The vendor keys the managed service needs simply aren't in the picture.

[ 03 ]

Governed like the rest of AWS

IAM roles, VPC isolation, KMS-managed keys and CloudTrail audit logs: model access is controlled by the same policies that already secure your infrastructure.

Get started with ChatPlotDB