Skip to content
SumioSumio home
Start Free
Trust

Built so the AI can't hurt your data

Everything below is an implemented behavior of the engine — not a policy aspiration. If we haven't built it, it isn't on this page.

Your data

  • Sensitive values (card numbers, SSNs, Aadhaar/PAN, emails, phones) are detected and masked before anything reaches the AI — raw values never leave the trusted backend.
  • Your uploaded file is read-only. Every operation produces a new version; the original is never modified.
  • Files are processed in memory for your request and are never used to train any model.

The AI

  • The AI only proposes a small, validated Operation Plan — trusted code performs the changes, so a misread can never silently corrupt your data.
  • Destructive steps (deleting columns, dropping rows) show their concrete impact and wait for your confirmation.
  • Results are computed from your data, never invented; low-confidence analyses are labeled, and insufficient data is declined rather than guessed.

Access & transport

  • Passwords are hashed (bcrypt) on the server and never seen by the AI; sign-in uses short-lived signed tokens.
  • Optional two-factor authentication (TOTP) works with any standard authenticator app, with one-time recovery codes as a backup.
  • Enterprise single sign-on via OpenID Connect (Okta, Azure AD, Auth0, Google Workspace…) once your admin connects an identity provider.
  • AI keys and connector credentials live in server-side environment variables — never in the browser bundle, never returned by the API.
  • Per-IP rate limiting and origin-locked CORS protect the API; technical errors are translated so internals never leak.

The life of your data

  1. Stage 1
    Upload

    Read into memory over HTTPS; the file itself is not written to long-term storage.

  2. Stage 2
    Processing

    Transforms run in memory against a validated plan. PII is masked before any AI call.

  3. Stage 3
    Results

    Generated downloads are kept temporarily so links survive a restart, then evicted automatically (7-day cap, size-bounded).

  4. Stage 4
    Account data

    Your email and hashed password persist in the database. Delete your account data anytime from Settings.

What we don't claim (yet)

SAML specifically and formal certifications (SOC 2) are on the enterprise roadmap and intentionally not presented as controls today — we'd rather omit one than show one that doesn't enforce anything. (Two-factor authentication and SSO via OpenID Connect, by contrast, are live — 2FA in Settings, SSO once your admin connects a provider.) For contractual details see the Data Processing Addendum and Privacy Policy.