memTITAN® Back

Data Safety Summary

Private AI memory, withclear data boundaries.

This public summary explains what memTITAN® keeps local, how the local phone-to-Core connection works, and how mobile permissions are used. It is written for users and app-store review, not as raw internal compliance notes.

1. Data that stays local

By default, memTITAN® stores personal working data on the user's own local Core, not in a central memTITAN® cloud account.

  • chat messages and conversation context
  • personal memories such as names, pets, preferences, corrections and relationships
  • uploaded images, screenshots, documents and OCR text
  • meeting preparation details and local memory indexes
  • local Core access keys and local configuration

2. Local connection and remote relay status

When used, the official memTITAN® relay may see
  • IP addresses
  • timestamps
  • technical session or routing IDs
  • encrypted packet size
  • delivery status or technical errors
When used, the official memTITAN® relay cannot read
  • chat messages
  • memories or memory content
  • images, screenshots or documents
  • meeting notes or memTITAN® answers
  • encryption keys or the Core access key

memTITAN® supports local same-network phone-to-Core connection and remote phone-to-Core connection through the official memTITAN® relay hosted by Hetzner Online GmbH in Helsinki, Finland. Relay traffic is end-to-end encrypted.

3. Technical logs

The official memTITAN® relay creates limited technical relay logs for security, abuse prevention, reliability and troubleshooting. Ordinary technical relay logs are retained for up to 7 days unless longer retention is legally required or necessary for a security investigation.

Technical relay logs do not contain private chat content, memories, images, documents, meeting content, memTITAN® answers, encryption keys or plaintext packet contents.

4. Mobile permissions and device-first actions

memTITAN® may prepare actions such as WhatsApp drafts, email drafts, calendar entries, reminders or map routes. These actions are device-first: memTITAN® prepares the draft or link, and the user decides whether to send, save or open it.

If the operating system asks for a permission, such as calendar access or notifications, that permission is used for the selected device action. memTITAN® does not automatically send messages or add events without the user's action.

5. App-store data safety alignment

This summary is intended to align with the Google Play Data Safety document. Before store publication, app-store forms must match the actual released build and the published Privacy Policy.

Local data stored only on the user's own device is not readable by a central memTITAN® cloud account. Platform providers such as Google Play or Apple App Store may process their own account, download, payment or diagnostic data under their own terms.

6. More information

For the complete legal text, see the Privacy Policy. For questions, contact info@memtitan.ai.