US Tech Automations

Checks we run for you monthly vault We store nothing after the run

Document custody vault

A one-to-five person AI consultancy handling clients’ documents gets two questions on a form: do you keep our data after processing, and can you show us what you did with it? This is a record the client checks with a key they hold, so we cannot go back and change it. The free portable-profile tool runs on your machine. The paid half is one solo vault. Only the $9/mo tier is chargeable in the prototype today. We store nothing after the run.

Price
$9/mo
Built for
A 1 to 5 person AI consultancy handling clients' documents
Cadence
monthly vault
Status
Solo vault

No pay button on this one yet. Email us. A person replies with how the free tool works and, when a checkout exists, the link. Only the $9/mo tier is chargeable in the prototype today.

Email us about the vaultNo card needed to ask. We reply with what we hold.

Read this before anything else

The free tool prints a profile and a retention receipt on your machine. The paid vault is a log of what was processed, signed with a key your client holds. We never see the files. After the run we store nothing.

Only the $9/mo solo vault is chargeable in the prototype today. There is no team price to take, and no pay button on this page yet. A person emails you the custody log after you pay.

Your client checks this with the key you give them. A stranger cannot. Whoever holds that key can check the log — and could also sign with it. This is a record your client can check, not a public proof anyone can check.

“We store nothing” means our own folders, during the run. The guard watches the directories it is told to watch while extraction runs. It is not a claim about your machine, about anything before or after the call, or about memory. If you save the printed profile, that copy is yours.

A clean extraction is not an accurate one. The free tool matches patterns in English text. It will miss things, and it will pull out odd phrases. It is a starting point you edit. We prove we kept nothing; we do not prove the profile is complete or correct.

We are not a legal product. We produce a record. What you do with it is yours. No regulation is named here because we do not certify you against one.

The free portable profileprototype on a local fixture, 25 Aug 2026

You run this on your own machine, on your own exported AI chat history. Nothing is uploaded. The sample below is an example from the prototype running on a local fixture. It is not a live-web read.

Retention receipt from the free tool unsigned · files written: 0
WhatValue from the run
Fingerprint of the export it readc61753562632f0d5179da1d385267514dc18971c114c03aac3814654f12ffedf
Fingerprint of the profile it produceda0cf46d481ed97aed375ce8ff40b9667e8ebedd9d5b012a4fea726a940125b63
Files written under the watched folders0
Signedfalse
Profile date (from the export, not the clock)2026-08-20T00:00:00Z
Schema / extractorportable-context/1 · 1.0.0
Source named in the fixtureacme-ai · exp_demo_1

The last line the free tool prints:

This receipt is unsigned. Anyone, including you, can edit it. A signed record your client can check — and that we cannot rewrite — is $9/month.
What the tool pulled out of the fixture local fixture, not a live export
FieldValue from the run
PreferencesI always use sqlite for local work; I prefer short, direct answers
FactsI work on a trading system in python; My database is postgres
ProjectsDeploy pipeline; Local tooling
Toolsdocker, git, postgres, python, sqlite
Counts2 conversations, 3 messages, 2 from the user, 11 days apart
Top topics (word counts)python 2; work 2; answers 1; code 1; credential 1; database 1; direct 1; local 1; postgres 1; prefer 1

“credential” is in the topic list because the fixture contained that word. That is the tool doing what it does: counting words, not understanding them. Edit the profile before you show it to anyone.

The signed custody logfour events, chain checked

The paid half appends events to a log. Each event stores a fingerprint of what was processed, not the file. Each event is linked to the one before it. Each event carries two signatures: ours, and one made with a key your client holds and we never see. The sample is the same prototype run, still on the local fixture, still not a live-web read.

Custody log before anyone tried to edit it vault_demo1 · 4 events checked
SeqWhen (from the prototype clock)What was recordedWhoFingerprint stored (the file is not stored)
02026-08-25T00:01:00+00:00vault.openedservice2a28a4c5a6c2f489cd90af6a712724944fc0fc1181f2cfc6727f5cd42908dcd0
12026-08-25T00:02:00+00:00profile.extractedusera0cf46d481ed97aed375ce8ff40b9667e8ebedd9d5b012a4fea726a940125b63
22026-08-25T00:03:00+00:00export.receiveduserc61753562632f0d5179da1d385267514dc18971c114c03aac3814654f12ffedf
32026-08-25T00:04:00+00:00subscription.chargedservicebfe450a34ec33cc2833a7e1a59168e0bb4c5134604e3b78ef7a8049b2fbe8f3e

The profile fingerprint in event 1 is the same string as the free tool’s profile fingerprint. The export fingerprint in event 2 is the same string as the free tool’s export fingerprint. Event 3 is the prototype recording the $9 monthly charge — a pretend charge inside the prototype, not a real card. Client key id on this run: 2f27855c2381841e. Head of the log: 7bee9a5844c15218324360764645b65242e9e324d8547cc7993d2b9084af70c6. Chain check: ok. All 4 events countersigned.

What happens if we try to rewrite itsame run, after the log above

The prototype then tampers with copies of the log on purpose. The client-key check is the one that matters, because we can re-sign our own half.

Four attacks, each named by the check that caught it prototype, 25 Aug 2026
What we didDid the check pass?Reason the engine printed
Changed a middle entryNoentry_hash_mismatch at seq 1
Rewrote the whole log and re-signed our halfInternal-only check: yes (fooled). Client-key check: nouser_countersignature_invalid
Dropped the newest entries and rewrote the count to matchInternal-only check: yes (fooled). Client-key check: nohistory_rolled_back
Added a hidden field to a past entryNorecord_schema_violation

Catching a shortened log needs one fact on the client’s side: the last entry they signed. If they lose that, we still cannot edit a past entry, but a shorter log is harder to tell from an honest one. Keep that last entry. We cannot recover the key if it is lost — that is the same property that stops us forging it.

What you get at $9/mo

  • One solo vault.A running log of what was processed, with the client holding the key. Cancel any month by email. No account to close and no notice period.
  • The free tool stays free.The portable-profile command runs on your machine, prints the profile and the unsigned receipt, and writes nothing. No account.
  • We store nothing after the run.The log stores fingerprints, not files. If the extraction guard sees a file written, it refuses and you get no profile.

After you pay, a person emails you the custody log. The portable profile is produced on your machine.

Questions we are actually asked

Do you ever see my client’s files? No. You send a fingerprint of the file and a short description of what you did. The file itself never leaves your machine.

Why should I believe the “we store nothing” part? Run the free tool with the network off and watch it work. It is the same guard the paid product runs behind. The receipt prints files written: 0, or it prints no profile.

Can a third party check this without the key? No. Handing someone the key lets them check — and also lets them sign. Do not call this a public proof.

What if I lose the key? You lose the ability to check the history, and the strongest part of the guarantee goes with it. Keep a backup. We cannot restore it.

Is this a certification? No. It is a record. Nobody has audited us and we do not claim otherwise.

Is there a team plan on this page? No. Only the $9/mo solo vault is chargeable in the prototype today. Anything else is not for sale yet, and we will not take money for it until it is.

Ask before you pay

No pay button on this one yet. Email operations@ustechautomations.com. Say you want the solo vault. We reply with how the free portable-profile tool works and the checkout link, before you spend anything.

What you would be paying for: $9 a month, billed monthly, for one solo vault. Cancel any month by email, with no account to close and no notice period. Only this tier is chargeable in the prototype today. There is no pay button on this page yet. After you pay, a person emails you the custody log. The portable profile is produced on your machine. We keep nothing after the run.

Email us about the vault

No card needed to ask. We reply with what we hold.