Private Preview
Join Waitlist →

Secure Package Sharing

Share redacted content safely with end-to-end encryption

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

Outcome

Choose a safe last-mile path: copy, export, secure package, or recovery guidance.

Your progress

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

0 / 3 steps complete

Before you start

Finish redaction review before sharing anything.
Know whether the recipient needs only the redacted content or a protected package.
Choose a separate channel for any password or recovery material.

Visual frame

Review asset

Secure package sharing storyboard

Synthetic secure sharing frame only. It uses fake package names and avoids delivery, retention, or identity-proof guarantees.

OutputReviewed first
PackageAccess settings
RecipientOpen path checked

Synthetic frame

Reviewed output

Packaging starts after review.

FindingsResolved
OutputOpened and checked
Raw sourceNot packaged by default
Secure sharing does not replace output inspection.

Instructional secure-sharing frame

A simplified last-mile frame for deciding between copy, export, and protected package sharing.

Reviewed outputOnly share after the redacted result has been checked.
Package controlsUse expiration and password decisions deliberately.
Separate secretsDo not send link and password together.

Guided steps

Follow the task, then check the result.

Choose copy, export, or secure package

If the recipient only needs the redacted text, copy or export may be enough. If they need a protected package, use Secure Share guidance and keep passwords separate.

Share decision frame with copy, export, and package paths.
Success check: You know which sharing path fits the recipient.

Set package controls deliberately

Choose expiration, access, and password handling before sharing the link. Send any password through a separate channel.

Package controls for expiration, password, and link sharing.
Success check: The link and password are not sent together through the same channel.

Confirm the recipient can open the right thing

Ask the recipient to confirm access to the redacted material. If recovery or restoration is needed, use reversible redaction guidance rather than sending raw originals.

Recipient access confirmation and recovery path.
Success check: The recipient can access the intended redacted material and no raw original text was sent by mistake.

Branch questions

Completion check

The shared content is the reviewed redacted version.
Any password or recovery material uses a separate channel.
The recipient can access the intended redacted material.

Support boundary

Support can use by default

  • Share action name, article slug, and selected symptom.
  • Package state such as created, expired, revoked, or access failed.
  • User-provided description or redacted sample only 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/secure-sharing
Selected issue: A protected package cannot be opened after the recipient follows the instructions.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Share action name, article slug, and selected symptom.
- Package state such as created, expired, revoked, or access failed.
- User-provided description or redacted sample only 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

Share Safely, Sleep Soundly

You've redacted your document. Now you need to share it with your lawyer, accountant, or team member. But email attachments feel risky, and cloud drives can be compromised.

Secure Share solves this.

Think of it like sending a locked briefcase where only your recipient has the key. The briefcase passes through public channels (email, Slack, cloud storage), but no one can peek inside.

How It Works

Package Your Content: Upload your redacted document. Redactorr wraps it in an encrypted package with a unique share link.

Share the Link: Send the link however you want - email, Slack, Teams, text message. The link itself is safe to send through untrusted channels.

Recipient Opens: Your recipient clicks the link and enters the password (which you share separately). The document decrypts in their browser.

What Makes It Secure

End-to-end encryption: Protected sharing uses browser-side encryption before the package is shared.

Expiring links: Set packages to expire after 7 days, 24 hours, or as soon as they're opened once. After expiration, the encrypted data is permanently deleted.

Revocable access: Changed your mind? Revoke the link instantly. Anyone who hasn't opened it yet won't be able to.

Password protection: Only people with the password can decrypt. Share the password through a separate channel (like a phone call or secure messaging app).

Real-World Use Cases

Sharing with contractors: Send redacted client data to freelancers with a 7-day expiry.

Legal document exchange: Share case files with opposing counsel with single-view access.

Healthcare providers: Send redacted patient records to specialists with audit trails.

Financial reporting: Share quarterly reports with auditors using time-based expiration.

Onboarding documents: Give new hires access to org documents with revocable links.

Privacy Boundary

Encrypted package boundary: Protected sharing uses encrypted packages and recipient-scoped access controls.

Expiration controls: Configured expiration and access controls limit how long shared packages remain available.

Audit trails: Track who accessed what and when for protected sharing workflows.

Share Workflow

Redact document → Use workspace to sanitise content

Create package → Upload to Secure Share

Set expiration → Choose time limit or single-view

Copy link → Get shareable URL

Share password separately → Use phone, Signal, etc.

Recipient opens → Decrypts in browser

Link expires → Data deleted automatically

1 / 7

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: secure-sharing
Route: /knowledge-base/secure-sharing
Selected issue: A protected package cannot be opened after the recipient follows the instructions.

Safe context:
- Share action name, article slug, and selected symptom.
- Package state such as created, expired, revoked, or access failed.
- User-provided description or redacted sample only 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.

Safe to include
  • Share action name, article slug, and selected symptom.
  • Package state such as created, expired, revoked, or access failed.
  • User-provided description or redacted sample only after consent.
  • 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