Private Preview
Join Waitlist →

Reversible Redaction

Replace sensitive data with placeholders you can restore later

4 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: March 2026

Outcome

Understand what redacted items mean, when they can be restored, and how to share placeholder-based content without exposing the original values.

Your progress

Mark each step as you complete it. This is saved only in this browser.

0 / 3 steps complete

Before you start

Have a reviewed redacted output or use a synthetic sample.
Know whether the recipient needs only the safe output or also needs restoration context.
Keep any restoration material separate from the redacted content unless your workflow explicitly requires it.

Visual frame

Review asset

Redacted items storyboard

Synthetic token frame only. It explains placeholders and maps without asking users to expose original values.

Token[TYPE_1]
MeaningContext kept
MapHandle carefully

Synthetic frame

Placeholder labels

Typed placeholders keep the document understandable.

Email[EMAIL_1]
Phone[PHONE_1]
Unknown[DATA_1]
A placeholder should show what kind of value was removed, not the value itself.

Placeholder and restoration frame

A simplified view of how raw values become placeholders and how restoration material must stay controlled.

Raw valuePrivate value before review.
PlaceholderSafe label used in the redacted output.
MapSensitive restoration material when restoration is needed.

Guided steps

Follow the task, then check the result.

Read the placeholder, not the original value

Look at placeholders such as [EMAIL_1], [PHONE_1], or [ACCOUNT_1]. The label tells you the kind of value that was hidden without exposing the original.

Before/after sample with raw values replaced by typed placeholders.
Success check: You can explain what each placeholder represents without seeing the raw value.

Decide whether anyone needs restoration

Many workflows only need the redacted output. If someone needs to restore values later, treat the redaction map or recovery material as sensitive and keep it separate from the shared output.

Decision split: safe output only versus output plus restoration material.
Success check: You know whether this workflow requires restoration or safe sharing only.

Protect restoration material like sensitive data

If the workflow creates a map between placeholders and original values, treat that map as sensitive. Do not attach it to support requests or send it with the redacted content by default.

Redacted output and restoration material stored as separate objects.
Success check: The redacted output and restoration material are not sent together accidentally.

Branch questions

Completion check

You understand the difference between redacted output and restoration material.
You know whether restoration is needed for the current workflow.
You did not include raw values or restoration material in a support request by default.

Support boundary

Support can use by default

  • Placeholder type labels and article slug.
  • Workflow category such as safe output only or restoration needed.
  • User-written description after consent, without raw original values.
  • 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/understanding-tokens
Selected issue: Placeholders do not match the detection types you reviewed.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Placeholder type labels and article slug.
- Workflow category such as safe output only or restoration needed.
- User-written description after consent, without raw original values.
- 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

Reversible Redaction: Your Data, Temporarily Disguised

Most redaction tools are one-way streets. Once you redact, that data is gone forever. Redactorr is different - it uses reversible redaction, which means you can get your original data back whenever you need it.

The Concept

Think of it like a valet service:

  • You hand over your car (sensitive data)
  • They give you a ticket (redacted item)
  • Later, you return the ticket and get your exact car back

How It Works

When Redacting: 1. Redactorr finds "[email protected]" 2. Replaces it with [EMAIL_1] 3. Stores the mapping: [EMAIL_1] → [email protected] 4. Saves the mapping in your browser's local storage

When Restoring: 1. You paste the redacted text back into Redactorr 2. Click "Restore" 3. Redactorr looks up each redacted item in the map 4. Swaps redacted items back for original values

Magic: Your original data returns.

Real-World Use Case

You're sharing a customer support transcript with your dev team to debug an issue. The transcript contains customer emails and phone numbers.

Redact**

1 / 1

Paste the transcript into Redactorr. It becomes:

text
Customer [EMAIL_1] called [PHONE_1] about order [ORDER_1].
Rep [NAME_1] offered refund.

Share this safely with your dev team.

Restore**

1 / 1

After the bug is fixed, paste the redacted transcript back into Redactorr. Click "Restore". Original data returns:

text
Customer [email protected] called (555) 987-6543 about order #ORD-456.
Rep John Smith offered refund.

Redaction Map Storage

The redaction map is stored in your browser's IndexedDB:

  • Handled as browser-side review state during redaction
  • Persists across sessions (until you clear it)
  • Can be exported for backup or sharing (encrypted)
  • Can be deleted anytime

Security Considerations

Is the redaction map a security risk?

The redaction map alone is useless. An attacker would need: 1. The redaction map 2. The redacted document 3. Access to your browser's local storage

If someone has all three, you have bigger problems.

Can I make it more secure?

Yes! Use Secure Share to encrypt the redaction map with a password. Now even if someone gets the map, they can't read it without the password.

When to Use Restoration

Temporary Sharing Redact for external review, restore internally after feedback.

Audit Compliance Store redacted logs long-term, restore specific entries when auditors request details.

Testing Workflows Test your app with redacted data, restore when debugging failures.

Cross-Team Collaboration Share sanitised data across teams, restore for privileged users.

When NOT to Use Restoration

Permanent Deletion If you want data gone forever, don't use reversible redaction. Use one-way redaction or deletion.

External Sharing (No Return) If you're sending data to a third party and don't need it back, skip the redaction map.

Compliance Requirements Some regulations require irreversible deletion. Check your compliance needs.

Exporting the Redaction Map

Click "Export Redaction Map" to save it as a JSON file:

json
{
  "version": "1.0",
  "createdAt": "2026-01-06T14:30:00Z",
  "mappings": {
    "[EMAIL_1]": "[email protected]",
    "[EMAIL_2]": "[email protected]",
    "[PHONE_1]": "(555) 123-4567"
  }
}

Store this file securely. Anyone with this file can restore your data.

Pro Tips

Auto-Expiration Set a TTL (time-to-live) when redacting. The redaction map auto-deletes after the specified time.

Selective Restoration You don't have to restore everything. Click individual redacted items to restore just that value.

Version Control Export redaction maps with timestamps. Keep versions for different redaction sessions.

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.

Support can start here
  • Article slug
  • Selected issue
  • Screen name
  • Action name
Redactorr support case

Source: Article playbook: understanding-tokens
Route: /knowledge-base/tokenization
Selected issue: Placeholders do not match the detection types you reviewed.

Safe context:
- Placeholder type labels and article slug.
- Workflow category such as safe output only or restoration needed.
- User-written description after consent, without raw original values.
- 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.

Safe to include
  • Placeholder type labels and article slug.
  • Workflow category such as safe output only or restoration needed.
  • User-written description after consent, without raw original values.
  • Article slug
  • Selected issue
  • Screen name or article section
Consent boundary

Private material belongs behind an explicit consent step, not in the initial case.

6 default exclusions

Before you copy0/4 ready
Open safe support guide