BYOK stands for Bring Your Own Key. It means PROVEAiBLE connects to an AI model using your organisation’s own API account — not ours. Every AI call made during intake runs under your account, subject to your provider’s terms, governed by your data processing agreement with them.
When intake software uses a shared AI account, your client data passes through a system the vendor controls. You have no direct relationship with the AI provider. You can’t audit the calls. You don’t know what the retention terms are. With BYOK, you do.
BYOK on its own doesn’t fully protect client confidentiality — the AI still processes the conversation. PROVEAiBLE combines BYOK with pre-LLM PII redaction: personal identifiers are stripped before any AI processing, so the model never sees client names or contact details.
Redaction before the call, your key for the call, zero retention after — that combination is the only intake architecture that satisfies ABA Model Rule 1.6 at every step. See exactly how the AI never sees client data →
Pre-LLM redaction, your own key, zero retention — the full confidentiality architecture, explained.
More on the architecture and jurisdictions: our compliance page →