What Linse Stores (Memory)

Understand how Linse captures context, how long it keeps it, and the controls you have over your data.

Linse treats memory as a transparent ledger of the interactions you approve. You always see what is stored, where it lives, and how to remove it.

Types of memory

Linse separates memory into three scopes so you can decide who should benefit from stored knowledge.

1
Personal threads
Private conversations only you can see. Use them for drafts, brainstorms, or sensitive planning.
2
Workspace memory
Shared context that teammates can reference, like project briefs or onboarding guides. You approve every addition before it becomes shareable.
3
Temporary context
Information Linse holds just for the current session. It disappears automatically when the conversation ends unless you choose to save it.

You decide how long Linse keeps your data. Default retention is 180 days, but you can shorten or extend it per workspace or source.

1
Auto-expire conversations
Apply expiration windows (7, 30, 90 days) to sensitive threads. Linse deletes them without manual follow-up.
2
Bulk delete sources
Remove entire folders or integrations from workspace memory with one action. Linse confirms once all copies are gone.
3
Request an audit trail
Generate a report showing who saved, edited, or deleted memory items over time.

• Set retention policies in Settings → Data Control. Changes apply retroactively.

• Exports are always available in JSON or Markdown before you delete anything.

Every response cites the exact memory segments used. Hover a citation to review the source, share it, or revoke access.

• Revoking a memory segment immediately updates past responses that referenced it.

• Workspace admins can require citation review before answers are shared externally.

Reach out and we will walk through your governance requirements and provide detailed documentation.