Understand privacy score
Use privacy score as a review aid, not as a guarantee that a document is safe or legally compliant.
Outcome
You understand what the score can help prioritise and why final output review still matters.
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
Privacy score interpretation storyboard
Synthetic score frame only. It presents the score as a review aid, not as proof of safety, anonymity, certification, or legal compliance.
Synthetic frame
Privacy score
A signal to guide review.
Understand privacy score workflow frame
Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.
Guided steps
Follow the task, then check the result.
Read the score as a signal
Use the score to notice whether the document still has unresolved detections, risky categories, or review work left.
Check the reasons behind it
Look for the categories or review states contributing to the score before deciding what to do next.
Verify the output anyway
Use the score to guide review, then inspect the final output as the recipient would.
Branch questions
Can you see the privacy score panel surface described in this guide?
Did the result match the completion check?
Completion check
Support boundary
Support can use by default
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-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/privacy-score-explained Selected issue: The score changes without a visible review change. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-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
Understand privacy score
Use privacy score as a review aid, not as a guarantee that a document is safe or legally compliant.
Use this guide when the privacy score panel surface is available in your workspace. If you cannot see the screen or control described here, use the safe support path instead of guessing.
Outcome
You understand what the score can help prioritise and why final output review still matters.
Before You Start
- Complete or start a scan so the score has context.
- Treat the score as a signal, not approval.
- Know what kind of content your recipient must not see.
1. Read the score as a signal
Use the score to notice whether the document still has unresolved detections, risky categories, or review work left.
Check before you continue: You know what the score is drawing attention to.
2. Check the reasons behind it
Look for the categories or review states contributing to the score before deciding what to do next.
Check before you continue: You can name the next review action rather than only quoting the number.
3. Verify the output anyway
Use the score to guide review, then inspect the final output as the recipient would.
Check before you continue: The document has been reviewed beyond the score.
Completion Check
- The score was used to guide review, not replace it.
- Score reasons or risky categories were checked.
- Final output was inspected before sharing.
Safe Examples
- A fake document with low-risk and high-risk example categories.
- A synthetic score screenshot with all values masked.
If You Need Support
Contact support when:
- The score changes without a visible review change.
- The score reason does not match the document state.
Include only support-safe context:
- Article slug and selected workflow step.
- Screen or action name.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-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: privacy-score-explained Route: /knowledge-base/privacy-score-explained Selected issue: The score changes without a visible review change. Safe context: - Article slug and selected workflow step. - Screen or action name. - Browser, viewport, workspace type, and file type category when relevant. - Synthetic sample shape or already-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.
- Browser, viewport, workspace type, and file type category when relevant.
- Synthetic sample shape or already-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