Rules & Regulations
The terms every engagement runs under.
What is in scope, what we will and will not do, what you receive, how fees and retests work, and how your data is handled. Short enough to read before you sign — which is the point.
- Written authorization first
- No DoS, no social engineering
- Fixed fee, never per bug
- NDA on request
Scope of Engagement
Every engagement covers exactly what the signed statement of work lists: named domains, API endpoints, app builds and test accounts. Anything outside that list is out of scope, even when it belongs to you — the written scope is what keeps a test lawful and a report accurate.
Testing begins once the statement of work is signed and the fee has been received. Nothing is probed before that.
- In scope is whatever the statement of work names by hostname, repository or app build.
- Production data is read-only. Test objects are created and removed with your permission.
- Third-party services — payment processors, identity providers, cloud providers — are excluded; they run their own disclosure programmes.
- A new asset discovered mid-engagement is added only by written agreement, never assumed.
Deliverables & Reporting
Every finding arrives with the affected endpoint or screen, a severity, a reproduction, a short proof-of-concept video and a remediation note your engineers can act on. If it cannot be reproduced, it is not reported.
Findings land in the client portal as they are confirmed, and the engagement closes with a PDF written to be read by someone who was not in the room — an auditor, a customer's security team or an investor.
- Severity follows exploitability and impact, and the finding explains the reasoning rather than printing a bare score.
- Every plan includes a retest of the fixes made inside its retest window.
- A retest confirms the reported findings are fixed. It is not a second full assessment.
- Automated scanner output is never delivered as a finding on its own.
Fees, Refunds & Cancellations
The fee is the fixed price of the plan you bought — $150 Targeted, $250 Full Deep-Dive or $450 Enterprise — confirmed on the statement of work and payable before testing starts. It is never metered by the hour, and it never changes because more bugs were found than expected.
The fee pays for the assessment. FindHyde neither charges nor pays a bounty per finding: the value of a bug is in it being fixed, not in it being counted.
- Reschedule or cancel at no cost up to 48 hours before the agreed start date.
- After that, or once testing has started, the fee covers the work already performed; anything undelivered is refunded if the engagement cannot be completed.
- A retest outside the plan's window, or a scope added later, is quoted separately before it is started.
- The 30-day support window in Enterprise runs from delivery of the final report.
Confidentiality, Data & Liability
Both sides keep what they learn confidential. An NDA is available on request and is signed before credentials are shared; without one, this page and the signed statement of work are the agreement.
Credentials, test accounts and any data touched during testing are used only for the engagement and are deleted or handed back when it closes, unless a longer retention is agreed so a retest can run.
A pentest is a point-in-time assessment by humans. It reduces risk; it cannot prove the absence of vulnerabilities, and it is not a compliance certificate — the report is evidence for an audit, not the audit itself.
- Liability for an engagement is limited to the fee paid for that engagement.
- Neither side is liable for indirect or consequential loss, including lost profit or lost data.
- These terms are governed by the law named in the signed statement of work, and that document governs if the two ever disagree.
Something unclear?
Ask before you sign. If the answer changes how an engagement should run, it goes into the statement of work rather than into a footnote here.