What Linse Stores (Memory)
Understand what Linse can store, how long it keeps it, and the controls you have over your data.
Linse treats memory as a transparent record of context you choose to keep. You can see what’s stored, where it belongs, and how to remove it at any time.
Types of memory
Linse can separate memory into clear scopes, so you decide who benefits from saved knowledge.
- Personal threadsPrivate conversations only you can access—useful for drafts, brainstorming, and sensitive planning.
- Workspace memoryShared context teammates can reference, like briefs or onboarding notes. You stay in control of what becomes shared.
- Temporary contextContext used only for the current session. It’s not saved unless you explicitly choose to keep it.
Retention controls
You decide how long Linse keeps stored information. Retention can be configured by workspace (and, where applicable, by source).
- Auto-expire conversationsApply expiration windows (for example 7, 30, or 90 days) to sensitive threads so they’re removed automatically.
- Bulk delete sourcesRemove entire sources or connected integrations from memory in one action—so you don’t have to clean up item by item.
- Audit trailWhen enabled, generate a report of memory activity over time (saved, edited, and deleted) for visibility and accountability.
- Retention policies live in Settings → Data Control.
- Exports (for example JSON or Markdown) can be available before deletion, where supported.
Transparency features
Linse is designed to make context visible—not hidden. Where available, responses can show what remembered context was used, so you can review the source and remove access if needed.
- Revoke instantlyRemoving a memory item prevents it from being used going forward.
- Workspace safeguardsAdmins can set policies for how memory is shared and reviewed within a workspace.
Questions about data handling?
Reach out and we’ll walk through your requirements and share the right documentation for your use case.
Talk to us
What Linse Stores (Memory)