Legal

Security & Responsible Disclosure

Effective: April 20, 2026

Plain-English summary

If you've found a security issue in FirmBase, email security@firmbase.build and we'll acknowledge within 48 business hours. Please don't test on customer data or publicly disclose before we've fixed the issue. We don't pay bounties yet, but we credit reporters (with permission) in release notes and we won't threaten legal action against good-faith researchers.

1. What we run

FirmBase is a Next.js application hosted on Vercel, backed by a managed Postgres database (Neon), file storage on Vercel Blob, and transactional email via Resend. Authentication is JWT-in-httpOnly- cookie. All application code is written by Arthur Wilmoth (with AI-assisted drafting). Vulnerabilities in third-party services should be reported to the respective vendor; we'll coordinate if the issue affects us.

2. Scope

In scope for responsible disclosure:

  • firmbase.build and its subdomains
  • firmbase.app (if and when we launch it)
  • APIs under /api/ served from the above domains

Out of scope:

  • Vercel, Neon, Resend, Stripe, Sentry, Anthropic, Google, LinkedIn, or any other third-party we depend on — report directly to them.
  • Social engineering of FirmBase employees (there's one; he's busy).
  • Physical attacks on Arthur's home office.
  • Denial-of-service (please don't), volumetric scanning, or any testing that would impact real customer data or availability.

3. How to report

Email security@firmbase.build. Include:

  • A clear description of the vulnerability
  • Steps to reproduce (ideally a minimal proof-of-concept)
  • Impact assessment (what can an attacker do?)
  • Your contact info so we can follow up
  • If you want credit, how you'd like to be named (handle, real name, or anonymous)

Do NOT include real customer data in your report. If your proof-of- concept requires touching real data, stop and describe the path abstractly instead.

4. What happens next

  1. Within 48 business hours: we acknowledge receipt.
  2. Within 7 days: we confirm whether the report is reproducible and in scope, and give you a tentative severity assessment + fix timeline.
  3. Fix timeline depends on severity:
    • Critical: targeting 48 hours to patch
    • High: targeting 7 days
    • Medium: targeting 30 days
    • Low: next regular release
  4. After the fix: we notify you, credit you in the release notes (if you want), and encourage public disclosure within the next 30 days if you'd like to write it up.

5. Safe harbor

We won't take legal action against researchers who follow this policy in good faith. "Good faith" means: you tested only on accounts you own, you didn't access or modify real customer data, you didn't disclose publicly before we patched, and you didn't extort or threaten us. If you broke any of those in the course of a report, we may not extend the same protections.

6. Bounty

We don't run a paid bounty program yet. When we add one (typically around SOC 2 time), it'll be listed here. In the meantime, we'll send swag + public credit (if you want it) + a personal thank-you from Arthur.

7. Contacting us about non-security issues

Customer support goes to support@firmbase.build. Privacy requests (data access, deletion, etc.) go to privacy@firmbase.build. Legal notices (DMCA, subpoenas, etc.) go to legal@firmbase.build.