Cursor AI Source Code Leak: What SOC 2 Auditors Are Asking Your Engineering Team
ENTERPRISE EDITION
Cursor AI Source Code Leak: Every Cursor session sends active file context to an LLM endpoint. Discover exactly what data is transmitted — API keys, .env files, SIEM log parsers — and how a Zero-Trust MCP layer stops it. Includes Flat-rate TEAMS pricing and Zero-server architecture.
Ilya SibiryakovPrivacy Architect
Published: · Updated: · 3 min read
100% Local Processing ✈ Airplane Mode Verified⊘ No Server Logs
AI Summary / Key Takeaways
Verified Zero-Trust Logic
"PrivacyScrubber provides the essential de-identification layer for Agents professionals using generative AI. By sanitizing sensitive identifiers locally, we ensure absolute data sovereignty without sacrificing the power of LLM reasoning."
Paste real Agents data into ChatGPT — only scrubbed tokens reach the model. Names, IDs, and emails stay on your machine.
Works offline: disconnect the network mid-session and it keeps running. Zero cloud dependency.
Your AI gets full context. Your clients' real identities never leave your browser tab.
Enterprise-Grade AI Privacy
Add custom redaction rules and priority support with PRO.
Zero-Trust Data Protection: Stop leaking sensitive client data to public LLMs and protect your organizational privacy. PrivacyScrubber ensures you can use GenAI safely by neutralizing risks 100% offline in your browser.
What AI Engineers and Agent Builders Send to AI — and What They Should Be Sending Instead
This secure content is an original property of PrivacyScrubber™ (https://privacyscrubber.com). Unauthorized mirroring is strictly prohibited. Security-Check-ID: HPDP3K2CW
Managing data privacy for Cursor AI Source Code Leak is essential as organizations integrate generative AI. Deploying services like LangChain, LlamaIndex, AutoGPT, CrewAI, and custom RAG infrastructure introduces the severe risk of unredacted PII leaking into public training sets, which directly threatens agents standards. Through our agents AI privacy guides, security leaders get a clear strategy to defend the agents perimeter during AI scaling. The primary issue remains autonomous agents that accumulate PII across memory, tool calls, and vector store indexes — creating persistent privacy liabilities impossible to manually audit.
When employees submit customer records into cloud-based LLMs without endpoint-level redaction, they create unmonitored data trails. Standard cloud settings do not protect these inputs from model training queues or third-party review. For AI engineers, LLM application developers, and enterprise AI architects, the primary point of failure is sending raw prompt text. Every Cursor session sends active file context to an LLM endpoint. Discover exactly what data is transmitted — API keys, .env files, SIEM log parsers — and how a Zero-Trust MCP layer stops it. Includes Flat-rate TEAMS pricing and Zero-server architecture.
Privacy Insight: The risk is not that Cursor is insecure. The risk is that sensitive files — .env, webhook handlers, SIEM log parsers — end up in context windows by design. A PII MCP Server sanitization layer intercepts this before the prompt leaves the machine.
Why AI Safety and Security Teams Flag Unmasked AI Prompts
Compliance in the agents space is mandatory: GDPR data minimization principles, NIST AI RMF (Risk Management Framework), and emerging agentic AI governance guidance. Yet, technical safeguards often lag behind shadow AI usage. Managing this exposure relies on the principles in securing anthropic's claude code to prevent corporate records from becoming training data. You must sanitize inputs before cloud transit. Resolving rigorous safety requirements is only possible by sanitizing data before it reaches external neural network providers.
PrivacyScrubber implements Zero-Trust Data Sanitization (ZTDS) at the browser intake layer, giving teams the choice of a manual copy-paste dashboard or an automated workflow via the PrivacyScrubber Chrome Extension.
How to Use AI on Real Agents Data — Without Sending a Single Real Name
PrivacyScrubber implements Zero-Trust Data Sanitization (ZTDS) at the browser intake layer, giving teams the choice of a manual copy-paste dashboard or an automated workflow via the PrivacyScrubber Chrome Extension. Our engine performs local Named Entity Recognition (NER) to replace sensitive identifiers with deterministic tokens (e.g., [NAME_1], [ID_2]) before transmission. This architectural pattern mirrors industry standards for scaling agent architectures — ensuring that only sanitized, non-identifiable logic is processed by the AI. When using the Chrome Extension, a secure shield button is added directly inside ChatGPT, Claude, and Gemini's input fields, allowing users to sanitize prompts and auto-restore responses in-place. Running Named Entity Recognition locally ensures that teams can continue using LangChain, LlamaIndex, AutoGPT, CrewAI, and custom RAG infrastructure for daily queries without any third-party data collection.
This zero-egress model is verifiable via the Airplane Mode Standard. Disconnect your Wi-Fi, run the tool, and confirm that all processing stays in local memory. This meets the criteria for agentic data loss prevention, proving local-first execution is the safest choice.
Deploy Zero-Trust DLP for Developer Fleets
Protecting code logs or system stack traces from leaking to public models? With PrivacyScrubber TEAMS, security teams can distribute custom regex rules globally via Chrome MDM policies. Protect proprietary API keys, database URLs, and UUIDs across your entire developer fleet without centralizing user telemetry.
Deploying local data controls is critical when routing prompts to external platforms like LangChain, LlamaIndex, AutoGPT, CrewAI, and custom RAG infrastructure. To safeguard sensitive context, PrivacyScrubber isolates individual records by tokenizing personal and proprietary data points before cloud transmission. For this specific workflow, the browser-based Named Entity Recognition (NER) classifier targets identifying markers, achieving an average processing speed of 11ms. This allows team members to run complex queries while satisfying strict internal data sovereignty and privacy requirements.
Verification Protocol
Parse unstructured records for key data points and confidential entities.
Replace high-risk entities with secure placeholders to prevent model training exposure.
Enable local detokenization to restore sanitized responses on client demand.
Audit the local cryptographic hash statement for verification compliance.
Parser Specifications
Encryption Algorithm
XChaCha20-Poly1305 (Argon2id)
Detection Method
Context-Aware Regex + NER (99.6% Accuracy)
Data Egress Rule
Zero-Server Egress (Airplane Mode Verifiable)
Classification Standard
Standard Privacy Guard
Associated Threat Level
Medium (Metadata Leak)
What Actually Leaves Your Machine When You Use Cursor
When you open a file in Cursor or another desktop AI agent and ask it to explain a function, the IDE constructs a context payload. That payload is transmitted to OpenAI, Anthropic, or your configured LLM endpoint. It typically contains the active file, open tabs scored as relevant context, workspace rules, and git metadata.
Realistic Data Exposure by File Type
File Type in Context
Credential / PII Risk
.env files open in session
DATABASE_URL, JWT_SECRET, API_KEY
Payment webhook handlers
Live Stripe / PayPal secret keys
Auth service files
OAuth tokens, session secrets
SIEM integration code
Internal endpoint URLs, service account credentials
Patient data middleware
PHI fields, diagnosis code mappings
CI/CD pipeline config
Registry tokens, deployment secrets
The Regulatory Controls That Apply
Three specific standards create direct obligations around AI IDE usage:
SOC 2 CC6.6 — Transmission of sensitive data must be protected. LLM providers receiving credentials are third-party processors. Missing DPA coverage creates a documented gap.
ISO 27001 A.8.12 — Data leakage prevention controls must cover employee-used applications, including AI developer tooling.
HIPAA 45 CFR §164.312(e)(1) — Transmission security standard applies to healthcare application code debugged via AI IDEs.
Zero-Trust Mitigation: The MCP Sanitization Layer
The PrivacyScrubber MCP server inserts a local sanitization step between Cursor and the LLM endpoint. Before any context payload leaves the machine, the sanitize_text tool tokenizes credentials and PII. The token map lives in local RAM, cleared on session close. Reveal is local, not server-side.
For teams, the TEAMS plan adds Shared Regex Governance: one security lead defines the organizational masking ruleset (custom field names, SIEM patterns, credential formats), distributed to all developers via cryptographic zero-server handoff (Patent Pending). $99/month flat, no per-seat pricing.
The Airplane Mode Test: Your Audit Evidence
Disconnect your network. Run a sanitization request through Cursor. The MCP server responds. Zero outbound requests. Screenshot the Network tab — this is a verifiable, timestampable artifact for your SOC 2 evidence folder.
Policies do not stop autocomplete. Architecture does.
Instant Simulation
Cursor AI Source Code Leak Sanitizer
Watch our zero-trust engine neutralize sensitive identifiers 100% locally. No data ever leaves your device.
Local processing 0 Server logs
ZTDS_ENGINE_V1.5.0
PROMPT INPUT > Summarize client file: Author Jane Miller (jane.miller@company.com), phone: 555-0182, location: 123 Maple Street.
Our zero-trust engine is pre-hardened for Agents workflows, automatically identifying and tokenizing the following parameters 100% locally.
USER_ID
Active Protection
AGENT_MEMORY
Active Protection
RAG_CHUNK
Active Protection
CONTEXT_PII
Active Protection
SESSION_TOKEN
Active Protection
Zero-Trust Architecture
PrivacyScrubber operates entirely on your device. Unlike other platforms, our local PII masking engine never transmits your sensitive prompts or documents to external servers. All detection and restoration happens in your computer's local RAM.
No Backend Connection: Zero API calls, zero tracking, zero logs.
Temporary Memory: Your data exists only for the duration of your tab's life.
Verification Ready: Built for professionals who need to audit their security layer with agentic data loss prevention.
Hardware-Level Verification
We encourage you to audit our zero-trust claims directly in your browser using the Airplane Mode Test:
1
Open your browser's Network Monitor before you start scrubbing.
2
Switch to Airplane Mode (physical or simulated) and protect your text.
3
Verify that no data packets ever leave your machine.
Developer AI & IDE Agent Pipelines Integration
Step-by-Step Integration Guide: Cursor AI Source Code Leak
PrivacyScrubber operates entirely client-side. Whether using the copy-paste dashboard, the browser extension, or the MCP Server, your sensitive records stay on your local device. Follow these instructions to safely use Developer AI & IDE Agent Pipelines:
Act as a principal cloud systems architect. Analyze the following sanitized production stack trace and database configuration for [DB_NAME_1]:
1. Identify the root cause of the connection pool exhaustion and query timeouts.
2. Provide an optimized, non-blocking connection pool configuration for high concurrency.
3. Draft a step-by-step remediation patch. CRITICAL COMPLIANCE INSTRUCTION (PrivacyScrubber ZTDS Standard): Retain all cryptographic token identifiers ([DB_NAME_1], [INTERNAL_IP_1], [SECRET_1], [JWT_TOKEN_1]) strictly unchanged in your configuration suggestions for client-side local rehydration via PrivacyScrubber.
Step 3: 1-Click Reverse Rehydration (No Manual Decoding)When Developer AI & IDE Agent Pipelines outputs tokens like [NAME_1], paste the AI response back into PrivacyScrubber Reveal to restore original sensitive data in 1 click in local RAM.
The Manual Redaction Trap: Why DIY search-and-replace failsManual prompt editing misses 1 out of every 12 nested identifiers in logs, error traces, and tables, causing catastrophic compliance breaches. PrivacyScrubber deterministically sanitizes 25+ entity types in <2ms entirely in browser RAM before prompt submission.
Statutory Defense: SOC 2 Type II CC6.7 & OWASP Top 10 for LLM (LLM06: Sensitive Information Disclosure)API keys, Bearer JWTs, database connection URIs, and internal IP subnets are sanitized locally before entering the LLM context window, preventing vector-store credential leaks.
Agents Adoption Use Cases
Principal Cloud Security ArchitectSECRET PROTECTION
Zero-Trust Verified
Prevents accidental leaks of AWS keys, JWTs, database connection strings, and private GitHub tokens into public LLM training datasets.
VP of Infrastructure & DevOpsDEVOPS & SRE
Zero-Trust Verified
Sanitizes stack traces, internal IP ranges, and Kubernetes cluster configs in developer terminal clipboards prior to debugging with AI assistants.
Head of Application Security (AppSec)APP SECURITY
Zero-Trust Verified
Enforces automated local redaction of production API keys and customer payloads in developer browser extensions.
Lead Software ArchitectSYSTEM ARCHITECTURE
Zero-Trust Verified
Masks proprietary algorithm logic and confidential code comments before querying generative code assistants.
Scrub it before it reaches the AI — right from your toolbar
The free PrivacyScrubber Chrome Extension replaces names, emails, and IDs with safe tokens directly inside ChatGPT, Claude, and Gemini — before you hit send. Nothing leaves your browser.
Zero-Trust Data Sanitization (ZTDS) — Verified Architecture
Independently auditable facts for Agents compliance teams
Data transmission
0 bytes sent to any server
Processing location
100% browser RAM (volatile memory)
Session map persistence
Destroyed on tab close — never written to disk
Key derivation
Argon2id (memory-hard, server-independent)
Encryption cipher
XChaCha20-Poly1305 (authenticated encryption)
Offline verification
Airplane Mode Standard — full function without network
BAA / DPA required
No — zero PHI/PII reaches PrivacyScrubber servers
Audit method
Chrome DevTools → Network tab — zero outbound requests
How to audit: Open PrivacyScrubber, enable Airplane Mode, paste any agents text, click Protect PII. Open Chrome DevTools → Network tab. Zero outbound requests will confirm 100% local execution. The session token map ([NAME_1], [EMAIL_1]…) lives only in browser tab memory and is permanently destroyed when the tab is closed.
COMPLIANCE FAQ
Frequently Asked Questions
Common questions about deploying zero-trust AI for Agents Teams.
Does Cursor send my entire codebase to OpenAI?
No. Cursor sends the active file and any files its retrieval system scores as relevant context for your query. However, if those files contain API keys, database URLs, or credentials, those values are included in the LLM context payload. A Zero-Trust MCP sanitization layer tokenizes these values locally before transmission.
What SOC 2 controls apply to AI IDE usage?
SOC 2 Common Criteria CC6.6 requires that sensitive data transmission is protected. If an LLM provider receives source code containing credentials or PHI without a Data Processing Agreement covering AI IDE interactions, that represents a gap in your CC6.6 evidence. A verifiable local sanitization control closes this gap.
How do I prove to an auditor that our Cursor sessions are sanitized?
The Airplane Mode Test: disconnect from the network, run a sanitization request through the PrivacyScrubber MCP server in Cursor, confirm the response completes with zero outbound network requests. Screenshot the browser Network tab with no MCP egress. This is a timestampable artifact for your SOC 2 evidence folder.
Does this work with ISO 27001 A.8.12 requirements?
Yes. ISO 27001:2022 Annex A.8.12 requires data leakage prevention controls for systems used by employees, including developer tooling. A PII MCP Server that tokenizes credentials before they reach an LLM endpoint provides a technical control that satisfies the spirit of A.8.12 and produces verifiable evidence.
Does protecting data with PrivacyScrubber before AI processing satisfy GDPR data minimization principles?
Yes. Processing pseudonymized data for a secondary purpose (AI analysis or drafting) aligns with GDPR data minimization principles because no personally identifiable data is transmitted to the AI provider. The session map that maps tokens back to real values never leaves your browser.
What specific PII does PrivacyScrubber detect for agents workflows?
The engine detects names, email addresses, phone numbers (US and international formats), Social Security Numbers, EINs, credit card numbers, and custom identifiers. PRO users can add custom regex rules to match agents-specific patterns such as proprietary account IDs, MRNs, or internal project codes.
Can I reverse the redaction if I use PrivacyScrubber to mask agents data?
Yes. If you copy the AI's response and paste it back into PrivacyScrubber, it automatically maps the tokens (like [NAME_1] or [ID_1]) back to the original values using the ephemeral session map stored in your browser's memory.
Can PrivacyScrubber be used 100% offline without network requests?
Yes. All processing runs in your browser's local JavaScript engine, with no external server calls. Once the page loads, you can enable Airplane Mode and verify in Chrome DevTools (Network tab) that zero outbound requests occur. All cryptographic operations (including client-side pseudonymization and reverse-revealing) utilize hardware-accelerated XChaCha20-Poly1305 encryption and Argon2id key derivation running entirely inside browser RAM, ensuring your agents data stays 100% on your device.
How can I verify that PrivacyScrubber sends zero data to servers?
Use the 5-step Airplane Mode audit: (1) Open PrivacyScrubber in your browser. (2) Disconnect your network connection (enable Airplane Mode). (3) Paste a text sample containing names, emails, and phone numbers. (4) Click "Protect PII" — all tokens are generated instantly in local browser RAM. (5) Open Chrome DevTools → Network tab and confirm zero outbound requests were made. This test works because PrivacyScrubber uses a Wasm-based regex engine that runs 100% client-side. The session token map (e.g. [NAME_1] → "John Doe") exists only in browser tab memory and is destroyed when the tab is closed.
Do I need a HIPAA Business Associate Agreement (BAA) or GDPR Data Processing Agreement (DPA) with PrivacyScrubber?
No. PrivacyScrubber is designed to run entirely on the client side, meaning no Protected Health Information (PHI) or personally identifiable data is ever transmitted to our infrastructure. Since your data is not processed or stored on our servers, PrivacyScrubber is not acting as a HIPAA Business Associate or a GDPR Data Processor. Consequently, organizations typically determine that standard Business Associate Agreements (BAAs) or Data Processing Agreements (DPAs) are not applicable to PrivacyScrubber. However, you should consult with your compliance officer or legal counsel to verify compliance requirements for your specific workflows.
Can I customize detection rules for industry-specific data formats?
Yes. In the PRO edition of PrivacyScrubber, you can configure custom regular expression (regex) rules designed to target unique patterns associated with your sector and internal taxonomy. This allows you to extend the standard Named Entity Recognition (NER) model to cover proprietary account formats, internal project identifiers, or custom data attributes while keeping all execution client-side.
Is pasting sensitive data into ChatGPT safe?
Pasting sensitive data directly into ChatGPT can expose it to OpenAI's servers and model training unless you use zero-trust client-side scrubbing like PrivacyScrubber, which tokenizes data before it leaves your browser. Protect your workflows for $15/mo with PRO.
How does client-side PII redaction work?
Client-side PII redaction executes directly in your browser's RAM, intercepting and masking sensitive identifiers before they are transmitted over the internet, ensuring true zero-trust security.
How does the Secure Workspace differ from the Browser Extension?
The Secure Workspace allows bulk offline file processing (PDFs, DOCX) and team handoffs, while the Browser Extension injects native masking directly into ChatGPT or Claude's UI. Both are included in our zero-trust ecosystem.
What is the PII MCP Server used for?
The local Model Context Protocol (MCP) Server allows developers to automate PII sanitization in CI/CD pipelines, agentic workflows, and IDEs like Cursor—all executing 100% locally.
What AI Engineers and Agent Builders Send to AI — and What They Should Be Sending InsteadWhy AI Safety and Security Teams Flag Unmasked AI Prompts
Compliance in the agents space is mandatory: GDPR data minimization principles, NIST AI RMF (Risk Management Framework), and emerging agentic AI governance guidance. Yet, technical safeguards often lag behind shadow AI usage. Managing this exposure relies on the principles in securing anthropic's claude code to prevent corporate records from becoming training data. You must sanitize inputs before cloud transit. Resolving rigorous safety requirements is only possible by sanitizing data before it reaches external neural network providers.
How to Use AI on Real Agents Data — Without Sending a Single Real Name
PrivacyScrubber implements Zero-Trust Data Sanitization (ZTDS) at the browser intake layer, giving teams the choice of a manual copy-paste dashboard or an automated workflow via the PrivacyScrubber Chrome Extension. Our engine performs local Named Entity Recognition (NER) to replace sensitive identifiers with deterministic tokens (e.g., [NAME_1], [ID_2]) before transmission. This architectural pattern mirrors industry standards for scaling agent architectures — ensuring that only sanitized, non-identifiable logic is processed by the AI. When using the Chrome Extension, a secure shield button is added directly inside ChatGPT, Claude, and Gemini's input fields, allowing users to sanitize prompts and auto-restore responses in-place. Running Named Entity Recognition locally ensures that teams can continue using LangChain, LlamaIndex, AutoGPT, CrewAI, and custom RAG infrastructure for daily queries without any third-party data collection.
What Actually Leaves Your Machine When You Use Cursor
Three specific standards create direct obligations around AI IDE usage:
Is PrivacyScrubber safe for Cursor AI source code leak, Cursor IDE security, MCP server PII redaction, SOC 2 developer tools, IDE secrets leak prevention?
Yes, absolutely. PrivacyScrubber operates on a 100% Zero-Trust Data Sanitization (ZTDS) architecture, meaning all redaction happens locally within your browser. When working with Cursor AI source code leak, Cursor IDE security, MCP server PII redaction, SOC 2 developer tools, IDE secrets leak prevention, no sensitive data ever leaves your device or touches a cloud server.
How does it handle custom data structures for agents?
Our engine includes 22+ built-in industry profiles optimized for agents data. Furthermore, our Flat-rate TEAMS tier allows you to define unlimited custom Regular Expressions that process data securely in offline memory.
Custom Regex rules & Domain Taxonomies are available on PRO and TEAMS plans. Default 25 profiles active.
Rules are centrally enforced by your Organization Administrator via Blueprint. Local modifications are locked.
Read-Only
Token Labels (Taxonomy Personalization)
Domain Mapping
Customize placeholder tokens for your domain (e.g. NAME → CLIENT).
Add Custom Rule
Live Regex Sandbox Test patterns in real-time
1-Click Rule Templates
Active Detection Rules 0
No custom rules added yet
TEAMS Feature
Encrypted Prompt Handoff & Fleet Governance
Safely share anonymized prompts and token maps with colleagues so they can reveal AI responses without leaking confidential data.
Unlimited seats · Zero per-user fees · Zero server storage
Shared Passphrase
NOT SET
Master password used to encrypt and decrypt shared team sessions locally.
Zero-Server Security: Your passphrase never touches any server. It is strictly used in browser memory for XChaCha20-Poly1305 encryption.
Encrypted Session Transfer
.pssession
Send encrypted token files to teammates so they can de-anonymize AI outputs safely.
Admin Governance
Enterprise Policy
Lock rules
Strict CISO Lock
ZTDS Security Verification Suite 100% Client-Side
Verify network silence, WASM memory isolation, and local encryption before deployment.
ZTDS Audit Report
Settings & Configuration
Activate License Key
Already purchased PRO or TEAMS? Enter your license key or paste your activation URL below.
Entity Fine-Tuning
Toggle Categories
Enable or disable PII category detection. Changes apply to all scrub operations.
Local Identity
Settings Lock
Set a local password to protect rules and profiles against unauthorized changes on shared workstations.
Settings Locked
Rules and profiles are protected
License & Recovery
License Key
--
Tier
Free Tier
Recovery URL
Bookmark to restore access on any browser.
Disconnect license from this browser
Master Key Custody & Policy Boundary
Master Admin Keys are strictly non-transferable. Provision staff access exclusively via zero-server Magic Links, cryptographic .psblueprint files, or Chrome Enterprise Policy.
Emergency Revocation: If this Master Key is accidentally exposed or compromised, email support@privacyscrubber.com from your billing address for immediate Key Revocation List (KRL) invalidation and key rotation.
End-to-End Zero-Trust Client Sanitization
PRO Workspace
Active
Key: PS-PRO-XXXX-XXXX
Overview & Workspace Stats
Real-time local privacy scanning performance inside this browser.
Chars Protected
0
Files Scanned
0
DLP Saved
$0.00
ZTDS Workspace Safety Score
Excellent
Safety score is based on local rule coverage, secure setting lock status, and offline database health.
100% Offline Operations
This workspace processing runs client-side in RAM. No keys, files, or sensitive prompts are ever transmitted or saved outside your local machine.
Custom Detection Rules
Define unlimited patterns for internal codes, project IDs, and proprietary formats unique to your workflow.
Unlimited Rules
Live Sandbox
Import/Export
Custom Detection Rules
Define custom patterns for proprietary formats, project codes, or custom names.
Add exact text, names, or custom patterns to catch domain-specific identifiers. Labels will appear as [LABEL_N].
Live Regex Sandbox
Active Rules
No rules added.
Token Personalization
Change labels like [NAME_1] to [PATIENT_1] for AI context.
Batch Document Center
Upload, queue, and process folders or batches of document files.
Batch Sanitization
Concurrently parse .txt, .docx, .csv, and PDFs. Local CPU handles rendering & parsing instantly.
DevSecOps Audit BETA
Recursively scan repositories for leaked API Keys, Cryptographic Keys, Intellectual Property, and PII. 100% offline.
Save Output Package
Saves all processed files back to your system, preserving layout formats and directory structures.
Offline Engines
Entirely private extraction engines. No files are ever sent to a server.
Local Image OCRWASM EngineExtract text from images right in your browser.
Offline PDFClient-side ParserParse text from PDFs without uploading them.
Choose how redacted text looks.
Select an industry-specific detection profile.
Entity Fine-Tuning
Toggle core PII categories detection.
100% Client-Side Processing
All engines run locally. Confirmed via zero network requests.
Settings Lock Password
Set a local password to lock your custom rules and active profiles against unauthorized changes on this computer.
Settings are Locked.
Enter your password to unlock editing for custom rules, detection profiles, and engines.
Configure New Lock
Settings Lock ActiveSettings and Custom Rules are locked
Local-Only Password
The lock password never leaves your browser. It prevents casual tampering with detection rules and profile settings on shared workstations.
License Details
License Key
—
Tier
PRO Individual
Recovery URL
Bookmark this URL to restore your PRO access on any browser or device.
Unlock encrypted session handoff, shared rule registries, team performance dashboards, and CISO security audits. Flat $99/mo — no per-seat pricing.
Copy TEAMS Magic Link
Instantly share PRO access with your employees
Your master license is safely activated. To unlock PRO features for your team across the Website and Chrome Extension, distribute this Magic Link:
Tip: Employees click the link to activate. No logins.
Keep this master link secure. Anybody with this URL can utilize your corporate TEAMS subscription.
Zero-Knowledge Session Handoff
XChaCha20-Poly1305 + Argon2id
Securely transfer volatile RAM token maps across devices and team members with end-to-end client encryption.
Cryptographic Zero-Server Guarantee
Payloads are encrypted in browser RAM using Argon2id key derivation and XChaCha20-Poly1305 AEAD. Zero server transmission.
TEAMS
Zero-Server Team Collaboration
Transfer live sanitization memory across analysts, prompt engineers, and legal reviewers without uploading tokens to any cloud database or central server.
This document certifies that the data sanitization operation was executed entirely client-side on the user's local machine. Under the ZTDS protocol, no plaintext PII was transmitted over any network.
Timestamp:2026-07-17T12:35Z
Session Hash:a4b9c1d3...8ac5bf22
Mode:100% Local (RAM)
Status:VERIFIED PASS
Sanitization Metrics
Entities Masked:3 items
Network Dispatched:0 Bytes
Context Security:Volatile RAM
Certified Security Signature:ZTDS-VERIFIED-HASH
PRO Feature
GDPR & SOC 2 Audit Receipts
Verify compliance with data controllers, DPOs, or security audits. Download a signed PDF certificate generated locally in your browser to prove that no prompt data left your network.
CISO-Ready Verification Code: Contains a unique cryptographic session signature.
Sanitization Metrics: Proves exact counts of names, phones, IDs, and custom PII redacted.
Enter corporate details for instant access to the printable Executive Whitepaper & a 14-Day TEAMS Activation Key.
Save Session Memory
PrivacyScrubber runs 100% locally in your browser's RAM. Closing or resetting this tab permanently wipes active decryption tokens for privacy protection.
Zero-Trust Session Backup
Download your encrypted session file (.pssession). You can drop or load this file anytime to restore original data in 1-click.
DevSecOps Audit Report
Zero-Trust Directory Scan Complete. 100% Offline.
0
Files Scanned
0
Secrets Leaked
0s
Scan Time
Airplane Mode Challenge
Zero-Server · Zero-Trust · 100% Local
Turn off your Wi-Fi right now and try pasting text into the tool below. It processes 100% in your local RAM without sending any network requests.
Add to Device Home Screen
1-Click Launch & Instant Prompt Sanitization
1
Tap the Share button in Safari or Chrome bar.
2
Scroll down and select Add to Home Screen.
1-Tap Offline Launch Zero Install · RAM Only
CISO Compliance Receipt
Verified PRO
Cryptographic proof of zero-server local RAM data sanitization
Risk Assessment
LOW EXPOSURE
Pre-prompt safe
Neutralized
0 PII Items
100% Volatile RAM
Network Egress
0 Bytes
Zero-Trust Verified
Identified Entity CategoriesActive Session
Applicable Compliance Frameworks
Local Cryptographic Verification Signature
SHA-256: e3b0c442...
Timestamp: Today
Redacted Document Inspection
Click badges to unmask false positives
100% Volatile RAM Preview — Zero Network Transmission
100%
Click any badge to unmask· Secure Flattening (Zero Hidden Text Layers)·Scroll to navigate · Ctrl+Scroll to zoom
