Private Preview
Join Waitlist →

Manage privacy and memory controls

Understand local preferences, assistant memory boundaries, and deletion controls without implying private document training.

Updated 31 May 20266 min readAuthor: Redactorr Support Team · [email protected]Last reviewed: May 2026

Outcome

You can see which controls affect local preferences, assistant context, saved sessions, and deletion choices.

Your progress

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

0 / 3 steps complete

Before you start

Know whether you are changing local preferences, Vault sessions, or AI Assistant context.
Do not assume memory means raw document learning.
Use deletion controls when saved work is no longer needed.

Visual frame

Review asset

Privacy and memory controls storyboard

Synthetic privacy frame only. It separates visible controls from unsupported assumptions about raw document learning.

LocalBrowser preferences
SavedVault sessions
BoundaryNo raw-learning claim

Synthetic frame

Privacy controls

Different controls affect different surfaces.

Browser preferenceLocal display choice
Vault sessionSaved redacted work
Assistant contextSelected redacted context
The word memory is not enough; identify the surface first.

Manage privacy and memory controls workflow frame

Instructional frame for this operational guide. Replace with product screenshots only after the current screen state is approved.

FindIdentify the type of control
DecideInspect the current state
VerifyConfirm the change and its limit

Guided steps

Follow the task, then check the result.

Identify the type of control

Separate browser-local preferences, saved redacted sessions, AI Assistant context, and account privacy controls before acting.

Success check: You know which kind of data the control affects.

Inspect the current state

Read the current setting, saved-session list, or context boundary before deleting, enabling, or exporting anything.

Success check: You can describe the current state without guessing.

Confirm the change and its limit

After saving or deleting, check that the visible state changed and that you understand what the control did not change.

Success check: The control result and its boundary are clear.

Branch questions

Completion check

Local preference, Vault, and assistant-context boundaries were separated.
No raw document learning claim was assumed.
Deletion or setting changes were verified.

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-memory-controls
Selected issue: A privacy control is unclear or missing.
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

Manage privacy and memory controls

Understand local preferences, assistant memory boundaries, and deletion controls without implying private document training.

Use this guide when the privacy and memory settings 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 can see which controls affect local preferences, assistant context, saved sessions, and deletion choices.

Before You Start

  • Know whether you are changing local preferences, Vault sessions, or AI Assistant context.
  • Do not assume memory means raw document learning.
  • Use deletion controls when saved work is no longer needed.

1. Identify the type of control

Separate browser-local preferences, saved redacted sessions, AI Assistant context, and account privacy controls before acting.

Check before you continue: You know which kind of data the control affects.

2. Inspect the current state

Read the current setting, saved-session list, or context boundary before deleting, enabling, or exporting anything.

Check before you continue: You can describe the current state without guessing.

3. Confirm the change and its limit

After saving or deleting, check that the visible state changed and that you understand what the control did not change.

Check before you continue: The control result and its boundary are clear.

Completion Check

  • Local preference, Vault, and assistant-context boundaries were separated.
  • No raw document learning claim was assumed.
  • Deletion or setting changes were verified.

Safe Examples

  • A fake saved session named Demo redacted brief.
  • A synthetic assistant context summary with no private values.

If You Need Support

Contact support when:

  • A privacy control is unclear or missing.
  • Deleted or disabled context still appears visible.

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.

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

Source: Article playbook: privacy-memory-controls
Route: /knowledge-base/privacy-memory-controls
Selected issue: A privacy control is unclear or missing.

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.

Safe 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.
  • Article slug
  • Selected issue
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