Security and data handling

Holstr is a desktop app. This page explains what it records while you test, where that data lives and how to report a security issue.

Last updated 8 November 2026

What Holstr records

  • Captr takes screenshots of your screen, logs the clicks you make and notes CPU, GPU and memory use, but only while recording is on.
  • Cybr loads the pages of the site you enter, the same way a visitor’s browser would. It does not try to break into a site or submit forms.
  • Injectr sends only the requests you build and run, with the headers, tokens and certificates you provide.

Where your data is kept

Your work is saved in session files on your computer, in the place you choose with Save or Save as, and in the PDFs you export. [Confirm that screenshots, scan results and Injectr credentials are stored only on the device, and whether certificate passwords and tokens are saved in session files.]

What Holstr sends to us

[Confirm what the app sends to RedevIO, for example licence activation, update checks or crash reports, and what each includes.]

Good practice

  • Close private windows and messages before you start a Captr recording.
  • Use test accounts, test tokens and test environments in Injectr.
  • Only scan or test sites you have permission to test.
  • Check exported PDFs before you share them outside your team.

Reporting a vulnerability

If you believe you have found a security issue in Holstr, email help@holstr.io. Please give us reasonable time to fix it before disclosing it publicly.

Procurement and questionnaires

We are happy to complete security questionnaires and supplier assessments. Contact us to start.