Privacy
This page describes what the Le Menu d'Amour app actually stores. It is written to match the code, not to make promises we cannot keep.
Who is responsible
- The operator named in the footer of this site is responsible for this website and for the data described on this page.
- Questions about privacy and requests about your data can be sent to [email protected].
What we store
- Your Google account identifier, used to create and secure your account.
- Your interface language, so the menu and cards match your choice.
- Which cards you have already seen, with the course level and the round they came from.
- The Android app is retired. Existing Google Play subscriptions are not cancelled automatically. Manage or cancel them at https://play.google.com/store/account/subscriptions. Contact [email protected] about historical purchases; retain your order reference.
- Your two guest names stay on your device and are never sent to us.
What we never store
- Your answers to the cards, and whether you actually performed an action.
- Why you skipped a card, or any note you write for yourself.
- We do not collect your contacts, photos or precise location. Advertising data is described separately below.
Why we process it
- To sign you in and keep your account secure.
- All four courses are free. Each round contains up to 50 cards. Google sign-in is required; no purchase is offered.
- To avoid repeating cards you have already seen.
- To provide, validate and refund purchases, and to keep the required purchase record.
- Our legal bases are the contract with you, our legal obligations to keep purchase records, and our legitimate interest in keeping the service secure.
How long we keep it
- Seen-card history is kept until you delete your account.
- A minimal purchase record is kept without any link to your account after deletion, because accounting, tax and dispute questions must remain answerable.
- Access and refresh tokens are stored in sessionStorage for this tab. Names, language and account-isolated pending seen-card events are stored in localStorage. Cards remain only in memory; refreshing ends the round.
- Purchase records that tax and accounting law requires us to keep are stored for the statutory retention period (commonly six to ten years, depending on the jurisdiction) and then deleted.
Who else is involved
- Google provides sign-in and, when enabled with consent, advertising. Google Play and RevenueCat may still process historical purchase records.
- These providers may process data outside your country, including in the United States, under their own privacy policies and transfer safeguards.
Your choices and rights
- You can ask for a copy of the data linked to your account.
- You can have inaccurate data corrected, and you can ask us to restrict or stop processing it.
- You can delete your account and the data linked to it at any time.
- You can ask for the data you provided in a portable format.
- If you are in the EEA or the UK, you also have the right to complain to your local data protection authority.
- Send requests to [email protected]; we answer within the period the law allows.
Deleting your account
- Delete your account using this site’s account deletion page, or request deletion at [email protected].
- Deletion revokes all sessions, removes your seen-card history and unlinks the purchase record.
- A minimal purchase audit is retained without a link to your account for the legally required retention period.
- Deleting your account does not cancel your Google Play subscription.
- If deletion fails, nothing is removed and you can safely try again.
Advertising and browser storage
- When enabled and after consent through the configured certified CMP, Google AdSense may use cookies, device identifiers and usage information to deliver and measure advertising. No ads are loaded without verified consent. You can refuse or withdraw through Ad privacy choices; playing remains available.
- Access and refresh tokens are stored in sessionStorage for this tab. Names, language and account-isolated pending seen-card events are stored in localStorage. Cards remain only in memory; refreshing ends the round.