About this policy
This policy explains how EmemoX handles information on ememox.com, in EmemoX-demo, and in the developer console and hosted memory API. If you use an application built by another developer with our API, that developer also controls how your information is collected and used. Independently hosted copies of EmemoX are managed by their own operators.
Information we handle
Account information includes your email address, display name, verification status, and profile image where provided. Password sign-in stores a password hash. Third-party sign-in stores the provider account identifier and authentication tokens returned by the provider.
When you use the service, we process conversations, replies, documents or events you submit, extracted memories and their sources, and feedback. The developer console also stores organizations, memberships, projects, API key records, usage, and plan requests.
Session and operational records may include IP addresses, browser information, request times, errors, and usage counts. Cookies keep you signed in across the demo and console. Browser storage retains interface preferences and cached conversation state.
Google sign-in
Google sign-in requests only your basic profile and email information: your Google account identifier, name, email address and verification status, and profile image when available. We use this information to create or link your EmemoX account, authenticate you, and display your profile. We do not request access to Gmail messages, Google Drive files, contacts, or calendars.
We do not sell Google account data, use it for advertising, or use it to train general-purpose AI models. EmemoX's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
You can revoke EmemoX's Google access in your Google Account connections. Revoking access does not by itself delete information already stored in EmemoX. Use Account & invitations in the console to request deletion.
How information is used and shared
We use information to provide sign-in, maintain conversations and memory, retrieve relevant context, generate replies, manage project access, enforce usage limits, and investigate service failures or abuse.
When you use AI features, your submitted content and relevant conversation or memory context are sent to model and embedding providers to generate replies or process memories. The hosted service currently uses Tencent Cloud TokenHub for model requests. Avoid submitting secrets or sensitive information that you do not want processed this way.
We use Resend to deliver email verification codes. Google or GitHub handles authentication when you choose that provider. Hosting and infrastructure providers process the information needed to run the service. Authorized organization members can access project information according to their roles. Service operators may access records when necessary for support, security, and maintenance. Information may also be disclosed where required by applicable law.
Storage and retention
Account and service records are stored on our servers. Conversations and extracted memories are stored separately so that useful context can carry across conversations. Information may be processed in different countries or regions by the providers involved in delivering the service.
We retain information while it is needed to provide the service and address operational, security, or legal needs. Signing out, revoking Google access, or clearing browser storage does not delete server records. Deleting a conversation does not automatically delete the long-term memories extracted from it. Memory revisions, source records, operational logs, and backup copies may have separate retention lifecycles.
The hosted service has not published a default retention period, backup expiry, hosting region or recovery guarantee. These details must be confirmed for your deployment before you rely on a fixed duration or location. Independently hosted deployments are controlled by their own operator.
Your choices and requests
You can clear conversations and manage visible memories using the controls in EmemoX-demo. Developers can manage project keys and use the API's memory controls. These controls have different scopes; check the confirmation shown for each action.
In Account & invitations, export your account data or submit an account-wide deletion request and check its status. Submitting a request does not mean deletion is complete. The request must cover conversations, extracted memories and sources separately; logs and backup retention need confirmation. If another application submitted your information, contact that application's operator as well.
For support with data requests, contact the EmemoX service team: miaohonghit@gmail.com
Updates and contact
We will update this page when our information practices change and revise the date above. For questions about this policy or Google sign-in data, contact the EmemoX team at miaohonghit@gmail.com.