How I treat your data and what can access it
- Where it runs: on my machine.
- Who can access it: me and the machine's administrator account. One AI tool on this machine is denied your directory.
- How long it is kept: 30 days after the report, unless you and I agree on another day.
- How deletion works: I run a command that removes your directory and logs the date.
- Technical controls, marked ENFORCED: an owner-only directory and an encrypted disk.
- Procedural controls, marked PROSE ONLY: who else reads your files and what leaves the machine.
Each control below is marked ENFORCED, with what enforces it, or PROSE ONLY, which means I keep it and nothing checks me. A control is marked ENFORCED only where a program refuses or a permission denies, and the limits are written beside it.
Your directory is owner-only and outside every code repository
ENFORCED
A program creates the directory readable by me alone and refuses to create it inside a code repository. A status check reads the setting back
Your files are put there and nowhere else
PROSE ONLY
no program checks where I copy a file
Nothing of yours is committed or pushed
ENFORCED for run output
The programs that run and bundle your software refuse an output folder inside a code repository, a check fails on any tracked file under the customers folder or inside a default output folder, and the repository ignores the same names
The same, for the rest
PROSE ONLY
the output of a replay or a run page, a file of yours under another name and the cache folders are not judged by any of those checks
An AI tool reads only structured outputs (counts, kinds, places, times, hashes), never console or log text, unless you agree in writing
ENFORCED for one AI tool on this machine only
a permission rule in that tool's settings blocks its file reads, file edits and shell commands that name the customers folder. It covers that one tool on this machine and nothing else. A shell command that avoids the literal path, such as one with a wildcard, gets past it
An AI tool is given structured outputs to read
ENFORCED for what the export writes
the export writes counts, finding kinds, places, severities, exit codes, run lengths, replay codes and digests, and nothing else, to a separate folder that only I can read, so the permission rule above does not cover it. The record it writes has no field that can hold free text, and the export is compared with the console, docker-compose and report files of the runs, and removed if any line of those files appears in it (a check runs the same comparison on demand). The comparison finds a whole line of 8 characters or more, and a line inside a longer one when that line is 16 characters or more. It does not find a fragment, a line under 8 characters, or a line of 8 to 15 characters inside a longer one.
Which tool reads which folder
PROSE ONLY
an AI tool may read the structured folder and is denied your directory, for the one tool and machine described above. Nothing stops another tool or another machine from reading either folder
Which other outputs are not structured
PROSE ONLY
findings, summaries, result files and reports quote console lines, so I keep AI tools away from those files and give them the export instead
Other accounts on this machine cannot read your files
ENFORCED
the directory and the home folder it sits in are readable by me alone. The machine's administrator account can still read it