Contacting RowShield support and security

Writing a message we can act on quickly

For anything about a specific project, include the project reference shown on the project page, the article or rule involved (a link such as /help/findings/severities is ideal), what you expected, and what happened instead. For billing questions, the organisation name and plan suffice. If something is urgent, say so in the subject line; mail is answered in order, and a subject that states the problem plainly gets routed to whoever can act on it.

If you disagree with a finding, say which rule and which table. Findings can be challenged, and the challenge path works best when the dispute arrives attached to the artefact it concerns.

Reporting a security issue

Security disclosure goes to the same address, info@getveristria.com, with the word security in the subject so it is routed immediately. Describe the issue, the affected surface — the site, the API, a deployed probe behaviour — and how to reproduce it; precision in that first message is the single biggest factor in how fast an issue moves. Every report receives an acknowledgement, and we will keep you informed as it is assessed and fixed.

Please give us a reasonable window to fix before public disclosure; we extend the same courtesy to researchers reporting on deployments that use RowShield.

Related questions

Where do feature requests go?

To the same address. Requests that recur get written into the roadmap, and the roadmap is public — asking costs nothing and several shipped rules began as single emails.

Can we talk over a call instead?

Email comes first because it produces a written trail both sides can quote, and most threads close within a reply or two. Calls are arranged from a thread when a problem genuinely needs one.