Skip to content
How it works

How MemScope decides who can recall a memory

Your AI saves only what you ask. AI suggests labels. Your organization’s policy decides who can see each memory. And only the right memory reaches the right person.

  1. 01

    Save

    An AI saves a memory

  2. 02

    Label

    AI suggests labels

  3. 03

    Decide

    Your policy decides who can see it

  4. 04

    Recall

    Each person’s AI recalls only that

01

Save

An AI saves a memory

You ask your AI to save something. It sends exactly that to MemScope — nothing is scraped from your chats. It can ask for Shared or Personal, and sending the same memory twice won’t save it twice.

Your AI saves: "Project Falcon switched to Supplier B."
Who can see it: Project Falcon
02

Label

AI suggests labels

When AI labeling is on, a fast AI model suggests how sensitive the memory is, its topic and tags, with a confidence score. Low-confidence labels go to a review queue for a person to check. The AI never decides who can see a memory.

Suggested by AI
  Sensitivity:  Internal
  Topic:        Engineering
  Confidence:   High (94%)
03

Decide

Your policy decides who can see it

Your organization’s rules can only make a memory more private, never less. For example, you can require that HR memories are always Highly restricted and only reach the People team.

Your organization’s rules
  Lowest sensitivity:  Internal
  HR topics:           People team only,
                       Highly restricted
04

Recall

Each person’s AI recalls only that

When someone’s AI looks something up, MemScope checks every possible match against your organization’s policy first. Only memories that person is allowed to see are ranked and returned — and anyone can ask why they can see one.

Decided by your organization’s policy
  Can see it:  yes
  Why:         member of Project Falcon

See it with your own data

Create an organization, connect a client and watch a memory travel from being saved to being recalled by the right people.