The essentials: your personal chat history stays on your device. mesme does not maintain a permanent server archive of your conversations. Encrypted delivery data may be held temporarily. Account, contact, group-administration and payment records are separate service data. Content you submit to AI is processed by our assistant service and OpenAI.
1. Who we are
mesme operates mesme. For questions about this policy, personal-data requests or support, contact [email protected]. The Android application identifier is app.mesme.ai.
This policy covers our app and website. Google Play, AI providers, websites you open and other services you choose also have their own privacy policies.
2. Information we handle and why
| Information | Purpose and handling |
|---|---|
| Account and public profile | Username, peer identifier, public contact card, display name and any profile details you choose to publish help people find and recognize you. Public profile information can be shared with other users and directory nodes. |
| Authentication and recovery | We store password/recovery verification values, salts, a hash of the active device credential, device names and activation/revocation timestamps. An encrypted recovery bundle can contain your identity and contacts. It excludes chat history. Your recovery phrase and app-lock PIN are not sent to the account service. |
| Contacts and groups | Contact relationships, group membership, roles, invitations, restrictions, bans and administration events support contacts, group management and anti-spam rules. Group statistics can include message counts. These records are distinct from the encrypted contents of group messages. |
| Messages, media and calls | History and downloaded media are kept on your device. Relays can temporarily handle encrypted messages, call signaling and attachment fragments. Calling services handle connection and routing information. We do not operate a call-recording archive. |
| AI requests | Text, selected images or audio, task settings and relevant assistant-chat context are sent for the task you request. Usage counters enforce the free allowance and technical limits. See section 4. |
| Purchases and Premium gifts | Google Play purchase tokens, product/plan identifiers, entitlement and renewal status, expiration times, and payer/recipient identifiers let us verify purchases, restore access and deliver gifts. Google handles the payment method; mesme does not receive your full payment-card details. |
| Technical and support information | Network addresses, connection events, errors, rate-limit counters and information you send to support help deliver the service, diagnose faults and prevent abuse. Installation credentials are used for account security; they are not proof that one physical device can create only one account. |
We use information to provide the features you request, protect accounts and the network, fulfill purchases, answer support requests and meet applicable obligations. Where required, we rely on your consent for optional access or processing. Other processing is necessary to provide the service, protect it against misuse or comply with law.
3. Messages, local history and connections
Personal messages and attachment content are encrypted for delivery. Your readable chat history is stored locally. “No permanent server chat archive” does not mean that no information ever reaches a server. Relays and distributed nodes may store encrypted packets, encrypted file fragments, routing data, public directory entries and presence information to deliver messages.
Delivery records have expiration times, generally up to 48 hours under the current configuration. Some copies can expire sooner. A recipient's acknowledgement can remove queued group-delivery envelopes earlier. Delivery is not guaranteed when no route is available or a packet expires.
Direct calls and nearby networking can reveal network addresses or proximity to participating peers. Relay services can see connection metadata. Mesh availability depends on the available devices, range and routes; it is not a guarantee of anonymity or connectivity.
Recipients control their own copies of information you send. App-level copy restrictions do not prevent screenshots, photographing a screen, modified clients or other forms of capture. Public usernames and profile details may be visible to people outside your contact list according to your settings.
If you create an optional encrypted history export, you decide where it is saved and how long to keep it. mesme does not upload your personal chat history to its account server. Google Drive linking is not currently offered in this release; a future integration will require a separate user choice.
4. AI helpers, translation and transcription
When you ask a helper to translate, rewrite, solve a problem, generate an image or transcribe a voice message, the necessary content is sent to the mesme assistant service and OpenAI. In the shared assistant chat, relevant preceding messages may be included so the helpers can understand follow-up requests and coordinate a task.
Ordinary conversations are not automatically sent to the AI service. If you enable automatic translation, eligible incoming messages are submitted for translation until you turn that setting off. Voice dictation can also use your device's speech-recognition provider; that provider may process audio under its own settings and policy.
Our assistant service uses content to fulfill your request. It does not intentionally write the text, image or audio contents of AI requests and responses into a permanent content database or application logs. It uses bounded, short-lived memory caches for retries and keeps usage/status metadata. Your assistant conversation history remains on your device.
For text responses, mesme requests non-stored responses from OpenAI. This does not guarantee zero retention by the provider. OpenAI describes separate abuse-monitoring, caching and safety retention, including retention of up to 30 days for many endpoints, with exceptions. Review OpenAI's API data controls for current details.
AI output can be inaccurate. Review it before relying on it or sharing it. Only submit content you are entitled to share, and avoid including unnecessary sensitive information about yourself or others.
6. Device permissions
The app requests access as needed for its features. You can review and revoke permissions in Android settings.
- Microphone and camera: voice messages, calls, video and chosen photo/video capture.
- Photos, videos, audio and files: selecting, sending, playing or saving content. The system picker may let you grant access only to selected items.
- Bluetooth, nearby devices, Wi-Fi and location-related permissions: discovering nearby peers, local networking and routing call audio. Android versions and nearby-network APIs may require location-related permission for discovery; this is not a location-tracking timeline.
- Notifications and foreground-service access: incoming messages, calls, active audio and connection status.
Sharing a contact or media item sends the content you choose. An app PIN or a second-PIN chat list affects local access and display; it does not remove information from a recipient's device.
7. How long information is kept
- Local history and media: until you delete them, clear app data or uninstall, subject to any copies or backups you keep.
- Encrypted delivery buffers: until acknowledged where supported or until their expiry, generally no more than 48 hours in the current service configuration. Expired entries are removed during cleanup.
- AI content caches: short-lived memory only; retry results have a two-minute reuse window and are removed as cache cleanup runs or the service restarts. Provider retention is separate.
- Group metadata: composition, permissions and administration records are kept to operate the group. Current message-deduplication metadata is cleaned after seven days, and daily aggregate group statistics after 90 days.
- Account, contact and recovery data: while needed to operate the account, until an appropriate verified deletion request is processed, or where retention is required for security or law.
- Purchase and gift records: for entitlement verification, restoration, dispute handling, fraud prevention and applicable accounting/legal obligations. Deleting an account does not automatically cancel a Google Play subscription.
- Operational records and backups: kept as needed for troubleshooting, security and recovery. Encrypted database pages or administrative backups can retain earlier records until rotation; deleting live data is not a promise of immediate physical erasure of every storage copy.
8. Your choices, requests and account deletion
You can edit your profile, change available privacy settings, disable automatic translation, control nearby-network use, revoke permissions and delete local content. You can manage or cancel subscriptions through Google Play subscriptions.
To request access, correction or deletion of account data, contact [email protected]. Depending on where you live, you may also have rights to portability, restriction, objection, withdrawal of consent or a complaint to a data-protection authority. We may need reasonable verification before acting on a request.
For an account-deletion request, follow the Delete account instructions. Do not send your password, recovery phrase, app PIN or payment-card information. Removing the app alone does not delete your server account. We cannot delete copies held independently by other users, relay operators or a backup provider you chose.
9. The mesme.ai website
This website serves product information and these policies. We do not add advertising trackers, marketing analytics or embedded social feeds. Images and scripts are served from the site itself. The interactive assistant examples run locally in your browser and do not send an AI request.
Cloudflare provides the website's DNS, proxy and security services. It and our hosting server receive your network address and request information to deliver pages and protect the service. Cloudflare may process security/performance telemetry and use cookies necessary for its security features. See Cloudflare's Privacy Policy. We do not set advertising cookies.
Technical error logs may include request details. Clicking Google Play, an email link or another external link takes you to that provider, which handles subsequent activity under its own policy.
10. Children
mesme is not directed to children under 13 or under the minimum age required in their country. If you believe a child has provided personal information inappropriately, contact us so we can investigate and take appropriate action.
11. Changes and contact
We may update this policy as the app, service providers or legal requirements change. The date at the top identifies the current version. Where required, we will provide additional notice or request consent for material changes.
mesme · Privacy & support
[email protected]
Please describe your request without sending passwords, recovery phrases or unnecessary sensitive data.