Privacidad

Zefro is a log of things about your body. We think that means we owe you an unusually direct answer about where it goes, so this page is written in plain words rather than in the language these pages are usually written in.

Zefro is made by Walene. Until Walene is incorporated, Zefro is published by Waleed Hussein, an individual trading as "Walene", of Hecham El Khalil, Tallet El Khayat, Fakieh and Itani Bldg, 1st Floor, Beirut 0000, Lebanon, who is the controller of your data under data protection law — the person who decides what is collected and why. This is the same name the App Store and Google Play show as the developer. You can reach us at contact@zefro.app, which is our email address for support and for privacy questions, or by opening a support ticket inside the app, under Settings.

Our representative in the EU, EEA, UK and Switzerland. Waleed Hussein (trading as Walene) has appointed DataRep as its data protection representative for the GDPR in the EU and EEA, the Data Protection Act 2018 and UK GDPR in the United Kingdom, and the FADP in Switzerland. If Walene has processed or is processing your personal data, you may be entitled to exercise your rights over it. If you want to raise a question to Walene, or exercise those rights, you can do so by:

• sending an email to DataRep at datarequest@datarep.com quoting <Walene> in the subject line;
• contacting them on their online webform at www.datarep.com/data-request; or
• mailing your inquiry to DataRep at the most convenient of the addresses below.

Please note: when mailing inquiries, it is essential that you mark your letters for ‘DataRep’ and not ‘Walene’, or your inquiry may not reach them. Please refer clearly to Walene in your correspondence. On receiving your correspondence, Walene is likely to request evidence of your identity, to ensure your personal data is not provided to anyone other than you. For general questions about Zefro, write to contact@zefro.app rather than to DataRep.

This page covers the Zefro apps for iPhone and Android, the Zefro web app at app.zefro.app, and this website.

Version 1.10 — effective 2 November 2026.

What we hold

