Security

How BoundOS protects the documents and data agencies trust us with.

Our approach

BoundOS handles sensitive insurance documents, so security is built into how the product works — not bolted on. This page describes the practices in place today.

Infrastructure and encryption

• The Services run on established cloud platforms (Supabase, Railway, Vercel).
• Data is encrypted in transit using TLS/HTTPS.
• Data is encrypted at rest by our managed database provider.
• Secrets and API keys are stored in platform-managed environment configuration, kept out of client-side code, and rotated when needed.

Authentication and tenant isolation

• Users authenticate through a managed identity provider; sessions use signed, expiring tokens verified on every request.
• Every data request is authorized against the user’s identity and their membership in the specific agency whose data is requested — one agency cannot read another’s data.
• Each agency’s documents, briefs, leads, and AI search index are segregated by agency, so document search only returns that agency’s own content.
• Privileged database credentials are used only server-side; the browser never holds them.
• Newly provisioned users are required to change a temporary password before accessing the dashboard.

Data handling and minimization

• Uploaded document files are processed transiently and deleted after processing; we retain the extracted data, not the raw files.
• Sensitive personal identifiers (such as Social Security, driver’s license, and bank or card numbers) are automatically redacted from document text before it is indexed for in-product search.
• Shareable client links use unguessable tokens and expire automatically.
• For the website widget, generated proposals are delivered to the visitor by email rather than exposed through the public widget, and visitor documents are not added to the searchable store.
• Our AI providers process inputs to return results and do not use them to train their models.

Application security

• Uploads are validated by type, size, and content signature, with per-request file and size limits.
• Rate limits and per-account usage quotas guard against abuse and runaway cost.
• Cross-origin access is restricted to known origins; the embeddable widget is constrained to each customer’s authorized domains.
• We follow least-privilege access and review changes before release.

Reporting a vulnerability

If you believe you’ve found a security issue, please email security@boundos.app with details and steps to reproduce. Please give us a reasonable opportunity to investigate and remediate before any public disclosure; we will not pursue good-faith researchers who follow this process.