How Redactorr Works
Understanding the browser-local redaction workflow
Outcome
Understand the browser-local redaction flow and choose the correct task playbook without over-sharing private content.
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
How Redactorr works storyboard
Synthetic architecture frame only. It explains the browser-local redaction boundary without making storage, training, or compliance claims.
Synthetic frame
Browser workspace
Detection starts from the local session.
Browser-local flow map
A reference frame for the product sequence, with task routes separated from architecture notes.
Guided steps
Follow the task, then check the result.
Read the boundary before acting
Start with what the article says is available, measured, preview-only, or not a product claim. Do not treat reference material as permission to send raw private content to support or external tools.
Move from product overview to the right task
Use this article to understand the sequence: input, detection, review, output, and optional sharing. If you need to act, open the closest playbook instead of trying to infer steps from the overview.
Prepare safe support context if something disagrees
If the article and product screen do not match, describe the route, step, browser, and symptom. Do not paste raw original document text, secrets, restoration material, or private files by default.
Branch questions
Are you trying to complete a redaction or sharing task right now?
Does the product screen disagree with this article?
Completion check
Support boundary
Support can use by default
- Article slug and product route.
- Stage name such as input, detection, review, output, or sharing.
- Browser and viewport after consent.
- Intent ID
- Article slug
- App route
- Browser and viewport
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/how-it-works Selected issue: A product screen no longer matches the article sequence. Playbook progress: 0/3 steps marked complete Safe context to include: - Article slug and product route. - Stage name such as input, detection, review, output, or sharing. - Browser and viewport after consent. - Intent ID - Article slug - App route - Browser and viewport 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
Your Browser as a Privacy Shield
Think of Redactorr as a private screening room for your documents. You bring a document in, it finds and replaces sensitive items with safe placeholders during browser-local detection and redaction.
Browser-Local Detection
Here is what makes Redactorr different: detection and redaction run in your browser.
When you paste text or open a file, detection, verification, and redaction run locally in your browser.
Original sensitive values stay local during detection and redaction.
How Detection Works
Pattern Screening**
Redactorr scans your text for known sensitive formats: emails, phone numbers, card-like values, credentials, government identifiers, and more. The scan happens locally in the browser.
Validation**
Finding a pattern is not enough. Matches are validated where possible. Card-like values are checked against standard format rules, emails are checked for valid structure, and identifiers are reviewed against the rules available for that type.
Context Analysis**
Redactorr looks at surrounding text. A number string in a test example can mean something different from the same string in a payroll report. Context helps decide what should be marked for review.
Redaction**
Once confirmed, sensitive data is replaced with a labelled placeholder like [EMAIL_1] or [TFN_1]. The same value always gets the same placeholder — so relationships in the document are preserved.
What Gets Detected
Personal identifiers
- Email addresses
- Australian and international phone numbers
- Names and addresses
Australian government identifiers
- Tax File Numbers (TFN)
- Medicare numbers
- ABNs, ACNs, BSBs
- State-specific licence numbers
Financial data
- Credit card numbers
- Bank account numbers
Credentials
- API keys (AWS, Stripe, GitHub, and many others)
- Passwords in configuration files
- Database connection strings
Industry-specific
- Medical record numbers, patient identifiers
- Legal matter references, AHPRA numbers
- Construction licence numbers, site details
Custom patterns
- Your organisation's internal ID formats
- Internal codes and proprietary identifiers
Why This Matters
Traditional cloud-based redaction tools upload your file to a server, process it remotely, then send you back a result. Your sensitive data travels over the internet and sits on someone else's infrastructure.
Redactorr's approach: open the file in your browser, run detection and redaction locally, then choose what reviewed output moves to later workflows.
Privacy by Architecture
Redactorr's privacy is not a setting you toggle on — it is built into the architecture. Detection and redaction run inside a sandboxed environment in your browser. Optional Vault, sharing, and AI workflows use processed or reviewed redacted context when you choose.
After the app loads, browser-local detection and redaction can continue without connectivity.
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: how-it-works Route: /knowledge-base/how-it-works Selected issue: A product screen no longer matches the article sequence. Safe context: - Article slug and product route. - Stage name such as input, detection, review, output, or sharing. - Browser and viewport after consent. - Article slug - Selected issue - Screen name or article section - Action name - Browser and viewport 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 product route.
- Stage name such as input, detection, review, output, or sharing.
- Browser and viewport after consent.
- Article slug
- Selected issue
- Screen name or article section
Private material belongs behind an explicit consent step, not in the initial case.
6 default exclusions