Security & trust

Effective date: September 1, 2026Last updated: September 1, 2026

Privacy at a glance

Privacy-first by design for households—not a HIPAA-covered health plan or clinic for this direct-to-consumer product.
Built with HIPAA Security Rule–inspired safeguards (access control, encryption in transit, document PII redaction, private storage)—without claiming HIPAA certification.
We do not sell your health information to advertisers or data brokers.

Family-scoped access: Signed-in sessions (Clerk) and household (organization) checks gate plans, documents, chat, and claims. APIs derive identity from the session—not from body fields you could forge.
Encrypted in transit: TLS for the website, APIs, auth, storage fetches, and vendor calls.
Private file storage: Uploads use private object storage with server-side signed reads—not public URLs.
Document PII redaction + encrypted vault: After extraction, identifiers are redacted before most follow-up AI analysis; plaintext PII maps are stored with AES-256-GCM when the vault key is configured.
Database lockdown: Supabase PostgREST roles are revoked; the app talks to Postgres from our servers only.
Your controls: Export or schedule deletion under Settings → Your data; AI consent under Settings → Privacy & AI.

We are not “HIPAA compliant” or “HIPAA certified” for this consumer product, and we are not acting as your HIPAA business associate here.
We do not currently hold SOC 2, ISO 27001, or HITRUST attestations for BenAsk.
We do not say we “never send data to third parties.” Auth (Clerk), hosting (Vercel), database (Supabase), and AI (OpenAI) process data as described in our Subprocessors list and Privacy Policy.
We avoid vague slogans like “bank-level” or “military-grade” encryption.

Security & trust

Effective date: September 1, 2026Last updated: September 1, 2026

Privacy-first by design for households—not a HIPAA-covered health plan or clinic for this direct-to-consumer product.
Built with HIPAA Security Rule–inspired safeguards (access control, encryption in transit, document PII redaction, private storage)—without claiming HIPAA certification.
We do not sell your health information to advertisers or data brokers.

Family-scoped access: Signed-in sessions (Clerk) and household (organization) checks gate plans, documents, chat, and claims. APIs derive identity from the session—not from body fields you could forge.
Encrypted in transit: TLS for the website, APIs, auth, storage fetches, and vendor calls.
Private file storage: Uploads use private object storage with server-side signed reads—not public URLs.
Document PII redaction + encrypted vault: After extraction, identifiers are redacted before most follow-up AI analysis; plaintext PII maps are stored with AES-256-GCM when the vault key is configured.
Database lockdown: Supabase PostgREST roles are revoked; the app talks to Postgres from our servers only.
Your controls: Export or schedule deletion under Settings → Your data; AI consent under Settings → Privacy & AI.

We are not “HIPAA compliant” or “HIPAA certified” for this consumer product, and we are not acting as your HIPAA business associate here.
We do not currently hold SOC 2, ISO 27001, or HITRUST attestations for BenAsk.
We do not say we “never send data to third parties.” Auth (Clerk), hosting (Vercel), database (Supabase), and AI (OpenAI) process data as described in our Subprocessors list and Privacy Policy.
We avoid vague slogans like “bank-level” or “military-grade” encryption.