Last updated: November 17, 2026
Privacy Policy
iMem is a private memory service for people and the AI tools they choose to connect. This page describes the data handled by the current iMem service and the first iOS TestFlight release.
Data we process
| Data | Purpose and handling |
|---|---|
| Account information | Username, email address, password hash, verification state and session records are stored to create and secure your account. Plain-text passwords are not stored. |
| Memories and artifacts | Titles, text, tags, uploaded text artifacts and related metadata are stored so you can save, search and retrieve them. |
| Schedules and reminders | Schedule, reminder, recurrence and delivery metadata are stored to provide time-based features. |
| Quick-capture text | When AI-assisted capture is used, the submitted capture text and contextual fields are sent to the configured DeepSeek model endpoint to produce a structured preview. Provider credentials remain server-side. |
| OCR and voice | The current backend does not accept image or audio uploads for OCR or transcription. Text produced on the device is handled as quick-capture text if the user submits it. |
| Service records | Request identifiers, route, status, timing, App version/build when supplied, operation type and security events may be retained for reliability, abuse prevention and troubleshooting. Private memory text is not required in these records. |
Third-party processing
iMem sends content to a model provider only when a feature requiring model processing is invoked. The current AI-assisted capture provider is DeepSeek. Connected agents and integrations receive only the access authorized by the user through their session or scoped API key. We do not use a marketing or advertising SDK in the current iOS release.
Retention and deletion
Account and content data is kept while the account is active. Items placed in trash are retained for up to 14 days for recovery. Unverified registration records are retained for up to 7 days; verification challenges and registration-attempt security records are retained for up to 30 days. Account-linked operation records are kept while the account is active and are removed with the personal workspace. Content-free aggregate traffic statistics may be retained for service trend reporting because they are not linked back to an account. Server troubleshooting logs and encrypted backups expire under their configured rolling rotation; they may be held longer only when required for an active security investigation or legal obligation.
A signed-in password account can request deletion directly in the App. The request is normally completed within seven days. Completion disables the account and revokes active sessions and API keys; personal workspace content, schedules, reminders and private artifacts are removed from active storage. Residual encrypted backup copies expire through the normal backup rotation and are not restored as an active account.
Account deletion currently supports a sole-owner personal workspace only. Shared workspaces and personal workspaces with other active members are not supported in this phase and are never silently deleted.
Your choices and security
- You can revoke an integration's API key at any time.
- You can delete individual entries through supported clients before deleting the account.
- Account deletion requires an active password session, password re-verification and explicit confirmation.
Contact
For privacy or product support, email feedback@imem.xin.