How we handle your data.

What we do, and what we ask, when we work on your site or your app.

Agreement first.

Every engagement starts with a signed agreement. For security testing, that includes an NDA, written rules of engagement and data processing terms. The rules of engagement fix the scope, the dates and anything that is off limits.

Only what is in scope.

We test the systems named in the rules of engagement, on the dates we agree, and nothing else. If we think something outside the scope needs attention, we ask you before touching it.

The access we ask for.

We ask for the least access we need. Where possible we use test accounts rather than real customer accounts, and we ask you to remove our access when the work ends.

Credentials.

We ask you for test accounts instead of real customer logins, and we only use a credential for the work you hired us to do. Share them with us the way we agree in the rules of engagement, never in a plain email, and remove or change them when the work ends.

Findings go to you.

Reports go to the contacts you name. We do not publish or share your findings, or your name, without your written permission.

Why we do not show real reports.

We can’t show you real reports. Our clients’ security results are covered by signed NDAs, so the example here is invented. The sample report on our home page is written the same way as a real one.

If we find something serious.

If we find a critical issue, we tell you straight away instead of waiting for the final report.

Report a problem with our site.

If you find a security problem on this website, email groviatechh@gmail.com with the subject “Security report”. We read every report and reply by email.

Tell us about your site.

Book a free audit. We will tell you what fits, or that you don’t need anything yet.

Book a free audit