Mimmo Privacy Policy

Last updated: 13 November 2026
Data controller: Gianmaria Cacco
Address: Via Pietro Polato 21, 35027 Noventa Padovana (PD), Italy
VAT number: IT05149390287
Contact: ciao@heymimmo.com

This policy explains, under Articles 13 and 14 of Regulation (EU) 2016/679 (the "GDPR"), which personal data are processed when you use the Mimmo app for Android (published on Google Play by the developer HeyMimmo) and the heymimmo.com website, for what purposes, on what legal basis, for how long, and what rights you have.

1. In short

Mimmo shows no advertising and includes no analytics, tracking or crash-reporting tools; the only exception is the technical data that Google's scanner library sends to Google (§3.2).
The fruit and vegetable catalogue is bundled with the app: browsing it needs no connection.
You choose your country and zone yourself: the app does not use your location.
Favourites, shopping list and settings stay on your phone, unless you turn on the optional account to find them on your other devices.
Payment for Mimmo Premium is handled by Google Play: we never see or store your payment details.
On our server we mainly keep technical fingerprints (hashes) and, if you use the account, the data you sync; we do not keep your name or your e-mail address.
The heymimmo.com website uses no cookies and no trackers.

2. Data controller

The data controller is Gianmaria Cacco, a natural person who develops and publishes Mimmo under the name HeyMimmo, reachable at the address shown at the top of this page. For any privacy matter you can write to ciao@heymimmo.com.

No data protection officer (DPO) has been appointed, as one is not required for processing of this kind and scale (Art. 37 GDPR).

3. What data we process, why, and on what basis

3.1 Data that stay on your device only

The app stores in its private storage, on your phone: favourites and shopping list; the chosen country and zone; the language; notification preferences and time; onboarding state and usage statistics (for example consecutive months); the "barcode → product" associations you teach the app and the number of scans made that day; the Mimmo Premium status and, if you subscribe, the downloaded Premium content, kept encrypted; your invite code and invitation status; a cryptographic key created at random on first launch and kept in the Android Keystore, which cannot be extracted from the phone.

If you confirm the safety warnings of a Premium category, the app also keeps the record of the warnings you confirmed (which warning, which version, when, with which app version and in which language).

These data are not sent to us, except as described in §3.3–3.5. You delete them by uninstalling the app or via Android Settings → Apps → Mimmo → Storage → Clear data. If you have Android backup turned on, the system may include some preferences in your Google account backup: this is a feature run by Google under its own policy, which we cannot access.

3.2 Barcode scanner

The camera turns on only when you open the scanner and only after you grant permission. Frames are analysed on the phone with a library bundled in the app (Google ML Kit, which works offline): no image is saved or sent, and analysis stops as soon as the code is read or you leave the screen.

The Google ML Kit library that reads the codes on the phone sends Google, when you use the scanner, some technical operating data (phone model and system, app version, response times, error codes and a random installation identifier), which Google uses to maintain and improve the library. They contain no images and not the code read.

If the app does not already know the code, it sends Open Food Facts (a French non-profit association that runs an open food database) only the barcode number, to find out which product it is. As with any Internet connection, Open Food Facts also receives your phone's IP address and a technical header identifying the Mimmo app (not you). The number identifies a product on sale, not a person. Open Food Facts processes these data as an independent controller, under its own policy.

Legal basis: performance of the service you request by using the scanner (Art. 6(1)(b) GDPR).

3.3 Mimmo account (optional)

You can use Mimmo without an account. If you choose Continue with Google, sign-in goes through Firebase Authentication, a Google LLC service we use as a processor (Art. 28 GDPR) only to verify your identity. Firebase keeps on our behalf the e-mail address, name and picture of your Google account and a user identifier; we do not copy them to our server and do not use them to write to you, for statistics or for advertising.

On our server (api.heymimmo.com, on Cloudflare) we keep only:

the Firebase user identifier (not your name, not your e-mail), to recognise your account;
a fingerprint (hash) of the technical key of each linked phone and the date it was last used, to know which devices are yours;
favourites, shopping list, country and zone and language, with the time of each change, to keep them the same on all your devices;
the link between the account, your invite code and the rewards received, so you do not lose them when you change phone;
the fingerprints of the Premium purchase codes verified while you were signed in, to recognise Premium on your other devices;
the record of the safety warnings you confirmed (which warning, which version, when, with which app version and in which language), as long as you keep the account.

Legal basis: performance of the service you request by turning on the account (Art. 6(1)(b) GDPR).

When you tap Got it on the safety warnings of a Premium category, we record when and which version of the warnings you confirmed (with the app version and the language), on the phone and, if you have an account, also on our server with the account's data, to document that you were informed (legitimate interest, Art. 6(1)(f) GDPR); Delete account erases this record together with the rest.

In Settings, Sign out unlinks the phone from the account; Delete account immediately erases the account's data from our server and also deletes the user in Firebase (Google may ask you to confirm the sign-in); invite and Premium data linked to a single phone, which do not contain your account, follow the periods in §8. You can also ask for deletion without the app: see Delete your Mimmo account. A Premium subscription stays with Google Play and is cancelled there.

