Private Preview
Join Waitlist →

Security Architecture

How Redactorr keeps your data safe

Updated 20 Jan 20265 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: March 2026

Outcome

Use the security article as a product-boundary reference and route operational questions to the right safe workflow.

Your progress

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

0 / 3 steps complete

Before you start

Do not treat this page as a certification or legal attestation.
Know whether your question is about redaction flow, support data, exports, or compliance review.
Keep originals, secrets, and restoration material out of support by default.

Visual frame

Review asset

Security architecture storyboard

Synthetic architecture frame only. It explains product boundaries without certification, audit, or compliance-guarantee claims.

BoundaryBrowser-local review
OptionalReviewed handoff
EvidenceWorkflow notes

Synthetic frame

Architecture boundary

Review locally before any handoff.

InputBrowser session
DetectionLocal review
Optional handoffAfter review
Security architecture starts with where original values are handled.

Security boundary map

A boundary frame that separates browser-local processing, reviewed output, optional support context, and consent-only material.

BoundaryWhat the article can and cannot safely claim.
Next routeThe playbook or reference page that should handle the actual task.
Safe contextWhat support can receive without raw originals by default.

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.

Article boundary note followed by the next task route.
Success check: You know whether this article is a task guide, a reference page, or a product-boundary note.

Match the security question to an operational route

Read the browser-local, review, export, and support-boundary notes. Then use the task route that matches what you are doing instead of relying on a broad architecture summary.

Security boundary map
Success check: You understand what stays local by default and which workflow needs the next review step.

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.

Safe support bundle with route, symptom, and consent-only fields separated.
Success check: Any support description avoids raw private content unless you explicitly consent.

Branch questions

Completion check

You know whether this page is instructional, reference-only, or a product-boundary note.
You opened a task playbook when step-by-step guidance was needed.
Any support escalation avoids raw document text, secrets, files, and restoration material by default.

Support boundary

Support can use by default

  • Question category such as local processing, export, Vault, or support diagnostics.
  • Article slug and route.
  • Consent state for any optional diagnostic material.
  • 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/security-architecture
Selected issue: A security claim appears to conflict with the product screen.
Playbook progress: 0/3 steps marked complete

Safe context to include:
- Question category such as local processing, export, Vault, or support diagnostics.
- Article slug and route.
- Consent state for any optional diagnostic material.
- 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

Built for Security

Your data is valuable. Redactorr is designed around a simple boundary: detect and redact sensitive values in the browser before reviewed output moves anywhere else.

Zero Trust by Design

Browser-Only Processing: Detection and redaction run in your browser. Optional Vault, sharing, and AI workflows use processed or reviewed redacted context when you choose.

When you paste sensitive text into Redactorr, original sensitive values stay local during detection and redaction.

What This Means:

  • Original sensitive values stay local during detection and redaction
  • Vault stores processed redaction sessions and safe summaries when you choose
  • AI Assistant receives reviewed redacted context, not raw original document text
  • Browser-local detection can work offline after first load

Defence in Depth

Redactorr uses multiple layers of security:

Browser Sandbox Modern browsers isolate web applications from your operating system. Processing happens inside a fully sandboxed environment — no access to your file system, network connections, or other browser tabs.

Content Security Policy (CSP) Strict CSP headers prevent code injection or unauthorised network requests. If something tries to send your data out, the browser blocks it.

Web Crypto API All cryptographic operations use the browser's built-in Web Crypto API — hardware-accelerated and continuously audited by security researchers.

Supporting Privacy and Security Review

Redactorr's browser-local detection and redaction boundary can support privacy and security review workflows, but it does not replace your organisation's compliance programme.

Australian Privacy Act 1988 (APPs): Original sensitive values stay local during detection and redaction, which can support APP 11 security review workflows. This is not a legal compliance attestation.

PCI-DSS (Payment Card Industry): Card-like values can be detected and redacted locally during sanitisation, supporting payment-data review workflows. Your organisation still controls its PCI-DSS scope, validation, and evidence.

ASD Essential Eight: Redactorr can support credential hygiene by helping identify secrets and credentials before reviewed outputs move to later workflows.

ISO 27001 / ISMS: The client-side model can be documented as part of an information security management system, alongside your access controls, retention rules, training, and audit process.

Important Note: Redactorr is not a certification, legal opinion, or complete compliance control. Your organisation's compliance programme still requires appropriate policies, access controls, retention rules, training, and auditing.

Encrypted Sharing (Optional)

When you choose to share content via Redactorr's secure sharing feature:

Content is encrypted in your browser using AES-256-GCM

The encryption key is generated locally and never sent to any server

Only the encrypted blob is uploaded

Recipients decrypt locally using the share link

1 / 4

Even when sharing, the server only ever sees encrypted data. The decryption key lives in the URL fragment, which browsers never send to servers.

Third-Party Services

Redactorr uses minimal external services, all privacy-preserving:

Have I Been Pwned (HIBP) for Breach Checking: Uses k-anonymity — only hash prefixes are sent, never actual passwords or emails. Only the required hash prefix is transmitted for the breach check.

No Analytics Without Consent: Basic anonymised metrics are only collected if you opt in. No tracking pixels, no third-party analytics.

Reviewable Boundaries

Security teams should evaluate the product by checking the live browser workflow, current network behaviour, the product screens, and the public source-of-truth pages. Do not treat old articles, mockups, or draft API examples as implementation proof.

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: security-architecture
Route: /knowledge-base/security-architecture
Selected issue: A security claim appears to conflict with the product screen.

Safe context:
- Question category such as local processing, export, Vault, or support diagnostics.
- Article slug and route.
- Consent state for any optional diagnostic material.
- 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
  • Question category such as local processing, export, Vault, or support diagnostics.
  • Article slug and route.
  • Consent state for any optional diagnostic material.
  • 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