Skip to content

Security policy

Responsible disclosure

How we handle security issues we find in public organizations, and how to tell us about an issue in our own systems.

  • Last updated Nov 18, 2026

Part 1: Issues we find in public organizations

How we disclose

Through our free public-data health check, we sometimes see a problem in what a public organization shows the internet. When we do, we follow coordinated disclosure:

  1. We tell you first, privately

    We write to the contacts your organization lists publicly, explain what we saw from outside, and how this kind of issue is usually fixed.

  2. We bring in help where appropriate

    If an issue is serious, or we can’t reach anyone, we may share it with your state’s chief information security officer (CISO) or with CISA, so it reaches you through official channels and you have support fixing it.

  3. We stay available

    Your team, your IT vendor or the agency helping you can ask us questions about what we saw. There is no charge for this, and no sales pitch attached.

  4. We never publish it

    We never publish details that identify an organization or its issue. The figures we do publish are aggregate counts only.

Findings from paid engagements belong to the client and are handled under that engagement’s agreement.

What we never do

  • Exploit an issue, log in, or access anything that isn’t public, to confirm a finding or for any other reason.
  • Ask for payment, or make any information conditional on buying a service.
  • Name an organization, or share its findings with anyone outside your organization, your state CISO or CISA, unless a court or the law compels us (and then we tell you first where the law allows).
  • Keep checking your domains after you opt out.

Part 2: Issues in our own systems, and how to report them

Scope

We welcome reports from security researchers and anyone else who finds a weakness in our systems. This policy covers our own systems, and nothing else:

In scope

  • americasecure.com and its subdomains
  • Our public-data health check scanner, including if it ever behaves differently from what we describe

Out of scope

  • Denial-of-service, load or volumetric testing
  • Social engineering or phishing of our team, and physical attacks
  • Third-party services we use (please report those to the vendor)
  • Automated scanner output without a demonstrated security impact
  • Systems belonging to any public organization, including ones we have notified

How to report

Email team@americasecure.com with “Security report” in the subject. A useful report covers four things:

What to include

To
team@americasecure.com
Subject
Security report
  • What and whereThe issue, and the URL or system it affects
  • How to reproduceSteps, with any proof of concept
  • ImpactWhat you believe an attacker could do with it
  • CreditHow you’d like to be credited, if at all

Encrypted email isn’t supported yet. We don’t publish a PGP key, so please don’t email credentials or personal data. If your report involves sensitive details, say so and we’ll arrange a secure way to receive them.

Our contact details are also published in /.well-known/security.txt.

Guidelines

To stay within this policy, please:

  • Act in good faith, and only access what you need to demonstrate the issue.
  • Don’t view, change or delete data that isn’t yours. If you come across personal information, stop and tell us.
  • Don’t degrade our services or anyone’s experience of them.
  • Give us a reasonable chance to fix the issue before you discuss it publicly.

Our commitments

When you report an issue under this policy, we will:

  • Confirm and update

    We confirm we have your report, and keep you informed as we look into it.

  • Fix and tell you

    We fix confirmed issues, and tell you when they are fixed.

  • Credit you

    We credit you publicly for the find, if you’d like us to.

We don’t currently run a paid bug bounty program.

Safe harbor

We want people who find a weakness in our systems to feel safe telling us about it. Research that makes a good-faith effort to follow this policy is covered by these protections.

If you follow this policy, we will:

  1. Consider your research authorized, and not pursue or support legal action against you for it.
  2. Not bring a claim against you for working around technical measures, to the extent the research needed it.
  3. Treat your research as an exception to any part of our terms that would otherwise prohibit it.
  4. Make clear that you acted under this policy if anyone else brings legal action over your research.

Limits. This safe harbor covers America Secure’s own systems only. It doesn’t authorize testing of any other organization’s systems, including the public organizations we notify.

If you’re unsure whether something is covered, ask us first at team@americasecure.com.

Questions

Questions about this policy, or about an email you received from us? Write to team@americasecure.com.

How the health check works