Privacy Policy
This Privacy Policy explains how Beiusanu Horia-Paul PFA ("izeeva", "we") collects and uses personal data when you use the izeeva app and website. We are the data controller: Beiusanu Horia-Paul PFA, a sole trader (PFA) registered in the Romanian Trade Register under no. F2025004325003, fiscal code (CUI) 51276117, with registered office at B-dul Bucureștii Noi 136, et. parter, ap. 5, Sector 1, București, Romania. For privacy questions, contact hello@izeeva.com.
What we collect
- Account data
- your email address, an optional display name, and a securely hashed password. If you sign in with Apple or Google, we receive from them your email address, your name if you choose to share it, and an account id they issue for izeeva, which is how we recognise you next time. With Apple's “Hide My Email”, the address we receive is a relay address, not your real one. We never receive your Apple or Google password.
- Health and diet data
- what you tell izeeva about your body and eating: your answers when you set up (goal, sex, age, height, weight, activity, pace), your weight entries, the foods you log, your daily targets, fasts, supplements, dietary needs and allergies, and your taste profile. This is data concerning health, a special category under the GDPR (see “Legal bases”).
- Your content
- your chats with izeeva, recipes, meal plans, and the feedback you send, plus usage counters used to enforce your plan's daily allowance.
- Reactions and reports on replies
- when you like, dislike or report one of izeeva's chat replies, we store your reaction, the reason and note you give for a report, a copy of the reply's text, and which AI model wrote it. We use this to find and fix wrong or unsafe answers and to choose better models. It is kept while your account exists, even if you delete the chat, and is deleted with your account.
- Meal photos
- if you use AI calorie detection, the photo you take or upload is sent to our AI provider to identify the meal. We strip embedded metadata (such as location) on our server, before the photo is analysed or stored, and we store the processed image together with the result so we can review and improve the accuracy of the feature. The resulting nutrition figures are estimates and are informational only, not medical or nutritional advice.
- Label photos
- if you use the label scanner, the photo you take or upload is processed to transcribe the ingredient list (location and other photo metadata are stripped first, on our server) and is stored together with the transcription so we can review and improve the scanner. Ingredient notes shown by the scanner are general information about additives, not medical or dietary advice.
- Payment data
- a subscription bought in the app is charged by Apple or Google; we receive only its status (active, renewal date, cancelled) through RevenueCat, never your card or bank details. Earlier web subscriptions were charged by Stripe, and we do not store full card details for those either.
- App usage
- in the izeeva app, which screens you open and when the app is opened, closed or brought back, together with your account, a random id for that one launch of the app, whether it runs on iOS or Android, and the app's version. We use it to understand how the app is used and to improve it. We record it ourselves: it is not sent to analytics or advertising companies, and we do not read your device's model, identifiers, location or advertising id. It is kept while your account exists and deleted with it. You can object at any time (see “Your rights”).
- Push notifications
- if you allow notifications, we store your device's push token (an address for sending notifications to that app on that phone) and the time zone the app reports, so we can send the notes you turned on. Turning them off in the app stops them being sent; the token is deleted when your phone stops accepting notifications from izeeva, or with your account. The daily reminder is scheduled on your phone and needs nothing from us.
- Technical data
- basic server logs to keep the Service running and secure.
How we use it
- To provide and personalise the Service and learn your tastes.
- To process subscriptions, billing, and support.
- To secure the Service and prevent abuse.
- To improve features and fix problems.
Legal bases
- Contract
- to provide the Service you signed up for: your account, your diary, your plan and its allowance, subscriptions and support.
- Explicit consent (GDPR Art. 9(2)(a))
- for your health and diet data. You give it in the app when you create your account: the line under the sign-up buttons says that creating it lets izeeva keep the health details you enter. izeeva cannot work without it. You can withdraw it at any time by deleting your account, which deletes the data.
- Consent
- for sending what you share with izeeva to AI providers (see “Sharing & processors”), for push notifications, and on the website for advertising cookies. Each can be withdrawn at any time, without affecting what was done before.
- Legitimate interests
- security and abuse prevention, improving the Service, recording app usage, and reviewing reactions and reports on replies. You can object to these (see “Your rights”).
- Legal obligation
- for example, keeping invoicing and accounting records.
Sharing & processors
We share data only with service providers who process it on our behalf, including:
- Stripe
- payment processing and subscription management.
- Apple, Google Play and RevenueCat
- subscriptions bought in the app.
- Apple and Google
- sign-in, if you use Sign in with Apple or Google.
- Expo
- delivers push notifications to your phone, through Apple's and Google's notification services.
- AI providers
only with your consent, which the app asks for before any AI feature works and which you can withdraw in Profile. We send what you write in chat, the meal and label photos you submit, the text of what you dictate, and the parts of your profile and food log a reply needs (such as your goals, diet and recent meals). Never your password or payment details. They go to:
- OpenRouter, which passes each request to an AI model. The models we may use through it are made by Alibaba (Qwen), Anthropic (Claude), DeepSeek, Google (Gemini), Meta (Llama), Mistral, OpenAI (GPT) and xAI (Grok). Meal and label photos are read by Google's Gemini. OpenRouter can run a model on its maker's servers or on another hosting company's, and each keeps data under its own policy.
VoiceWhen you dictate a meal, your phone turns your voice into text, on the device where it can, otherwise through your phone's own speech service (Apple or Google, under their terms). The recording is not sent to us; only the resulting text is, and it is treated like anything you type. We switch between these models as they improve. If this list changes in a way that matters, the app asks for your consent again before anything is sent to someone new.- Hosting & infrastructure
- our hosting, database, file storage and cache providers (Vercel, Neon, Upstash).
We do not sell your personal data.
International transfers
Several of these providers are based, or run their servers, outside the European Economic Area, mainly in the United States. Some of the AI models izeeva may use are made by companies based in China(DeepSeek, Alibaba), and a request can be run on their servers there. Where a provider is certified under the EU-US Data Privacy Framework, or offers the European Commission's Standard Contractual Clauses in its terms, the transfer relies on that. For sending your content to AI providers, the consent you give in the app, after being told who the recipients are and that some are outside the EEA, is also the basis for the transfer (GDPR Art. 49(1)(a)). Countries outside the EEA may not protect personal data to the same standard.
Retention
We keep your data while your account is active and as needed for legal, accounting, or security purposes. You can delete your account at any time in the izeeva app (Profile → Delete my account). Deletion is immediate and removes your account together with everything it holds: your food log, chats, meal plans, recipes, profile, and the photos and files you uploaded. A web subscription is cancelled with it; an App Store or Google Play subscription must be cancelled in the store, which the app links to before you delete. You can also ask us to delete it by contacting us.
Your rights
Depending on where you live, you may have rights to access, correct, delete, export, or restrict processing of your data, and to object or withdraw consent, and to receive your data in a portable format. To exercise these, email hello@izeeva.com. You may also complain to a data-protection authority: in Romania, the ANSPDCP (dataprotection.ro), or the authority where you live.
- Opting out of app usage recording
- Email hello@izeeva.com from the address on your account and ask to opt out of usage analytics. We stop recording your app usage and delete what we have recorded, and confirm by email. Everything else in izeeva keeps working as before.
Children
izeeva is for people aged 16 and over, as our Terms of Service require, and the app does not accept a younger age when you set up. It is not directed at children. If you believe someone under 16 has given us their data, email us and we will delete the account.
Cookies & advertising measurement
Essential cookies keep you signed in and remember your cookie choice. These are required for the site to work and are set without consent.
Advertising & measurement cookiesare set only if you press “Accept” on the cookie banner. Nothing in this category is stored or sent anywhere before then, and you can decline without losing any part of the service. They cover:
- Ad click identifier
- when you arrive from a Google ad, the link carries a click id. If you accept, we store it in a first-party cookie for up to 90 days so we can tell which ads lead to real signups. If you decline, or leave before choosing, it is discarded.
- Google Ads
- we report signups and purchases to Google, both from your browser and from our servers. Where you have accepted, this may include a one-way hashed (SHA-256) version of your email address so Google can match the conversion to your ad click. Google never receives your email in readable form.
- Meta (Facebook/Instagram) Pixel
- the same measurement, for ads run on Meta’s platforms, likewise sent from your browser and our servers. Where you have accepted, this may include a one-way hashed (SHA-256) version of your email address. Meta also uses advanced matching: contact details you type into a form on this site (such as your email address) may be hashed in your browser before being sent, so Meta can match the conversion to your ad click. Advanced matching is limited to contact details of this kind. Meta never receives your email in readable form, and we never send it the content of what you log about your meals, weight, or health.
- Traffic analytics
- aggregate page and performance statistics.
To change your mind after choosing, clear this site’s cookies and site data in your browser and the banner will appear again. You can also block cookies entirely through your browser settings.
Changes
We may update this policy and will post the new version here with an updated date. If a change affects how your data is used in a way that matters, we will tell you in the app first, and where the change needs your consent (for example, a new kind of recipient for what you share with izeeva), the app asks for it again.
- Beiusanu Horia-Paul PFA
- 51276117
- RO54845870
- F2025004325003
- B-dul Bucureștii Noi 136, et. parter, ap. 5, Sector 1, București, Romania