Privacy Policy
The short version: we collect what running MERCI! requires and do not sell personal data. Hosting, access and retention are explained below.
1. What we collect
To run the Service we process: your email address and display name; your password in hashed form, authentication details for the passkeys you register, and two-factor authentication settings; the files you store and their metadata (names, sizes, types, folder structure, and the capture date and location recorded in photos and videos); the share links you create; and activity and connection logs (sign-ins, sign-outs, uploads, deletions, shares and account changes), with the request records described below. Files are transferred over HTTPS and stored on our infrastructure in Paris. They are not encrypted on your device: the service operator can read them in order to operate the Service, for example to generate previews. We process no payment data, since paid plans are not on sale.
If you choose to sign in with Google, Google sends us, each time you sign in with it or link it, after you agree on its own screen: the identifier of your Google account, your email address, whether Google has verified it, your name, with your first and last names, a link to your profile picture and, for a Google Workspace account, its domain. We use the domain only to check that Google vouches for your address, and the name only when your account is created, where it becomes the display name of your account, which you can change. We keep the identifier of your Google account for as long as Google stays linked to your account. We keep neither the link to your profile picture, nor the domain, nor any token giving access to your Google account, and we ask for access to no other data of that account, such as your contacts, emails, files or photos.
On the iPhone, if you choose to sign in with Apple, Apple sends us, each time you sign in with Apple or link it, after you agree in its own window: the identifier of your Apple account for MERCI!; your email address, which is your real address or a relay address created by Apple if you choose “Hide My Email”; whether Apple has verified it and whether or not it is a relay address; and, the first time only, your first and last names. We use the address to sign you in or create your account, and these two indications to check that Apple vouches for this address (a relay address or an iCloud address). We use the name only when your account is created, where it becomes the display name, which you can change; without a name, the account is created without one. If an attempt fails, the app keeps this name in memory, without writing it on the iPhone, until a successful sign-in or until the app is closed. We keep the identifier of your Apple account for as long as Apple stays linked to your account, as well as a token issued by Apple, encrypted, which is used only to withdraw your authorisation at Apple when Apple is unlinked or your account is deleted. We keep neither the identity token, nor the authorisation code, nor any access token, nor the address of your Apple account when it differs from that of your account, and we ask Apple only for your name and your address.
On the iPhone, signing in with Google goes through Google’s sign-in component, built into the app. It acts only when you tap “Continue with Google” or, in Settings → Security, “Link my Google account”, and opens Google’s page in a system window. According to Google’s declaration, this component processes, linked to your account and without advertising tracking: for sign-in, your name, your email address, your phone number and an approximate location; for sign-in and for Google’s statistics, the identifier of your account and other data; for Google’s statistics only, a device identifier and usage data. These data go to Google, not to MERCI!. Because we chose to build this component into the app, we are responsible together with Google for this collection and for this transmission to Google, made in the app when you tap one of these buttons; Google alone is responsible for what it does with them afterwards. Google also uses technical information (the version of the component, the device’s operating system) for its own statistics, under its sole responsibility and according to its privacy policy. This information contains neither your photos nor your files. We accept this in our legitimate interest in offering you sign-in with Google. To avoid it, sign in by email or with Apple, without linking your Google account. After each attempt, the app erases from the component the Google account used. What Google then sends to our servers, and what we keep of it, is described above.
For every request made to the Service, we keep a technical record (a request record) with: the date and time; the operation requested and its result; the identifiers of your account and session; the channel used (website, Android app, iOS app, administration, direct call to the interface, or background job); the version and build of the app; the operating system and its version; the device model; the browser and its version; the screen size and pixel density; the language and time zone of the device; the network type; your full IP address; the approximate country, region and city deduced from that address; the network operator associated with the address; and the HTTP and TLS protocol versions. We collect the same information for every request, with no setting to change it. This information is not used for advertising, for audience measurement, or to create an identifier of your device. These records are not analytics: we do not measure which pages of the website or screens of the apps you visit, and we run no tracking scripts.
Each session you open keeps the channel, the device, the app or browser, the full IP address and the approximate country of the sign-in, so that you can recognise it in Settings → Activity and revoke it.
The Android app, distributed by Google on Google Play, asks only for the permissions it uses: access to your photos and videos (all of them, or only those you select), to upload them and, if you turn on automatic backup, to back them up; access to the location recorded in your photos, so that the originals you upload keep it; notifications, to tell you about uploads and backups, and for the notifications described below; biometric unlock, only if you choose to lock the app (your fingerprint or face is checked by your device and never reaches us); and network access, including whether you are on Wi-Fi or mobile data. Automatic backup is off until you turn it on. Once it is on, the app sends the new photos and videos of your device to your account, also in the background when the app is closed; background runs take place only while the device is charging, with enough battery and storage, and only on Wi-Fi unless you allow mobile data. In the app’s settings you can turn it off, allow mobile data or leave videos out. The app reads nothing else on your device, except a file you share with it. It contains no advertising component, and MERCI! does no audience measurement in it; for notifications, it contains Google’s Firebase Cloud Messaging component, without Google Analytics, described below.
The iPhone app, distributed by Apple on the App Store, gives access to the same Service. It asks only for the permissions it uses: access to your photos and videos, all of them or only those you select, which you can change at any time in the iPhone’s Settings, to upload them and, if you turn on automatic backup, to back them up; notifications, described below; and Face ID or Touch ID, only if you choose to lock the app (your face or fingerprint is checked by the iPhone and never reaches us: the app receives only a success or a failure). It never asks for the iPhone’s location: only the coordinates already recorded in your photos and videos travel with their copy. Automatic backup is off until you turn it on. Once it is on, the app sends to your account the new photos and videos you have allowed it to read, when you open it and in the background when iOS allows, while the iPhone is charging and connected to a network; only on Wi-Fi if you choose. The app never changes your photo library and reads nothing else on the iPhone, except a file you choose in the Files app, of which it sends a copy. It contains no advertising component, and MERCI! does no audience measurement in it; the only component of another service is Google’s, for signing in with Google, which collects the data described above for Google’s statistics.
So that the same photo is never sent twice, each photo or video backed up by an app is identified to our servers by a fingerprint (SHA-256) of its reference on the phone or, on the iPhone, of its iCloud identifier when it has one; we keep it after the file is deleted, for the period stated in section 5, so as not to send again a photo you have deleted. The apps keep your session and working files on the phone (copies being uploaded, previews, lists of files, the upload log). On Android, the session is encrypted by the phone’s key store, and these data are excluded from Android’s backup and erased with the app. On the iPhone, the session is kept in the iOS keychain, tied to this iPhone and never copied to another device; iOS may keep it after the app is deleted: sign out first, or revoke it in Settings → Activity on the website, or Settings → Security in the app. The working files are excluded from iCloud backup, and your app preferences (language, lock, backup) stay in its settings. If you create a passkey, its secret part stays in the manager you choose (iCloud Keychain, Google Password Manager or another): we receive only its public key.
When you report a shared link or a media in a shared album, we keep your report: the reason, the details you write, your account if you are signed in and, for a link, the name and email address you choose to give. We use them to handle the report and, if you gave an email address, to confirm receipt and tell you our decision. This processing rests on our legitimate interest in protecting the Service and its users, and on the obligations of hosting providers.
In a shared album, every member sees, for each member, their name, their email address (including an Apple relay address), their role, the date they joined and who invited them, and the owner sees the addresses they have invited. For each photo or video, members see who added it, its name, its date and its size, and can download the original with the information it contains, including the place recorded in it. In the iPhone or Android app, you can block another member of a shared album, or the author of a photo or video in a shared album you belong to. We then keep whom you blocked, and the date. You no longer see the photos and videos this person has added or will add to shared albums, including yours. They leave the albums you own, where what they added stays visible to the other members, and your invitations to them that are still open are revoked. Their invitations are no longer sent to you by email, even to a variant of your address, an invitation from them you already received can no longer be accepted, and you receive no notification about what they do. They are not told about the block, and we never tell them who blocked them. You cannot block anyone on the website: it shows the list of the people you have blocked, and you can unblock them there.
Once you are signed in, and if notifications are allowed on your phone, the iPhone and Android apps send you notifications, in three categories. “Shared albums”: an invitation to an album, your removal from an album, someone joining your album, new photos or videos in an album, grouped into a single notification, the deletion of an album you are a member of, and a change of your role in an album. “Storage space”: your storage is 90% full, then completely full. “Security”: a sign-in to your account from a new device, sent to your other devices. A notification contains as little as possible: the name of the album, the name of the person concerned, the number of photos and videos added or your new role, or, for a sign-in, the type of device (for example “an iPhone”); what is needed to open the album or the invitation in the app; and technical identifiers used to group or replace notifications on your phone (see section 4). It never contains a photo, a video, a place or an IP address. We write it in the language chosen in the app. We send no advertising or commercial message by notification. You never receive a notification about what you do yourself in an album, or about what a person you have blocked does; the sign-in alert is not shown on the device that has just signed in.
To send them to you, we keep, for each installation of the app signed in to your account: an installation identifier drawn at random by the app, the notification token that Apple or Google issues to it, the system (iOS or Android), for the iPhone, Apple’s environment (production or test), the language and version of the app, and the dates of registration and update. This token is tied to the app’s session, and the app requests it only once you are signed in and notifications are allowed on your phone. On the iPhone and on Android 13 or later, the phone first asks for your permission. On Android 12 or earlier, the system allows notifications by default, without asking you anything: the app registers as soon as you are signed in, unless you have turned notifications off in the phone’s settings. On the iPhone, the token comes directly from iOS. On Android, Google’s Firebase Cloud Messaging component, built into the app, obtains it from Google, creating for this purpose an installation identifier specific to Firebase. The three categories are on by default. You can turn each one off in Settings → Notifications in the app, or Settings → Profile on the website, and refuse or withdraw permission at any time in your phone’s settings. We also keep on your account the last storage threshold we warned you about (90% or full), so as not to repeat it. The sign-in alert email keeps arriving even if you turn off the “Security” category.
In the administration interface, viewing or downloading file content requires a passkey check bound to the requested action, a reason and confirmation of the target. These accesses are logged; access links expire after five minutes. The activity history shown in your account does not include every internal administrative access, including views of archived email content.
Each time an administrator opens a record that holds personal data, lists or searches accounts, sessions or logs, or opens the audit log, the access is recorded in the audit log with the administrator’s identifier and the time. Search text is recorded only as a keyed fingerprint, never in clear.
2. What we never collect
No ad profiles. No selling data. No training of models on your files. No advertising tracking in our apps.
We do not build advertising profiles, sell or rent personal data, scan your files for marketing purposes, or use your Content for unrelated purposes.
We do not create an identifier or fingerprint of your device from its characteristics. The malware scan of your files described in section 4 is not used for marketing, profiling or any other purpose. The identifiers used for notifications (section 1) are drawn at random or issued by Apple or Google, never computed from the characteristics of your device.
3. How we use data
To verify the content of emails MERCI! has addressed to you and diagnose support requests or incidents, we keep an encrypted copy of the recipient, subject and exact content prepared for sending, including the values and links it contains. This processing is based on the operator’s legitimate interest in following up communications and operating the service securely. You may object on grounds relating to your particular situation through the privacy contact given in this policy.
We use personal data to operate and secure the Service (legal basis: contract), to prevent abuse and fraud and to keep the activity and connection logs that let you and us investigate what happened on an account (legitimate interest and the legal obligations of hosting providers), to send service emails such as sign-in links and codes, address verification and sign-in alerts (contract), to answer contact-form messages (legitimate interest), and to manage your newsletter subscription when you submit your address (consent; subscriptions require email confirmation, and you can unsubscribe using the link provided by email). Signing in with Google is used only to sign you in to your account; it rests on the contract. Signing in with Apple is used only to sign you in to your account; it rests on the contract. Keeping Apple’s token while Apple is linked to your account also rests on the contract. Once Apple is unlinked or your account deleted, keeping this token in the withdrawal queue, then using it to withdraw your authorisation at Apple, also rests on the contract: it completes the unlinking or the deletion you asked for, as Apple’s rules require of us.
On the iPhone, the collection made by Google’s sign-in component when you tap “Continue with Google” or “Link my Google account” rests on the contract, for what is used to sign you in; it takes place only on that tap. What Google’s sign-in component on the iPhone and the Firebase Cloud Messaging component on Android send to Google for its own statistics rests on our legitimate interest in offering you sign-in with Google and notifications; you can avoid it as described in sections 1 and 4. Blocking a member rests on the contract and on our legitimate interest in the safety of members. Notifications rest on the contract: they are part of the service you use, and you can turn off each category or refuse them on your phone at any time. Reading and keeping the notification token on your phone is strictly necessary to send them to you, and therefore requires no other consent (Article 82 of the French Data Protection Act). Likewise, what the apps keep on your phone or read there (your session, working files, your preferences, the identifier of each backed-up photo) is strictly necessary for the service you use, and requires no other consent.
We keep request records and audit logs to investigate security incidents and abuse, to establish who performed an action on an account or in the administration, and to answer support requests. This processing rests on our legitimate interest in the security of the Service and in the accountability of administrative actions (GDPR Articles 6(1)(f) and 5(2)). You may object on grounds relating to your particular situation; where we demonstrate compelling grounds for security, the processing may continue.
4. Sharing & processors
Amazon Web Services is our hosting processor. The API, database, file storage and account email delivery run in eu-west-3 (Paris, France). CloudFront distributes this website through locations that are not limited to France. Native authentication stores passwords in hashed form; on the website, it uses secure HttpOnly session cookies, and in the apps, a session kept on the phone (section 1). You can review and revoke your sessions in Settings → Activity. No payment provider is involved, since paid plans are not on sale. Email privacy@merci.photos to request the current processor categories and processing locations. We disclose data to authorities when legally required.
The iPhone app is distributed by Apple on the App Store, and the Android app by Google on Google Play. Apple and Google process the data of the download and of your account with them, under their own responsibility, according to their privacy rules. They show us statistics on installations and, if you have agreed to share this information with developers, crash reports, without your name or your address.
When you choose to sign in with Google, you identify yourself to Google LLC, which processes the data of your Google account as a separate controller, under its own privacy rules, including outside the European Union. Google therefore learns that you are signing in to MERCI!. Our servers, in Paris, exchange with Google's servers only what is needed to verify the sign-in (the code or the token Google issued); we send Google no other data, and Google is not our processor. You can unlink Google in Settings → Security, and remove the access of MERCI! from the third-party apps page of your Google account.
When you choose to sign in with Apple, you identify yourself to Apple, which processes the data of your Apple account as a separate controller, under its own privacy rules, including outside the European Union. Apple therefore learns that you are signing in to MERCI!. For this sign-in, our servers, in Paris, exchange with Apple’s servers only the authorisation code, to obtain the token described in section 1, then this token, to withdraw your authorisation; we send Apple no other data for this sign-in, and Apple is not our processor for it. Notifications on the iPhone are described below.
If your account uses an Apple relay address, our emails (codes, links, alerts, invitations) go through Apple’s relay service, which forwards them to your real address. If you turn off this relay at Apple, you no longer receive our emails, including sign-in codes.
To send you the notifications described in section 1, our servers transmit to Apple’s notification service (Apple Push Notification service) for the iPhone, and to Google’s Firebase Cloud Messaging for Android: the notification token, the content of the notification, the link it opens, including the code of an invitation for the person invited, and technical identifiers (of the album, of the invitation, of the session that has just signed in or of the person joining an album), used to group or replace notifications on your phone. Google routes them on our behalf, as a processor; Apple routes them under its own terms, as a provider that delivers notifications. Both see these data in order to deliver the notification and process them outside the European Union. On Android, the app’s Firebase Cloud Messaging component also sends Google the Firebase installation identifier, to obtain the token and keep it up to date, as well as the version of the app and technical information about the component and the phone. Google also uses this technical information (the version of the component, the device’s operating system, brand and model, the store that installed the app) for its own statistics, under its sole responsibility and according to its privacy policy. It contains neither your photos nor your files. We accept this in our legitimate interest in offering you notifications. To avoid it, refuse notifications when the phone asks you, or turn them off in its settings before you sign in: the app then requests no token from Google. If you refuse them later, the app requests no new token, and has Google delete its token when you sign out. Turning off the categories in the app is not enough. Our Firebase project does not use Google Analytics.
Emails sent to our contact addresses (such as support@merci.photos and privacy@merci.photos) are received by Amazon Web Services (Amazon SES, Paris region, France) and forwarded to our mailbox hosted by Google (Gmail), which may process them outside the European Union. Our replies are sent from that mailbox. Apple’s relay may refuse these replies: if you signed in with Apple and hid your address, write to us from an address at which we can answer you.
When our providers process data for us outside the European Union, these transfers rest on the European Commission’s adequacy decision for companies that adhere to the EU–U.S. Data Privacy Framework, and on the Commission’s standard contractual clauses provided for in their terms. This is the case for Amazon Web Services, whose delivery network (CloudFront) serves the website and your files from locations that are also outside the European Union, and for Google LLC, for our mailbox and Android notifications. For iPhone notifications, Apple transfers these data under its own safeguards, described in its privacy rules. You can obtain a copy of these clauses by writing to privacy@merci.photos.
Each original file you upload is checked for malware by an automated scan run by Amazon Web Services (Amazon GuardDuty Malware Protection, Paris region). Until the scan is complete, the original cannot be downloaded or shared. A file found to contain malware is blocked: it can no longer be downloaded or shared, the event appears in your activity history, and you can delete the file. No person reads your files for this check. Its result serves no other purpose, and no scan detects every threat. Request records are stored in Amazon CloudWatch Logs in the Paris region.
5. Retention
We keep an encrypted copy of the content prepared for our outgoing emails: recipient, subject, HTML and text, without redaction, including any codes and links they contain. Authorized administrators can view this copy after a passkey check and providing a reason; each view is logged. The sending log and its copy become eligible for deletion after 90 days during periodic cleanup. Account purging deletes linked email bodies earlier, while the technical log follows its own retention deadline. No body copy is retained for the final account-deletion notification. Older emails without an archive are not reconstructed.
Account data is kept while the account is active. Items moved to the trash remain available for 30 days unless you empty it sooner. You can request account deletion from Settings after a recent sign-in. For an account that has completed setup, deletion is scheduled seven days after the request and can be cancelled before that date. This deadline makes the account eligible for background purging; completion is not guaranteed at an exact time. An unfinished registration can be scheduled without this waiting period. Once the account is purged, its files, folders, albums, share links and profile are removed from the Service.
Removal from the Service and deletion of stored file copies are separate steps. Storage deletion runs in the background after active upload links have expired. Previous versions held by our storage provider become eligible for automatic removal seven days after they become noncurrent; removal is not guaranteed at an exact time.
Deleting data from the active database does not immediately remove it from database backups. Automatic backups for point-in-time restoration are retained for seven days. A separate protected daily backup is retained for fourteen days. Manual snapshots may be kept for restoration needs and are subject to review, without a fixed automatic expiry. Access to these copies is restricted. If a backup is restored, applicable erasure requests must be reapplied before the service is reopened.
Activity history has a retention threshold of 365 days. Security audit logs in the database have a thirteen-month threshold and are deleted by complete calendar months during periodic cleanup, so some records can remain longer. A separate daily export of security audit events and their integrity records is stored in Paris, protected against deletion for 400 days and eligible for automatic removal after 401 days. These records can remain after account deletion. Identifiers, IP addresses and connection information remain personal data even when no profile is associated with them. Access to the audit archive is restricted to security and incident investigation. Acceptance records become eligible for deletion after five years; their IP addresses and user-agent information become eligible for removal after thirteen months. Periodic cleanup applies these thresholds, so removal is not guaranteed at an exact time.
Contact-form messages become eligible for deletion after 365 days. Unconfirmed newsletter sign-ups become eligible after 30 days. Confirmed subscriptions remain active until you unsubscribe; unsubscribed entries become eligible 365 days after unsubscribing. Periodic cleanup applies these thresholds. Deleting an account does not automatically unsubscribe its email address or erase contact messages. A broader erasure request can be sent to the privacy contact.
A raw copy of each email received on a contact address is held in encrypted storage in Paris and becomes eligible for automatic deletion after 30 days. Storage cleanup is asynchronous, so deletion is not guaranteed at an exact time. The forwarded message stays in our mailbox as long as needed to handle the request.
Request records are kept for one year. Administrators’ views of personal data are kept in the audit log for thirteen months. The technical logs of background jobs, database migrations, mail forwarding and the API gateway are kept for thirty days. Periodic cleanup applies these thresholds, so removal is not guaranteed at an exact time.
A session is deleted as soon as you sign out or revoke it; an expired session is deleted 30 days after it expires. Reports are kept for 365 days after the decision on them. Periodic cleanup applies these thresholds, so removal is not guaranteed at an exact time. The identifier of your Google account is deleted as soon as you unlink Google, or with your account when it is purged. Only a fingerprint of it, computed with a secret key, remains in the security audit logs, for the periods stated above (thirteen months in the database, 401 days for the daily export), including after your account is deleted. The identifier of your Apple account and Apple’s token are deleted from your account as soon as you unlink Apple, or with your account when it is purged. The encrypted token, the identifier of your Apple account and the internal identifiers of your account then go into a withdrawal queue, until Apple accepts our request to withdraw your authorisation; if it fails, we try again at growing intervals, at most one day apart, until Apple accepts the request. If you link this Apple account again before this withdrawal, the request is dropped. Only a fingerprint of the identifier of your Apple account, computed with a secret key, remains in the security audit logs, for the periods stated above.
The fingerprint that identifies a photo or video backed up by an app is kept for as long as the file exists, then for 365 days after its deletion. A block is kept until you unblock the person, or until your account or theirs is purged. A removal from an album caused by a block remains after you unblock. The block, the unblock and the removals it causes are recorded in the security audit logs, for the periods stated above, including after the unblock or the deletion of an account. A notification token is deleted when you sign out of the app, when its session is revoked or deleted, with your account when it is purged, when Apple or Google tell us it is no longer in use, or when it is registered for another account on the same phone; the app also deletes it the next time it is opened if you have withdrawn permission for notifications. A notification that Apple or Google cannot deliver is dropped after 24 hours. Each sending, each registration or deletion of a device and each change to your notification settings is recorded in the security audit logs, without the token or the text of the notification, for the periods stated above.
6. Your rights
Settings lets you update profile information, review your activity history, request a structured account-data export and request or cancel account deletion. For a broader access request, portability, restriction, objection or another privacy request, email privacy@merci.photos. EU/EEA residents have the full set of GDPR rights, detailed on our GDPR page, including the right to complain to your supervisory authority (ours is the French CNIL).
On a privacy request, we provide the audit entries and request records that concern your account, except what would reveal another person’s choices, such as a block.
You can unlink Apple in Settings → Security, on the iPhone or on the website. Removing MERCI! from the settings of your Apple account does not unlink Apple from your account: unlink it in Settings → Security as well. You unblock a person in Settings → Privacy, in the app or on the website. You choose notifications in Settings → Notifications in the app, or Settings → Profile on the website, and can refuse or withdraw them in your phone’s settings. The export of your data contains the blocks you made, your notification settings and the devices registered for notifications, without their token.
You can give us directives on the retention, erasure and communication of your personal data after your death, and name a person to carry them out (Article 85 of the French Data Protection Act). Send them to privacy@merci.photos from the email address of your account; you can change or withdraw them at any time. Without directives, your heirs can ask us to take your death into account, for example by closing the account, and, as far as needed to settle the estate, to communicate the data useful to it, including family memories such as photos.
7. Children
MERCI! isn't directed at children under 15 in France, or under 13 elsewhere (or the higher age local law sets in your country). A parent or guardian must provide any consent required by local law and supervise the account. If we learn we hold data of a child below the threshold without consent, we delete it.
8. Privacy contact
Data controller: EURL ZENATI (operating the Service under the trade name “MERCI!”), a French single-member limited liability company registered with the Paris Trade & Companies Register under no. 981 830 227, registered office: 60 rue François 1er, 75008 Paris, France. Privacy requests can be sent to privacy@merci.photos.







