π Local Processing
Why does processing location matter?
Some anonymization tools send your data to remote servers to perform masking. This means you must fully trust their infrastructure β and if their server is compromised, your original sensitive data (names, emails, IBANsβ¦) can be seen and exploited.
ChatWall takes a fundamentally different approach: all masking happens inside your browser, via client-side JavaScript. No payload β not even the masked version β is ever sent to our backend.
π Isolated
Why does the editor window matter?
The chat website can technically access everything you type in its native input fields before you even send your message β through JavaScript event listeners, keyloggers, or telemetry scripts. When you type in the ChatWall editor overlay, your text is entered in an isolated extension window that the host website's scripts cannot read. Only the already-masked version is ever pasted into the chat input.
π¦ How ChatWall Compares
| Feature | ChatWall | Other tools (cloud-based) |
|---|---|---|
| Masking location | β In your browser | β On a remote server |
| Your data sent to vendor's server | β Never | β Yes (to mask it) |
| Protected from AI website scripts | β Yes β Shadow DOM isolated | β οΈ Often no β masking in native input or not isolated DOM |
| Token mapping / Favorites | β
Tokens: session only (memory) β οΈ Favorites: stored locally on device, never synced |
β οΈ Varies |
| Code transparency | β Source Available (GitHub) | β Closed source |
π Verify It Yourself (F12 Check)
You don't have to take our word for it. You can prove that ChatWall makes zero data requests while masking, directly using your browser's built-in developer tools.
Verify the Extension (Service Worker)
- Open
chrome://extensionsin your browser. - Find ChatWall and click Details.
- Click service worker β this opens DevTools for the extension background.
- Switch to the Network tab and use ChatWall normally.
- You will see only the license-status heartbeat. No chat content is ever transmitted.
Verify in the Sandbox (Browser DevTools)
- Open ChatWall Sandbox in your browser.
- Press F12 (or Right-Click β Inspect) to open DevTools.
- Go to the Network tab.
- Type and mask some text in the Sandbox editor.
- The Network tab will show zero outgoing requests triggered by typing or masking. All processing is in memory.
π What Minimal Data We Do Handle
- License Validation: The extension periodically contacts our licensing server to verify your subscription status. This transmits only your installation ID and license key. No chat content or PII is ever transmitted during this check.
- Ephemeral Tokens: The token mapping table (e.g.
[NAME_1]= 'John') exists only insessionStorageβ in memory only. It is wiped when you close the browser tab and is never sent anywhere.
Note: only your Favorites (custom reusable terms) are persisted, stored locally in Chrome Storage (base64 encoded) and never synced to the cloud. - Secure Favorites: Custom favorite terms are stored locally in Chrome Storage (base64 encoded). They are not synced to the cloud. Do not add sensitive data to favorites on a public or shared computer.
- Account & Payment: Payments are handled exclusively by Stripe. We only validate licenses β we never store payment card data.
π¬ Contact
For any security or privacy inquiries:
StarObject S.A.
Email: [email protected]
Rue Jinken, 9 β L-9909 Troisvierges, Luxembourg