M ManageMetadata Client-Side Metadata Suite

Confidential Document Privacy

Remove author, company & editing time from Word DOCX files online

Microsoft Word silently records who created the document, who last saved it, how many minutes were spent editing, and company fingerprints. ManageMetadata purges hidden OpenXML properties directly in browser memory with zero server uploads.

Inspect Word PropertiesPDF SanitizerExifTool WebUniversal Cleaner
100% Client-Side Privacy Tool Zero Server Uploads

Lossless Word Document Metadata Cleaner

Select or drop a Microsoft Word (.docx or .dotx) document to inspect detected author credits, company tags, and editing duration, then export a sanitized copy.

or drag and drop a .docx file here

Supports Microsoft Word (.docx, .dotx) • 100% client-side

No document selected yet.

Document Properties

Core & App XML Telemetry

Waiting for file
  • Select or drop a .docx file to inspect author, revision, and company metadata.

The Architecture of Office Open XML: What Lies Beneath a .docx Extension

Since the release of Microsoft Office 2007, Microsoft Word documents have been standardized under the Office Open XML (OOXML / ISO/IEC 29500) specification. Rather than proprietary monolithic binary blobs (the legacy .doc format), a modern .docx file is actually a standard compressed ZIP archive containing a structured directory of XML markup files, media assets, and relationship maps.

When you compose a document, Microsoft Word continuously monitors your editing session, registering keystrokes, template inheritance, and operating system credentials. Upon saving, Word automatically injects these personal telemetry vectors into dedicated metadata XML files stored inside the ZIP package:

Primary Hidden Metadata Files in a DOCX Archive

  • docProps/core.xml: Contains Dublin Core metadata properties: dc:creator (originating author), cp:lastModifiedBy (name of the user who last pressed save), cp:revision (cumulative revision count), dcterms:created, and dcterms:modified.
  • docProps/app.xml: Extended application properties: Company (registered employer or enterprise tenant), Manager, TotalTime (cumulative editing duration in minutes), Application (e.g., "Microsoft Office Word 16.0000"), and Template (original template file path).
  • word/people.xml: Reviewer identity registry storing author names, email addresses, and initials linked to tracked changes and inline comments.
  • docProps/custom.xml: Enterprise document properties, sensitivity classification labels, and custom client tags.

High-Risk Real-World Exposure Scenarios

  • Legal & Discovery Breaches: Opposing counsel inspecting a contract's TotalTime or lastModifiedBy can determine whether an agreement was drafted from scratch or copied from another client's proprietary confidential file.
  • Vendor Invoicing Audits: A billing consultant invoicing for 40 hours of legal research risks catastrophic disputes if the document's internal TotalTime counter reveals only 45 minutes of active editing.
  • Job Applicant Disclosure: Submitting a resume with an internal Company tag pointing to a current employer or a different recruiting firm exposes confidential background details.
  • Academic Integrity Flagging: Submitting research papers with a dc:creator belonging to a different student or essay-writing service immediately triggers academic integrity investigations.

The Total Editing Time Vulnerability (TotalTime in Minutes)

One of the most dangerous and widely overlooked metadata tags in Microsoft Word is the TotalTime property located within docProps/app.xml. This integer represents the cumulative number of minutes the document has been open and actively edited across all sessions:

<Properties xmlns="http://schemas.openxmlformats.org/officeDocument/2006/extended-properties">
  <Template>Normal.dotm</Template>
  <TotalTime>14</TotalTime>
  <Company>Acme Global Consulting LLC</Company>
  <Application>Microsoft Office Word</Application>
</Properties>

If a student, consultant, or contractor claims to have spent days drafting a comprehensive 30-page proposal, an internal TotalTime of 14 minutes proves that the text was copy-pasted or cloned from another source. ManageMetadata permanently resets this counter to 0.

Why Built-in Word "Document Inspector" Is Inconvenient

Microsoft Word includes a native feature called the Document Inspector (located under File → Info → Check for Issues → Inspect Document). While functional, it suffers from severe workflow friction:

ManageMetadata's 100% Client-Side OpenXML Sanitization Pipeline

ManageMetadata executes zero-upload OpenXML sanitization directly in your browser:

  1. In-Memory Unzipping: The .docx archive is inflated into memory using JSZip without uploading a single byte over the internet.
  2. W3C DOMParser XML Scrubbing: Our engine parses docProps/core.xml and docProps/app.xml using native browser XML parsers, clearing creator, lastModifiedBy, Company, Manager, and resetting TotalTime to zero and revision to 1.
  3. Reviewer Anonymization: Identities in word/people.xml are replaced with neutral author placeholders.
  4. Custom Properties Removal: Proprietary enterprise classification tags in docProps/custom.xml are excised.
  5. Deflate Recompression: The sanitized files are re-packed into a standards-compliant .docx file with Deflate level 6 compression, preserving 100% of body text, fonts, tables, styles, and embedded images.