3.4 Mimmo Premium

Mimmo Premium is bought through Google Play billing. Payment, card or payment-method details, billing address and the Google account you buy with are processed by Google as an independent controller, under the Google Play Terms of Service and the Google privacy policy. We do not receive your name, your e-mail or your payment details.

To activate Premium and protect it from abuse, the app sends our server the purchase code provided by Google Play, a Play Integrity attestation (by which Google confirms that the app is the original one, installed from Google Play, on an unmodified device) and the phone's public key. The server checks the purchase with Google through the Google Play Developer API and keeps only: a fingerprint of the purchase code (the plain code is not kept), a fingerprint of the key of each device using the subscription with the dates of first and last use, and the state and expiry of the subscription. Google also sends us technical notices about the state of the subscription (renewal, cancellation, refund). The check is repeated periodically, normally once a day, and on every download of Premium content.

Device fingerprints also enforce the limit of 3 active devices per subscription and per account. If the check fails (for example on a rooted phone or an emulator), Premium cannot be activated on that device: this is an automatic technical anti-abuse check, not an assessment of you as a person; if you think it is a mistake, write to us.

Legal bases: performance of the subscription contract (Art. 6(1)(b) GDPR) and our legitimate interest in preventing fraud and unauthorised use of the service (Art. 6(1)(f) GDPR).

3.5 Invite a friend

The "Invite a friend" programme (a month of Premium for you and for the friend who starts using Mimmo with your code) is switched on only if you use it: when you tap "Invite" or when you accept a friend's gift. Only from that moment does the app register its installation with our server, with a Play Integrity attestation, and receive a random invite code; then, when you open the app, it tells the server on which days you used it, for the "at least 3 days of use" rule. If you do not use invites, none of these data is sent. The server keeps only:

a fingerprint (hash) of that installation's public key and its invite code;
the date of first launch and the number of different days the app was opened, for the "at least 3 days of use" rule;
which installation used which other installation's code, and when;
the gifted Premium days and when they end;
the number of attempts with non-existent codes, to stop people trying codes at random.

You send the invite link and code yourself, with the app you choose: we do not see to whom or the text of the message. If your friend installs Mimmo from that link, Google Play hands the code to the app (Play Install Referrer): the app reads it once and looks at it only on the phone (if it contains no Mimmo code it is not kept), then asks your friend whether they want the gift; the code is sent to the server only if they say yes. If you already subscribe, the server may ask Google Play to move your next renewal back by 30 days, using the subscription already linked to your phone, without sending Google any other data.

Legal basis: performance of the rules of the programme you chose to join (Art. 6(1)(b) GDPR) and our legitimate interest in preventing its abuse (Art. 6(1)(f) GDPR). You can object at any time (§10).

3.6 Shared shopping lists

When you share the list, the products (code and name, nothing else) are written inside the link, after the "#" sign. Browsers never send this part to servers: the list does not pass through our servers and is not stored anywhere. Someone without Mimmo who opens the link sees a heymimmo.com page that reads the list in their own browser, with no cookies and no analytics. Anyone who has the link can see the list: share it only with people you choose.

3.7 Website, server and connection data

The heymimmo.com website and our server are hosted by Cloudflare, Inc., which acts as our processor. To deliver pages and responses, Cloudflare processes the technical data of each connection, including the IP address, the type of browser or app and the address requested. We use the IP address only to limit the number of requests and to protect the service from abuse and attacks; we do not write it to our database. The server's technical logs contain no IP addresses, purchase codes, keys or e-mail addresses and are kept by Cloudflare for at most 7 days. If Mimmo is not yet available in your country and you tap "Request Mimmo in my country", the request is anonymous: we store only the country code, the date and the number of requests; to count only one per connection per day we keep an encrypted fingerprint of the IP address for at most 26 hours, after which it deletes itself.

Legal basis: our legitimate interest in providing the website and the service securely (Art. 6(1)(f) GDPR).

3.8 When you write to us

If you write to ciao@heymimmo.com, we process your e-mail address and what you tell us only to reply and handle your request.

Legal basis: replying to your request (Art. 6(1)(b) GDPR) and, to keep proof that we followed up a privacy request, our legitimate interest (Art. 6(1)(f) GDPR).

3.9 Notifications and crash reports

Notifications are generated locally on the phone from your favourites and settings: there is no system of notifications sent by a server. The app includes no crash-reporting tools; if you agreed to share usage data with Google, Android may send Google technical reports (Android Vitals), which Google processes under its own policy.

3.10 Legal obligations and defence of rights

We may process the data described above when necessary to comply with a legal obligation or an order of an authority (Art. 6(1)(c) GDPR) or to establish, exercise or defend legal claims (Art. 6(1)(f) GDPR).

4. What we do not do

We do not collect your location, contacts, photos, microphone or files.
We use no advertising identifiers, profiling cookies or cross-app and cross-site tracking.
We do not build profiles, and we do not sell or hand over data to third parties for marketing.
We take no decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR); the technical anti-abuse checks in §3.4 and §3.5 only decide whether a benefit (Premium, a gift) can be granted to a device.