• Your account. The email address you sign in with, and a display name. If you sign in with Apple or Google, they pass us your email address (Apple may give us a private relay address instead) and, if you let them, your name; we never receive your Apple or Google password. When you sign up with an email address we send a six-digit code to confirm that it is yours. We also keep a record of which version of these Terms and this Privacy page the sign-up screen showed you, and when.
• The launch waitlist. If you type your email address into the "Get notified at launch" box on this website, we store that address, the language of the page you used and the time you signed up, in our database. We email you to confirm the address, and once you confirm, a few short emails about Zefro before launch and one when it is live. Each of those emails has an unsubscribe link, and an address that has unsubscribed is never emailed again: we keep only the address, marked "do not write", so that stays true. The waitlist is not linked to any account. To have your address removed completely, write to contact@zefro.app.
• What you log. Workouts and sets, food and drink, body weight, body-fat estimates, measurements, progress photos, and any notes you type on any of those. This is the app.
• A few things about you that the calculations need: your date of birth (we store the date and work out your age from it), sex, height, what you are training for and how fast. You can change them in Settings.
• A one-way code for your phone. Your phone makes a code from its app-specific device identifier (the Android ID, or the identifier for vendor on iPhone) that cannot be turned back into that identifier, and Zefro keeps it with your account. It is used for one thing: spotting a free trial being started again and again on the same phone. If several accounts that used the free trial share a code, a person on our team may look at those accounts; nothing is switched off by the code alone. It is never used for advertising or tracking and is never shared. It is deleted with your account and is included when you export your data.
• Your location, only when you start something that needs it. If you start a run, ride or walk and allow location access, Zefro records the GPS route, distance and pace of that session, including while the screen is off or the app is in the background. If you send your location in a chat, Zefro sends the place you chose. If you choose to share your live location in a chat, for 15 minutes, 1 hour or 8 hours, Zefro keeps that one message up to date, including while the app is in the background, and keeps only your latest position: there is no trail, and it is deleted when the share ends or you stop it. Nothing is recorded outside a session or share you started. A cardio route is saved with the session and is visible to your coach only if you have allowed them to see your training.
• Heart rate, power, steps and workouts from your devices. If you connect a Bluetooth heart-rate strap, power meter, speed or cadence sensor or foot pod, Zefro reads from it during a session and saves the readings with that session. Zefro does not scan for anything else. If you allow it, Zefro also reads steps, heart rate and workouts from Apple Health (iPhone) or Health Connect (Android), one type at a time, and can write your finished cardio sessions back to them. You can withdraw any of these in your phone's settings. Health data from these sources is never sent to advertisers or data brokers and is never used for advertising. Workouts imported from them become sessions in your log. They are never included in what Zefro sends to Anthropic for Ask AI or the weekly report: those summaries leave them out.
• Strava. If you connect your Strava account, Zefro asks it for permission to read your activities (including activities you have marked private) and adds them to your log as sessions. Nothing is pulled until you connect. Disconnecting deletes the connection and its access token straight away; sessions already added stay in your log like any other session until you delete them or delete your account. Strava activities are shown only to you: Zefro does not show them to your coach and does not send them to Anthropic or any other AI service.
• Chats with your coach or client. Messages, voice notes, photos, videos, documents, a location and links you send are stored with that conversation for as long as the conversation exists, or until you delete a message for everyone. Voice notes are recorded only while you hold the record button. Videos are shrunk on your phone before they are uploaded. Chats are end-to-end encrypted, so only you and the other person can read them. The same goes for a message a coach broadcasts to several clients: the coach's phone encrypts it separately for each client, so our servers cannot read it. The exceptions are messages a coach schedules in advance and messages a coach sends to a group: our servers prepare and deliver those, so they are not end-to-end encrypted, and they are protected in transit and at rest. If you send a link, our server fetches the page to build the preview, so the person who receives it does not hand their address to the site you linked.
• Chats with friends and crews. Messages, photos, videos, voice notes and cards you send to a friend or a crew are end-to-end encrypted, like chats with a coach: our servers hold only who sent a message, when, and for a file its size, never the words, the picture or the voice. Text is kept until you delete it. Photos, videos and voice notes are kept for 90 days and then removed, and the message shows that the file has expired. When you send a friend a finished workout as a ghost, they see its numbers one set at a time, as they log their own, for 7 days. When you train together, each of you sees the other's current set only while you are both in a workout; nothing is kept afterwards except the fact that you trained together on a day, for 30 days. We count how many different people send or receive ghosts, train live with, or import plans from one account, to notice an account being used to coach for free; staff see those counts and never your messages or workouts. Friends never see your food, weight, measurements or photos.
• Calls. Voice and video calls with your coach or client use your microphone and camera and are carried by Stream, a real-time communications provider. Stream receives your account ID, your display name, your username and the link to your profile picture for the call; it never receives your email address. Zefro does not record calls. We keep a log of each call: when it happened, how long it lasted and whether it was answered.
• Shared plan links. If you create a link to share a workout routine or a food plan, anyone who has the link can see the plan as you shared it, and nothing else about you: not your logs, weight, photos or history. You can switch a link off at any time.
• Crash reports. When the app breaks it sends us a technical report so we can fix it. It carries device and error information, not your log, and it is tagged with your account ID (a random identifier, never your email or name) so we can tell which reports come from the same account. Crash reports are on by default; you can switch "Crash reports" off in Settings > Privacy at any time, and from then on none are sent.
• Usage events. Outside the EU, EEA, UK, Switzerland, Brazil, Turkey, South Korea, India, Saudi Arabia and the UAE, usage events are on by default and you can switch "usage events" off in Settings. In the EU, EEA, UK, Switzerland, Brazil, Turkey, South Korea, India, Saudi Arabia and the UAE, they are off unless you answer Yes when the app asks, once while you set up, whether to share anonymous usage data (you can change your answer in Settings). When on, Zefro sends counts of which screens and features get used to PostHog, an analytics company, stored in the EU. PostHog does not receive your account ID: our server turns it into a scrambled identifier using a secret key that only we hold, and that scrambled identifier is all PostHog sees. Events never include what you log: no foods, no exercises, no weights, no measurements, no messages.
• Reminders and coaching that fit your routine. Each night our server works out, from what you already log in Zefro, when you usually open the app, train and eat over the last four weeks, which days you usually train, how active you have been, and which reminders you opened. It uses this only to time reminders and coaching to your routine. It is never shown to a coach, never sold and never used for advertising. The daily record of when the app was opened is kept for 35 days and the reminder history for 13 months. It is part of how Zefro works and is covered by the health-data agreement you give when you sign up. Withdrawing that agreement in Settings > Privacy stops it and deletes what was worked out.
• What you send for automatic estimates and Ask AI. If you turn automatic estimates on, what you enter for that feature — a food photo, a nutrition-label photo, the text you typed, your goal, the question you ask, or a short summary of your own recent training and food numbers — is sent to Anthropic, the company that provides our AI, to produce your result. Nothing is sent before you agree, and you can turn it off again at any time in Settings. We keep a count of how many times you have used each AI feature, so the usage limit works. If you are coached, your coach can switch Ask AI off for you.
• Foods other users share. When someone submits a food to the shared catalogue, we send its name and nutrition numbers — not who submitted it — to Anthropic, our AI provider, which checks the numbers look right before the food is made public to everyone. This happens automatically, on our schedule, after the food is submitted; agreeing to your submission going public at the time you submit it covers this verification step.
• Adaptive targets. If you turn on adaptive targets (part of Zefro+), a weekly calculation on our own servers uses your logged weight and food to suggest new calorie and macro targets. It uses no AI and sends nothing to any other company. Targets are applied automatically unless you switch that off in Settings, and you are shown what changed and why. Zefro does not ask you any health questions to use this; the goals screen carries a note telling you to talk to a doctor first if you are pregnant, breastfeeding or have a history of an eating disorder.
• Notifications. If you allow notifications, your phone or browser is given a delivery address (a "push token", issued through Expo's push service on the phone and through your browser's own push service on the web) that we store so we can reach it, together with which kinds of notification you have asked for. A notification says who sent you something and what kind of thing it was — never what it says, and never anything about your body or your food.
• On the web app and this website. The Zefro web app at app.zefro.app keeps your sign-in session, your settings and a copy of your Zefro data in your browser's own storage, as the phone app does on your phone; signing out deletes that copy. This website remembers the language you pick in the same way. There are no advertising or tracking cookies. Visits to this website are counted with PostHog, without cookies.
• Support tickets. If you contact support from inside the app, what you write, any screenshot you attach and the replies we send are stored with your account so the conversation can continue. Walene support can read your tickets in order to answer them. Tickets are deleted when your account is deleted.

