generated: '2026-08-12'
method: searched
probe: true
source: https://empowerly.com/security
program:
  formal_vdp: false
  bug_bounty: false
  safe_harbor: null
  note: >-
    Empowerly publishes NO formal vulnerability disclosure policy, no responsible-disclosure page,
    no safe-harbor language, and no bug bounty. /responsible-disclosure and /vulnerability-disclosure
    both 404, and /.well-known/security.txt is not served (the S3 origin answers 403 AccessDenied for
    the path, which is an absence rather than a gate). What DOES exist is a reachable security
    contact address published on the security commitments page, alongside a statement that
    vulnerabilities are patched by severity. A researcher has somewhere to send a report; they have
    no published policy, scope, or disclosure timeline to rely on.
contact:
- type: email
  value: security@empowerly.com
  source: https://empowerly.com/security
  published_purpose: SOC 2 report requests (no stated vulnerability-intake purpose)
security_txt:
  served: false
  probed:
  - url: https://empowerly.com/.well-known/security.txt
    http_status: 403
    note: S3 AccessDenied XML — no document served
  - url: https://api.empowerly.com/.well-known/security.txt
    http_status: 403
bounty_platforms_checked:
- platform: HackerOne
  found: false
- platform: Bugcrowd
  found: false
- platform: Intigriti
  found: false
evidence:
- url: https://empowerly.com/security
  http_status: 200
  fetched: '2026-08-12'
- url: https://empowerly.com/responsible-disclosure
  http_status: 404
- url: https://empowerly.com/vulnerability-disclosure
  http_status: 404
- url: https://empowerly.com/.well-known/security.txt
  http_status: 403
recommendation: >-
  Serving an RFC 9116 /.well-known/security.txt naming security@empowerly.com, plus a one-page
  disclosure policy with scope and safe harbor, would convert an implicit contact into a real
  program at near-zero cost.