Redact document metadata
Check document properties, author names, and hidden fields before exporting or sharing.
Outcome
You know whether metadata needs attention and how to verify the exported copy before sending it onward.
Your progress
Mark each step as you complete it. This is saved only in this browser.
0 / 3 steps complete
Before you start
Visual frame
Review asset
Document metadata review storyboard
Synthetic metadata frame only. It distinguishes visible content from file properties without claiming every hidden field can be removed in every format.
Synthetic frame
Metadata review
Visible text and file details are different surfaces.
Redact document metadata workflow frame
Instructional frame for this workflow. Use product screenshots or animation captures after the article copy is stable.
Guided steps
Follow the task, then check the result.
Look for metadata warnings
Check the metadata or file details area for author names, document properties, comments, or other fields that could identify someone.
Decide what to remove or keep
Remove metadata that exposes people, organisations, internal paths, comments, or tool history. Keep fields only when they are intentionally safe for the recipient.
Verify the export
Open the exported file and check its properties where your operating system or document viewer allows it.
Branch questions
Can you see the screen or control described in Redact document metadata?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
- Intent ID
- Article slug
- App route
Requires your consent
- User-written description
- Email address
- Explicit attachment
- Redacted sample
- Support bundle previewed to the user
Not collected by default
- Raw original document text
- Full local file paths
- Pasted private content
- Unmasked screenshots
- Replay capture
Safe support summary
Copy a scrubbed handoff.
Redactorr KB support summary Article: /knowledge-base/document-metadata-redaction Selected issue: Metadata still appears in an exported file after you removed it. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name, such as Canvas review, Vault resume, or Share package. - Browser, viewport, file type category, and error category when relevant. - Synthetic sample shape or redacted sample only after review. - Intent ID - Article slug - App route Requires explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture User note: - Describe the step and symptom without pasting raw document text, secrets, files, or restoration material.
Article details
Redact document metadata
Check document properties, author names, and hidden fields before exporting or sharing.
Outcome
You know whether metadata needs attention and how to verify the exported copy before sending it onward.
Before You Start
- Use a supported document type.
- Know that visible text and document metadata can be separate.
- Plan to open the export before sharing it.
1. Look for metadata warnings
Check the metadata or file details area for author names, document properties, comments, or other fields that could identify someone.
Check before you continue: You know whether the document has metadata that needs review.
2. Decide what to remove or keep
Remove metadata that exposes people, organisations, internal paths, comments, or tool history. Keep fields only when they are intentionally safe for the recipient.
Check before you continue: Every metadata field is removed, replaced, or intentionally kept.
3. Verify the export
Open the exported file and check its properties where your operating system or document viewer allows it.
Check before you continue: The exported file does not expose metadata you intended to remove.
Completion Check
- Metadata review is separate from visible-text review.
- The exported file was opened before sharing.
- Unsupported metadata concerns are routed to support with safe context only.
Safe Examples
- Synthetic author names and fake organisation names.
- A fake file path such as /example/project/redacted-demo.docx.
If You Need Support
Contact support when:
- Metadata still appears in an exported file after you removed it.
- You cannot tell whether a field is metadata or visible content.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
Still stuck?
Copy a safe article handoff.
Start support with the article, the issue, and safe context. Raw document text, files, restoration material, and unredacted screenshots stay out unless you explicitly choose otherwise.
- Article slug
- Selected issue
- Screen name
- Action name
Redactorr support case Source: Article playbook: document-metadata-redaction Route: /knowledge-base/document-metadata-redaction Selected issue: Metadata still appears in an exported file after you removed it. Safe context: - Article slug and selected workflow step. - Screen or action name, such as Canvas review, Vault resume, or Share package. - Browser, viewport, file type category, and error category when relevant. - Synthetic sample shape or redacted sample only after review. - Article slug - Selected issue - Screen name or article section - Action name Only include with explicit consent: - User-written description - Email address - Explicit attachment - Redacted sample - Support bundle previewed to the user Do not include by default: - Raw original document text - Full local file paths - Pasted private content - Unmasked screenshots - Replay capture - Hidden diagnostic uploads User note: - Describe what you tried and what happened. Do not paste raw document text, secrets, files, restoration material, or unredacted screenshots.
Support case builder
One case format, wherever you start.
This is the same support case shape used by diagnostics and article handoffs.
- Article slug and selected workflow step.
- Screen or action name, such as Canvas review, Vault resume, or Share package.
- Browser, viewport, file type category, and error category when relevant.
- Synthetic sample shape or redacted sample only after review.
- Article slug
- Selected issue
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions