Privacy

Your workbook is parsed entirely on your own device, inside your browser, using a Web Worker. Tripwire DX never uploads the file, its name, its contents, or anything derived from it to any server. There is no server-side file handling in this product at all. Because workbook data is never transmitted, closing the tab clears the in-memory analysis state.

Tripwire DX uses limited server-side website analytics to understand basic traffic such as page views. This measurement does not use a client-side analytics script or cookies.

Workbook files, filenames, formulas, cell values, findings, generated reports, and other scan-derived content are not sent to website analytics.

Feedback is voluntary. If you choose to send it, Tripwire DX sends only the rating, category, comment, and reply email you enter, together with the fixed feedback page path, app version, submission time, and a random feedback ID. A transactional email provider delivers that feedback to the Tripwire DX support inbox for product improvement and support follow-up. Feedback and an optional reply address are retained there under the support inbox retention practice chosen by the founder. Providing a reply email is optional.

Your workbook remains local. Feedback never attaches the workbook, filename, model type, findings, cell values, formulas, report, or anything derived from the scan. Please do not place confidential workbook or report information in the feedback fields yourself.

During a controlled beta, Tripwire DX receives an anonymous invitation code only when you redeem it. The code is checked against the current beta access list but is not stored by the app. Successful redemption creates a signed, HttpOnly access cookie containing an anonymous credential identifier, access revision, beta generation, and issue and expiry times. The cookie lasts no more than seven days and can be removed with Log out.

Beta access does not require a name, email address, account, or profile. It never carries workbook, filename, cell, finding, report, or PDF information. In public mode, the scanner does not require the invitation code or cookie.

The controlled-beta foundation stores only anonymous operational access and quota state: random request and reservation identifiers, the anonymous credential identifier, UTC dates, successful-completion counts, timestamps, and terminal control states. It stores no workbook or Report data. Beta usage limits are enforced as part of the check workflow.

There are no user accounts, identity profiles, or payments in this version. Beta access is anonymous. Nothing is tied to a personal identity unless you voluntarily provide a reply email with feedback.

Contact: support@tripwiredx.comEmail copied