Privacy Architecture & Document Security
At wordwordcount.com, privacy is treated as a fundamental engineering requirement rather than a marketing statement.
1. 100% Client-Side Processing for .DOCX & Text
When you drag and drop a Microsoft Word .docx document or type into the live editor, the entire file decompression, XML extraction, and tokenization happens directly inside your web browser using JavaScript and Web Workers.
2. Ephemeral In-Memory Processing for Legacy .DOC Files
Legacy binary Word files (.doc) utilize the proprietary Compound File Binary Format (CFBF/OLE). These are parsed in isolated server memory workers, analyzed in milliseconds, and the memory buffer is immediately wiped.
3. Zero-Auth Public Google Docs Architecture
We deliberately do not ask for Google logins, OAuth tokens, or Google Drive permissions. Only publicly accessible links ("Anyone with the link can view") are retrieved via standard export streams, counted in memory, and discarded.
4. Zero Document Content in Analytics or Logs
Our operational telemetry tracks only anonymous system metrics (such as whether an upload succeeded or timed out). We never log, store, or transmit your document contents, titles, or extracted passages. Your text is never used to train artificial intelligence or machine learning models.