Memory & contextWhat it keeps, and how to erase it

Two kinds of memory. Both yours to erase.

The facts the assistant keeps about you, each saying where it came from, and the links LumenQube drew between your own notes, tasks and meetings. See both, read the exact text they add to your next question, and forget anything with a receipt for every place it reached.

Download freeSee exactly what is sent

Settings → Memory & context. Each store switches off on its own; the editors never need either.

The graph lives
On this computerShared with your phone only if you set it up
Sent with a question
Titles and distancesNever the contents
Forget reaches
Every store that holds itAsks first, then a receipt for each
Switches
One per storeMemory and context, separately

01What it does

What you told it, and what it worked out.

Two stores with different lifecycles and different rules. Software that calls both “memory” behind one switch is hiding a store from you.

01The request

Read every word before it leaves.

Both blocks are shown verbatim, before you send anything. The context pack carries titles and how far apart things are — never the contents. Switch memory off and its block is never built, so there is no second copy anywhere in the request.

  • Shown verbatim, before sending
  • Titles and distances, never file contents
  • Memory off means the block does not exist
One question, as it leavesReadable before send
Memory blockCore cached · rest per message
What it remembers about you The facts that always matter ride the cached part; the rest join only the message they are about, and the answer names them. Off means the block is never built — no second copy anywhere in the request.
Context packNever the contents
What it connected Titles and how far apart things are: “Q3-model — directly linked”, “Pricing review — 2 steps away”.
PassagesOn request
What the step needs Only when a step reads a document, and only the part it reads.
Your questionYours
“Draft the variance section of the board memo.” Exactly what you typed.
Never in the request: file contents from the graph, other memories’ sources, anything excluded.

02It connects your work to itself

Links between your notes, tasks, meetings, events and people, built on this computer — nothing is fetched to build them. Notes and tasks stay out of the plaintext index, so the graph reaches an encrypted note no search could.

Board memo — Q3Q3-model1 stepQ3 board prep1 stepPriya Kapoor1 stepPricing review2 stepsVariance note2 steps Built on this computer Notes stay out of the text index

03Durable memory

Facts you told it, ones it saved while working and — with “Notice things on its own” on — ones it noticed in a conversation you finished. Each says which, and links to the conversation it came from. Credentials, keys, card and identity numbers are never kept; health, beliefs and the like only when you ask in so many words.

Kept, and where each came from PreferenceWants variance in percentyou told itProjectBoard pack due last Fridayit saved thisPersonPriya owns the variance noteit noticed on its own
Never kept, whoever asks API keysk-live-••••••••3f9aCard number•••• •••• •••• 4242Passport number•••••••12Recovery phrase12 words, redacted Health, beliefs and the like: only when you ask it to remember, in so many words.

04Two sets, read both ways

This computer keeps up to 200 facts per space; the phone keeps a cloud set of up to 64. The phone and the web read this computer’s most recent facts, this computer reads the phone’s in your Home space, and a fact forgotten on either side is forgotten on the other.

This computer 37 / 200 Up to 200 per space. Reads the phone’s facts in your Home space.
The phone 21 / 64 A cloud set. The phone and the web read this computer’s newest facts.
Read both ways — and a fact forgotten on either side is forgotten on the other.

05Forget, everywhere it lives

Deleting a note is one row. Forgetting it reaches every store that holds a piece of it — on this computer, on your other devices and in the cloud copy. It asks first, with the counts, then tries each store on its own, and the receipt names anything it could not reach — never a false success.

A receipt for every forget

Forget the open noteIt asks first, with the counts — then each store on its own.
01
The map The item and every link to it.
02
The search index Erased explicitly, or the title stays findable. No cascade reaches here
03
The embeddings Held in a separate process. Asked directly. A different process
04
Memories that name it Here and on your other devices.
05
The cloud copy The copy your other devices read. Not on this computer
Forgotten: the item, 12 connections, its search entry, 8 stored comparisons, 2 remembered notes, the copy on your other devices.
Partly forgotten — the semantic engine was unreachable, so some of it is still stored. Try again once it is back.

02LumenAgent + Memory

It remembers the brief, not the secrets.

LumenAgent starts every job already knowing how you like the work done and what it connects to — so it does not search to rediscover what your workspace already knows, and it does not ask you twice.

Remembers
Preferences, projects, people, goals — and says where each came from
Never keeps
Credentials, keys, card and identity numbers
Connects
Notes, tasks and meetings — on this computer
Sends
Titles and distances, never contents

03The full toolkit

Everything you can see, change and erase.

A privacy surface that only listed features would not be one. So this one also says what it does not do yet.

See it

Live, not a policy page.

  • Live counts by type and by source
  • Both blocks, verbatim, before sending
  • Where each memory came from
  • Which memories an answer used
  • Up to 200 per space here, 64 on the phone

Control it

A switch per store, and one for noticing.

  • Memory off — the block is never built
  • Context engine off — no context pack
  • “Notice things on its own”, separately
  • Remove remembered facts one by one
  • Secrets and ID numbers never kept

Forget it

Every store, one action.

  • Asks first, with the counts
  • The item and its links
  • Its search entry and embeddings
  • Memories that name it, on every device
  • The cloud copy
  • A receipt naming what was missed

Deliberately not, yet

Said here, so it is not a surprise.

  • No per-project AI access rules
  • Home’s quick search skips the graph

04Works with the rest

Memory is what lets the rest stop asking.

  1. Feeds it

    Notes and meetings

    Every link you make, and every meeting you keep, becomes part of the graph.

  2. Connects it

    Memory & context

    Built and kept on this computer. Readable before anything is sent.

  3. Uses it

    LumenAgent

    Starts each job knowing your preferences and what is connected.

  4. Erases it

    Forget

    Every store that holds it, attempted one by one, with a receipt.

05Questions

Common questions

Does LumenQube train on my documents?

LumenQube does not use your content to train a generalized AI model as a product purpose. Content is sent only when you request an AI feature, to the selected processor or eligible fallback needed for that request. A provider’s own data use, retention and permitted security or legal processing depend on the service and our account terms and settings. See Privacy Policy §7.

What exactly is sent when I ask a question?

At most two blocks, both shown verbatim in Settings → Memory & context: the memory block — the facts that always matter, plus any this question is about — and a context pack of titles and distances. File contents are never part of either, and each answer names the memories it was given beyond the core.

If I forget something, is it really gone?

From LumenQube, yes: the object, its links, its search entry, its embeddings and any memory that names it — on this computer, on your other devices and in the cloud copy. It asks first, with the counts. If a store cannot be reached, the receipt says so. It cannot recall copies made elsewhere or messages already sent to a model.

Why is memory on my phone different?

It is two stores read as one. The desktop keeps up to 200 facts per space; the phone keeps a cloud set of up to 64. The phone and the web read this computer’s most recent facts, this computer reads the phone’s in your Home space, and a fact forgotten on either side is forgotten on the other. Each screen still says which set a fact lives in.

Can I turn all of this off?

Yes, separately. Memory off means no memory block; the context engine off means no context pack; and “Notice things on its own” can be off while memory stays on. Neither affects the editors, which work fully offline.

Know what it knows.

Open Settings → Memory & context, read the block before you send anything, and erase whatever you like.

Download freeRead the security page

Memory and the context engine each switch off on their own, and neither is needed by the editors.