Guarantees we can show, not just sign.
Retention you configure and a purge job that enforces it. Tenant isolation tested per endpoint. Credentials encrypted at rest. And a source log that makes every answer auditable.
Retention with teeth
Each client sets a retention period — 90 days by default — and a nightly job actually purges transcripts and personal data past it. Policy and cron agree.
Your data, walled per client
Every record is scoped to your company, and every endpoint carries an automated test proving another client cannot reach it.
An audit trail by design
The source log records which approved knowledge produced every answer — so a complaint, an audit or a curious manager gets evidence, not assurances.
From the console
Questions buyers actually ask
Where is our data hosted?
We are completing formal verification of the hosting region and provide the full subprocessor list with processing locations before any signature — the claim you get is the one we can evidence, contractually. Transfers outside the EEA are covered by Standard Contractual Clauses.
How long do you keep conversations?
As long as you configure — 90 days by default. Past that, a nightly job purges transcripts and personal data. Ticket summaries your team explicitly kept follow their own lifecycle in your hands.
Who at SayTrue can see our conversations?
Platform administration is limited to the Bytecode team for setup and support, every client operates behind tenant isolation that automated tests exercise on every endpoint, and provider credentials are encrypted at rest.
What do the AI providers see?
Conversation content necessary to produce answers, under our agreements with each provider — the current provider list with processing locations is part of the pre-signature documentation, so you evaluate it before committing, not after.
Answers your customers can trust.
Grounded in your knowledge, honest about its limits, and handed to your team the moment it should be.