Effective 27 August 2026

Privacy

Journey Failure Receipts is local-first software. The documentation site does not create an account, set analytics cookies, or send test artifacts to us.

What the library writes

When an assertion wrapped with receipt.soft fails, the library writes a receipt into the output directory you configure. It can contain a masked screenshot, scrubbed DOM and ARIA text, console messages, network metadata, the test name, and the assertion error. Those files stay on the machine or CI system running Playwright unless you choose to upload them elsewhere.

Privacy safeguards

• Form controls and configured selectors are masked before screenshots.
• Form values and configured content are redacted from structure captures.
• Request and response bodies and headers are never captured.
• Query strings, fragments, URL credentials, tokens, emails, and card-like numbers are removed from recorded text where detected.
• All evidence categories have finite default caps.

Automated redaction is defense in depth, not a substitute for configuring maskSelectors for application-specific sensitive content. Treat CI artifacts according to your organization’s retention policy.

This website

The public documentation site uses no analytics, advertising, third-party scripts, external fonts, or account storage. A service worker may keep public site files in your browser cache so the docs work offline. Clear the site’s storage in your browser to remove that cache.

Contact

Questions or security reports may be opened in the project’s public GitHub repository. Do not include credentials or private receipt files in a public issue.