1. Scope and operator
This policy explains how SeeMe handles information for accounts, personal profiles, relationship analysis and AI conversations. It applies to the related services provided by SeeMe, which are intended only for adults aged 18 or older.
2. Information we process
Accounts and authentication
Email addresses, password authentication information, account identifiers and login status support registration, sign-in, identity verification and account security. The client stores login credentials to maintain your session; protect your device. Phone registration, SMS verification and phone linking are available according to configuration. These flows process phone numbers and verification records, and use the configured Alibaba Cloud SMS service to send and verify codes. Apple and Google sign-in receive identity information needed for authentication when enabled. Google sign-in does not request access to Gmail messages.
Birth information and personal profiles
Birth dates, times and places you provide, along with profile fields such as your name, gender and personality preferences, are used to store profiles, calculate astrological and traditional cultural characteristics, and generate reference analyses of personal characteristics, partner preferences and relationship themes. Birth information is not used only to display your age. Some deterministic calculations take place on the server; information or calculation results may be included in AI analysis context.
Conversations and analysis results
Conversations, related profiles, generated responses and analysis results, response preferences and feedback support conversations, history display, continuity and troubleshooting. Health, emotional or third-party information you voluntarily share may become part of these records. Avoid unnecessary sensitive content.
Images you upload
Image files, file types, dimensions, associated messages and recognition results are used to store and display attachments, understand images and support conversations. Features that understand images send image content to the AI provider; this may include the current image and historical images referenced in the conversation. Uploading an image does not authorize access to your entire photo library.
Relationship memories and conversation state
The service processes relationship facts, preferences, memory entries and conversation state to provide continuity. Memories are stored separately from the original conversation. Extracted information may be inaccurate; review, correct or delete it as appropriate.
Technical and security records
Requests, errors, invocation times, model and usage information are processed to troubleshoot and maintain the service. Authentication security may process information such as request IP addresses to limit abuse. AI telemetry may also include inputs, outputs and context. It is not limited to performance statistics without content.
3. Storage and providers
Self-hosted storage
Accounts, profiles, conversations, memories and uploaded files are stored and managed in the operator’s deployed PocketBase instance. PocketBase is software; using it does not by itself make it an external recipient of this data.
DeepSeek: AI analysis and conversations
AI calls currently integrate DeepSeek. To provide the requested feature, the service sends relevant prompts, necessary birth information or calculated characteristics, conversation context, related memories and conversation state. Image understanding also sends image content. Returned text and invocation information support responses, stored results and maintenance. The actual scope varies by feature.
Langfuse: AI observability
The project integrates Langfuse telemetry. When enabled and configured, model inputs, outputs, model and usage information, timing and errors may be transmitted to the configured telemetry endpoint. Inputs and outputs may include conversations, profiles and image-related information. These records may contain personal information.
The purposes listed here do not authorize disclosure to arbitrary third parties. Changes to features, providers or processing purposes require updated explanations and any applicable notice and consent.
4. Access, correction, deletion and account closure
Before relevant AI data is sent, the App asks for sharing permission and displays the configured recipients. Refusal prevents sending. You can withdraw permission in Settings; signing out also clears the device permission record. Withdrawal affects future sending, not data already sent or tasks already running.
Use the profile and memory controls actually available in the product to view, correct or delete the relevant information. The App provides an account deletion option. For requests without self-service controls, email us to request access, correction, deletion, withdrawal of consent or account closure. We may verify account ownership and explain the scope and outcome. Never send passwords or verification codes.
Deleting a memory does not delete the original conversation. It does not automatically delete messages, images, profiles, analysis results or existing technical records. Stopping use, signing out or uninstalling the client does not automatically delete server data. Specify the scope when requesting deletion of conversations and related information.
For privacy requests, contact support@in-echo.com. Identify the account and action you are requesting, without including unrelated sensitive information.
5. Retention and security
Accounts, profiles, conversations and memories support ongoing features. We do not currently promise automatic deletion after a fixed number of days. Some temporary images have a cleanup mechanism; this does not mean every image or conversation follows that schedule.
Authentication, access controls and deployment permissions help protect data. No system can guarantee absolute security. If a personal information security incident occurs, we will take remedial action and give notices as required by applicable rules.
6. Adults and information about others
The service is intended only for adults aged 18 or older and does not offer registration or emotional companionship services to minors. Do not submit minors’ personal information. Contact us if such information was collected by mistake so we can investigate and respond.
Provide information about others only when entitled to do so. Prefer descriptions without identifying details. Relationship analysis does not require identity document numbers, contact information or other unrelated sensitive data.
7. This documentation site and policy updates
Reading this site does not require sign-in. Pages do not use analytics scripts or load third-party resources. Providing network access still involves connection information.
We may update this policy as the service and data practices change. Important changes will be notified as required, and consent will be obtained where necessary. For service terms, see the Terms of Service.