5. Android permissions

Internet: for Open Food Facts, Google Play, our server and the optional account.
Notifications (Android 13 and later): to deliver the alerts you turned on. Optional.
Camera: only to read barcodes, requested when you use it. Optional.

If you deny an optional permission, the rest of the app still works.

6. Who we share data with

Data are processed by the controller and by the following parties, only as far as necessary:

Cloudflare, Inc. (hosting of the website and the server, network, database), as processor;
Google LLC / Google Ireland Limited for Firebase Authentication, as processor, under the Firebase data processing terms;
Google Cloud (Google Cloud Pub/Sub), as processor, to receive Google Play's notices about the state of subscriptions;
Google for Google Play, billing, Play Integrity, the Install Referrer and the Google Play Developer API, which processes the data of its own services as an independent controller;
Google for the scanner's Google ML Kit library, which receives the technical data described in §3.2 and uses them as an independent controller to maintain and improve the library;
Open Food Facts (France), as an independent controller, for scanner lookups;
public authorities, only when required by law.

We do not sell personal data and do not share them with anyone else.

7. Transfers outside the European Union

Google and Cloudflare are based in the United States and may process data outside the European Economic Area as well. These transfers rely on the European Commission's adequacy decision of 10 July 2023 on the EU-U.S. Data Privacy Framework, which both companies have joined, and in any case on the standard contractual clauses approved by the Commission (Articles 45 and 46 GDPR) included in their data processing terms. Open Food Facts processes data in the European Union.

8. How long we keep data

Data on the device: until you uninstall the app or clear its data; Premium content is deleted when Premium ends.
Account: as long as you keep the account. Accounts unused for 2 years are deleted automatically from our server; in that case we also delete the identity in Firebase within the following 3 months. Items you delete (for example a product removed from the list) remain as a mere deletion marker for 180 days, so that the deletion reaches all your devices.
Deleted accounts: we keep only an encrypted fingerprint of the account identifier, which contains neither name nor e-mail, for 24 months, to prevent the same account from receiving invite rewards again.
Premium: for the duration of the subscription; Premium data are deleted 24 months after the subscription ends (expiry, cancellation or refund), the time needed to handle renewals, refunds and disputes.
Invite a friend: data are deleted when the app has not been opened for 400 days (about 13 months), and the data of an invitation in any case 400 days after the invitation.
Technical logs and connection data at Cloudflare: at most 7 days.
E-mails you send us: for the time needed to reply and at most 24 months from the last message, unless they are needed longer to defend a legal claim.

9. Security

We take technical and organisational measures appropriate to the risk (Art. 32 GDPR): encrypted connections (HTTPS); device keys kept in the Android Keystore; fingerprints (hashes) instead of purchase codes and keys; no personal data in the server logs; server secrets kept only at Cloudflare; access to the systems restricted to the controller. No system is 100% secure: should a personal data breach occur, we will act as required by Articles 33 and 34 GDPR.

10. Your rights

Within the limits of the GDPR you have the right to:

access your data and receive a copy (Art. 15);
have them rectified (Art. 16) or erased (Art. 17);
request restriction of processing (Art. 18);
receive the data you provided to us in a structured, machine-readable format (Art. 20);
object at any time, on grounds relating to your particular situation, to processing based on legitimate interest (Art. 21).

You can do many things yourself in the app: Delete account, Sign out, Clear data, uninstalling. For anything else write to ciao@heymimmo.com. On the server we keep almost only technical fingerprints that, on their own, do not let us know who you are: to find your data we may ask you to sign in to the account from the app or to give us your invite code, shown in Settings (Art. 11 GDPR). We reply within one month, extendable in the cases set out in Art. 12 GDPR.

You also have the right to lodge a complaint with the Italian supervisory authority, the Garante per la protezione dei dati personali, or with the supervisory authority of the country where you live or work (Art. 77 GDPR), and to seek a judicial remedy (Art. 79 GDPR).

11. Children

Mimmo is suitable for all ages and can be used without an account. The optional account and the purchase of Premium are intended for people aged at least 14, or the higher age set by the law of their country for using online services on their own (for example 16 in Germany and the Netherlands, 15 in France); below that age the consent of the holder of parental responsibility is required. Google's rules on children's accounts and purchases also apply. If we find out that we have processed a child's data without the necessary conditions, we delete them; you can tell us at ciao@heymimmo.com.

12. Users outside the European Union

Mimmo is also available in countries outside the European Union, such as Switzerland, the United Kingdom, the United States and Canada. We apply the same rules and safeguards described in this policy to all users, in addition to the rights the law of your country gives you.

13. Changes to this policy

We may update this policy, for example if we add features or change providers. The version in force is always the one published here, with the date at the top. If a change materially alters how we process your data, we will tell you in the app before it applies.

14. Contact

Data controller: Gianmaria Cacco, Via Pietro Polato 21, 35027 Noventa Padovana (PD), Italy. E-mail: ciao@heymimmo.com.

The conditions of use of the app are in the Terms of use.