Confidentiality isn’t a feature we bolted on. It’s the reason Sable Forensics exists. Here’s exactly what we commit to — and what it means in practice for your practice and your clients. No overbroad marketing claims that do not survive contact with how AI actually works.
To analyze your files, the AI must be able to read them — that’s unavoidable. What we promise is that your case data is processed exclusively on dedicated private infrastructure, under explicit confidentiality obligations. It never reaches any third-party AI service, and no one outside the operation touches it.
Not ours, not a third party’s. Not anonymized, not aggregated. Your files are processed to answer your queries and generate your outputs — then they sit in encrypted storage until deleted. They are never ingested into any training pipeline.
You set the retention schedule. When the period expires, files are permanently deleted — from the processing infrastructure and from any working storage. No indefinite retention, no shadow copies, nothing left on local machines.
Your case data is not sent to OpenAI, Anthropic, Google, or any other AI provider. Analysis happens on private infrastructure. Your files don’t leave the system.
Investigator licensing in most jurisdictions carries explicit confidentiality obligations to clients — obligations that extend to the tools you use. Upload a client’s materials to a general-purpose cloud AI and you may be creating a record of that data outside your control, accessible to the provider and potentially to legal process.
There’s a legal current moving here, too. In the Heppner matter, the question of which AI tool handled privileged material was treated as relevant to whether protections still held. The lesson for investigators and firms is plain: routing confidential material through public AI can put privilege and confidentiality at risk in ways that are hard to walk back. Processing locally, on infrastructure that never hands your data to a third-party model, keeps that exposure off the table. Review your licensing board’s current guidance and consult your attorney for specifics.
Technically, yes — and we’re being straight with you about that. For the AI to analyze your files, they must be decrypted on the server during processing. What we promise is that we access them only to run the analysis you requested, we operate under strict confidentiality obligations, and no one outside the operation ever sees your case data. That’s a policy and contractual commitment, not a cryptographic one — but it’s an honest one. Anyone claiming an AI can analyze files it can’t read is selling you a fiction.
Never. Your case data is used only to produce the outputs you request — transcripts, analysis, reports — and then sits encrypted until deleted. It is not fed into any training pipeline, ours or anyone else’s.
We would comply with valid legal process. What we can tell you is that this is a single, accountable operation — not a massive cloud provider routinely processing millions of customers’ data under broad terms of service. Your files are encrypted at rest, access-logged, and deleted on your schedule, which limits what could exist to be produced at any given time. We encourage investigators and attorneys to consult counsel about jurisdiction-specific obligations around AI tool use.
They are permanently deleted from the infrastructure. We do not retain backups of client case files beyond your retention window, and nothing is kept on local machines. Deleted means deleted.
No. Processing happens on dedicated private infrastructure. Your case files do not leave the system or pass through any third-party AI API.
Sable Forensics is designed around investigative confidentiality requirements, but those requirements vary by jurisdiction and licensing board. We recommend reviewing your board’s current guidance on AI tool use, and we’re glad to talk through your specific situation before you commit to anything.
We’d rather answer them before you sign up than have you find a gap after. Request access and let’s talk through your specific situation.