Custodly by Datics AI · Legal tech service
Transcripts sold and released through your platform, readable only by the attorney who paid.
Your platform keeps the sale and the audit trail, and gives up the ability to read the file. Custodly encrypts each transcript in the agency's browser at release, so only the paying attorney can open it.
Built in your codebase and tested in your vendors' sandboxes.
Encrypted transcript and record release for legal marketplaces
- PIN protected key pairs. Each user sets a PIN at onboarding, and the browser creates a key pair and locks the private key before it leaves the device.
- A content key per transcript. At release, the agency's browser encrypts the file with its own key and locks that key to the paying attorney.
- Release only after payment. Release opens once the request is paid at the agency's price, and the agency confirms it with its PIN.
- Decryption in the attorney's browser. The attorney enters their PIN and reads the file in their browser; the readable copy never reaches the server.
- An honest PIN warning. The platform never holds a PIN, and onboarding says plainly that a lost PIN can mean lost access.
What it does
What the integration service covers.
PIN protected encryption for record delivery: the agency's browser encrypts each file at release and locks its key to the paying attorney, while payment, release and audit stay on your platform under one request ID.
PIN protected key pairs
Each user sets a PIN at onboarding, and the browser creates a key pair and locks the private key before it leaves the device.
A content key per transcript
At release, the agency's browser encrypts the file with its own key and locks that key to the paying attorney.
Release only after payment
Release opens once the request is paid at the agency's price, and the agency confirms it with its PIN.
Decryption in the attorney's browser
The attorney enters their PIN and reads the file in their browser; the readable copy never reaches the server.
An honest PIN warning
The platform never holds a PIN, and onboarding says plainly that a lost PIN can mean lost access.
How it works
Keys are created and locked in each user's browser, and the platform stores only encrypted files, encrypted private keys and locked content keys. There is no AI in the file path: people enter their own PINs.
Built on PIN protected transcript encryption we have added to a live transcript marketplace.
Transcripts U.S.
Court reporting · Encrypted release
Attorneys receive deposition transcripts that even the marketplace cannot read
The marketplace could once read every transcript it held; now each file is encrypted in the agency's browser and opens only in the paying attorney's.
Transcripts U.S.
Court reporting · Transcript indexing
Court reporting agencies publish transcript metadata without the file ever leaving their browser
Agencies once uploaded full transcripts to the marketplace; now title page details are read in their own browser, and they confirm what is published.
Early-stage dataset marketplace startup
Custody · Files the platform never holds
On-device scanning and encryption for a dataset marketplace that never holds a file
Buyers of AI data could not check what they paid for, and exchanges held the files. A desktop agent now scans and encrypts on the seller's machine.
Why it sells
What the integration service makes possible.
Best fit: Transcript marketplaces, records release and legal document delivery platforms.
Admins out of the trust chain
Your team cannot open the files, and can say so.
The sale stays on your platform
Payment, release and audit run where they always did.
An answer for cautious agencies
Agencies worried about who reads their files get a design that rules it out.
Controls
What the integration touches, and who approves.
Built in your staging; nothing changes in your product unless your team merges it.
Who uses it
Court reporting agencies, attorneys, platform admins
What it connects to
Your request, payment and delivery flows
What a person approves
The agency releases each paid request with its own PIN
How to get it
A fixed-scope integration, then it runs.
Scoped in the Product Review and quoted before we start. Add more only if you want it.
First · Scope · fixed quote
One piece of work, scoped
- Your staging
- Pull requests
- Your team merges
- Built and tested in your staging
- Reviewed by your engineers
- Monitoring before go-live
Then · Live in production
A finished product, yours to run
- Fixed quote
- Tested before launch
- Switch per customer
- A finished, working Custodly in your product
- Runs in your cloud, under your name
- Fixed quote, agreed before we start
Optional · Add more later
Only if you want it
Modules it feeds:
- Each one quoted on its own
- Nothing ongoing unless you ask
Already built or tried AI? Get it scored with the AI Scorecard. Need something else? Start with a Planning Sprint.
FAQ
Questions about Custodly.
Is Custodly AI?
No. It is encryption, and no model sees the file. It sits beside the AI modules because it answers the question every agency asks first: who can read the record.
What if a user loses their PIN?
The platform never holds a PIN, so a lost PIN can mean lost access to encrypted files. Onboarding says so plainly.
Can the agency keep the file itself?
We are exploring that design: the platform keeps metadata, payment and audit, and the agency stays the custodian. We scope it per agency in the Product Review.
See the integration service on your own product.
Bring your product and the systems your customers run. In 30 minutes we look at what the integration would cover and what it would take.
Calls run in US Central time. No generic AI presentation: we discuss your product, users and production constraints.