Security

Last updated: June 2026

Our Approach

Heario supports two modes. On the free/BYOK path, your audio and meeting content are processed on your device and sent only to the AI provider you configure (Anthropic, OpenAI, Deepgram) — none of it reaches our servers. On a paid managed plan, your questions are sent to our backend (api.heario.ai) so we can relay them to our own Anthropic key and enforce your plan's usage limit; we do not store the content of your questions or answers beyond what's needed to process that single request.

Data in Transit

• All communication between Heario and external services uses TLS 1.2 or higher
• API keys you enter for the BYOK path are stored locally in a config file on your device and never transmitted to our servers
• If you're on a managed plan, your licence key is sent to our backend solely to verify your plan and process your request

Overlay Protection

Heario's answer overlay uses the Windows SetWindowDisplayAffinity(WDA_EXCLUDEFROMCAPTURE) API — the same mechanism used by banks and DRM software. This excludes the window from all screen-capture pipelines at the OS level, before any application (Zoom, Teams, OBS) can access the frame buffer.

Payment Security

Payments are handled entirely by Stripe, a PCI DSS Level 1 certified payment processor. Heario never sees, stores, or logs your card details.

App Shell Transparency

The desktop app shell (the Tauri/React wrapper you install) is published on GitHub so you can see how the window and overlay are built. The AI pipeline and our managed-plan backend are proprietary and not publicly source-available.

Responsible Disclosure

If you discover a security vulnerability in Heario, please report it privately before public disclosure. Email support@heario.ai with the subject line "Security Disclosure". We will acknowledge your report within 48 hours and work with you to resolve the issue promptly.