We do not sell any of this, and we never will. There is no advertising in Zefro, and no data about you is shared with an advertiser, a data broker, an insurer, or an employer.

Zefro sends no newsletter and no advertising email. The email we send is of these kinds only: the codes and links that confirm your address, sign you in, reset your password or confirm a new email address; a confirmation when you delete your account, and a link to a copy of your data when you ask for one; a notice when a link you shared is removed by our staff; the replies to a support message you sent by email or through the form on this website; the emails of the launch waitlist, if you joined it (see above), each with an unsubscribe link; a coach's welcome email when you turn coaching on; for people who book or apply through a coach's public page on zefro.app, the booking confirmations and reminders that the page sends on the coach's behalf; for a person a coach has finished working with, a request from that coach to share a testimonial, and a come-back offer, which arrives only if you switched come-back offers on in the app (they are off until you do). While Tips and reminders is on in Settings (it is on by default), we also send a few short messages in your first weeks, by email and as notifications: a tip for logging your first meal, a note that your first weekly report is coming, a note after several days away, and a notice two days before a free trial ends. Every such email has an Unsubscribe link, and switching Tips and reminders off stops them by email and in the app. A reply to a support ticket you open in the app arrives in the app, not in your inbox.

What your coach can see

If you accept an invitation from a coach, you answer four separate questions before the relationship starts. None of them is switched on for you.

• Your training — sessions, exercises, sets, and notes on them.
• Your food — food logs, meals, and your current targets.
• Your measurements — weight, body fat, measurements, and notes on them.
• Your progress photos.

Four things are shared whichever way you answer: your age, your sex, your height, and what you are training for. A coach setting your intake without those is guessing. Your coach can also see when you last logged something, even if you have switched everything else off.

You can change any of these at any time, and it takes effect immediately. Pausing or ending the relationship cuts your coach's access at once. Only you can change your own permissions — your coach cannot, and neither can we.

Notes your coach writes about you

Coaches keep private notes on the people they coach. Those notes are not shown to you in the app, and they are kept for 24 months after a coaching relationship ends, together with the frozen record of your check-ins.

They are still information about you. If you formally ask us for everything we hold about you, those notes are included in what you get, even though the app does not display them. We would rather tell you that here than have you discover it.

What a coach can never do

Change anything you logged. Export your log. See anything once the relationship is paused or ended. See another coach's relationship with you, your conversations with the app, your email address, your sign-in history, or anything about anyone who is not their own active client. There is no directory: no coach can find you, browse you, or search for you.

What Walene staff can see

Our staff do not browse accounts. When a person on our team needs to help you, the tool they use shows account facts: your email address, your plan, which devices you are signed in on (type and app version, never a push token), which coach you are linked to, which version of these pages you accepted, the kinds and times of messages we sent you, and your recent crash reports. It does not show what you logged, your photos, your food, your measurements or your chats. Every look-up is recorded in an audit log.

