Security · Continuity · Support
The Boring Answers,
On Purpose.
You’re trusting a system with the machinery of your business, so here are the questions that deserve specific answers — not badges and buzzwords. Everything below is current practice. If a question here isn’t answered, ask it: (318) 713-3781. Trevor answers.
Where does my system run?
On enterprise cloud infrastructure (Vercel for the application, managed Postgres for the data), in the United States. Every client runs in their own isolated environment with their own database. Your records never share a database with another business, and nothing about your business is shown to anyone else, ever.
How is my data backed up?
Automatic backups run continuously at the database layer, with point-in-time recovery. And every migration we do is itself a proof of the restore path: we rebuild your records from source exports and match them against the originals — in the money systems, to the penny — before anything goes live.
Is my data encrypted?
Yes — in transit (TLS on every connection) and at rest at the database and storage layer.
Who in my business can see what?
Every person gets their own named login, and roles wall off what each role has no business seeing — a yard crew login can print pull sheets but cannot open the money screens, by design. You can revoke any person’s access with one tap, and the walls are enforced on the server, not just hidden in the menu.
Is there an audit trail?
The money records are append-only: once an entry is written, no one can edit it — not you, not an employee, not us, not the AI. Corrections are visible, dated reversals. The mistake shows and the fix shows. That is the same discipline your bank uses, and it is enforced by the database itself.
What is the AI allowed to do?
The AI reads your records to answer you and to file and draft. It cannot rewrite history, it cannot spend money, and its outbound messages wait for a human tap where the business calls for it. Queries are processed through enterprise AI APIs that do not train on your data. Where an AI answering would hurt the business — a bail office’s collect calls from the jail — it is banned from the phone entirely, and the ban is printed on the screen.
What happens when something breaks?
You text or call, and a human who knows your system answers — the builder stays involved after launch. Real breaks jump every line and get fixed when they happen, not on a ticket queue’s schedule. No phone trees, no offshore tier one, no “your call is important to us.”
What happens if Found It disappears?
Your system keeps running — it is yours, on your accounts, and it does not phone home for permission. The Owned Software Standard defines the full handover you hold: the runnable source repository, the database and backups, the hosting transfer, the credentials and documentation, and the legal right for any developer to maintain it.
Who owns the accounts my system depends on?
You do, or you hold a documented transfer of them. Your payment processing runs on your own account — the money settles to your bank, not through ours. Third-party services that bill on their own (phone lines, card processing, AI usage) are listed for you in plain terms, per the Owned Software Standard.
What do you refuse to build?
Payroll and tax filing, permanently — that work belongs to a licensed person who signs their name to it. And any automation that would hurt the specific business it serves. Half of custom software is knowing what to refuse.