Security

Every workspace is fully isolated. Row-level security (RLS) in our database ensures no tenant can read or write another tenant's data — not through the UI, not through the API, not through MCP tools. Membership is verified server-side on every request.

Recipient briefing links are token-scoped, time-limited, and single-use. Tokens are stored as cryptographic hashes — the raw token is never persisted. Pricing-related briefs are visible only to assigned recipients.

We do not use tracking pixels to determine if a recipient has read a brief. "Viewed" is recorded only when the recipient actually opens the briefing page. Acknowledgment requires an explicit action.

Every status-changing action records the actor, timestamp, previous and new value, and provenance (web, API, or MCP). No silent destructive writes occur.

Data processing

We use the following processors: hosting (Bolt/Netlify), database (Bolt Database/Supabase), and transactional email (SendGrid). We do not track user behavior, sell data, or use tracking cookies. For customer workspace data, the operator acts as a processor; a Data Processing Agreement is available on request.