Security

A short overview of security at OHSupport, and how to report a vulnerability to Obsidian Heron.

Last updated: October 5, 2026

Obsidian Heron operates OHSupport on Cloudflare. These are the main protections:

  • Encryption in transit. All traffic uses HTTPS. The site sends HSTS and content security policy headers.
  • Encryption at rest. Cloudflare encrypts the data in D1. OHSupport also encrypts the keys and tokens of integrations with AES-256-GCM.
  • Tenant separation. Each request works in one tenant. A request for the data of another tenant gets 404.
  • Sign-in. Sign-in links and Google sign-in. Sign-up is only by invitation. A session uses an HttpOnly cookie and ends after 12 hours without use.
  • Access controls. Agents have roles, and can have access to some brands only. OHSupport keeps API keys only as hashes.
  • Webhooks and email. OHSupport checks the signature of each webhook. A reply by email joins a conversation only if the sender passes the SPF, DKIM or DMARC check.

For the data that we process for clients, see the Data Processing Agreement.

Browser protections

The Worker adds these headers to each page that it renders:

  • Strict-Transport-Security with a period of one year. It includes subdomains.
  • Content-Security-Policy that allows scripts, fonts and images from this site only. The one exception is the script of Cloudflare Web Analytics.
  • X-Frame-Options: DENY and frame-ancestors 'none'. No other site can show OHSupport in a frame.
  • X-Content-Type-Options: nosniff and a strict referrer policy.

Sessions and sign-in links

On ohsupport.app, the session cookie has the __Host- prefix. It is Secure, HttpOnly and SameSite=Lax. Scripts on the page cannot read it.

A request that changes data and uses the cookie must come from the origin of the app. OHSupport refuses other origins. A sign-in link works for 10 minutes and one time. OHSupport keeps only a hash of it. OHSupport also limits the rate of sign-in requests.

Protection of integrations

  • The chat widget works only from the origins that you allow for the brand.
  • A handoff token must use the HS256 algorithm and must expire in one hour or less. OHSupport rejects all other tokens.
  • Each webhook and each request to the agent sidebar has an HMAC-SHA256 signature and a time stamp.
  • OHSupport sends webhooks only to public HTTPS addresses. It does not follow redirects.
  • AI help makes drafts only. OHSupport does not send a draft to a customer. An agent reads it, changes it and sends it.

Report a vulnerability

Send an email to security@ohsupport.app. Give the steps that show the problem, and the URL or the API endpoint. We reply in 5 business days.

  • Test only with accounts and data that you own.
  • Do not get access to the data of other customers. Do not change or delete it.
  • Do not do denial-of-service tests or spam. Do not try to deceive our staff.
  • Give us a reasonable time to correct the problem before you make it public.