← Security

Vulnerability Disclosure Policy

Draft — pending legal review. Not a final legal commitment.

We take security seriously and welcome reports from security researchers. This policy describes how to report a vulnerability responsibly and what you can expect from us in return.

Scope

In scope: the ExposureIQ application and its infrastructure as controlled by this codebase — authentication, authorization, tenant isolation, the discovery/ correlation engine, the Server Action API surface, and the database/RLS layer.

Out of scope:

  • Vercel's or Supabase's own platform (report to them directly)
  • Denial-of-service or load testing against our production infrastructure
  • Social engineering or phishing attempts against ExposureIQ staff
  • Automated scanning that generates excessive traffic
  • Findings requiring physical access to a device
  • Third-party services we integrate with but don't control (CISA, NVD, FIRST, Resend)

What not to do

  • Don't access, modify, download, or delete another customer's data — even to demonstrate impact. Scope any proof-of-concept to your own test account.
  • Don't run automated vulnerability scanners against our production systems without prior written permission.
  • Don't attempt denial-of-service.
  • Don't use ExposureIQ to scan or attack any third party's infrastructure while researching ExposureIQ itself.
  • Don't publicly disclose a vulnerability before we've had a reasonable opportunity to remediate it, unless we've explicitly agreed to an earlier disclosure date with you.

How to report

Include:

  • A clear description of the issue and its impact
  • Steps to reproduce
  • Any relevant proof-of-concept, scoped to your own account/data only

Our response process

  1. Acknowledgment within 3 business days.
  2. Triage and severity assessment within 10 business days — we may ask follow-up questions.
  3. Remediation, prioritized by severity — critical issues first, with progress updates.
  4. Resolution confirmation — we'll let you know once fixed, and you're welcome to verify.
  5. Credit, with your permission, once the fix has shipped.

These are operational targets, not contractual SLAs.

Safe harbor

Standard responsible-disclosure “safe harbor” language — a commitment not to pursue legal action against good-faith researchers who follow this policy — requires legal drafting to be enforceable and appropriately scoped, and hasn't been finalized yet. Don't treat the absence of this section as an invitation to test outside the scope stated above in the meantime.

Legal

This policy does not grant permission to violate any law. Independent legal risk (e.g., under the Information Technology Act, 2000 in India, or equivalent laws elsewhere) is not eliminated by following this policy — it describes ExposureIQ's own response commitment, not a blanket legal authorization.