How we keep nothing

This is the page that matters most. Here is exactly what happens to your data, step by step.

1. Your provider key arrives in a header, is held in a single memory variable, used for one upstream call, and goes out of scope. It is never stored — not even encrypted — never logged, never echoed in an error.
2. The mask mapping (real value ↔ stand-in) exists only inside the request. When we send your answer, it is destroyed. It never touches our database, our logs, or a backup.
3. Uploaded files live in RAM during the job and are deleted the moment it finishes. We never use object storage. There is nowhere for a file to linger.
4. Our logs record counts and timings only — never a single real value. So our backups contain zero personal data by design, not by filtering.

The only two things we ever store encrypted: your secret-words list, and Deep Read results for at most 24 hours (delivered once, then deleted). Everything else is memory-only.