Inspect and correct memory
The Memory interface supports source inspection and local corrections. These changes are not yet a confirmed update to stored service data.
Explore Memory ↗SECURITY & DATA CONTROLS
Useful context.
Informed choices.
Understand what you connect, what you share, and what each control means. This guide separates the current interface from controls that still need live service integration.
UNDERSTAND THE CONNECTION
Capture and recall are different.
Connecting a tool is a workflow decision. Check its setup guide before enabling it, especially for conversations containing personal or confidential information.
- 01 / YOUR TOOL
Choose what to connect.
Supported capture hooks send conversation events from the configured tool. Review the capture guide before installation.
- 02 / CTX
Bring context into memory.
Capture, processing, and recall are separate stages. A received verification message confirms capture, not that every memory is ready or recall is working.
- 03 / YOUR ASSISTANT
Request useful context.
An MCP connection lets a supported assistant request memory. Follow the recall guide and check the tool provider's own data policies.
KNOW WHAT A CONTROL DOES
Clarity before confidence.
Exclude, remove, or export
Local memory exclusion, reversible removal, and export are available in the interface. They do not establish server deletion, backup removal, or a complete account export.
Ask about a data request ↗Review a proposed action
Loop's example task shows the recipient, content, and one-action permission scope. Approving it does not send anything. External execution is not connected.
Understand Loop ↗Preview an attachment
Loop file previews remain local. Selecting a file does not upload it or mean an assistant has analyzed it. Avoid sensitive files when trying sample workflows.
Explore Loop's interface ↗CREDENTIAL HYGIENE
Keep keys out of conversations.
A setup prompt should explain the task without containing an API key. Environment variables are not automatically redacted from tool output or assistant context.
- Do not paste keys into chat, screenshots, issue reports, or public repositories.
- Use only credential methods documented for your installed CLI. Do not assume an environment-variable name is supported.
- Review proposed installation and configuration changes before allowing an agent to make them.
- If a key may be exposed, stop using it and contact the team if you cannot confirm that revocation succeeded. A local UI change is not proof of revocation.
BEFORE A SENSITIVE WORKFLOW
Get the details you need.
This page is not a certification or a security audit. It does not make guarantees about encryption architecture, data residency, retention periods, model training, or compliance.
Where can I find the data-handling policy?
The privacy policy describes data handling. For questions about your intended use, contact the team before sharing sensitive information.
Does archiving a chat delete its memory?
No. Local chat archiving hides a conversation from the active history list. It does not delete memory or service data.
Are security certifications or audit reports available?
No certification or independent audit is asserted on this page. Ask the team for available evidence and scope before relying on a particular assurance.
REPORT A CONCERN
Help us investigate responsibly.
Send a description, affected page, and safe reproduction steps. Never include passwords, API keys, or someone else's private data. Ask for an appropriate channel before sharing sensitive evidence.