Questo documento è disponibile solo in inglese.
ezecal Privacy Policy
How this policy is laid out. Start here is the short version. Below it, each purpose has its own section: what data, why, the legal basis, who receives it, where, how long, and how to stop it. Words in bold that look like labels are the ones you see in the app.
Start here
Who we are. ezecal is made by Epic House SIA, Duntes iela 6, Riga, LV-1013, Latvia. We are responsible (the "controller") for the personal data that reaches us. Write to privacy@ezecal.app.
Your log stays on your phone. What you eat, weigh and train, your photos, your profile and what Apple Health or Health Connect hands over are kept in a database on your phone. It is not sent to us, and no feature of ezecal fetches it, unless you choose that (§2).
What reaches us. Some things reach us only if you choose. Others reach us or our providers automatically, because the app needs them to run:
- Automatically: an account the app makes by itself, with your IP address and device type on its session record; usage counts and request limits; checks for the app's version and updates; crash reports; and request logs with your IP address. None of this needs your name or email address, and none of it includes your meal log, body figures or workouts (§3, §18).
- Sharing (§5). Meals, Training (with Heart rate and Routes each set on its own), Body & goals, Apple Health imports or Health Connect imports, and Meal photos each have a switch, Off at the start. On my account keeps a copy in Frankfurt, Germany, by US-owned providers whose staff may reach it under EU contract clauses. Much of it is health data, and your "I agree" is your explicit consent. Switching off deletes the copy at once, and from backups within 35 days.
- Your settings (§5). Language, appearance, units and how your views look are kept with your account so every device uses them. Anything that says something about your body or training stays under the Body & goals switch.
- The AI (§4). A meal you want analysed, a few days of meals you want planned, a training week you want drafted, a plan for an event or a suggested change to one goes to the AI only when you ask, and only after you have said yes to sending it. It goes through Vercel to Anthropic in the United States and can show things about your health. We add no name or email address. Anthropic is bound not to keep it or train on it, and Vercel keeps the request's details, not its content. But Anthropic may keep a request its safety systems flag, for up to two years.
- What you share with people (§8 to §11). What you post, say, put in a challenge or publish is seen by the people it is for. A recipe is seen by everyone signed in to ezecal. Other people's copies can stay after you delete yours.
- Smaller things: a barcode or food search (§12), a purchase (§15), an invitation (§14), reports you send us (§17), and an address on the waitlist (§19).
- Ads (§16) appear only in the free version. We do not ask for personalised ads. In the EEA, the UK and Switzerland, if you say no, Google's ad software is not started. We send Google nothing you logged. But an ad request does tell Google that it comes from ezecal, a calorie and training app, from your IP address and device.
- Why
To give you what you ask for (contract, Art 6(1)(b)). To keep or send what you agreed to (consent, Art 6(1)(a), and for health data explicit consent, Art 9(2)(a)). To meet legal duties (Art 6(1)(c)). And, for a few named purposes such as security and fixing errors, our legitimate interests (Art 6(1)(f)). We use your data to run and protect ezecal and to meet our legal duties, as listed here.
Who else gets it. Vercel (hosting, file storage, website visit counts, the route to the AI, the bot check on the website's forms), Anthropic (the AI), MongoDB (our database), Resend (email), Expo (push notifications and app updates) and Stripe (website payments) work for us under contract. Apple and Google handle purchases and platform services largely as controllers in their own right; where our app starts their software, we can share responsibility for that collection. Map services and your browser's maker see what your device asks them for. Several of these are US companies. §21 lists every recipient, its role and the legal tool for each transfer.
What you control. Every Sharing switch, each AI answer, Health access, notifications and ad consent can be changed at any time: in the app under Profile, on the website under Settings. Exporting your data and deleting your account are free, in the app and on the website.
- How long
A copy on our server stays while its switch is on. It is deleted from the live database at once when you switch it off or delete your account, and from backups within 35 days. Each section says how long its data is kept, including the few records we keep after you delete your account (§20, §23).
Your rights. You can ask for access, correction, erasure, restriction and a portable copy. You can object to anything we do on legitimate interests and withdraw consent at any time. You can complain to the Latvian data protection authority (DVI) or the one where you live (§23).
Age. ezecal is for people aged 16 and over. We ask your age once when you start, and we do not check it against a document (§26).
What you say about others. What you post can be about other people. Please keep their details, and health details, out of it. We remove such details when asked, and our duties for what reaches our servers stay as this policy describes (§9, §17).
The policy, purpose by purpose
1Who is responsible
- Controller: Epic House SIA, Duntes iela 6, Riga, LV-1013, Latvia. Registration number 40203716958, Register of Enterprises of the Republic of Latvia. privacy@ezecal.app.
- Data protection officer: none appointed. Privacy questions go to privacy@ezecal.app.
- Lead supervisory authority: Datu valsts inspekcija (DVI), Elijas iela 17, Riga, LV-1050, Latvia, https://www.dvi.gov.lv.
- Which law. We are established in the EU, so the GDPR applies to everything here, wherever you live (Art 3(1)).
- "Our hosting" below means Vercel and MongoDB, in Frankfurt, Germany. Both are US companies; §21 gives the legal tool for that.
2What stays on your phone
First, the surprising parts. If a different account signs in on your phone, the previous account's data is removed from that phone first, and what it never switched on in Sharing is gone (the app warns you). Your phone's backup does not carry your log: a new phone starts empty unless you kept a copy On my account or exported one.
What is kept there. Meals, photos, saved foods, meal sets, planned meals, shopping list and home stock (with the product each food is, and what you threw away); profile, goals, weigh-ins, fasting plan and fasts, diet plan and its check-in answers, streak; workouts, sessions, training week, event plans, movements; readings from Apple Health or Health Connect; each session's heart-rate summary and route; preferences and reminders.
Legal position. While it stays on your phone it does not reach our servers and we do not hold it. Keeping your own records on your own phone is your personal activity (Art 2(2)(c)), so we need no lawful basis to hold it, because we don't. We remain responsible for how we build the app: its security and its privacy-protective defaults (recital 18, Art 25).
- How long
Your log and small notes, such as answers to the app's offers: until you delete them, delete your account in the app, a different account signs in, or you delete the app. Unfinished drafts, such as a setup or a new challenge: until finished or discarded, and cleared on their own after a while.
3Your account and signing in
First, the surprising part. On the phone, the app makes an account by itself, with nothing asked of you. It has a random identifier and no name or real email address, but it is still personal data, because it is tied to your device and to a session record with an IP address.
- What data
- The account: random identifier, whether you signed in, timestamps, the date the app first synced.
- Until you sign in: the name "Anonymous" and a made-up address. That address is not yours and we never send mail to it.
- After signing in: your email address and, from Apple or Google, your name (a private relay address if you hide yours from Apple), their identifier for you and their tokens.
- Session record: token, expiry, IP address, device or browser type.
- A sign-in link's record.
- After you change your email address: the old address, with a link that puts it back.
- Why
To give each person a fair AI allowance, keep you signed in, keep one plan across phone and website, and stop someone taking over your account.
- Lawful basis
Art 6(1)(b) for the account, sign-in and first-sync date. Art 6(1)(f), security, for the IP address and device type, the notice to your old address and keeping that address.
- Who receives it, and where
Our hosting. Resend (US) for the mails. Apple or Google when you sign in with them.
- How long
Account, sign-in identifier and tokens: until you delete it or it is deleted as unused (§20). The made-up record goes when you sign in. Session record: until you sign out, delete the account, or it expires after 7 days, counted again from each day you use it. The IP address on it: 30 days after it was last set. Sign-in link, and the code that carries a sign-in into the app: ten minutes, or until used. Old address and its link: 30 days.
- How to stop it
Delete your account (§23). Signing in is needed to buy credits, for the first week's larger allowance and invitation rewards, and for Sharing, the community and the website.
4The AI
First, the surprising parts. What you send goes to the United States and can show things about your health. Anthropic may keep a request its automated safety systems flag, for up to two years, and the safety classification for up to seven, or where the law requires it. For that it acts as an independent controller. Otherwise, under our contract, Anthropic keeps no copy, and Vercel keeps the request's details, not its content.
You are asked once, for every kind of request: meals, meal plans, training weeks, event plans and home stock. The question names each, and says what goes, through whom, where, and the exception above. You answer "I agree" or "No". Your answer and the wording you saw are kept on our server (§20). Every send is still a tap of yours. Plans are labelled as drafted by AI.
When the question's words change. If newer words name more data than the ones you agreed to, only what your words named is sent: the rest below is left out until you agree to the newer words. The app asks you once, when you use a feature that would send more; if you say "No", your earlier answer stays. Home stock needs the newer words, so it asks each time until you agree. If the words change anything else they promised, such as who receives the data, where or why, everyone is asked again and nothing is sent until you answer.
- What data
We add no account identifier, name or email. Words you or our staff type may themselves contain a name or health details.
- Meals. The photo or words; for a correction, the current foods and numbers and your words, and the first photo while it is still being analysed. Also language, estimation mode, units and meal categories, and, while Take from stock is on, the names of what is at home (no amounts or dates), so a food the meal holds is named as it is there and can be taken from it. A food at home that is a known product (a scanned pack, a nutrition label, the food database, one of your foods) is not described to the AI: our server puts that product's values on the AI's answer, and the AI's amount stays. Not sent for a meal analysis: name, email address, account identifier, weight, targets or history, or anything from Apple Health or Health Connect.
- Meal plans. The days; your saved meals with calories, macros, category and how often you logged them; each day's calorie target, which for a weekly or monthly target is worked out from what you logged, and which with training-day and rest-day goals differs on the days you have a session scheduled; macro targets; eating approach; the eating restrictions you set (Premium), as plain words such as "vegan" or "free from gluten"; how many meals you eat a day, if you set it; with the Endurance approach, which days have an hour or more of planned training; corrections. For meal suggestions in Plan my meals, also what is at home, with its amounts and the days left before it should be used, and the meals already planned on those days. Not sent: name, weight, log, photos or Health data. Your fasting plan and fasts are not sent, and the days it sets lower are not drafted.
- Training weeks. Goal, how long you have trained, usual days and time, session length, equipment, the movements it may use, including ones you named; for a change, the current week and your corrections. Please leave health details out of corrections.
- Event plans and suggested changes. Sport, distance, date, target time; six weeks' volume, longest session, number of sessions, best timed effort, and for a running plan your walks' weekly distance and longest walk; or the figures you typed instead; training days and experience; for a correction, the current plan, your words and earlier corrections, and the figures a correction set (where you start, the most your long session may be); for a suggestion, last week's planned and done figures, missed key sessions, and the coming sessions' kinds, distances or minutes and planned heart-rate zone. Not sent: any heart-rate reading, average or zone bound, name, body figures, routes or meals.
- Home stock. A photo of a receipt, of your fridge or cupboard, or of a nutrition label, or the words you type or say about what you have; with a receipt, also the names of what is on your shopping list, to tick them off; also your language. The photo goes with the request and is kept nowhere: not on your phone by us, not on our server. What comes back (foods, amounts, kinds, a label's figures, which list item a receipt line is) is kept with your home stock, your foods or your shopping list. Not sent: name, weight, targets, log or Health data.
- Count my Health workouts. Off to start. If you switch it on and agree in its own question, imported workouts' distance, duration and date count in those totals. Their heart rate and routes are not sent.
- Why
To do what you asked.
- Lawful basis
Art 6(1)(b), you asked for it; and, to the extent it says something about your health, your explicit consent, Art 9(2)(a), given by your "I agree" and the tap that sends it. Count my Health workouts: Art 6(1)(a) and Art 9(2)(a), by its own question.
- Who receives it, and where
Vercel Inc., our processor, which routes the request, and Anthropic PBC, our processor under our own agreement, which runs the model. Both in the United States (§21). Zero data retention and no training are terms of that agreement.
- How long
Our server passes the content on and does not store it. Records of each request, without its content, are kept up to 30 days. Anthropic: as in the first paragraph. What you keep from an answer stays with your meals or training. A suggestion stays on the event until you answer it. Your answers to these questions: §20.
- How to stop it
Permissions (Profile in the app, Settings on the website), on its one AI line. Withdrawing it also ends Count my Health workouts, which you can also switch off on its card. Adding a meal by hand, scanning a barcode, finding a food by name and Quick add work without the AI.
A recipe link. If you paste a recipe page's address into Describe, our server fetches that page, with nothing about you, and keeps neither address nor page. If you then tap Analyse, its ingredients go as a meal analysis. Basis: Art 6(1)(b).
Searching your meals on the website. Your words are matched on our server. Nothing goes to the AI until you press Analyse.
5Sharing: a copy On my account
First, the surprising parts. Each session keeps what you weighed that day, so that one figure travels with Training even if Body & goals is Off. Switching Meals or Training Off also deletes the copies you sent to people or put in groups. Meals Off also deletes your published recipes, and Meal photos Off takes the pictures out.
- What data
Each category is Off (only on your phone), On my account, or, where offered, Connections.
- Meals: logged and saved meals, each logged meal with the time offset it was logged at (so a meal stays on its day when you travel or the clocks change), categories, meal sets, planned meals and repeat rules, how many people a planned meal is cooked for, skipped days, shopping list, home stock, the product each food at home is, what you threw away, and what a meal took from it.
- Training: workouts, presets, training week, event plans, your movements and their muscles, sets you keep, the weight kept with each session; which health store your workouts and steps are linked to, and your answer on the daily step reading. Connections shows your last five finished sessions: the name, the day, the sport, how long and how far. Not sets, weights, notes or a photo.
- Heart rate and Routes, inside Training and never above it: see §7.
- Body & goals: sex, age, height, weight history, body fat, goals, how often you train and why, the burn taken from your log, heart-rate figures you gave, streak rule, what counts as a good day, fasting plan and fasts, the fasting confirmation you saw, your diet plan and your answers to its check-ins, the eating approach each goal was set under, your training-day and rest-day goals, goals you set ahead for a day or a stretch of days, the days you marked as training or rest days, and which health store your phone linked. While Training is also on, our server reads which days have a session scheduled to work out each day's goal, as your phone does. Setting up a plan or a diet plan on the website needs this on.
- Apple Health imports / Health Connect imports: meals, weigh-ins, workouts, daily activity, resting heart rate and VO2 max from Health. Connections also lets a session's measured energy show, if your profile's energy switch is on.
- Meal photos: the pictures on your meals, as files, shown only to you by a link that works for a few hours.
Your settings follow your account, whatever Sharing says: language, appearance, units, estimation mode, how your views look, how many people you usually cook for at each meal (a number only), which maps the website draws, which parts of ezecal you set up, when your day ends, your answer on Google's translator, the eating restrictions you set (Premium: vegetarian, vegan, free from gluten and the like, which pre-set the recipe filters and go to the AI only in a meal plan, §4), how many meals you eat a day, and notes you put away.
- Why
To reach your data on another phone and the website, to show it to anyone you choose, and to work out features you use, such as challenges and recipe counts.
- Lawful basis
Art 6(1)(a), your consent, and for every category your explicit consent, Art 9(2)(a), given by "I agree, keep a copy" after the screen says what is copied and that it is health data. Settings: Art 6(1)(b). The history of your choices: Art 6(1)(c), Art 7(1).
- Who receives it, and where
The copy is stored in Frankfurt, Germany, by our providers Vercel and MongoDB. Both are US companies, and their staff may reach it from outside the EU under EU standard contractual clauses (§21). At Connections, the people you connect with; sharing a group with somebody is not enough. Connections you choose in Home stock › Share with see your shopping list (what to buy and how much of it is at home, never the meals it is for or how many people you cook for), can tick it, and add things to it and remove what is not yet bought; what they add is kept with your list, in your account. They see your name and the other people on your list they are connected with themselves. Scanning in the shop, they also put what they bought into your home stock with its product's values, as your own phone would. Each of them can leave your list, and comes back only if you ask and they accept. Removing one of them, ending your connection, turning Share at home off or switching Meals Off ends it at once.
- How long
While the switch is on. Signing out keeps the copy. Off deletes it at once, and from backups within 35 days (§20). Settings, and your Sharing settings with their history: until you delete your account.
- How to stop it
The Sharing screen. It needs a signed-in account and uploads nothing until you switch something on. Your phone keeps its own copy.
6Apple Health and Health Connect
First, the surprising part. Withdrawing permission in Apple Health or Health Connect stops new readings. It does not delete the copy on our server: switch Apple Health imports or Health Connect imports Off for that. When the app sees the permission has gone, it offers to do so.
- What data
Only what you allow, type by type, on the system's own screen, at the feature that uses it:
- Sex, date of birth and height, once, if you ask setup to fill them in. We keep your age and the day it was read, not your date of birth.
- Active and resting energy; weight, body fat, and meals' energy and macros that other apps wrote.
- Workouts from other apps, now or further back if you ask: times, type, distance, energy, app and device, heart-rate summary, time in zones, and routes once you allow them.
- A day's resting heart rate and VO2 max. Steps and distance, for a goal or step challenge, or daily for Insights if you agree. Sleep, if you switch on Use sleep records: it sets your waking window and where your day ends. Only the middle of each night's sleep is kept, for two months, on your phone alone. The nights are never sent to our server; only the day each entry counts toward follows them.
What we write there. Meals you log and workouts you finish, with route and any heart rate a watch measured. Not fasting, weight, or anything we estimated. When you extend a session, ezecal replaces the workout it wrote for it with one over the longer time, its route included.
- Why
To fill in your plan, count what you did, and keep Health and ezecal in step.
- Lawful basis
Art 6(1)(a) and Art 9(2)(a), your explicit consent, asked feature by feature.
- Who receives it, and where
It is kept on your phone and is not used for advertising. It is not sent to our server except in these cases: the Health imports switch; Count my Health workouts, as totals to the AI (§4); energy and distance kept on a workout you recorded yourself, which travel with Training; and a weight kept when you first sign in or set by a scale before you typed one, which travels with Body & goals. It can also leave by your own choice: at Connections (§5), in a challenge (§10), or in your export.
- How long
On the phone, as §2. On our server, until you switch the category off. Workouts in Health stay until deleted there; ezecal deletes what it wrote where the store lets it.
- How to stop it
Unlink on the app's Health page, part by part; iPhone Settings › Privacy & Security › Health › ezecal; Health Connect › App permissions › ezecal; Stop reading steps; the daily step reading in Permissions.
7Watches, heart rate, routes and maps
First, the surprising parts. Hiding a route's start and end makes the spot where you set off from, often your door, harder to find. This reduces the risk but does not remove it: someone who sees several routes may still work out your area. A larger distance hides more. And when your watch and phone are apart, Apple or Google may carry what passes between them through their own services.
- What data
- While a session runs: heart rate, energy, distance and, outdoors, position and height, read by the watch and passed to your phone. Live figures do not go to our server.
- Kept with the session: average, highest and lowest heart rate, which watch measured it, and seconds in each of five zones. Not the readings.
- A route: its points with times and heights, distance, climbs, moving time, who recorded it. Your phone records one only with Record my route on, while a session you started runs, with location while using the app. Your watch records one only while an outdoor workout it records is running. When you extend a session your Apple Watch recorded, the watch reads that workout’s route back from Apple Health, to move it onto the longer workout. If its location is approximate, it may ask once, on that watch, for precise location for the route; approximate location records no route.
- A route imported from a GPX, TCX or FIT file. On the website the file goes to our server and needs Routes on. A heart rate in the file is not stored.
- Heights for a route. Where nothing measured a route's heights and the route is on your account, our server looks them up in open terrain data (Terms, section 2), at a hosting provider in Germany. It is sent the route's points alone, without their times, your account or the session, and keeps no record of them. A route Health handed over is never looked up. With Routes Off, nothing is looked up.
- Zone figures you typed or accepted. Recent workouts, copied to your watch.
- Why
To record sessions, show your zones and climbs, and show routes to you and anyone you choose.
- Lawful basis
Heart rate, and the energy and distance a watch measures, are health data. On your watch and phone they stay in your own records (§2), and the permission screens let you decide what the app may read. Keeping them on your account is a separate choice: your explicit consent (Art 6(1)(a), Art 9(2)(a)), given by the level you set in Sharing and withdrawn by switching it off, which deletes the copy. A route is treated the same way, because a series of routes can reveal your home, your routine or a place of worship or care.
- Who receives it, and where
At On my account: our hosting. At Connections: the people you connect with see, beside a session they can see, its average and highest heart rate and time in each zone, and its route without its start and end, from the age of 18; a session Health imported also needs Health imports at Connections.
Maps. Whoever draws a map sees the area on screen and your device's IP address: Apple Maps on iPhone and Apple Watch; OpenFreeMap on Android and Wear OS; in a browser OpenFreeMap, or Google Maps if you choose it. We send them nothing about you.
- How long
As long as the session or planned session. Off deletes them from our server. On the watch, a session stays until your phone has it; copied workouts until replaced or the app is removed.
- How to stop it
Record my route off; the watch's or phone's settings; Map during runs off; Hide the start and end; lower Heart rate or Routes in Sharing.
8Connections and your profile
First, the surprising parts. Your username is what other people see; it can be changed but not cleared. If you fill in your goal or how often you train, people in your groups and anyone who finds you can see it, and it can say something about your health, so we ask for an express "I agree" first.
- What data
Username and when it last changed; display name; picture and its original; short description, sports, how often you train, goal; Let people find me; connect code; connection requests; blocks; copies you send, frozen at that moment, with pictures only while Meal photos is on.
Who sees what. Every account starts private and appears in no search. Let people find me lets anyone signed in find you by username, shown name or a sport you listed; they see your username, your display name if you show it, and those four fields, not your picture, meals, weight, training or streak. People you connect with and people in a group with you also see your picture. Connecting shows nothing you logged; recent training goes to connections only through Training at Connections. Anyone holding your connect code can ask to connect. A block is not shown to the person blocked.
- Why
So people can find you, connect and pass things to each other.
- Lawful basis
Art 6(1)(b): finding and connecting with people is part of the community you chose to use. A health-related field: your explicit consent, Art 9(2)(a), withdrawn by clearing it or under Permissions, which hides it from others. A copy of a meal or workout: Art 6(1)(b), with your explicit consent, Art 9(2)(a), asked the first time in the words "This can show others information about your health". A block, for the person blocked: Art 6(1)(f), your interest in not being contacted.
- Who receives it, and where
The people above; our hosting; Expo with Apple or Google for pushes (§13).
- How long
Profile fields and pictures: until cleared or replaced, or the account is deleted. Username after a change or deletion: 30 days, so nobody can take it at once. A connection or block: until ended or either account goes. A copy: until the sender or recipient takes it down, the connection ends, either account is deleted, or the category is switched off; one taken into someone's library is theirs.
- How to stop it
Clear a field; withdraw an ask under Permissions (a copy already sent stays as above); switch Let people find me off; replace your code; end a connection; block.
9Groups, clubs and teams
First, the surprising parts.
- Members of a group see each other's usernames, pictures and profiles. In a group anyone can walk into, that starts as soon as they join.
- The owner and admins of a club can read every channel, each team's included, without joining, and it leaves no mark.
- Whoever wrote a message sees who has read it. This cannot be switched off.
- Leaving a group does not delete what you said in it: it stays with your name until you delete it or your account. Deleting your account removes every message you sent, in every group.
- An announcement, comment, chat message or picture reported by two different accounts is hidden as soon as the second report lands. This happens automatically; the author is told why and that it was automatic, and can ask us to look at it.
- Youth teams for children under 16 are not offered.
- What data
- The group: name, description, picture, sports, place, code, settings, and each person's role, nickname and name setting.
- What is said: announcements, comments, chat, reactions, polls and votes, last-read moments, links, photographs, short videos, voice messages. A photograph's location and time are stripped; a video's own file details are not, so strip them first if that matters to you.
- Events, with invitations, answers and notes, tasks and waiting lists. Away days.
- Teams: squads, lineups, a coach's note, and the attendance register. If you switch on Add trainings and matches I attend to my log, with Training on, a session written when you are marked Present.
Where a group meets. An admin picks a place from a list, taps a map, or presses use my location, which shows the point with a note that if this is someone's home, members will see it; nothing is kept until the admin saves the form. An exact spot starts at members only. What is kept is a place somebody chose to save for a group or event. It can be the location where they were when they pressed the button, or someone's home, so it can be personal data, and it can be changed or cleared at any time. Near me and My location use your position for that request and discard it.
Someone not on ezecal. A coach may add them by name. No email, phone or picture is taken, but we then also hold what the team records about them: shirt number, positions, answers a coach records, attendance marks, lineup places and a coach's note. The club and we are responsible for this together. The club must tell the person, and we delete it 12 months after their last mark or lineup, or sooner if they ask at ezecal.app/report.
Who sees what. Members see what is in the group. A club's admins see each team's schedule. Can't go and notes go to coaches and admins. A register goes to organisers; each member sees only their own marks. A coach's note goes to that player and the team's coaches and admins. Organisers can download attendance or a team sheet; once downloaded it is the club's own copy, under its own responsibility.
Who is responsible. Whoever runs a club, or a group for an organisation or business, decides whom it lets in and what its teams record. For that, the club and Epic House are joint controllers (Art 26), under the arrangement in the Terms: we run and secure ezecal, give you this policy and answer what you ask; the club answers for whom it admits, what it records and any file it downloads. You may use your rights with either of us. For a group a private person runs for friends or family, we are the only controller towards you.
- Why
To run the groups, teams and events you take part in.
- Lawful basis
Art 6(1)(b): groups, chat, events and challenges are parts of the service you use under the Terms. What organisers record about you (marks, lineups, answers set for you) and removals and suggestions: Art 6(1)(f), the club's or group's interest in running itself, which you can object to (§23). Posting a copy of a meal or workout: your explicit consent, Art 9(2)(a), asked the first time. Please keep health details out of chat and notes; we remove them when asked.
- Who receives it, and where
The people above; our hosting; Expo with Apple or Google for pushes; Resend for some mail.
- How long
- Messages, posts, links and files: until the author or an admin deletes them, we remove them, the group ends, or the author's account is deleted. Photos, videos and voice messages in a group are also deleted after 24 months without activity in the group. A deleted message leaves a "Message deleted" marker; a note of its removal stays 30 days.
- Membership and the group's picture: until you leave or are removed, an admin removes it, the group ends or your account goes. If an owner deletes their account, the group passes to another member (Terms, section 4). A group with nobody else in it ends with everything in it.
- Marks and answers: until you leave or are removed. Marks you set for others stay without your name when your account goes.
- Events, tasks and lineups: until deleted or the group ends. Your task takes go when you leave. Away: 30 days after its last day.
- A removal record or an admin's Keep on a report: until the group ends or the person is let back. A suggestion: until answered.
- How to stop it
Leave; delete your own messages and files; mute a group or room; switch Show my name and your stream options off; object under §23.
10Challenges
First, the surprising part. A finish link can be opened by anyone who holds it, without an account. It shows the challenge's name and rules, the day you finished and your own figure, which can include what Health brought in and a watch measured. Where it does, Share asks for your express "I agree" first. A preview an app already drew stays with that app.
- What data
The challenge: name, requirements, window, who set it up. For each person: when they joined, who invited them, whether they show the day they finished, and that day. Invitations. Links: code, maker, a finish's figure. Your bar is worked out from what your account holds.
Who sees it. Your own bar: only you. Others see that you are in it, by username, or as a count if you are not connected or in a group together; whoever set it up is named. The day you finished, only if you switch that on. In a Together, one shared total. With two or three of you, people can work out what you added. Health's figures enter a Together only while Health imports is at Connections. An invitation's link shows who sent it.
- Why
To run challenges you choose to join.
- Lawful basis
Art 6(1)(b). Health-derived figures in a Together or on a finish link: your explicit consent, Art 9(2)(a), by the Sharing level or the express step. A report on a challenge's name: Art 6(1)(f) for its maker.
- Who receives it, and where
The people above; link holders; our hosting; Expo with Apple or Google for pushes.
- How long
The challenge: until its maker or a group admin deletes it, we remove it, its group is deleted, or the last person leaves. Your record: until you leave or delete your account; one you finished stays hidden until its window has ended everywhere. An invitation: until answered or withdrawn, the connection ends, or the challenge ends. An invitation's link: until the window has ended everywhere. A finish's link: 30 days after last shared, or until Stop sharing. The note that one ended: 14 days. A report on its name: until decided, it is deleted, or the reporter's account goes.
- How to stop it
Leave; Stop sharing; switch off showing the day; withdraw the ask under Permissions, which stops a link showing a Health figure.
11Recipes and weeks you publish
First, the surprising parts. A published recipe or week is seen by everybody signed in to ezecal. Copies people saved or imported stay theirs after you unpublish or delete your account. An "Anonymous" byline hides you from readers, not from us: staff can see the account when they look at a report. What you write is published as it is, and the app warns you first.
- What data
A recipe: name, description, foods and figures, method, tags, language, byline, and pictures while Meal photos is on. A week: its name, which meals fall on which weekday (not the dates), each meal as a recipe shows it, and averages our server works out. Not published: anything else from your log, body or health. Also a record that you made it, your stars, recipes you hid, and reports.
Who sees it. Everybody signed in; there is no public web page. Nobody sees who made or rated a recipe, its author included. A diet plan can suggest published recipes; the author is not told. Publishing needs Meals at On my account.
- Why
To let people publish, find and use recipes, and keep the Library safe.
- Lawful basis
Publishing, rating, hiding and reporting are parts of the Library you use: Art 6(1)(b). A "made it" record is made only when you press I made it, on your explicit consent, Art 9(2)(a), given by that press after the note beside it. Keeping a report and not showing an anonymous author: Art 6(1)(f).
- Who receives it, and where
Everybody signed in; our hosting.
- How long
A recipe or week: until you unpublish it, switch Meals Off or delete your account; one we removed is shown only to you until you unpublish it. Made-it records and ratings: until the recipe goes, Meals is Off, or you delete your account. Recipes you hid: until you delete your account. A report: until decided, the recipe goes, or the reporter's account goes.
- How to stop it
Unpublish; switch Meals or Meal photos Off.
Translating a recipe. The words are translated on your phone or in your browser and do not reach us. On Android, and on an iPhone for Latvian or an iOS older than 18, Google's ML Kit does this and reports its own use to Google: device, app, languages, timings, events and identifiers per installation, not the words or your account. We ask before the first translation that uses it. Basis: Art 6(1)(a), withdrawn under Permissions. Otherwise a language pack comes from Apple, Google or Microsoft. Models hold nothing about you and stay until you remove the app, or as Apple or the browser sets.
12Finding food and speaking meals
First, the surprising parts. A barcode you scan appears, with your IP address, in our host's request log for one day. A product you send to Open Food Facts is published for anyone, and we cannot withdraw it.
- What data
- Barcode. The number goes to our server, which looks it up at Open Food Facts with nothing about you. A meal you save keeps the barcode. Scan as you shop looks each pack up the same way; the product it finds (its name, barcode and values per 100 g or ml) is kept with your home stock under the list's name for that food. What a scan changed is kept on our server for 10 minutes so you can undo it, then deleted.
- Food search. Your words go to our server, answered from our copy of Open Food Facts and the US Department of Agriculture's FoodData Central. We do not store what you type.
- Adding a product. If a scan found nothing and you typed the product in, the app asks each time. Press ✓ and our server sends the barcode, name and nutrition per 100 g or ml under ezecal's account, nothing about you. We keep the barcode and when it was sent, not linked to you.
- Dictation. On the phone, speech is recognised on the device. On the website your browser's service is used, and the audio can go to its maker (Google for Chrome, Apple for Safari, Microsoft for Edge). We do not receive the audio.
- Why
To find food and let you speak instead of type.
- Lawful basis
Barcode and search: Art 6(1)(b). Adding a product: Art 6(1)(a), each time. Dictation: on the phone, no data reaches us. On the website, your consent, Art 6(1)(a) and Art 9(2)(a), asked before the first dictation; you can decline and type.
- Who receives it, and where
Our hosting; Open Food Facts (France), which publishes additions under the ODbL; your browser's maker, under its own policy, often in the US.
- How long
As above. You can ask Open Food Facts to correct or remove a product at openfoodfacts.org.
- How to stop it
Add meals by hand; press ✕; say no to the dictation question.
13Reminders and notifications
First, the surprising part. A push passes through Expo and then Apple or Google, and your phone shows it as its settings allow, the lock screen included.
Reminders you set are scheduled by your phone; nothing is sent to us.
- What data
For pushes: push token, platform, language, time zone, your notification settings, and for up to a day a record of recent pushes. A push says the group's name and who acted, in fixed words such as "Anna posted in Run Club"; you read the rest in the app.
- Why
To tell you what people did that concerns you.
- Lawful basis
Art 6(1)(b), on a phone where you allowed notifications.
- Who receives it, and where
Expo (the token and the words), then Apple's push service or Google's Firebase Cloud Messaging, in the US (§21).
- How long
The token: until you sign out on that phone, switch notifications off (withdrawn when the app next opens), delete your account, the push service says it no longer reaches a phone. Settings: until you delete your account.
- How to stop it
Reminders › From people; mute a group or room; your phone's settings.
14Inviting a friend
First, the surprising part. If you join through a group or challenge link, the person who shared it learns that you joined and may earn a reward if you keep using ezecal. You are told when you join, you can say no, and "no" records nothing. If you say yes, we note the days you open the app in your first 14 days: up to three dates, nothing you logged.
- What data
- Your invite code and a token on your group and challenge links, the same on all of them, so someone holding two can tell they came from one person.
- An invitation: who invited whom, when, time offset, up to three dates, the answer to the offer to connect, the reward.
- On the website, a cookie holds the code; for a group or challenge link, it and the phone's copy are set only after you say yes. An invitation counts when its link opens in the app.
- A mark that an account has used the iPhone app, kept until the account is deleted, which decides the kind of reward (Terms, section 5).
What people are told. An invite link and a challenge link name who sent them; a group link does not. Taking an invitation needs a signed-in account.
- Why
To reward invitations and apply the reward limits.
- Lawful basis
Art 6(1)(b) for an invitation you both accepted; for a group or challenge link, Art 6(1)(f), our interest in rewarding invitations, which you can refuse when you join.
- Who receives it, and where
Our hosting.
- How long
A record that earned nothing: 30 days after the friend joined. One that earned a reward: a year after it; a waiting week until it begins, then a year. Code and token: until you delete your account. Cookies: seven days. If an account is deleted, what identifies the friend goes at once; only the inviter's reward and date stay, until a year after it.
- How to stop it
Do not share links; say no when asked.
15Purchases, credits and your AI allowance
First, the surprising part. We keep an accounting record of a website purchase after you delete your account, because the law requires it.
- What data
- Allowance: credits used each month, nothing about what you analysed. The first week's larger allowance and the invitation reward need a signed-in account.
- Premium: where bought, plan, state, dates, trial, and the store's and our identifiers.
- Credits: balance, purchases, refunds, gifts (who, whom, how many, when). The person you give to sees your name, picture and the count.
- On the website: what you type in Stripe's payment form, on our plan page or on Stripe's page for a pack, goes to Stripe. We send it your email address, account identifier, currency, Terms version and refund requests. We hold no card or bank details and no billing address. Your approximate country picks the currency.
- Tax location evidence: for each purchase, the country your connection came from and, where Stripe Tax asked for an address, the billing address's country, under Stripe's identifier for the purchase, not your account's.
- Withdrawal, within 14 days: the purchase and the email's link. If you withdraw: the name and address you give, when we received it, and the refund.
- Accounting record: invoice or receipt number, date, product, net, VAT and total, currency, customer country and the evidence for it, Stripe's payment identifier, refund.
- Reminders and notices: which reminder went; each notice, and who it went to.
- Marks of packs granted, naming nobody, so a pack is not granted twice.
- Why
To sell, deliver, refund and keep the books, give a fair allowance, and tell you about your contract.
- Lawful basis
Art 6(1)(b) for the sale, allowance, gift, reminders and Restore. Art 6(1)(c) for the withdrawal function, confirmations, notices the law requires and the accounting record, also after deletion (Art 17(3)(b)). Art 6(1)(f) for abuse prevention on the counter, taking back what a refund paid for, the marks, and proof of a withdrawal.
- Who receives it, and where
App Store and Google Play, independent controllers for store purchases. Stripe (Ireland, and Stripe, LLC in the US), our processor for the payment and an independent controller for its own fraud prevention and legal duties. Resend for mails. Our hosting.
- How long
- Monthly count: 60 days.
- Subscription record: while active and 90 days after it ends, for refunds and disputes, then it goes unless you hold other Premium. When it ends, or you delete your account, the record is kept apart from the account for those 90 days.
- Balance, purchase records and your Stripe customer: until you delete your account.
- Gift: until both accounts are deleted, without the identifier of whichever went first.
- Withdrawal-period record: a day after the 14 days. Proof that you withdrew and were refunded: as long as the accounting record, without your account's identifier.
- Accounting record, kept apart from your account: five years from the end of the financial year, ten where the One Stop Shop applies or the buyer's country is not known, under Latvian accounting and VAT law. It holds no food, body or health data and is not used for anything else.
- Tax location evidence: ten years, under EU VAT law (Art 6(1)(c)).
- Reminder record: 30 days after its day. Who a notice went to: until a year after the change applies; the notice itself is kept.
- Marks of packs granted: 24 months from the purchase, also after the account is deleted, to stop a pack being granted twice. Art 6(1)(f).
- A parent's or guardian's objection: as long as the refund's record. Stripe's own records: as tax and anti-fraud law requires.
- How to stop it
Cancel in the store or under Settings › ezecal Premium; withdraw under Settings or from the email's link; delete your account.
16Advertising
First, the surprising part. We send Google nothing you logged: no meals, weight, goals, Health data, heart rate or routes, and we set nothing for targeting. An ad request does tell Google that it comes from ezecal, a calorie and training app, from your IP address and device. So we do not ask for personalised ads, anywhere.
When. One banner, for people without Premium. We do not ask Apple's tracking question, and the app does not use a device advertising identifier.
Your choice. Google's consent message asks you. If you decline in the EEA, the UK or Switzerland, Google's ad software is not started and no request goes to Google. You may see a banner of our own, which sends nothing to anyone. Refusing does not restrict the app, except that a chosen ad (below) is not offered.
A chosen ad. When your credits are used up, you can choose a short ad for one more. A one-time code tells us it was watched; Google does not get your account identifier.
On the website. One banner, for signed-in accounts without Premium. The rules are the same. If you agree, AdSense may set or read advertising cookies and browser storage.
- What data
IP address, device or browser information, the app or page and the page you came from, your answers in Google's message, ad interactions, and a chosen ad's code. Google uses them to serve the ad and detect fraud.
- Why
To fund the free version.
- Lawful basis
Art 6(1)(a) and ePrivacy Art 5(3), your consent, for everything Google's ad software does in the EEA, the UK and Switzerland. Elsewhere Google's message asks nothing, and we rely on Art 6(1)(f), funding a free app, which you can object to. A credit for a chosen ad: Art 6(1)(b).
- Who receives it, and where
Google, including outside the EEA (§21). We and Google may be joint controllers for the collection of ad request data in the app; Google answers for what it does afterwards under its own policy.
- How long
We store no ad request. Your choice stays on your phone until you change it or delete the app; on the website, in Google's cookie. A chosen ad's code: an hour; the day's count: two days. Google keeps its data under its own policy.
- How to stop it
Profile › privacy options, or Settings › Privacy and cookie settings. Premium removes ads.
17Reports, suggestions and moderation
First, the surprising part. Staff see your account's identifier with a report, so please leave out health details and check a picture first.
Telling us about a problem or an idea
- What data
Report a problem: your words, the part of the app, a failure's name, versions, up to three pictures. Suggest an improvement: your words and the part of the app. Leaving question: your reason and line, filed without your account. With each: language, when, your account's identifier. On the public website: the page and, if you want an answer, an email address with "You may reply to me".
- Why
To fix what is broken, learn what would help, answer you if you asked, and act on data requests.
- Lawful basis
Art 6(1)(f), our interest in hearing what goes wrong. If you write in health details anyway, sending them after the form's note is your explicit consent for us to read and act on them for this report only (Art 9(2)(a)). An answer on the website: Art 6(1)(a), your tick. Finding and answering your reports on a data request: Art 6(1)(c), Art 12.
- Who receives it, and where
Our staff, with your account's identifier. Our hosting. Resend, for an answer.
- How long
Two years after it arrived or after our last answer. Its pictures: 90 days after we close the report. Deleting your account deletes the reports sent from it, not the leaving answer.
- How to stop it
Do not send; ask at privacy@ezecal.app to delete your reports.
Reports about content, and our decisions
- What data
A report on an item: the item, its author, the reporter's account, the reason, when. A report on a profile or group at ezecal.app/report: what it says and names, the address left or the account. Our decision: what we changed, the ground, any note and its translations.
- Why
To act on forbidden content and tell people why.
- Lawful basis
Art 6(1)(c), Digital Services Act Arts 16 and 17, for telling the people concerned. Art 6(1)(f) for the person a report is about. Art 6(1)(b) for the reporter. Health details in a report are used only to read and act on it.
- Who receives it, and where
Our staff; a group's admins for reports in their group; the people concerned, who are not told who reported; Resend for letters.
- How long
Decisions, and reports on a profile or group: 18 months after the decision, or until a dispute about it ends, whichever is later. A report on an item: until decided, the item goes, or the reporter's account goes.
- How to stop it
Object under §23, or contest a decision by replying to the letter.
Verifying a club
- What data
The club's registered details, website and address, the code, who asked, and the decision.
- Why
Trust in the badge.
- Lawful basis
Art 6(1)(f), and Art 6(1)(b) for the person asking.
- Who receives it, and where
Our staff and hosting; the group's owner and admins; Resend, including a mail to the club's address naming the asker's username.
- How long
As long as the group; the address goes when the request is decided or closed.
- How to stop it
Withdraw the request or end the group.
Our community on Discord
- What data
None from the app or the website: Join us on Discord only opens Discord's invite link, and we send Discord nothing about you. On our server we see what Discord shows the people who run a server: your Discord name and picture, what you post there, the answers you pick when you join (your language, interests and interest in testing), and what Discord's automatic filters flag.
- Why
To answer questions, keep the server safe, post each update's notes in your language, and find testers among those who ask to test.
- Lawful basis
Art 6(1)(f), our interest in a safe and useful community. Picking "I'm interested in testing" is your request to hear from us about it, Art 6(1)(b).
- Who receives it, and where
Discord Inc. (US) runs the service as an independent controller, under its own privacy policy and terms; it is not our processor. Our staff and the server's moderators.
- How long
What you post stays until you or we delete it. Discord keeps its own records as its policy says.
- How to stop it
Leave the server, delete your messages, or write to privacy@ezecal.app.
18Keeping ezecal running and safe
First, the surprising part. Nobody signs up for this part, and it runs automatically. It keeps nothing you logged, except that a scanned barcode, and a calorie range you filter the Library by, is in the address of its request and so in the host's log.
- What data
Each item says how long it is kept.
- Limits. Your IP address, account or an email address, with a count, to stop abuse: a day at most.
- Host logs. Each request's address and IP address, and server logs: one day.
- Security log. IP address, route, method and status, without the request's query, kept for 30 days in our own database so that we can investigate an attack or a breach. Basis: Art 6(1)(f), and Art 32.
- Crash reports. Sent when the app breaks, and when it finds you signed out without having signed out yourself. The error's name and cleaned message, where in our code it happened, app version and build, update, system, screen name and language. A crash report carries no identifier, no account and nothing you typed. 30 days from an error's first report.
- Update check (Expo). Platform, versions, channel, current update, a random identifier for this installation (not your account's, kept on the phone until you delete the app), a failed start's message, and your IP address. Expo keeps its records as Expo's terms provide.
- Visits to the website. We set no cookie and store nothing on your device for this. Your browser tells us the page and the site you came from, and we keep only daily totals by page, language, site, country and phone or computer. Your IP address, the full address of the page you came from and your browser's details are not stored. Totals: two years. Vercel counts the same visits for us as well, also with no cookie: it is told the kind of page you opened, never a code, link or search in its address, and the site you came from. From your IP address and browser it works out your country, phone or computer, system and browser, and a code that changes every day, so a visitor is counted once a day without anyone knowing who it is. It keeps no IP address, drops the day's code and the visit after 24 hours, and keeps only totals: 12 months is what it promises us, and it may keep them longer.
- The bot check. The website's forms that anyone can send (joining the waitlist, feedback, and cancelling a website subscription) ask Vercel's bot check (BotID) whether a person or a script sent them. When you send one, your browser answers a short challenge with technical details about itself and your device, and our server asks Vercel for the verdict. We keep no record of the verdict. A message or a join a script sends is not kept; a cancellation always goes through, and only its email to an address with no plan here waits for the check. Basis: Art 6(1)(f), keeping the forms from being used against other people's inboxes, and ours.
- Staff access. Staff access to one person's account is logged: who, which account, when, why and what changed. Log: three years, to investigate misuse.
Cookies and browser storage. The app sets no cookies. The website sets ones it needs: your session, sign-in helpers (15 minutes at most), your day and time zone, the sidebar, your language (a year), a workout draft (a day), and an invite link you opened (seven days). For a group or challenge link's token we ask first (§14). Advertising cookies: §16. The website's browser storage holds:
- your appearance and the maps you chose;
- training plans you drafted and did not keep, and a new challenge you started filling in (30 days at most);
- your AI answer until your account holds it;
- small marks of what you have seen or done: a note or a Lose-plan notice you saw, a lineup you folded, a meal photo you tapped while photos were off;
- for that tab only: an unfinished setup, a first run's yes to tips, a purchase you just started until its receipt is read, a receipt's picture you chose on the Planner until your shopping list opens it, and whether live updates are unavailable.
Your appearance, chosen maps and drafts stay until you sign out or clear them; the tab's own items go when you close it.
- Why
To stop abuse, keep your account secure, fix errors, deliver updates, and know how the website is found.
- Lawful basis
Art 6(1)(f) for each. The update check's identifier is strictly necessary to deliver updates and security fixes (ePrivacy Art 5(3)). A crash report and a visit count carry nothing tying them to you, so we have nothing of yours to find. Vercel's count of the day is gone after 24 hours.
- Who receives it, and where
Our hosting; Vercel (US company) for its visit counts; Expo (US) for updates.
- How to stop it
Most of this comes with using the app. Deleting the app ends it; you can object at privacy@ezecal.app.
19The waitlist
- What data
While ezecal takes no new accounts: your email address, the page's language, when you joined and confirmed, and the links in our mail. No pixel and no click record.
The bot check. When you press Join, the page asks Vercel's bot check whether a person or a script sent the form (§18). A join refused as a script's leaves nothing of it with us.
- Why
One mail to confirm and one saying ezecal is open. The check keeps scripts from putting other people's addresses on the list, so that nobody gets our mail without asking for it.
- Lawful basis
Art 6(1)(a), by confirming. The bot check: Art 6(1)(f), keeping the waitlist from being used against other people's inboxes.
- Who receives it, and where
Resend (US) and our hosting; for the bot check, Vercel (US).
- How long
Unconfirmed: 7 days. Confirmed: until 30 days after the mail that ezecal is open.
- How to stop it
The link in every mail, or privacy@ezecal.app.
20Records we keep to show we followed the rules
First, the surprising part. A few of these outlast your account, on purpose. All are held by our hosting.
| What | Why and legal basis | How long |
|---|---|---|
| Your consent record: each answer with its version and time (Terms, the AI, Count my Health workouts, Google's translator, website dictation, the club addendum, the asks before you show health information to others), added to and not overwritten. Your Sharing choices keep their own history (§5) | To show what you agreed to. Art 6(1)(c), Art 7(1) | While your account exists and for three years after it is deleted or the answer is withdrawn, under the account's random identifier |
| Backups of our database | To recover from a failure. Art 6(1)(f), Art 32 | Up to 35 days |
| Deletion journal: an account's random identifier, categories switched off, a deleted entry's kind and identifier, who deleted it, when | To delete again after a restore. Art 6(1)(c), Arts 17 and 7(3) with Art 5(2) | 65 days |
| Register of rights requests and its correspondence | Art 6(1)(c), Art 12 | Three years after our answer |
| Mail to support@ and our answers | To answer you. Art 6(1)(f) | Three years |
| Register of personal data breaches | Art 6(1)(c), Art 33(5) | Five years after the breach is closed |
| A restriction you asked for | Art 6(1)(c), Art 18 | Until lifted or the account is deleted |
| Unused accounts: last use and a warning mark | Art 6(1)(c), Art 5(1)(e) | Never signed in: deleted after 12 months unused. Signed in: one email at 24 months, deleted at 25 if still unused and a month has passed. Not a paid or restricted account. The mark goes on use or on deletion |
21Who receives your data, and where
We share data with a public authority only where a valid legal duty requires it. "DPF" means the EU-US Data Privacy Framework. "SCCs" means the EU Standard Contractual Clauses.
| Who | What they get | Role | Where, and the legal tool |
|---|---|---|---|
| Vercel Inc. | Hosting and file storage; website visit counts (§18); AI routing (§4); the bot check on the website's forms (§18, §19) | Processor | Frankfurt; a request first reaches its network at the nearest point, which can be outside the EEA. US company. DPF, with SCCs Module Two in its Data Processing Addendum as fallback |
| Hetzner Online GmbH | Hosting: a route's points, without times or account, to look up its heights (§7) | Processor | Germany, in the EEA |
| Anthropic PBC | AI requests and answers | Processor under our agreement. Independent controller for anything it keeps for its own safety or legal duties | US. SCCs Module Two in that agreement, with zero data retention and no training as terms |
| MongoDB, Inc. | Our database and backups | Processor | Frankfurt. Support access from outside the EEA counts as a transfer: DPF, with SCCs Module Two in its Data Processing Agreement as fallback |
| Resend | Email: addresses and mails for sign-in, purchases, notices, reports and the waitlist, and mail you send us with our answers. It keeps its record of each email as its terms provide | Processor | US. DPF, with SCCs in its Data Processing Agreement as fallback |
| Expo (650 Industries, Inc.) | Pushes (§13) and update checks (§18). No account identifier or email | Processor | US. DPF, with SCCs Module Two under its terms as fallback; it keeps pushes and update records as its terms provide |
| Stripe Payments Europe, Limited; Stripe, LLC | Website payments (§15) | Processor for the payment; independent controller for its own fraud prevention and legal duties | Ireland and US. DPF first, SCCs in its Data Processing Agreement as fallback |
| Apple (Apple Distribution International Ltd, Ireland; Apple Inc., US) | App Store purchases; Sign in with Apple; push delivery; map tiles and Directions; the Watch link; language downloads | Independent controller | Its own published tools, including SCCs and DPF |
| Google (Google Ireland Limited; Google LLC, US) | Google Play; Sign in with Google on the website; push delivery; AdMob and AdSense (§16); ML Kit (§11); the Wear OS link; Google Maps if you choose it, which also sees the page's address; Directions | Independent controller; joint controller with us for collecting ad request data in the app, as §16 says, and for ML Kit's collection after you agree (§11) | Its own published tools, including SCCs and DPF |
| Your browser's maker (Google, Apple, Microsoft) | Website dictation audio; language packs | Independent controller | Its own terms, often the US |
| OpenFreeMap (Zsolt Ero, Hungary) | Your IP address and the map area | Independent controller | Hungary, in the EEA |
| OpenStreetMap Foundation | Your IP address and the pin, when you press Directions in a browser not using Google Maps | Independent controller | United Kingdom, under the EU's adequacy decision |
| Other people on ezecal, and clubs | What you chose to show them (§5, §8 to §11). A club is joint controller of what it records about its members | Your choice; joint controller for a club | Wherever they are |
Equal protection. Every recipient we share your data with is bound to protect it to the same standard as this policy, or an equal one: our processors by their contract with us, and independent controllers by the GDPR and their terms with us.
Transfers to the US. Where a recipient is listed under the Data Privacy Framework, the transfer rests on the Commission's adequacy decision (EU) 2023/1795. If that listing or decision lapses, the SCCs named above apply, with our assessment of US law and the extra measures named in it. You can ask for a copy of the safeguards at privacy@ezecal.app.
If you are in the United Kingdom or Switzerland. UK data protection law and the Swiss Federal Act on Data Protection apply to you. Transfers to the US rest on the UK extension to the Data Privacy Framework and the Swiss-US Data Privacy Framework where the recipient is listed for them, otherwise on the Standard Contractual Clauses with the UK Addendum or the Swiss adaptations. You can complain to the ICO (ico.org.uk) or the FDPIC (edoeb.admin.ch).
22Data we get from someone other than you (Art 14)
- Apple Health and Health Connect: what other apps and devices wrote there, and your profile in Health.
- Apple and Google, at sign-in: your name and address. App Store, Google Play and Stripe: the state of a purchase. Google: that a chosen ad was watched.
- Other people: a coach's records and notes, marks, answers set for you, invitations, suggestions, mentions, messages, and reports about you. A person typed into a squad is told by the club (§9).
- Public sources: food data, and the public register for a club.
23Your rights
Using your rights costs nothing. We answer within one month, which we can extend by two more for complex requests, telling you if so. Write to privacy@ezecal.app.
Checking it's you. Write from the email address your account uses; we then send that address a link to confirm before we act.
An account you never signed in to has no address or name. Export, correction and deletion work inside the app. For the server records, use Report a problem in the app, which carries the account. An identifier quoted by mail is not enough without a one-time code the app shows you. We have no address to write back to. Where we genuinely cannot identify you, Art 11(2) limits what we can do.
- Access (Art 15). Open the app, or use the exports. On request we also tell you which staff looks and changes the log records for your account, when and why (not who), and the actual recipients of your data.
- Correction (Art 16). Tap and change it. For anything else, write to us.
- Erasure (Art 17). Profile › Delete account, Settings › Delete account, or ezecal.app/delete-account for how to do it without the app. In the app this also erases the phone's data and clears its secure storage; on the website your phone keeps its data until you delete the app. What stays, as each section says: the accounting record and proof of withdrawal; the consent record for three years; marks of packs granted; a gift, without your identifier; your username for 30 days; decisions and reports (§17); the staff log; backups for up to 35 days and the journal for 65; Stripe's and the stores' own records; copies others hold; a group you own with others in it, which passes on; and marks you set for others, without your name. Only part of it: set a Sharing category to Off (§5), delete a meal, session or weigh-in, take a photo off a meal, or clear a profile field; what our server held of it goes too, and from backups within 35 days (ezecal.app/delete-account says where).
- Restriction (Art 18). Ask us to freeze your server records. We then only store them, except as Art 18(2) allows. You can still download them.
- Portability (Art 20). Free, for everyone: meals CSV; a meals file with pictures; a workouts file; a route as GPX; Body and plan; your account's record; your photos as a zip.
- Objection (Art 21). Where we rely on Art 6(1)(f), you can object on grounds relating to your situation. We then stop, unless we show compelling legitimate grounds or need the data for legal claims.
- Withdrawing consent (Art 7(3)). Permissions for the AI, Count my Health workouts, the daily step reading, Google's translator and the asks before you show health information to others. Sharing for each copy. Your phone's settings for camera, microphone, location and notifications. Health's settings (§6). Record my route. Privacy options for ads. Clearing a profile field. The link in a waitlist mail. It works from that moment and does not undo what was lawful before.
- Complaint (Art 77). To the data protection authority where you live or work, or where you think something went wrong, or to the DVI (§1). You do not have to contact us first.
24Do you have to give us any of this?
No law requires it. To use an AI feature, what it needs has to go to the AI. The phone's own account is made automatically and is needed for the AI allowance. Signing in is needed to buy credits, for the first week's larger allowance and invitation rewards, and for Sharing, the community (with a username) and the website. We ask your age at first run, and without an answer you cannot go on (§26). Body details are optional, except that a goal to lose weight needs your age, height and weight. Health, a watch, location, dictation, reminders, camera and ad consent are optional. Say no and the rest of the app works.
25Automated decisions and profiling
A model does these things, each only when you ask (§4): estimates what is in your food, plans meals, drafts a training week, drafts or re-plans an event plan, and suggests changes. Every number can be edited.
Your plan, zones, diet plan steps and check-ins are arithmetic, not a model: fixed rules. Your plan and zones use published formulas; a diet plan's steps and check-ins work from your own goals, logged days and weigh-ins, and the AI plays no part in them. A check-in only suggests: nothing changes until you tap.
Profiling. Working out your goal, pace and zones, and a diet plan's steps and check-ins, evaluates your health figures, which is profiling (Art 4(4)); it is done only to give you those figures, and you can object or change them.
Automatic rules. A few fixed rules act without a person:
- a goal to lose weight and a fasting plan are not offered, and a fasting plan is switched off, under 18 or below a healthy weight (and the Fasting page says so);
- a diet plan's check-in suggests fewer calories to lose or hold weight only where a goal to lose weight is offered, and never a daily goal under 1,200 kcal;
- an age under 16 closes the account (§26);
- under 18, Routes at Connections is not offered, and the website does not sell to you;
- something reported by two different accounts is hidden until we have looked;
- the first week's larger allowance and an invitation reward need a signed-in account;
- unused accounts are deleted after the warning in §20.
We do not think these have a legal or similarly significant effect under Art 22, because they protect you, are limited, and can be changed or looked at. You can ask a person to look at any of them at privacy@ezecal.app.
26Age and children
ezecal is not for anyone under 16. We ask your age once when you start. We do not check it against a document. It is one question, before an account is made. We keep only whether you are under or over 16, and under or over 18, not the year, on your phone and with your account. Opening the community or publishing a recipe also asks you once to confirm you are 16 or over, and we keep that you said so and when.
If you say you are under 16, the app does not go on and no account is made. If you type an age under 16 later, or we learn it, we delete what your account holds on our server, stop the AI, Sharing and the community, and delete the account after 30 days unless you tell us the age was a mistake; what is on your phone stays until you delete the app. We close an account we learn is used by somebody under 16. If you believe a child uses ezecal, write to us.
- Lawful basis
Art 6(1)(c), with Arts 8 and 25, and Art 6(1)(f), to protect children. If you are 16 or 17 and the law where you live makes a contract with you depend on a parent's agreement, we rely on Art 6(1)(f) instead of Art 6(1)(b) for your account and the community. Held on your phone and by our hosting. The age in your profile, used for your plan, follows Body & goals.
Children in a youth team. Youth teams are not offered.
27Security and breaches
Your session is in the phone's secure storage and your log in the app's own storage. Traffic to our servers is encrypted. If you find a problem, tell us at security@ezecal.app.
If a breach is likely to put you at high risk, we tell you without undue delay, as Art 34 requires: what happened, whom to contact, what it may mean for you, and what we have done and you can do.
28Changes and languages
When this policy changes, its date at the top changes. Before we use your data for a new purpose, we tell you in the app first (Art 13(3)). Where a change needs your consent, we ask for it in the app first; if you say no, the old terms continue or the feature stops.
Languages. The full policy is in English for now. Start here, the consent screens and the in-app wording are in all 18 app languages of the app, checked by a person for the languages of the EEA; the rest is in English. If the English version and a translation differ and you are a consumer, the reading more favourable to you applies.
29Contact
Epic House SIA, Duntes iela 6, Riga, LV-1013, Latvia. privacy@ezecal.app. Security: security@ezecal.app.
Ask us anything about this policy, or about the data behind any number the app has shown you.
Your country
This section adds what your country's law gives you.
United Kingdom. The UK GDPR and the Data Protection Act 2018 apply; where this policy cites the GDPR, read the UK GDPR. Transfers to the US rest on the UK Extension to the Data Privacy Framework where the recipient is listed for it, otherwise on the UK Addendum to the Standard Contractual Clauses. You can complain to us first at privacy@ezecal.app, and we acknowledge a complaint within 30 days. You can also complain to the Information Commissioner's Office (ico.org.uk/make-a-complaint).
Switzerland. The Federal Act on Data Protection applies. Your health data is sensitive personal data, and we ask for your express consent where we rely on consent. Data goes to the United States and to the other countries named in this policy; for the US this rests on the Swiss-US Data Privacy Framework where the recipient is listed for it, otherwise on the Standard Contractual Clauses with the Swiss adaptations. You can report a concern to the Federal Data Protection and Information Commissioner (edoeb.admin.ch).
United States. If you live in Washington or Nevada, our Consumer Health Data Privacy Policy applies to your consumer health data and explains your rights, including how to appeal. We do not sell personal information. We are paid for showing ads, and ads are not shown to users in the United States. If you live in a state with a consumer privacy law, such as California or Connecticut, you can ask us what we hold about you, have it corrected or deleted, and take a copy: write to privacy@ezecal.app, and if we refuse you can appeal by replying. If we deny your appeal, you can complain to your state's attorney general; in Connecticut, at portal.ct.gov/ag/common/complaint-form-landing-page ("Consumer Data Privacy"). We keep personal information for the periods in this policy.
Canada. We ask for your express consent before collecting health information. Your information is processed outside Canada, including in the European Union and the United States, where its authorities may be able to reach it. The person in charge of protecting personal information can be reached at privacy@ezecal.app. If you are in Québec, we have assessed the protection your information receives outside Québec before sending it there. Features that work out your goals, zones and plans analyse your figures; you can stop them by clearing those figures or not using the feature. You can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, in Québec, the Commission d'accès à l'information (cai.gouv.qc.ca).
Australia. Health information is sensitive information, and we collect it only with your consent. We disclose personal information to recipients in the United States and hold it in Germany, and we require them by contract to protect it. You can ask to see or correct your information at privacy@ezecal.app, and complain to the Office of the Australian Information Commissioner (oaic.gov.au).
New Zealand. Your information goes to recipients in Germany and the United States, under contracts that require protection comparable to the Privacy Act 2020. Where we receive information about you from someone else, such as Apple Health, Health Connect or a club, this policy tells you so. You can complain to the Privacy Commissioner (privacy.org.nz).
Japan. We use personal information for the purposes in this policy. Your information goes to recipients in the EU, which Japan treats as equivalent, and in the United States, which has no general federal law of this kind; there they are bound by contract to the protections in this policy. §21 names each recipient, its country and what it receives. You can complain to the Personal Information Protection Commission (ppc.go.jp).
South Korea. We ask your separate consent for health information. Our overseas recipients are named in this policy (§21), with what they receive, the country, how and when it goes (online, when you use the feature), the purpose and how long they keep it. The AI and Sharing ask before anything goes; you can refuse, and that feature then does not work. Our privacy officer can be reached at privacy@ezecal.app. You can complain to the Personal Information Protection Commission (pipc.go.kr).
India. You can give and withdraw consent in the app, in the language you use it in, as easily as you gave it. You can reach us at privacy@ezecal.app, and if you are not satisfied, complain to the Data Protection Board of India.
Indonesia. Health data is specific personal data, and we ask your explicit consent. Data leaves Indonesia under binding protections equal to this policy. You can write to us at privacy@ezecal.app and complain to the authority responsible for personal data protection.
Ukraine. We ask your explicit consent for health data, and transfer it abroad under contract and with that consent. You can complain to the Ukrainian Parliament Commissioner for Human Rights (ombudsman.gov.ua).