Author and maintainer profile
metapeel Editorial Team
The team that documents metapeel's browser-based metadata inspection and cleaning behavior against the current implementation and primary format references.
Who is behind the byline?
“metapeel Editorial Team” is an organizational byline, not a fictional person. It identifies the maintainers responsible for keeping the guides aligned with the product. We use it because several disciplines meet here: file-format behavior, browser implementation, privacy language, and technical editing.
We do not attach invented qualifications or imply legal, forensic, or security certification. Where a guide touches those fields, it explains its scope and points to the relevant primary documentation.
How a guide is reviewed
Start with the implementation
We inspect the current reader and cleaner for the format before describing what metapeel can detect or change.
Separate metadata from hidden content
Document properties are not the same as comments, tracked changes, attachments, scripts, hidden sheets, or visual redaction.
Prefer primary references
Format specifications, official vendor documentation, and the libraries used by the implementation take priority over recycled advice.
State the verification path
A cleaning claim should tell readers how to inspect the resulting copy and what technical fields are expected to remain.
Update dates honestly
The modified date changes when the guidance, capability boundary, or cited evidence changes—not simply to make a page look fresh.
How privacy affects the editorial process
The site does not collect filenames, extracted fields, thumbnails, file contents, or file-processing actions for analytics. Guides therefore use synthetic examples and generic field names rather than publishing a user's real file metadata. Search performance is measured through aggregate tools such as Google Search Console, not through session replay or clickstream tracking.
Corrections are welcome
If a capability statement or source is outdated, email the exact page and field at issue. We will compare it with the current implementation and correct the article where needed.
[email protected]