S
SageOps

Data Handling & Security

A plain-English summary of where your data lives, who can see it, and how we use AI. Last updated June 2026.

Where your data lives

SageOps runs on Supabase (managed PostgreSQL) for data and authentication, hosted on AWS in the United States (us-east-1), with the application served by Vercel. Data is encrypted at rest by the database provider and in transit over TLS. We do not run our own servers or store data on local machines.

Per-organization isolation

Every record belongs to an organization, and access is enforced at the database layer by PostgreSQL Row-Level Security— not just in application code. A signed-in user can only read or change rows for an organization they are a member of. There is no shared or cross-tenant view: one customer's projects, forecasts, and financials are never visible to another.

Who can see what

Access within an organization is role-based: owner, admin, member, and viewer. Members can create and view projects; updating a project is limited to its creator and admins; deleting projects and changing organization settings is limited to admins and owners. Membership is by invitation only.

How we use AI

SageOps' numbers come from a deterministic Monte Carlo engine, not from an AI model. AI is used only to write the narrative advice (“The Sage”): the project's details — name, description, sizing, team, budget, and risk context — are sent to Anthropic's API to generate that explanation. Anthropic does not use API data to train its models. If no AI key is configured, SageOps falls back to a built-in template and no project data leaves the system.

Authentication & secrets

Sign-in is handled by Supabase Auth, and every application route is gated by server-side session checks — unauthenticated requests are redirected to the login page. API keys and other secrets are stored as server environment variables, never in the database and never exposed to the browser.

What we don't collect or store

SageOps does not process or store payment-card data. We ask only for the project and organization information needed to produce a forecast. You can request deletion of your organization's data at any time.

What's on the roadmap (and not yet in place)

We believe in matching claims to reality. SageOps does not yet have SOC 2 certification, SSO/SAML, or a formal third-party audit trail. These are planned for our enterprise track. For SMB use on managed, isolated infrastructure, the controls above are in place today; we will not represent enterprise-grade compliance until it is independently verified.

Questions? Contact your SageOps administrator or Prudent Sagacity, LLC.

Back to dashboard →