1. Controller
The controller responsible for data processing in connection with memTITAN® is:
memTITAN®
Switzerland
Email: info@memtitan.ai
Privacy requests and data protection questions can be sent to info@memtitan.ai.
2. Local-first processing in the Core
The memTITAN® Core processes and stores data locally on the user's device. This may include:
- chat messages between the user and memTITAN®
- personal facts shared by the user, such as name, pets, preferences, relationships, corrections or work context
- local memory stores and search indexes
- local conversation and context data
- uploaded images, screenshots or text for OCR/text recognition
- documents, notes or research sources added by the user
- locally generated security data, such as Core access keys
- local settings, such as Desktop/Mobile pairing information
These local contents are not automatically transferred to memTITAN® and are not stored in a central memTITAN® account.
3. Mobile app and Core connection
The mobile memTITAN® app can connect to the memTITAN® Core. For this connection, the app may locally store technical connection data, such as Core address/server URL, pairing status, technical session information and, for encrypted connections, cryptographic key material in the operating system's secure storage.
Cryptographic keys must not be stored in normal local storage. On mobile devices they are stored in secure operating system storage, such as Android Keystore or iOS Keychain.
4. Local connection and official relay
The mobile app can connect to the user's own Core on the same local network or through the official memTITAN® relay for remote access.
The official memTITAN® relay is hosted by Hetzner Online GmbH in Helsinki, Finland, within the European Union. It transports only end-to-end encrypted packets and limited technical routing metadata.
The relay is designed so it cannot read chat content, memories, images, documents, meeting notes, AI answers, encryption keys or the local Core access key.
5. End-to-end encryption
For encrypted remote access, memTITAN® uses established cryptographic methods. Private keys do not leave the respective device.
- Core and app generate local keys.
- Only public keys are exchanged during pairing.
- The pairing code is not an encryption key.
- Session keys are derived locally on the devices.
- Message packets are authenticated and encrypted.
- The official relay stores no private keys and cannot decrypt content.
There is no plaintext fallback through the relay if end-to-end encryption is unavailable.
6. No telemetry and no analytics
memTITAN® does not send telemetry, usage analytics or automatic crash reports to memTITAN®. In particular, memTITAN® does not automatically transmit chat messages, stored memories, uploaded images/documents, usage behavior or local debug logs.
If optional diagnostics or crash reporting are introduced later, this policy will be updated first and the function will be described transparently.
7. Website, domain and downloads
The website memtitan.ai is hosted through Infomaniak. When visiting the website or downloading memTITAN®, technically necessary access data may be processed, such as IP address, time of request, requested page or file, browser, operating system, referrer URL and technical server logs.
memTITAN® does not use marketing cookies, tracking cookies or external analytics services on this website.
Technical Infomaniak hosting logs are used only for security, operation and troubleshooting and are normally deleted after 7 days unless longer retention is legally required or necessary for security investigation. memTITAN® does not create additional website tracking profiles.
8. App stores and platform providers
If memTITAN® is downloaded through app stores or platforms, such as Google Play or Apple App Store, those providers may process their own data, such as account, device, payment, download or diagnostic information. That processing is governed by the privacy terms of the respective platform provider.
The Google Play Data Safety and Apple privacy label information must be kept aligned with this Privacy Policy and the actual technical implementation before any store publication. A public user-facing summary is available in the Data Safety Summary.
9. External services and device actions
memTITAN® may prepare device actions such as email drafts, WhatsApp drafts, calendar entries, map routes or meeting reminders.
memTITAN® does not send such contents automatically. The relevant app is opened as a draft, link or system action. The user decides whether to send a message, save an event or open a route.
If external apps or services are used, such as WhatsApp, email providers, Google Maps, Apple Maps or calendar services, their own privacy terms apply.
10. Research, news and external sources
For research or news features, memTITAN® may retrieve public sources, websites or feeds. External sources may see technical access data such as IP address, timestamp and requested URL of the requesting device or server.
Automatically found research content is not added to usable personal memory without user approval.
11. Legal bases
Where the GDPR applies, processing is based in particular on Art. 6(1)(b) GDPR where processing is necessary to provide app functions or perform pre-contractual measures, Art. 6(1)(f) GDPR where processing is necessary for security, stability, abuse prevention and technical operation, and Art. 6(1)(a) GDPR where consent is required for optional functions.
Where Swiss data protection law applies, personal data is processed according to the principles of lawfulness, transparency, purpose limitation, proportionality, data security and privacy by design.
12. Switzerland, EU and international transfers
memTITAN® is based in Switzerland. The European Commission recognizes Switzerland as providing an adequate level of data protection, which generally allows personal data to flow from the EU/EEA to Switzerland without additional transfer safeguards.
If memTITAN® targets persons in the EU or monitors behavior within the meaning of the GDPR, the GDPR may additionally apply. Where required by applicable law, memTITAN® provides the necessary contact or representative arrangements.
13. Retention and deletion
Local data remains on the user's device until it is deleted, the app is uninstalled, the Core is reset or the local data area is removed.
The official memTITAN® relay creates limited technical relay logs for security, abuse prevention, reliability and troubleshooting. Ordinary technical relay logs are retained for a maximum of 7 days unless longer retention is legally required or necessary for security investigation.
Website logs are kept only as long as necessary for security, operation and troubleshooting. Technical Infomaniak hosting logs are handled according to the applicable Infomaniak hosting configuration.
14. Rights
Depending on applicable law, data subjects may have rights of access, rectification, deletion, restriction, portability, objection, withdrawal of consent and complaint to a supervisory authority.
Because most memTITAN® data is stored locally on the user's own device, many rights can be exercised directly by viewing, changing or deleting local data.
For data actually processed by memTITAN®, such as website or relay metadata, requests can be sent to info@memtitan.ai.
In Switzerland, the competent authority is the Federal Data Protection and Information Commissioner (FDPIC). For persons in the EU, a competent supervisory authority in the relevant member state may also be contacted.
15. Security
memTITAN® is designed so personal memory data remains local and remote access through the official relay is end-to-end encrypted. Users should protect their computer and mobile device with a device PIN, password or biometric lock, keep pairing codes private, use memTITAN® only on trusted devices and reset connections if a device is lost or compromised.
16. Changes
memTITAN® is continuously improved. If relevant processing changes, especially around relay, mobile connection, platform builds, meeting actions or optional services, this Privacy Policy will be updated.
Last updated: 23 June 2026.