Relm · Vulnerability Disclosure

Relmcrm Com Vulnerability Disclosure

Vulnerability disclosure

Relm runs a coordinated vulnerability disclosure program on Hackerone. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CRMSalesContactsDealsSales PipelineAutomationWebhookMCPA2AAI AgentsAgent-NativeUnited Arab Emirates
Program: Hackerone security.txt present

Disclosure Policy

Security Contact

Contact
mailto:security@relmcrm.com

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-09-19'
method: searched
probe: true
source: well-known/relmcrm-com-security.txt (https://relmcrm.com/.well-known/security.txt, 200) + https://relmcrm.com/security (Responsible disclosure) + https://relmcrm.com/support
summary: >-
  A real but minimal disclosure channel: an RFC 9116 security.txt with a Contact, an Expires and a Canonical
  field (no Policy, no Encryption, no Acknowledgments), and a "Responsible disclosure" section on the security
  page that asks for reports by email and promises to "acknowledge and work with you in good faith". No bug
  bounty (not on HackerOne, Bugcrowd or Intigriti), no published response timeline, no safe-harbour statement,
  no PGP key.
contact:
- mailto:security@relmcrm.com
security_txt:
  file: well-known/relmcrm-com-security.txt
  url: https://relmcrm.com/.well-known/security.txt
  fields:
    Contact: mailto:security@relmcrm.com
    Expires: '2026-12-31T23:59:59.000Z'
    Preferred-Languages: en
    Canonical: https://relmcrm.com/.well-known/security.txt
  missing_fields: [Policy, Encryption, Acknowledgments, Hiring]
  valid: true
  expires_in_days_from_check: 103
disclosure_page:
  url: https://relmcrm.com/security
  section: Responsible disclosure
  quote: '"Found a vulnerability? Please report it to security@relmcrm.com. See /.well-known/security.txt. We will acknowledge and work with you in good faith."'
  http_status: 200
  fetched: '2026-09-19'
bug_bounty:
  program: none
  platforms_checked: [HackerOne, Bugcrowd, Intigriti]
response_commitment: none stated for security reports (general support aims for one business day — https://relmcrm.com/support)
safe_harbor: not stated
posture_statement: '"We are deliberate about the security basics above, and we are not going to claim certifications we do not yet hold (no SOC 2 badge theatre)." — https://relmcrm.com/security. No trust center and no certifications are published; no TrustCenter or Compliance pointer is emitted.'
evidence:
- source: well-known/relmcrm-com-security.txt
  kind: security.txt (harvested this pass, HTTP 200)
- source: https://relmcrm.com/security
  kind: responsible-disclosure section (HTTP 200)

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/relmcrm-com-vulnerability-disclosure"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.