Keeping, deleting and what leaves the machine
I replay a finding on request until the day I delete your files, which is 30 days after the report. Ask for a longer period before you send anything.
No subcontractor, and nobody else reads it
PROSE ONLY
my word, with no check
The disk is encrypted
ENFORCED
disk encryption on both volumes of the machine. It protects a disk that is switched off and does nothing for a running, unlocked machine. A key of your own, which deletion would destroy, does not exist yet
No disk snapshots or backups of your directory
ENFORCED only where the directory is a volume of its own
a command I run once makes the directory a volume of its own, and the status check says whether it is one. Reading whether a snapshot already exists needs the administrator account, and I do not run a backup: both PROSE ONLY
Deleted 30 days after the report
ENFORCED in part
When I set up your directory, the rule "30 days after the report" is recorded in a file outside the directory, and the status check says the deletion is waiting for the report and never calls the deletion overdue while it waits. A command records the day I wrote the report and fixes the delete-by day at 30 days after it. A day I give by hand always wins. The status check fails once the day has passed, and a delete command removes the directory and writes a dated line to a log outside the directory. That I run those two commands on the day is PROSE ONLY: nothing runs either by itself
Image caches and other copies are removed
PROSE ONLY
I empty them by hand after the delete command, and nothing refuses a command that forgot to keep its cache inside your directory
Your name stays out of this code
ENFORCED for the product's source folders
a check reads the list of customer names that setting up a directory fills. Docs and commit messages are not guarded
I publish nothing, reuse nothing, share nothing, keep no copy, and tell you within 72 hours
PROSE ONLY
my word, with no check
Only the pull of an image leaves the machine
PROSE ONLY
the product's one outbound path is pulling an image from the registry your docker-compose file names, and no firewall blocks other traffic. A script lists every destination a command tries to reach, and I run it on request