How Testfolio handles your data

This page describes how the Testfolio app behaves. Whoever runs this installation chooses the AI provider and controls the server, so ask them about their own policies.

No account

Testfolio has no sign-up or login and doesn't set tracking or analytics cookies.

Stored in your browser

Your draft input, test sets, undo history and settings are kept in this browser's local storage. They are not sent to the Testfolio server to be stored, and they aren't synced to other devices. They stay until you choose Clear local data in the app or clear this site's data in your browser. There is no copy elsewhere to recover them from, so export what you need to keep.

Sent for AI features

When you generate tests, improve a scenario, update tests from an answer or translate a set, your input text, the API details read from attached files and, where needed, the current test set are sent to the Testfolio server and passed to the AI provider configured for this installation. That provider processes and may retain the data under its own terms. Testfolio's server does not log your input or the generated tests. For each AI request it records only metadata: which feature was used, the model, token counts, an estimated cost, how long it took and, if it failed, why (for example, a timeout).

Viewing sample results, editing tests and exporting files happen in your browser and send nothing.

Credential redaction and its limits

Before input is saved or sent, credential values such as authorization and API-key headers, cookies, password and token fields, and well-known key formats are replaced with [REDACTED]. Redaction is pattern-based: it can miss secrets in unusual places and does not remove personal data such as names or email addresses. Don't paste information you aren't allowed to share with the AI provider.

More detail is in the documentation.