Last updated: June 8, 2026
The data controller is Matteo Palmieri, based in Mondragone (CE), Italy ("the Controller").
For any privacy-related question you can contact the Controller at: legal@memuraapp.it
To use the app you choose between two authentication methods: Google Sign-In (available on iOS and Android) or Sign in with Apple (available on iOS only). The two methods are mutually exclusive: each user is associated with a single identity provider.
If you sign in with Google, the Controller receives the following data from Google:
sub claim)If you sign in with Apple, the Controller receives the following data from Apple:
sub claim, stable and app-specific)xxxx@privaterelay.appleid.com generated by Apple, which forwards mail to your real address without revealing itgetCredentialState methodIn addition, to comply with Apple's account-revocation requirement, the backend (Cloudflare Worker) receives server-to-server notifications from Apple when the user revokes consent to Memura from their Apple ID settings or deletes the Apple ID itself. Such notifications contain only your anonymous Apple identifier and a timestamp, no content. On the next launch the app detects the revocation, deletes all local data and returns you to the login screen.
None of the authentication data, regardless of the provider, is stored on Memura servers. The claims (sub, email, name) remain on your device to derive the encryption key and identify your cloud container; tokens are kept in memory or in the Keychain, never sent to backends operated by the Controller (the Cloudflare Worker verifies token signatures statelessly, without storing them).
The text, extracted entities and metadata of your memories are your personal content. A single principle applies to this data, regardless of the authentication provider:
iCloud.com.memuraapp.memura), accessible only through your Apple IDWhen you create a memory or ask a question inside the app, the text is temporarily transmitted — in unencrypted form — to the AI service for processing:
Requests do not hit the AI API directly from your device: they are routed through a stateless proxy implemented as a Cloudflare Worker (edge compute), which merely forwards the request to the AI provider and authenticates it by verifying your token signature (Google or Apple). The Worker does not persist or log content of memories or queries.
Regarding AI API keys, Memura adopts a hybrid Bring Your Own Key model:
The AI provider does not retain requests beyond the limits set out in its own terms of service. We encourage you to read the privacy notices of Google and Cloudflare.
Memura can access certain external sources on your device to enrich AI responses. All these integrations are optional, require your explicit consent through the operating system's native prompt and can be revoked at any time from the app or device settings.
A single principle applies to all of them: access is always on-demand. The content read is never saved in the Controller's databases or in your personal cloud: it stays at the source and is used only when needed to formulate a response, then discarded from memory.
If you sign in with Google and authorize the calendar OAuth scope, the app reads your Google Calendar events to provide context to the AI and, optionally, to create events from memories with a future date. Access is read/write limited to the primary calendar. When an AI feature requires calendar context, the relevant event details may be transmitted to the AI provider as described in section 3. You can revoke consent at myaccount.google.com/permissions.
On iOS, regardless of the authentication provider, the app can access your Apple Calendar and Reminders through the system framework EventKit. The framework is initialized only after your explicit consent through the iOS prompt. The data read stays on the device: it does not transit via the Worker, does not reach Memura servers, and is passed to the AI model only if relevant to your current request. You can revoke at any time from Settings → Privacy & Security → Calendars / Reminders → Memura.
If you authorize access to the operating system Contacts, the app uses names to disambiguate the people mentioned in your memories (e.g. distinguishing "Marco" the colleague from "Marco" the brother). Only the minimum necessary is read (first and last name); phone numbers, emails and other fields are never collected. Contacts are not duplicated in a Controller archive. You can revoke from Settings → Privacy & Security → Contacts → Memura (iOS) or from the application settings (Android).
On iOS, if you authorize access to the Photos library, the app can analyze the metadata and text present in images (e.g. text on signs, faces of the people involved, ticket dates) to enrich the context of a memory. The analysis is performed entirely on your device through Apple's Vision and Core ML frameworks: no image is sent to Memura servers, to the Cloudflare Worker or to the AI provider. You can revoke from Settings → Privacy & Security → Photos → Memura.
If you use voice input, the audio is transcribed by a speech-recognition model running entirely on your device. The audio is never saved or sent to external servers: only the transcribed text is stored as memory content. You can revoke microphone access from the operating system settings.
To improve the stability and quality of the app, the Controller uses Google LLC's Firebase services. Enabling each service requires your explicit consent (toggle in the app settings, off by default). Without consent, no diagnostics data is collected.
The data is processed by Google according to the Firebase Privacy Policy. Firebase Analytics and Crashlytics never have access to the text of your memories, to the content of your AI queries or to the images in your Photos library, nor to any data obtained through the Google APIs.
This section explicitly summarizes with whom Memura shares, transfers or discloses the data obtained through your Google Account — that is, the data received through Google Sign-In and the Google Drive and Google Calendar APIs.
Memura does not sell your Google data and does not use it for advertising purposes. The data obtained from the Google APIs is handled as follows:
sub identifier, email, name, photo): stays exclusively on your device. It is not transmitted to the Controller's servers or to any third party.drive.file scope): your memory files are encrypted on the device (AES-256-GCM) before upload and stored only in the app-reserved folder of your Google Drive. Memura never accesses them in clear text and does not share them with any third party.calendar.events scope): events are read on-demand. When you use an artificial-intelligence feature that requires your calendar context (e.g. "what do I have scheduled this week?"), the relevant event details (title, date, location, attendees) are transmitted to the AI provider to generate the response you requested. They are not retained or used for any other purpose.The third parties (sub-processors) that may process the data obtained through the Google APIs are exclusively the following:
Memura does not share, transfer or disclose the data obtained through the Google APIs to any other party, except as may be required by law or for security purposes. In particular, the diagnostics services (Firebase Analytics and Firebase Crashlytics) never receive data obtained through the Google APIs.
Memura's use and transfer of information received from the Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
In compliance with these requirements, Memura:
Memories remain in your personal cloud (Google Drive or CloudKit iCloud) until you delete them.
Diagnostics and analytics data (Firebase Analytics and Crashlytics, if enabled by the user) is retained by Google according to the service's default retention — typically up to 14 months for analytics events and up to 90 days for crash reports — in aggregated or pseudonymous form.
The AI API (Google Gemini) and the Cloudflare Worker proxy may process data in transit on servers in the United States and Europe. Firebase Analytics and Crashlytics process data on Google's globally distributed infrastructure. These transfers take place in compliance with the safeguards provided by the GDPR (Standard Contractual Clauses or United States adequacy decisions — EU-U.S. Data Privacy Framework).
The data saved in CloudKit remains within the iCloud infrastructure of your Apple ID, managed by Apple Inc. according to the Apple Privacy Policy, and is not replicated elsewhere by the Controller.
As a data subject you have the right to:
To exercise your rights, write to legal@memuraapp.it. You also have the right to lodge a complaint with the supervisory authority of your country (in Italy: Garante per la protezione dei dati personali).
Your memories are protected by AES-256-GCM encryption with a key derived on the device and wrapped per device: each installation keeps its own encrypted copy of the master key, stored in the iOS Keychain or Android Keystore. The local database is encrypted with SQLCipher. The app supports access with Face ID, Touch ID or PIN.
The content stored in the CloudKit Private Database is accessible exclusively to your Apple ID and, on the Controller's side, is always encrypted before upload: even Apple, while hosting the blob, cannot read the content. The same applies to data in the Google Drive Application Data Folder.
No user data — neither in clear text nor encrypted — transits or resides on servers directly operated by the Controller. The only server-side component under the Controller's control is the Cloudflare Worker proxy, which verifies token signatures and forwards AI requests statelessly, without logging content.
The app is not intended for persons under 13 years of age. The Controller does not knowingly collect data from minors. If you believe a minor has used the app, contact the Controller to have the data deleted.
Any material changes to this notice will be communicated through an in-app notice. The updated version will always be available at this address.