Skip to main content
SECURITY & TRUST PROTOCOL
Independently verifiable · No trust required

How We Prove Your Privacy

Trust shouldn't be blind. Here's how to audit our code in real-time and confirm we never see your data.

offline-sanitizer.html — fully air-gapped

Download the Standalone Tool

For maximum-security environments — a self-contained HTML file with all logic embedded. Works with zero internet connection. No CDN requests, no external fonts, no analytics.

Download Standalone File (.html)
✓ No external dependencies✓ Air-gapped✓ Free forever
devtools-network-audit — how to verify right now

The Network Tab Audit

The most transparent verification: watch your own outbound traffic while using the tool. Takes 30 seconds.

01
Open any tool
Go to /tools/log-sanitizer
02
Open DevTools
Press F12 or Cmd+Opt+I
03
Click Network tab
Clear any existing entries first
04
Paste sensitive data
Type or paste into the input area
05
Watch — nothing happens
Zero new network requests appear
✓ Result: Zero outgoing requests during processing
ad-policy.md — why tool pages are ad-free

Zero Ads on Tool Pages

The guide and article pages on this site show Google AdSense ads — that's how we keep the tools free. But every page inside /tools/ and /legal-pdf-stamper/ is ad-free. No AdSense script, no ad cookies, no third-party network calls while you're using a tool.

Why this matters
  • No third-party scripts can read your input. AdSense has access to page content it's embedded on. We don't run it anywhere you're pasting sensitive data.
  • DevTools Network tab shows zero outbound requests. With ads enabled, you'd see dozens of requests to Google's ad servers. On tool pages, the only requests are for the tool itself.
  • No ad-targeting cookies set during use. Your session inside a tool leaves no fingerprint in the ad ecosystem.
  • The privacy claim is independently verifiable. The Network tab audit above actually passes — no exceptions to explain away.

We'd rather earn less per visitor and have you actually trust what you're using. If you find these tools valuable, reading a guide on the site (where ads do run) is the best way to support the project.

architecture.md — why zero-backend

Why Zero-Backend Logic

Standard tools send your data to a server, process it, and return results. Even if they claim not to save it, your data exists in their server logs, memory and transit history.

Traditional Tools
Your data → Internet → Their server → Processing → Back to you
Data in transit logs, server memory, backups
ResourceCentral
Your data → Local browser JavaScript → Result
Zero network latency. Zero exposure.

"We cannot be subpoenaed for data we don't have. We cannot leak data we never stored. This isn't just a policy — it's how the code is written."

All Verified Client-Side Tools
Log Sanitizer JSON Diff SQL Formatter JWT Decoder Python Cleaner Bates Stamper

Related