DocsOpen appApp

INTEGRATE SHREDDAR / PUBLIC ALPHA

ONE PRIVACY LAYER.
YOUR WORKFLOW.

Use SHREDDAR directly, put it in front of a project's model traffic, or make it the guard between an AI agent and its tools. Start with what works now; keep planned adapters clearly separate.

CHOOSE YOUR PATH ↓API REFERENCE →
INDIVIDUAL
BROWSER LOCAL
PROJECT
SELF-HOSTED GATEWAY
AI + AGENT
MODEL / TOOL GUARD
A private document is divided into bounded SHREDDAR routes before sparse protected context reaches separate AI destinations
BOUNDARY ACTIVESOURCE → SHREDDAR → DESTINATIONONLY POLICY-APPROVED CONTEXT MOVES
WORKFLOW CONTROL / 01ADD THE BOUNDARY WHERE CONTEXT LEAVES.

CHOOSE YOUR ENTRY POINT

One boundary.
Three ways in.

Start in the browser, place the gateway inside a project, or mediate an agent's model and tool calls. Each route states exactly what is live now.

NO INSTALL / BROWSER LOCAL

Inspect before you share.

Use the working browser lab to reduce a document to the facts an AI task actually needs. The source and identity mapping remain in the current tab.

STATUS
LIVE IN PUBLIC ALPHA
RUNS IN
THIS BROWSER TAB
01 / SOURCEPRIVATE SOURCE
02 / CONTROLBROWSER SHREDDARPOLICY · MINIMIZE · RECEIPT
03 / DESTINATIONREVIEWED OUTPUT
  1. 01

    Choose a safe source

    Start with a synthetic case or text you are authorized to process. TXT, Markdown, CSV, and JSON are supported up to 1 MB.

  2. 02

    State the exact task

    A narrow purpose lets SHREDDAR remove unrelated contact, financial, identity, and credential data.

  3. 03

    Review the outbound view

    Compare the private source, protected representation, simulated answer, local STITCH result, and metadata-only receipt.

  4. 04

    Send only after review

    The public lab does not call an external model. Copy the protected output only when it matches your intended boundary.

BOUNDARY PLAN
SOURCE     synthetic or authorized text
TASK       one explicit purpose
POLICY     balanced | strict | maximum
REVIEW     inspect OUTBOUND before use
EVIDENCE   retain the metadata-only receipt
No account, API key, wallet, or upload is required for the browser proof.
AVAILABLE NOW
  • Editable local source
  • Three privacy modes
  • Decision-by-decision inspection
  • Receipt JSON + integrity hash
BOUNDARY / NEXT

PDF, DOCX, OCR, and production-sensitive document handling remain self-hosted roadmap work.

OPEN THE APP LAB ↗

THE OPERATING PATTERN

Same controls.
Every surface.

Integration changes where the privacy boundary runs—not the responsibility to define purpose, review output, and validate the deployment.

01

Start with purpose

Describe the job before moving context. A narrower task gives the compiler a stronger basis for removing unrelated facts.

02

Keep control local

Run detection, policy, identity mappings, and reconstruction inside the browser or infrastructure you trust.

03

Inspect every boundary

Review the protected representation before a model or tool receives it, then inspect returned output before STITCH.

04

Retain evidence, not source

Use privacy-minimized receipts for operations and debugging without turning prompts or Vault mappings into telemetry.

ALPHA BOUNDARY

Integrate what exists.
Label what comes next.

LIVE

Browser-local product lab

Deterministic detection, task-aware transformation, local reconstruction, and metadata-only receipts run in the current tab.

LIVE / SELF-HOSTED

OpenAI-compatible gateway

Authenticated non-streaming chat, protect, reconstruct, policy, Vault, output guard, and receipt routes run inside deployer-controlled infrastructure.

PLANNED

Native MCP, ACP + x402

These dedicated adapters are roadmap interfaces. They are not represented as working capability until their routes, tests, and verification evidence exist.

TRY THE BROWSER LAB ↗REVIEW SECURITY →