Core Feature

Secure Team Collaboration & Session Handoff

The Circle of Trust, Digitally Enforced

5.0/5 rating based on 34 reviews. 100% Free ($0)
Airplane Mode Verified
Local Execution

The Problem

Collaboration usually breaks privacy. If one person redacts a document and another person needs to read the AI's output, they must manually coordinate the 'key' to the placeholders. Cloud-based 'Shared Workspaces' solve this by storing your data on their servers—creating a single point of failure. Teams need a decentralized way to share trust.

How It Works

1

Encrypt Session

Generate a unique 'Secure Handoff' link or .pssession file using your team passphrase.

2

Share Securely

Send the link via Slack, Teams, or Email. Not even the message provider can read the data.

3

Remote Reveal

Your colleague enters the passphrase to instantly 're-hydrate' the AI's response.

How This Feature Improved Workflows

"The magic link handoff is incredible. I can redact a sensitive incident report, send the tokens to our external consultant, and they can 'reveal' it locally using our shared team key. Zero exposure to the cloud."

M

Marcus D., Ops Director

Verified User

"Finally, a way to share sensitive mappings across a global team without a centralized database. The Argon2id encryption makes it virtually unbreakable."

J

Julia S., CISO

Verified User


Argon2id & XChaCha20: The New Standard for Team Privacy

PrivacyScrubber TEAMS introduces a breakthrough in decentralized data sharing. By leveraging Authenticated Encryption with Associated Data (AEAD) via the libsodium library, we provide a "Secure Handoff" mechanism that is faster and safer than traditional AES implementations.

The Handoff Architecture

  1. Key Derivation: Your team passphrase is processed through Argon2id (the winner of the Password Hashing Competition), making it resistant to GPU-based brute-force attacks.
  2. Local Encryption: Your SessionMap is encrypted into a binary buffer using XChaCha20-Poly1305.
  3. Stateless Transmission: This buffer is encoded into a URL hash or a .pssession file. You own the transport layer—we never touch the data.
  4. Local Decryption: The recipient's browser performs the inverse operation entirely in memory.

This "Zero-Server Handoff" ensures that your organization maintains absolute control over its Data Residency. Whether your team is in New York, London, or Tokyo, the PII never enters a third-party cloud, satisfying even the most stringent GDPR and HIPAA requirements.

Feature Reliability & Audit

This enterprise feature is powered by our Local-First Sanitization Engine. Unlike legacy cloud DLP tools, PrivacyScrubber processes your Secure Team Collaboration & Session Handoff logic 100% within your browser's V8 sandbox. This architectural decision ensures that even the most complex detection patterns never expose raw data to an external API.

WASM 1.2 Audited
Zero-Trace RAM Session

Airplane Mode

Verified feature operational integrity without network connectivity.

Frequently Asked Questions

How does the 'Magic Link' work without a database?

The link contains the entire encrypted session map as a Base64-encoded string in the URL hash. Since the hash is never sent to the server (it stays in the browser), the data travels with you across devices securely.

What happens if a link is intercepted?

The data is useless without your private team passphrase. We use Argon2id to derive a nearly-impossible-to-brute-force key, ensuring that even if a link is leaked, your PII remains safe.

Experience Zero-Trust AI Privacy Free

Try PrivacyScrubber Now

No account needed. Works 100% offline.

Better on Desktop

Protect data safely locally