What we keep

FixWalk walks your live app the way a brand-new user does. When you connect a read-only database key, it also reads the table behind the screen. This page says what that means for your data.

What is read

The walker opens the address you give us and signs up like anyone else. If you connect a test login, it uses that account so it can walk past onboarding and come back to the same account after a fix. If you connect a repo, it reads the code so a trip's fix prompt can name the file. If you connect a read-only database key, it reads the tables that key can see — only inside a walk, and only as a reader.

The key is stored encrypted, used only during a walk, and deleted the moment you disconnect. The walker writes only under its own account, never yours.

What is kept, and for how long

Three copies can exist after a walk finishes.

**The walk record** lives on your project: the score, the trips, the path it took. It stays so you can open the report and walk it again.

**The footprints** are what the walker saw at each step. They stay with the walk so the report can show the path.

**The training archive** is a copy of the finished walk — the record, the footprints, and the conversation the walker had with itself — used to improve the walker. It is not on any page you can open. A free walk is copied unless you turn that off. A paid walk is not copied until you turn it on. Turn it off on the connections screen for that project; later walks of that project are not copied. Copies already made stay.

We also keep a copy of every email we send you, with magic-link tokens stripped so the copy cannot sign anyone in. That mail copy is not on any page you can open.

What is never kept

The database key, passwords (the test login's, and the one the walker made for itself), and session values from your app. Those live only while a walk is queued or running, encrypted, and are deleted when the walk finishes.

How to opt out

On the project's connections screen, turn off "Keep this project's walks to improve the walker". New walks of that project will not be copied into the training archive. The walk record and the footprints on your project are your report; they stay.