Privacy Gateway v0.1 / MIT

01 Local-first PII boundary

Useful data goes out.
Sensitive data stays in.

One policy-controlled boundary sits between your data and any API, model, agent, or pipeline. It detects, transforms, audits, and restores, and it does not lock your stack to a single vendor.

Build a policy Read the source
  • MIT licensed
  • fail closed
  • runs offline
  • py + ts cores
policy.financetransform.log

before

Ask maya@acme.com about card 4111 1111 1111 1111.

transform

protected

Ask [[PG1|EMAIL|…]] about card [[PG1|CARD|…]].

2 values protected0 originals forwarded
17entity types
7transform actions
4trust modes
1portable policy

02 Guided setup

Build the boundary you actually need.

No all-or-nothing switch. Every rule stays visible and yours to change.

  1. 1StartChoose a baseline
  2. 2PolicyControl each type
  3. 3TrustChoose key custody
  4. 4TestPreview locally
  5. 5ConnectCopy your setup

Step 1 of 5

What are you protecting?

Pick the closest starting point. You can change every rule next.

Step 2 of 5

Decide what happens to each type.

Enabled rules are evaluated locally before data crosses the boundary.

Reversible Reduced precision Irreversible

Step 3 of 5

Where should restoration keys live?

This choice controls who can turn protected values back into originals.

Mapping retentionHow long reversible mappings may exist
Decision-audit retentionHow long classification metadata may exist. Originals are never audit fields.

Step 4 of 5

See your policy before you install.

This lightweight preview runs in your browser and never leaves this page. Run the installed verification probe before relying on your full detector set.

View generated policy JSON

            


            

              
Step 5 of 5

              
Your gateway configuration is ready.

              
Choose an integration, copy the snippet, then follow the verification check.

              

              

                
              

              

              

                
1
Save policy.jsonDownload the exact policy you just reviewed.

                
2
Run the probeConfirm PII cannot cross your configured boundary.
privacy-gateway verify

                
3
Need help?Point your coding agent at AGENT-GUIDE.md.
Open guide

              

            


            

              
              1 / 5
              
            

          

        

      


      

        

          
03 One boundary, any source

          
Designed to fit in, not take over.

        

        
    
          
  1. 
            01
            
    Detect locally
    Regex, checksums, allow and deny lists, Presidio, and pluggable recognizers run on your own host and record explicit provenance for every finding.
    
          
    2. 
          
  2. 
            02
            
    Apply policy
    Deterministic precedence turns each finding into a visible decision: keep, redact, tokenize, hash, generalize, or replace with a format-valid synthetic value.
    
          
    3. 
          
  3. 
            03
            
    Cross safely
    Only protected data reaches the external model, API, agent tool, webhook, or warehouse. If detection cannot complete, the call is blocked rather than sent.
    
          
    4. 
          
  4. 
            04
            
    Restore deliberately
    Client-held capsules or encrypted vault mappings restore approved output, while queryable audit records explain every classification and decision.
    
          
    5.