VULCANSECURITY

Assessment terms

Testing with consent. Reporting to you.

These terms explain how Vulcan handles authorization, scope, findings, and data. They are written to be read, not buried.

Last updated 17 November 2026

The short version
PrincipleWhat it means
ConsentWe test only targets you own or are authorized to request.
Data saleWe never sell or share your information or codebase.
ValidationWe validate findings with minimal proof and do not exploit them further.
ReportingFindings are reported directly to you with no third party in the loop.
HostingData is held on third-party infrastructure; we do not run our own servers.
01

Consent and authorization

Vulcan performs security assessments only with consent. By submitting a request, you confirm that you own the target or have written permission from the owner to request testing, and that you are authorized to accept these terms on behalf of your organization.

We may ask for proof of authorization before scheduling work. If ownership or permission is unclear, we will pause the request or decline it. No testing starts until we confirm the target, scope, and timing with you in writing.

02

What we test

We assess web applications, mobile applications, internal tools, and the APIs that support them. The exact scope is agreed in writing before work begins.

  • In scope: the targets and test accounts listed in the confirmed scope.
  • Out of scope unless explicitly agreed: social engineering, phishing, physical access, denial-of-service, destructive testing, and systems owned by third parties.
  • We do not perform persistence, lateral movement, bulk data extraction, or any action that could disrupt your users or operations.
03

Findings, validation, and reporting

Our focus is finding real security bugs and giving your team enough evidence to fix them. We validate a finding with the minimum proof needed to demonstrate impact. We do not exploit a vulnerability beyond that point, and we do not use a finding to access data or systems outside the agreed scope.

Findings are reported directly to you. We do not sell, publish, or share assessment results with a third party without your written permission. We do not sell or share your codebase, credentials, or target information.

04

Confidentiality and data handling

We treat your target details, code, credentials, and findings as confidential. Access is limited to the Vulcan team members who need it to deliver the assessment.

We do not sell, rent, or trade your information. Our service providers process data only to help us run the assessment and the business, under confidentiality and data-protection obligations.

Vulcan does not maintain its own servers. Data is hosted on third-party infrastructure providers, including cloud hosting, database, authentication, and email services. Those providers may process data in other countries, subject to their safeguards.

05

Your responsibilities

You are responsible for having the right to request testing, for telling us about sensitive systems or data, and for providing safe test accounts and entry points. Where possible, use staging environments and synthetic data rather than production customer data.

You are also responsible for remediating findings and for deciding what to deploy. We provide evidence, severity, and fix guidance, but we do not guarantee that a fix is complete or that an assessment will find every possible issue.

06

No guarantee

A security assessment is a point-in-time review, not a warranty that a system is free of vulnerabilities. To the maximum extent permitted by law, Vulcan provides the assessment without implied warranties and is not liable for indirect or consequential loss. Nothing in these terms limits liability that cannot legally be limited.

07

Changes and contact

We may update these terms as our service changes. Material changes will be posted on this page with a new date. Questions about scope, authorization, or these terms can go to vulcan@hyperdyn.in.

Questions about this policy?

Email vulcan@hyperdyn.in and a lead will answer directly.