What we can and can't see.
Trust
Confidentiality by architecture. Your build runs on hardware in your building.
Design my Garnet →Read the privacy policy
The whole argument
Two columns, in plain words.
Everything we can see lives in scoping and build. Your running system stays yours alone.
| What we can see | Only while we scope and build: the conversation with you, any sample material you deliberately share to test quality (destroyed on handover, certified in writing if you want, unless you ask us to keep it), and the contact details you send through this site. |
|---|---|
| What we can't see | Once your build is handed over: your documents, your prompts, its answers. Access ends at handover, the machine stays sealed, and it talks to us only when you open it. It is yours alone. |
The proof
Pull the network cable. It still answers.
A promise is only as durable as the company behind it. This removes the need to trust one.
- Nothing leaves the building. The AI thinks on a dedicated machine in your building, so the only copy of your material is the one you hold — the single thing a leak, a subpoena or a sale would have to reach.
- No standing access. After handover it is beyond our reach. Future help happens when you invite us in, and ends when the work does.
- Honest about the badge. We remove the exposure a certificate is meant to manage. Our assurance is architectural rather than certified — SOC 2, ISO 27001 and HIPAA are certifications we would still have to earn, and we say so plainly.
- Air-gapped, not frozen. When you want new capabilities or patches, you open the network on your schedule, pull them, and close it again. The airgap is a mode you control, not a wire we cut, and keeping it current is a choice you make, not an automatic feed.
How to check us
Proof you can verify, not a track record we assert.
Here is what you can confirm for yourself. We are early, and we say so: every example here is our own work, every name on this site is ours, and anything we point at is open for you to read.
- A real, named entity. Garnet Grid Consulting LLC owns everything here, sits on every filing, and stands behind every build. The company behind this page is named, filed and reachable.
- Trademarks on the public record. Garnet and Garnet Grid are filed with the USPTO under serials 99714919 and 99714851. Open the live records yourself; you do not have to take our word for it.
- A documented IP and provenance chain. The proprietary license is laid out in full on our legal and IP page.
- The working product, in the open. The best proof is the thing itself. See exactly how Garnet Workstation works and judge the capability on its own terms, before any conversation. Garnet Mesh™ is in build: the services are written and installed on the reference machine and have never been started in service, so single-machine Garnet is what there is to inspect today.
- Bring your own security team. The strongest check is your own. Before you rely on it, your people can inspect the offline boundary, watch everything that crosses it, and satisfy themselves that the list is empty. Confidentiality you verify beats confidentiality you are asked to take on faith.
Walk your own confidentiality requirements through it with the engineer who builds the systems. A conversation, with the person who writes the code.
Garnet builds are private, self-hosted AI systems that run on hardware in your building. Confidentiality is structural: it comes from the architecture rather than from a policy you have to trust. Because the AI does its thinking on your own machine, there is no outbound copy of your work for anyone to breach, subpoena, or sell. You can verify it yourself: pull the network cable and the system keeps answering.
What we can see lives entirely in the scoping and build process, never in your running system. During that period we see the conversation you have with us, any sample material you deliberately share so we can tune the system and verify quality (destroyed on handover unless you ask otherwise in writing), and the contact details you send through this site so we can reply. No third-party trackers and no advertising profiles.
What we cannot see, and never could: once your build is installed and handed over, we have no standing access. Your documents, your prompts, and its answers exist only on a dedicated machine in your building. There is no back door, no vendor account, and no maintenance tunnel that phones home. Garnet is a bespoke build practice, not a certified platform, so we are not SOC 2, ISO 27001, or HIPAA certified and we will not claim to be. Report a security issue to security@garnetgrid.com. Family office, private, and enterprise builds are scoped individually; contact us to scope a build.