Two exceptions, both because you gave them to us: a support ticket you send (with any screenshot) is read to answer it, and a chat message that someone reports to us is read, with the names of the two people, to decide what to do about it.

Health and body information

Some of what Zefro holds is information about your health or body: your weight and measurements, progress photos, heart rate and Health data, your location during sessions, and anything you choose to tell a coach in a chat. Where the law treats that as a special category of data (the EU's GDPR does), our basis is your explicit consent, given at the moment you choose to log it, connect a device or sensor, allow a phone permission, or share it. You can withdraw it at any time by switching the feature off or deleting the data, and nothing else in the app depends on a feature you leave off.

Zefro is a log and a set of calculations, not a medical service. What it shows you is information about your own numbers, not a diagnosis or treatment.

We never send this information to an advertiser, a data broker, an insurer or an employer. The only companies that handle it are the ones listed below, each for the one job described there.

Referral codes

If you sign up with a referral code, we record which code you used and which account signed up with it. Why: to know where a sign-up came from. Basis: our legitimate interest. How long: for as long as your account exists.

Who else touches your data

Running an app means other companies hold pieces of it. These are all of them, and what each one is for:

• Supabase — the database, the file storage and the sign-in system. Our project is hosted in Ireland (EU).
• PowerSync — the service that syncs your phone, or the web app in your browser, with the database.
• Anthropic (United States) — our AI provider; produces the automatic estimates and Ask AI answers. What you enter for those features is sent to that provider to produce your result, only if you have turned automatic estimates on. It also checks foods other users submit to the shared catalogue before they go public, described above.
• Sentry — crash reports, stored in the EU. Reports carry your account ID and nothing else that names you. Sentry keeps crash reports for 90 days, then deletes them, so that is how long a crash report can outlast your account.
• PostHog — usage counts, stored in the EU, and only where they are on (see "Usage events" above). It sees a scrambled identifier, not your account ID.
• RevenueCat — manages Zefro+ subscriptions. If you subscribe, it holds an internal identifier for your account and your purchase history, so we can tell which features you have paid for. It never sees your email address, your logs, or anything you have entered in the app.
• Expo — building and updating the app, and its push service, which passes notifications to Apple and Google using your push token.
• Stream — carries voice and video calls between you and your coach or client, and receives the details listed under "Calls" above.
• MapTiler — supplies the map pictures behind your cardio route and behind a location sent in a chat. Your phone asks MapTiler for the map squares for the area on screen, so MapTiler sees which area, and your phone's internet address, but not who you are or what you did there.
• Backblaze and Bunny.net — store and deliver the photos, videos, voice notes and documents sent in chats. Files are held by Backblaze in its EU (Central) data centre and delivered through Bunny.net's content network using short-lived private links; chat files uploaded before this change may still sit in Supabase until they are moved.
• Amazon Web Services (SES) and Resend — Amazon SES sends all the email described under "What we hold": the confirmation and sign-in codes, the waitlist emails, the other messages listed there, and our replies. Resend receives the messages you send to contact@zefro.app and through the support form. They see the address the email is for and its contents.
• Strava — only if you connect it; we read your activities from it.
• Apple Health and Health Connect — on your phone, not ours; Zefro reads from and writes to them only with your permission.
• Apple and Google — they handle sign-in if you choose Sign in with Apple or Google, their notification services carry a notification the last step onto your phone, and the Play Store and App Store record a purchase when you subscribe.
• Cloudflare — serves this website, the web app at app.zefro.app and the invite links.

The food catalogue itself comes from Open Food Facts, the United States Department of Agriculture and other public food tables, and from foods people share. Looking a food up does not tell them anything about you. If you scan a barcode we do not have yet, our server asks Open Food Facts for that barcode and nothing else: it never receives your name, your account or your phone's address.

Most of the companies above are based in the United States; Supabase, Sentry and PostHog store their data in the EU. When personal data from the EU, EEA, UK or Switzerland is sent to a company outside those places, the transfer rests on the Standard Contractual Clauses (SCC) approved by the European Commission, which form part of that company's data-processing terms (with the UK and Swiss addenda for UK and Swiss data). Where the company is also certified under the EU-US Data Privacy Framework (DPF), that certification covers the transfer as well.

Google Calendar

If you choose to connect your Google Calendar, Zefro asks Google for two permissions: to add, change and remove the sessions Zefro creates on your calendar, and to see only whether you are free or busy so a coach can offer you times that fit. We do not read event titles, guests or notes from your calendar. Disconnect at any time in Zefro, or at myaccount.google.com/permissions, and the connection is deleted.

Zefro's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the calendar feature you turned on, is never sold, never used for advertising or to train AI models, and is never read by people except with your consent or where the law requires.

Why we are allowed to process this, and how long we keep it

For readers who want the formal answer rather than the plain-English one above:

• Your account, your logs, your chats, and the coach data above — we process these because you asked us to, by using the app (performance of a contract with you, and our legitimate interest in running the service).
• Usage events (PostHog) — in the EU, EEA, UK, Switzerland, Brazil, Turkey, South Korea, India, Saudi Arabia and the UAE, your consent, given by answering Yes in the app; elsewhere they are on by default and you can switch them off in Settings.
• Reminders and coaching that fit your routine — performing our contract with you (Article 6(1)(b)) and, for health data, the explicit consent you give when you sign up (Article 9(2)(a)). Withdrawing that consent in Settings > Privacy stops it.
• Automatic estimates and Ask AI (Anthropic) — your consent, given when you agree to turn the feature on.
• Location, heart rate, sensor and Health data — your explicit consent, given when you allow the phone permission and start a session, a share or connect the source.
• Crash reports (Sentry) — our legitimate interest in keeping the app working (GDPR Article 6(1)(f)). Reports carry no logged health data, screenshots, screen contents or network addresses, so the impact on you is small; you can object at any time by switching "Crash reports" off in Settings > Privacy. In the EU, EEA, UK, Switzerland, Brazil, Turkey, South Korea, India, Saudi Arabia and the UAE, usage events (PostHog) are never sent without your consent (Article 6(1)(a)); elsewhere they are on by default and you can switch them off in Settings at any time. Either way you can withdraw the same way.
• The record of which version of these pages you accepted — our legitimate interest in being able to show what you were told.

Retention: we keep your account and what you log for as long as your account exists, and delete it when you delete your account, with the exceptions described on this page: a coach's own notes (24 months after the relationship ends), the text of chat messages you sent (see the next section), and a live location, which is deleted when its share ends. Our database provider keeps daily backups for disaster recovery for 7 days; data you delete can remain in those backups until they expire, and is then gone. We keep no other copy.

Getting your data out, and getting rid of it

Export is free and complete, and you do not have to ask us for it. So is deletion.

When you delete your account, what you wrote goes: your logs, your measurements, your photos, your cardio routes, your support tickets, and the photos, videos, voice notes and files you sent in chats, including the copies in storage. We also ask the services that hold a piece of you to delete it: your call profile at Stream, your billing record at RevenueCat, your usage records at PostHog (crash reports at Sentry expire on their own after 90 days), and, if you signed in with Apple, we revoke the sign-in link with Apple. Stored files are removed in the background, normally within minutes; if one of these outside services is down at that moment we record what is left and try again.

Two things survive, and we would rather be precise about it than tidy: the text of messages you sent in a chat stays in the other person's conversation, shown as coming from a deleted account, in the same way a message you sent to someone stays in their phone; and anything a coach wrote themselves — their notes, their side of a conversation — remains, attributed to a deleted account. It is their record of their own work, and the coach notes are subject to the 24-month limit above.

If you are a coach and you delete your account, each of your clients keeps a read-only copy of the text of their conversation with you, with you shown as a deleted account, and a copy of the plans you assigned to them. Voice notes, photos, videos and files are not kept, and nobody can reply. The copy sits on the client's own account, only the client can see it, and it is deleted when they delete it or delete their own account. Your private notes about your clients are not part of it.

Full instructions for deleting your account, from inside the app or without it, are on our delete-account page.

One thing is kept after deletion, and only if your account ever had a store refund: a one-way scrambled form of your email address, which cannot be turned back into the address. It is used only to refuse another free trial if the same email signs up again.

Your rights

Wherever you are, you can ask us at any time to see a copy of what we hold about you, correct it if it is wrong, or delete it — the app's own export and delete tools do the first and third of those for you directly, any time, without waiting on us. If you are in the EU, the UK, or a similar jurisdiction, you also have the right to object to our processing, to ask us to restrict it, to ask for your data in a portable format (export already gives you this), to withdraw a consent you gave us at any time going forward, and to complain to your own country's data protection authority if you think we have got this wrong. Write to contact@zefro.app for anything the in-app tools do not cover.

How a request works. Send it as a support ticket in the app or by email to contact@zefro.app. We confirm it is you by your account email: we never ask for an ID document or your password. We answer within one month. If a request is complex we may need up to two more months, and we tell you within the first month if so.

If you live in a US state with a privacy law

This section covers the California Consumer Privacy Act as amended (CCPA/CPRA), the privacy laws of other US states, the Washington My Health My Data Act and Nevada's consumer health data law (SB 370). It adds to the rest of this page and changes none of it.

What we collected in the last 12 months, by category. Identifiers (your name or username, email address, device identifiers); commercial information (that you subscribe, as reported by the App Store or Google Play); the content you log and send (food, training, cardio, body measurements, photos, chat messages, voice notes); internet and app activity (usage and crash data where you allow it); geolocation (a cardio route or a live location you choose to share). Of these, your health and body information, your precise location, and your account sign-in are sensitive personal information under California law. We collect each of them from you directly, or from the phone sensors and health services you connect. The sections above say why, with whom it is shared, and how long we keep it.

We do not sell your personal information and we do not share it for cross-context behavioral advertising, so there is nothing to opt out of. We use sensitive personal information only to provide the features you use, so the right to limit its use has nothing further to limit.

Your rights. You can ask to know what we hold and to receive a copy, to correct it, to delete it, and to withdraw consent for health data. We will not treat you worse for using any of these rights. The app's export and delete tools answer the first and third without a request.

How to ask, and how we check it is you. Write to contact@zefro.app from the email address of your Zefro account. We reply to that address to confirm the request before acting on it. An authorized agent can ask for you if they show your written permission, and we will still confirm with you. We answer within 45 days; if we need more time we tell you why and may extend once, by up to 45 more days. If we refuse, you can appeal by replying to our answer, and we will respond to the appeal within 45 days.

Consumer health data (Washington and Nevada). The consumer health data we collect is the health and body information described above. We collect and use it only to provide the features you turn on, and we share it only with the companies named under “Who else touches your data”, each for the one job described there. We do not sell it and we do not use a geofence around any health facility. You may withdraw consent to its collection or ask us to delete it at any time, in the app or by writing to us as above.

Age

You must be at least 16 to use Zefro. That is the minimum everywhere we are available. The app asks for your date of birth when you create an account and will not let you continue if you are under 16.

It is an honest question, not proof: we do not ask for identity documents and could not check them if we did. The date of birth you give is stored with your body profile, because the calculations need your age. A coach you work with sees your age, never the date itself, and you can change it in Settings.

If you believe an account belongs to someone under 16, write to contact@zefro.app and we will close it.

Governing law

These terms and this policy are governed by the law of Lebanon, where Zefro is operated from, without regard to conflict-of-law rules. If you live somewhere whose law gives you consumer-protection rights that cannot be signed away by agreement — for example, certain rights under EU or UK consumer law, or US state law — nothing here is meant to take those rights from you, and they continue to apply alongside this section wherever the law requires it.

Changes, and how to reach us

If this policy changes in a way that affects what we hold or who sees it, we will say so in the app rather than quietly editing this page.

Questions, or a request for everything we hold about you: contact@zefro.app.

Version 1.10 — effective 2 November 2026.

What changed in each version

• 1.10, 2 November 2026. The web app at app.pensum.fit is now the whole Zefro app for everyone, not only coaches: described what it keeps in your browser and that PowerSync syncs it too.
• 1.9, 30 October 2026. Reminders and coaching that fit your routine are now part of how Zefro works, covered by the health-data agreement given at sign-up, instead of a separate choice.
• 1.7, 23 October 2026. Added the reminder timing section: what is worked out each night, why, how long it is kept, and the switch that turns it off. Added chats with friends and crews, ghost workouts and training together.
• 1.6, 23 October 2026. Stated that when a coach deletes their account, each client keeps a read-only copy of their conversation and of the plans the coach assigned to them.
• 1.5, 23 October 2026. Corrected the text to match what Zefro does: the launch waitlist and the emails we send, the date of birth we store, Strava as the only connected service, and the coach-only web app as the only web app.
• 1.4, 23 October 2026. Stated that database backups are kept for 7 days. Added a section on US state privacy laws and consumer health data. Added this contents list and version history.
• 1.3, 15 October 2026. Named DataRep as our representative for the EU, EEA, UK and Switzerland.
• 1.2, 15 October 2026. Added the Google Calendar and Limited Use section, and the chat-media storage and delivery providers (Backblaze and Bunny.net).
• 1.1, 10 October 2026. First published version.