LUCI is a desktop application. Your screen recordings, meeting transcripts, and AI memory live on your computer in encrypted storage. Nothing is uploaded to any cloud unless you explicitly opt into Cloud features. You can verify this yourself — disconnect your network and LUCI keeps working.
Architecture: 100% on-device
All processing — screen capture, Memories.ai's on-device long-video understanding, speech-to-text, deep text search, and AI inference — runs locally on your machine via Microsoft Foundry Local and native OS APIs. There is no cloud backend in the data path.
All data is stored in a single folder on your machine (~/.luci/ on Windows, ~/.luciMicrosoft/ on macOS). LUCI never writes to cloud storage, third-party databases, or temporary servers.
Encryption at rest
Every piece of sensitive data is encrypted before it touches your disk:
| Data | Encryption |
|---|---|
| Index database (screen content, window titles, URLs, full-text search index, deep search index, audio transcripts) | ChaCha20-Poly1305 (page-level AEAD, via SQLite3 Multiple Ciphers) |
| Screenshot files | AES-256-GCM (per-file, HKDF-SHA256 derived key) |
| API tokens & credentials | OS keystore (DPAPI on Windows, Keychain on macOS) |
| Master encryption key | Sealed by OS keystore — never stored in plaintext on disk |
The master key is a 32-byte random secret generated once per device and sealed by the OS keystore (Windows DPAPI or macOS Keychain). It is bound to your OS login credentials — a different user account on the same machine, or an attacker with a copy of the disk, cannot unseal it.
Key boundary & honest limitations
The encryption trust root is your OS login credentials. This means:
Stolen device (not logged in)
Cannot read data
Other OS user on the same machine
Cannot read data
Attacker with a disk copy / backup
Cannot unseal key
Malware running under your account
Can request the OS to unseal the key
The same-account malware boundary is shared by every desktop application that uses OS keystore encryption (browsers storing passwords, password managers, etc.). Microsoft Recall uses TPM + VBS enclave + Windows Hello to close this gap, but that mechanism is only available to OS-level features on specific hardware — third-party apps cannot access it. We state this boundary honestly rather than pretend it does not exist. We recommend enabling BitLocker (Windows) or FileVault (macOS) for full-disk encryption as an additional layer.
Network transparency
In Local mode, none of your data — screen recordings, meeting transcripts, or AI memory — ever leaves your machine. The only outbound connections the app makes are the operational ones below: auto-update checks and, unless you turn it off, anonymous product analytics. Here is the complete list of domains the application may contact, and why:
| Domain | Purpose | Required? |
|---|---|---|
| github.com / OpenInterYRZ/luci-electron-release | Auto-update check — downloads new versions from GitHub Releases | Auto-update |
| api.memories.ai | Cloud features (login, sync) — only when you opt into Cloud mode | Optional |
| us.posthog.com | Anonymous product analytics — on by default (opt-out). No screen content, recordings, or transcripts are ever sent; only manually-defined product events. Turn it off in the onboarding step or Local Settings → Privacy. | Optional |
We commit to keeping this list current with every release. You can verify it yourself: run LUCI with a packet capture tool (Wireshark, Little Snitch, GlassWire) and compare outbound connections against this list. In Local mode, with both auto-update and anonymous analytics turned off, you should see zero outbound connections.
User control
- Pause capture: Stop screen memory at any time. No background recording while paused.
- Delete data: Delete by day or wipe everything with one click. Deletion removes both encrypted screenshots and index entries.
- Everything runs on your device: on-device screen understanding, deep text search, transcription, and AI inference all run locally, and your memory is stored on your machine, encrypted at rest. The Agent Bridge runs on your device and only answers authorized local agents — your agent reads only what it asks for.
Cloud features (opt-in)
LUCI includes optional Cloud features (login, cloud chat, sync) ported from a prior project. These are entirely opt-in — you must create an account and explicitly switch to Cloud mode. When Cloud features are active:
- Authentication goes through Supabase (hosted auth provider).
- Cloud chat messages are sent to remote LLM endpoints.
- Your screen memory, local meeting transcripts, and local AI memory are never sent to any cloud service, even in Cloud mode.
If you use the personal agent with a remote (BYOK) API endpoint, the app will warn you before the first message that conversation content will be sent to that endpoint. Local (Foundry) endpoints never trigger this warning.
Responsible disclosure
If you believe you have found a security vulnerability, please email security@memories.ai. Include reproduction steps and any relevant logs. We aim to acknowledge reports within two business days and will keep you updated as we investigate. Please do not publicly disclose the issue until we have had a reasonable opportunity to address it.
We will not pursue legal action against researchers who:
- Make a good-faith effort to avoid privacy violations and service disruption
- Report findings only to us before public disclosure
- Do not exploit the issue beyond what is necessary to demonstrate it
Contact
For security questions, vulnerability reports, or compliance documentation, contact security@memories.ai. For privacy-related inquiries, see our Privacy Policy.