Privacy Policy
Aloumi — Last updated: October 5, 2026
This Privacy Policy explains what data Aloumi ("the app", "we") collects, why, on what legal basis, how long it is kept, and how you can exercise your rights. Aloumi is an AI-powered recipe app for Android, published by JEYLAB (a French SARL, Paris Trade Register 943 632 588, registered office: 6 rue Émile Dubois, 75014 Paris), the "data controller" within the meaning of the GDPR (contact below, full details in the legal notice).
1. Data we collect and why
| Data | When | Purpose | Legal basis (GDPR art. 6) |
|---|---|---|---|
| Google account information (email address, display name) | When you sign in with Google (required to use the app) | Authentication, syncing your data across your devices | Performance of the contract |
| Your content: recipes, shopping lists, food finds, meal plans, kitchen equipment settings | As you use the app | Storing and syncing your data (Google Firebase Firestore) | Performance of the contract |
| Images (recipe and address illustrations generated by AI) | When an image is generated | Displaying your content (Google Firebase Storage) | Performance of the contract |
| Messages, photos and documents you submit to AI features | When you use the AI chef, recipe import or cooking assistant | Sent to the Google Gemini API to generate the response, through our server function which relays them without storing them. Chat history is stored locally on your device only — it is never uploaded to our servers. Not used to build a profile of you. | Performance of the contract |
| Photos and documents of a recipe to import | When you import a recipe from photos or a document | Temporarily uploaded to a private storage area specific to your account (Google Firebase Storage), where only our server reads them back to extract the recipe with the Gemini API. They are deleted as soon as the recipe has reached you, and in any case automatically no later than about two days after upload. | Performance of the contract |
| Your device's notification identifier (Firebase Cloud Messaging token) | When you sign in, and with each recipe import | Sending you the app's notifications: sharing requests and their approvals, and the "your recipe is ready" notice at the end of an import, sent only to the device that started it and containing the recipe title. Notifications are only shown if you allow them on your device. | Performance of the contract |
| Public content of a social media post (caption or description, and where applicable the video, of an Instagram, TikTok or YouTube link you submit) | When you import a recipe from a social media link | The post's content (caption and, where applicable, video) is fetched by a server-side service relying on an open-source tool, without signing in to any social media account, and sent to the Gemini API to extract the recipe. Any video transits temporarily through our server and is deleted immediately after analysis: no platform content is retained; only the resulting structured recipe is saved to your account. | Performance of the contract |
| AI usage counters (number of requests per day/month, token counts, model used) | When you use AI features | Abuse prevention, fair-use quotas, cost monitoring | Legitimate interest (protecting the service against abuse) |
| Anti-fraud tokens: two pseudonymized hashes (irreversible hashing with a secret key), one derived from your email address, the other from the identifier of your Google account | Stored when you start your free trial (and only then). When your account is created, they are only computed to check whether the trial has already been used, without being stored. | Preventing abuse of the free trial offer (deleting then recreating an account to claim it again). The second hash remains effective even if the email address of your Google account changes. For the same reason, the free trial is only granted if the email address of your Google account has been verified by Google. Under the GDPR, these pseudonymized hashes remain personal data. They cannot be used to recover your email address or the identifier of your Google account: only comparing them with that same data, using the secret key we hold, makes it possible to establish that the trial has already been used. They are never used for any other purpose. | Legitimate interest (fraud prevention) |
| Crash and stability data (Firebase Crashlytics: device model, OS version, crash stack traces) | If the app crashes or malfunctions | Diagnosing and fixing bugs | Legitimate interest (security and stability of the service) |
| Usage analytics (Google Analytics for Firebase: screens viewed, in-app events, pseudonymous app identifier, device information) | Only if you consent, at first launch or later in Settings | Understanding how the app is used to improve it | Consent — you can refuse or withdraw it at any time in Settings without losing any feature |
| Proof of consent (accepted terms version, analytics choice, timestamp, app version) | When you accept the terms and whenever you change your analytics choice | Being able to demonstrate that consent was collected, and which version was accepted | Legal obligation (GDPR art. 7.1) |
| Purchase data (product purchased, price, subscription status, credit balance) | When you buy a subscription or a credit pack through Google Play | Activating and tracking your paid benefits (through RevenueCat, see section 4). Your payment details (card number, payment method) never reach us: payment is processed by Google Play. | Performance of the contract |
2. What we do NOT do
- We do not sell or rent your data to anyone.
- We do not show ads and do not use advertising trackers.
- We do not use your recipes, messages or images for marketing or profiling.
- The service uses the paid tier of the Gemini API: under its terms, your AI prompts are not used by Google to train its models. Google may however retain them temporarily for abuse detection and legal compliance purposes.
- No connection to your social media accounts: importing from Instagram, TikTok or YouTube is performed server-side, without authenticating to any platform — the app never asks for social media credentials and stores no session or platform cookie.
Please avoid including sensitive personal information (e.g. health details) in messages sent to the AI — it is not needed for cooking advice.
3. Sharing with other users
Aloumi lets you share your recipes, shopping lists and addresses with people you explicitly authorize using a share code. An access request must be approved by you before the requester can see anything. Shared data is only visible to the people you grant access to, and you can revoke access at any time in the app settings.
4. Third-party services (processors)
Aloumi relies on the following services, operated by Google LLC / Google Ireland Ltd:
- Firebase Authentication — sign-in
- Firebase Firestore & Firebase Storage — data and image storage
- Firebase Cloud Messaging — sending notifications
- Google Gemini API / Vertex AI — AI text and image generation
- Firebase Crashlytics — crash reporting
- Google Analytics for Firebase — usage statistics (with your consent only)
Their processing is governed by Google's Privacy Policy.
For in-app purchases and subscription management, Aloumi also relies on RevenueCat (RevenueCat, Inc., USA): validating purchases made through Google Play and tracking your subscription status. RevenueCat receives your technical account identifier and your in-app transaction history (product, price, status) — never your payment details (card number, payment method), which are processed exclusively by Google Play. Its processing is governed by RevenueCat's Privacy Policy.
5. International transfers
Data processed by Google may be stored on servers located outside the European Union, including in the United States. These transfers are covered by the EU-U.S. Data Privacy Framework, to which Google LLC is certified, and by the European Commission's Standard Contractual Clauses where applicable. Data processed by RevenueCat is hosted in the United States (Amazon Web Services); these transfers are covered by GDPR-compliant contractual safeguards, including the Standard Contractual Clauses.
6. Retention
- Account and content data: kept as long as your account exists; deleted immediately when you delete your account.
- AI chat history: stored locally on your device only; removed when you delete it in the app or uninstall the app.
- AI usage counters: kept for a maximum of 13 months, and deleted with the account.
- Anti-fraud tokens (the two pseudonymized hashes, derived from the email address and from the identifier of the Google account): retained for 24 months, including beyond account deletion — this is precisely what prevents recreating an account to obtain a new trial offer. After that period they are deleted automatically. They are stored without any link to your account: no account identifier, no email address in clear text.
- Videos relayed during a social media import: ephemeral transit only — deleted immediately after analysis, never retained.
- Photos and documents uploaded for an import: deleted as soon as the recipe has reached you, and no later than about two days after upload.
- Your device's notification identifier: kept as long as that device is signed in to your account; removed when you sign out, as soon as it is no longer valid, and when the account is deleted. When attached to an import, it is only carried for the duration of that import.
- Purchase data: payment events sent by RevenueCat are kept on our servers for 90 days, then deleted automatically, and erased immediately when the account is deleted. Your RevenueCat record (account identifier and purchase history) is deleted with your account; Google Play, the seller of your purchases, keeps its own transaction records under its retention policy.
- Crash data: retained by Firebase Crashlytics for 90 days.
- Analytics data: retained for a maximum of 14 months.
- Anonymous aggregate statistics (daily usage cost across all users, sign-up and departure cohorts): these contain no identifier and no precise date, and are kept indefinitely — they cannot identify you.
- Proof of your consent (accepted versions of the terms, dates, analytics choices): kept for 5 years after account deletion, under a technical identifier that can no longer identify you — it is what lets us demonstrate that your consent was properly obtained.
7. Data deletion
You can delete your account and all associated data at any time:
- In the app: Settings → Account → "Delete my account". Deletion is immediate and irreversible; a second automatic pass, within the following hours, erases anything another still-signed-in device may have sent back in the meantime.
- Online: submit a deletion request form while signed in with the Google account you use in Aloumi: we only delete an account when the request comes from its email address. Requests are processed within 30 days and confirmed by email.
Deletion removes: your recipes, shopping lists, addresses, meal plans, equipment settings, sharing profile, generated images, photos uploaded for an import, your devices' notification identifiers, AI usage counters, your sign-in account, your record with our purchase provider (RevenueCat), and your identifier in our analytics tool (Google Analytics).
What remains, and why: transaction data (purchases, subscriptions) stays with Google Play, the seller of your purchases, which keeps it under its own obligations; proof of your consent is kept for 5 years; two pseudonymized anti-fraud tokens (see §1 and §6) prevent trial-offer recycling; and pseudonymized behavioral statistics, containing no content data, are kept for statistical analysis. Apart from the anti-fraud tokens and what Google Play keeps under your Google account, this data carries a technical identifier that has become orphaned: once your sign-in account is destroyed, none of it can re-identify you.
8. Your rights
Under the GDPR you have the right to access, rectify, erase and port your data, to restrict or object to processing based on legitimate interest, and to withdraw your consent at any time (for analytics, via the toggle in Settings). The app's local backup export (Settings → Maintenance) gives you a portable JSON copy of your recipes, lists, addresses and equipment at any time.
To exercise any right, email us at the address below. You also have the right to lodge a complaint with the French supervisory authority, the CNIL (cnil.fr), or with the supervisory authority of your country of residence.
9. Data security
Your data is stored on Google Firebase infrastructure, protected by per-user access rules: your data is only accessible to your authenticated account and to users you have explicitly granted sharing access to. Data is encrypted in transit (TLS) and at rest on Google's infrastructure.
10. Children
Aloumi is not directed at minors under 15 (the age of digital consent in France) and does not knowingly collect data from them.
11. Changes to this policy
If this policy changes, the update will be published at this address with a new "Last updated" date. For material changes, you will be informed in the app.
12. Contact — data controller
Aloumi is published by JEYLAB, a French SARL with share capital of €1,000, Paris Trade Register 943 632 588, registered office at 6 rue Émile Dubois, 75014 Paris. For any privacy question or request: privacy@aloumi.app (see also the legal notice).