Real Memory AI Agent is built for user-directed work. The exact information used depends on the product surface, the task, the permissions granted, and the provider or service the user selects. Local model use can keep inference on a user-controlled machine, but it does not make every connected service or feature local. Review the destination before sending sensitive content.
Information the product may handle
- Prompts, conversation messages, instructions, project requirements, and selected workspace file content.
- Validation output, source diagnostics, command results, changed-file paths, review records, task status, and generated artifacts.
- Images and screenshots when a user attaches them or requests screenshot evidence.
- For browser tasks, the active tab's URL, title, visible text, links, headings, metadata, form labels, and screenshots when the user requests an action that needs that context.
- Configuration such as selected provider, model, endpoint, feature settings, and connection status.
- Provider credentials entered by the user, used to authenticate requests to that user's selected provider or endpoint.
- When a user signs into or uses a Real Memory hosted service, account and service-request information needed to provide that service.
Where information is stored
- VS Code: conversation and runtime records are kept in extension-managed storage on the user's device. Provider credentials use VS Code SecretStorage where supported.
- Chrome and Edge: browser sessions, settings, messages, activity, screenshots, artifacts, and evidence use extension-owned browser storage, including IndexedDB and browser local storage.
- CLI and local MCP: local settings, sessions, runtime records, and generated evidence are stored in the user or workspace locations configured for those tools.
- Hosted services: information sent to a Real Memory hosted service is handled by that service under the applicable service terms and account controls.
Local records remain until the user removes them or the containing application data is cleared. Exact storage controls vary by surface and version.
When information is sent
When a user submits a request, the product sends the information needed for that request to the selected model provider or endpoint. This can include the prompt, relevant source context, attachments, screenshots, browser context, and validation output. Credentials may be included in the request's authentication headers. The product supports user-selected local, cloud, enterprise, Real Memory, and custom-compatible endpoints; the user chooses where inference runs.
Provider logging, retention, training, and deletion practices are controlled by that provider. Review the provider's terms before sending sensitive data. Browser content is gathered for a user-requested browser action or inspection; the browser agent is not designed to build advertising profiles from browsing activity.
Sharing, advertising, and sale
Reallexi LLC does not sell, rent, or trade personal information collected through the product, and does not use it to build advertising profiles or target ads. Information is shared with the selected provider or service to perform the requested feature, and may be disclosed when required for legal, safety, or security reasons.
Website requests
This static product information site does not include an analytics SDK, advertising pixels, or a product sign-in form. GitHub Pages and the user's browser may process ordinary technical request information under their own policies.
User controls and deletion
- Use the product's session, history, artifact, and settings controls where available to remove local records.
- Clear the extension's local browser storage or uninstall the browser extension to remove its device-held data.
- Use the operating system or application controls to remove local VS Code or CLI data.
- For information held by a selected model provider or hosted service, use that provider's or service's retention and deletion process.
Children and sensitive information
The product is intended for developer and workplace use, not for children. Do not submit secrets, personal information, customer records, or regulated data unless the selected provider, endpoint, workspace permissions, and your organization's policies allow it.
Policy changes and contact
We may update this policy as the product changes. The effective date above identifies the latest version. For privacy questions or data requests, contact info@reallexi.io.
Publisher: Reallexi LLC · Product: Real Memory AI