DATA HANDLING

Where your data goes,
written down before it goes live.

The questions a firm should ask any AI vendor, answered up front. The full vendor due-diligence pack and the services agreement are available on request.

A compact computer connects documents and a workstation within a local network boundary.

On a machine your firm owns, in your office.

The language model, the document index, search and transcription run on a Mac your firm buys as its own asset. I don't resell hardware, and I don't keep copies of your documents on my own devices or systems.

No client data goes to a third-party AI provider unless your firm approves that provider in writing first.

Healthcare practices: I don't access protected health information until we've both signed a business associate agreement.

Every outside connection is on a register you review.

A system in a real office still needs some outside connections. Each one goes on a written data-flow register, reviewed with your firm at handover and, with a support plan, every quarter. Nothing new goes live without your written approval. The usual entries:

Remote support

An encrypted connection over a Tailscale network your firm owns. You can remove my access at any time.

Off-site backup

Encrypted snapshots to a storage bucket in your firm's name. Only someone with your firm's password can read them.

Updates

Software and model downloads. With a support plan, I apply them monthly in an agreed window after checking the release notes and the previous night's backup.

Your office network

Core processing on your hardware
Approved documents

The files selected for indexing

Local indexing + AI

Find passages and prepare answers

Staff search app

Answers with source references

Access permissions and staff review are part of the deployment design.
Optional data connection

Approved external services

Email, calendars or other agreed tools. Document what data is exchanged and why.

Agreed support connection

Remote maintenance

Access-controlled VPN for agreed support. A disconnected system needs an on-site visit or an approved connection window.

Illustrative architecture, not a claim of complete isolation. Hosting location alone does not establish compliance.

What's in place on every install.

Encryption on the server
FileVault full-disk encryption. Your firm holds the recovery key; I keep no copy.
Encrypted backups
Nightly, one copy in your office and one off-site, both encrypted. Your firm holds the passwords.
Encryption in transit
HTTPS on every service staff use. Remote support runs over WireGuard through Tailscale.
No open ports
Nothing is opened on your router. Admin tools are reachable only over the support connection.
Model access
The language model listens only on the server itself. Desktop apps reach it through a keyed port.
Named accounts
Every admin has a named account, including mine. Your office manager approves each staff account.
My devices and accounts
Full-disk encryption on my devices and multi-factor authentication on every account that can reach your systems.
Restore tests
A restore from the off-site backup before handover. With a support plan, again every quarter, logged.

You hear promptly, and in writing.

If I discover actual or suspected unauthorized access to your data on the systems I manage, or on my own accounts or devices, I tell your firm without undue delay, and no later than five business days after discovering it, with what's known so far. If a rule your firm is under sets a shorter deadline, such as the 72 hours amended Regulation S-P gives financial firms' service providers, the agreement uses that deadline instead. You decide whether and how to notify your clients or regulators, and I help and keep the logs.

You keep the system, or it's wiped.

Keep it

I hand over every credential, remove my own access and confirm in writing that it has ended.

Wipe it

Your data is exported to you first. Then the server, the backup drive and the off-site copies are erased, and you get written confirmation of what was destroyed and when.

Your firm's duties stay your firm's.

Running AI on your own hardware doesn't by itself make a firm compliant with ABA Formal Opinion 512, the Georgia Rules of Professional Conduct, HIPAA or any other rule. Competence, supervision, client communication and fees remain the firm's calls. This page, the data-flow register and the vendor pack give you the facts to make them.

For the vendor questions to ask anyone, including me, see the AI vendor checklist for law firms.

Ask Me Anything on This Page

On a 30-minute call I'll go through how these answers apply to your office, and send the vendor pack afterwards.

Book a Free Discovery Call

Or call (470) 706-9787