Trust · draft

Security

This page describes the controls built into UpVoiced today, in plain language. UpVoiced has no security certification (such as SOC 2 or ISO 27001) and no external audit yet.

Keeping workspaces apart

• Every table that holds customer data carries a workspace ID and is protected by PostgreSQL row-level security. The application’s database role cannot bypass it, and automated tests check that one workspace cannot read another’s data.
• The workspace for each request comes from the verified sign-in, never from the request body.

Sign-in and keys

• Team members sign in through Clerk. End users sign in with a one-time email code.
• Single sign-on tokens from your app are signed with a per-workspace secret, expire within minutes and work only once.
• API keys are shown once, stored only as hashes, scoped and rate-limited.

Content and integrations

• Posts and changelog entries are rendered from Markdown through a strict allowlist, and our pages use a Content Security Policy.
• Branding import fetches only public web addresses, re-checks every redirect and refuses internal networks.
• Webhooks we receive from payment and email providers are verified by signature, and the webhooks we send are signed so you can verify them.

Operations

• All traffic uses HTTPS with HSTS.
• Our monitoring removes URLs, query strings, client addresses and user fields before logs leave our servers.
• Dependencies are locked, GitHub Actions are pinned by commit, and every change runs dependency audits and secret scanning in CI.
• [Production backup and restore policy — to confirm before launch.]

Reporting a vulnerability

Please email [security contact — to confirm] with the details and steps to reproduce. Test only against your own workspace, do not access other people’s data and give us reasonable time to fix the issue before telling others. We do not run a paid bug bounty; with your permission we will thank you on this page.

Incidents and status

A public status page will be linked here and in the footer before launch.If a breach affects your data, we tell workspace owners as described in thedata processing agreement.