Privacy Policy

1. Who we are, and what this covers

Fitext is a health and fitness app: workouts, runs, nutrition, recipes, weight tracking, challenges, chat with other people, and an AI coach called Lia that runs on your phone. This policy covers the Fitext mobile app and this website, fitext.com.

Developer: Fitext, HaTe'ena 3, Nesher, Israel 3686403.
App on Google Play: Fitext (com.fitext).
Contact for anything in this policy: yotam@fitext.com.

By using Fitext you agree to what is described here. If you do not agree with it, please do not use the app. This policy should be read together with our Terms of Service, which you can open from the app settings.

Please do not put sensitive documents in the app

Fitext is a fitness app, not a vault. Please do not upload or type government ID numbers, bank or card details, passwords for other services, or medical records. We protect what you give us as well as we reasonably can, but no service can promise perfect security, and anything you post to other people can be passed on by them.

2. What we collect

2.1 What you tell us

• Account details: a username, a password (we store it only as a bcrypt hash, never as text you could read back), and an email address. Accounts created before we added password recovery may have no email address on file.
• Profile: your name, date of birth, gender, country, an optional phone number you can add in settings, a profile picture and a short bio.
• Body and goals: height, weight, fitness level and the answers you give about what you can currently lift, run or hold. This is health data, and we treat it as the sensitive category it is.
• Things you make: posts, recipes, workouts, groups, challenges, reviews, hashtags, and the photos and videos attached to them.
• Messages: what you send in chats, who you send it to, and who you mention in a group.
• Support: anything you write to us by email.

2.2 What the app records while you use it

• Activity you log: workouts completed, runs, meals, weight entries and daily step counts.
• Searches you type inside the app, such as looking for a recipe, a workout, a group or a person.
• Which cards you were shown in Discovery, and what you saved, joined, liked or completed.
• The difficulty ratings you give a session, which is how the coach learns what to build next.

Fitext does not operate a separate analytics or crash reporting service. The app includes Google's Firebase Analytics library, but its data collection is switched off, so it collects no analytics. Google Maps and Google's barcode scanning library collect their own service diagnostics as described below. Nothing in Fitext follows you around other apps or websites.

Google Maps SDK. When a map opens, Google receives request metadata, SDK crash and usage diagnostics, your IP address and an app-specific Google Maps SDK identifier to provide and improve its services. See Google's Maps SDK data disclosures.

Google barcode scanning (ML Kit). When you scan a barcode, the code is read on your phone and the picture is not sent anywhere. Google's ML Kit library still sends its own diagnostics to Google: device and app information, performance metrics and an installation identifier that is not meant to identify you or your phone. See Google's ML Kit data disclosures.

2.3 Device and connection information

• A push notification token from Google's Firebase Cloud Messaging, and the Firebase installation identifier that comes with it, so we can deliver a notification to your phone.
• A device identifier the app generates for itself the first time it runs, plus a second one used when syncing your Lia conversation. Both are random values created on your phone. They are not the Android ID and not an advertising ID.
• Your device type and the app version.
• Your IP address, which our servers see whenever your phone connects to them, as every internet service does.

We do not collect an advertising ID. The permissions that would allow it are deliberately removed from the app.

2.4 Location

Location is used for one thing: tracking a run. It is collected only while you have a run in progress and only if you grant the permission. Your phone can grant precise or approximate location, and Fitext works with whichever you choose.

While you run, the route is drawn and measured on your phone. When you finish, the run summary we store is distance, time, pace, elevation and a picture of the route map. We do not upload the raw list of coordinates.

If a run counts toward a challenge you are in, its summary card, with its route map or photo, is also posted in that challenge's chat, where the other members can see it. See section 4.1.

Two honest details about that picture, rather than the tidier sentence we would prefer to write. The upload starts the moment the run ends, which is before you are asked whether to keep the run, so choosing Delete run on the summary screen drops the run record while the picture that was already uploaded can stay in our storage, with nothing in our database pointing at it. We are changing that so the upload waits for your answer. And there is no way to delete a single saved run inside the app today: your runs and their route maps go when you delete your account, and you can ask us to remove one sooner at yotam@fitext.com.

Step counts come from your phone's own step sensor, or from Health Connect if you connect it. Fitext also writes the steps your phone counts itself to Health Connect, where apps you allow can read them. We receive the daily totals, not a location trail.

2.5 Photos, video, and your photo library

When you choose a photo or a video from your gallery, Fitext opens your phone's own photo picker, and the app receives only what you pick. Fitext does not ask for permission to read your photo library, and a photo or a video leaves your device only when you select it and send or save it.

The camera is used when you take a chat photo, photograph a meal, your scale or a treadmill console, or set a profile picture. The app does not record audio: both in-app cameras are opened with audio switched off, and there is no voice recorder anywhere in Fitext.

2.6 What we never touch

Your contacts, your calendar, your files and documents, your call log, your text messages, your browsing history in other apps, and any payment information. Fitext is free and has no purchases, so there is nothing to bill.

3. How we use it

3.1 Running the app

• Creating and securing your account, and signing you in.
• Delivering your chats, groups, challenges and the content you publish to the people meant to see them.
• Keeping your history so a new phone can pick up where the old one left off.
• Shaping the workouts the coach suggests, from the sessions you have actually completed and rated.

3.2 Lia, the AI coach

Lia runs on your phone. The language model is downloaded to your device and answers you there, offline if need be. Your conversation is stored in a database on your phone, and typing to her does not send your words to us.

Information leaves the phone in these cases:

• When you tap Sync in the coach chat, every message in that conversation that is not on our servers yet is uploaded, so your history survives a new phone or a reinstall. You cannot pick which messages go. That is a button you press, not a background upload. Once synced, the conversation is stored with your account, where Fitext support can read it. Our admin tools record which conversations staff open. Fitext support can also write to you in this conversation at any time, whether or not you have synced it, and in the app their messages are marked as coming from the Fitext team. A synced conversation cannot be deleted from inside the app: it stays with your account until you delete your account.
• Notes and step answers. The notes you ask Lia to keep, and her answers about your step counts, are part of the conversation and are uploaded with it when you sync. Our support tools show a label in their place rather than their words, though a reply from Lia that repeats a note is shown as written, and a step answer you report is shown in full. When you remove a note in the app, its words are cleared from our copy the next time you sync. The message in which you asked her to keep it stays in our copy as you wrote it.
• When you report a Lia reply, after you confirm, the reply and the message it answered are sent to our servers for review. Other unsynced messages are not sent by that report.
• When you share a message, the selected content is sent to the destination you choose.
• When you finish a run or a workout, or log a meal or a weight, a summary card for it is filed into your coach conversation and sent to our servers, because that record is your training history rather than a chat message. Creating a recipe files a card the same way. If a card counts toward a challenge you are in, a copy of it is also posted in that challenge's chat (see section 4.1).

Lia's answers are generated automatically and can be wrong. They are general fitness guidance, not medical advice, and they are not a substitute for a doctor or a qualified professional.

3.3 Notifications

We send push notifications for new messages, mentions, invitations and challenge activity, through Google's Firebase Cloud Messaging. If someone types your name in a group chat, the list of people mentioned is stored with that message, and your notification says you were mentioned rather than that someone sent a message. If you have muted a conversation it stays silent, mention or not. You can turn notifications off entirely in your phone's settings.

3.4 Safety and keeping the app usable

We use what we hold to block abuse, to act on reports, to enforce our Terms, and to protect people using Fitext. See section 6 for what happens when something is reported.

3.5 Email

We send automated email for one purpose today: a code to reset your password when you ask for one. It is sent through Amazon Simple Email Service. A person at Fitext may also write to you, to answer a message you sent us or about a deletion request you made on the web. We do not send marketing email, and there is no mailing list.

4. Who else sees it

We do not sell, rent or trade your personal information, and we do not share it with advertisers. There are no ad networks in Fitext. Beyond that, your information reaches other people and other companies in five ways.

4.1 Other people using Fitext

• Anything you publish, such as a post, a recipe, a workout or a profile, is visible to the people you publish it to, and to anyone in Discovery if you share it publicly.
• Messages go to the people in that conversation. Group members can see who is in the group and what is posted to it.
• Challenge participants can see each other's progress in that challenge. When something you log counts toward a challenge you are in, its card is posted in that challenge's chat: for a run that includes its route map, or the photo you took of a treadmill or run summary; for a meal, its photo if it has one; and for a workout, the exercises and how hard you rated it. Anyone can join a public challenge from Discovery, so its members may include people you do not know. The card stays in the chat if you leave the challenge, and is erased when you delete your account.
• Once someone can see something you posted, they can screenshot it or pass it on. We cannot take that back for you.

4.2 Companies that run parts of the service for us

These process data on our instructions and for no purpose of their own:

• Amazon Web Services: our servers, our database and the storage that holds uploaded pictures and video, plus the content delivery network that serves them.
• Amazon Simple Email Service: password reset emails.
• Google Firebase Cloud Messaging: delivering push notifications to your phone.
• Google Maps: the map tiles the run screen draws your route on.

4.3 Services that receive something for their own purposes

These are genuine third parties. What reaches them is listed precisely, because it is the part of a privacy policy people actually need.

KLIPY (stickers and GIFs).

• The stickers and GIFs in the chat expression panel come from KLIPY. What you type into the sticker search is sent to KLIPY so it can answer, together with a scrambled code derived from your account. Your name, email and profile never go to them.
• The pictures themselves are loaded straight from KLIPY's servers, both when you browse them and when a sticker someone sent you appears in your chat. That means KLIPY sees the IP address of the phone loading a sticker, including the phone of a person who only received one.
• KLIPY's own privacy policy says it keeps a history of the search terms entered and of the content viewed, associated with the IP address that asked for it. You can read it at klipy.com/support/privacy-policy.
• If you would rather KLIPY saw nothing, do not open the sticker and GIF panel.

Google Gemini (reading a photo of a meal, a scale or a run summary).

• When you take a photo for Fitext to read, of a meal, a scale or a run summary, the photo and the optional note you type with it are sent to Google's Gemini service, which reads what it shows and returns the numbers, such as a meal's calories and macros or the weight on a scale. Your name, account and location are not sent with it. The photo is uploaded to our storage as soon as the reading starts, whether or not you then log it.
• The app asks for your consent the first time, and this feature does nothing until you agree.
• Fitext uses Google's free tier for this. Under Google's terms for that tier, Google may use what is submitted to improve its own products, and their human reviewers may read it. So photograph the plate, not the paperwork next to it.

USDA FoodData Central (searching for a food by name).

• When you type a food name to look up its nutrition, that text is sent from your phone to the United States Department of Agriculture's public food database. Only the words you typed are sent.

Open Food Facts (scanning a barcode).

• When you scan a product barcode, the barcode number is sent to the Open Food Facts database, which is a public, community-run food database. Only the number is sent, and this is covered by the same consent prompt as the photo analysis.

4.4 Law, safety and a change of ownership

We may disclose information if the law requires it, if we need to enforce our Terms, or if it is necessary to protect someone's safety. If Fitext is ever acquired or merged, your information would move with the service, and this policy would follow it until you are told otherwise.

4.5 People at Fitext

The people who run support and moderation at Fitext can open any conversation in the app from our admin tools: your synced chat with Lia, and also private chats, groups and challenges. We use this to act on reports, to keep people safe and to help you when you ask. In your chat with Lia they can also write to you, and in the app their messages are marked as coming from the Fitext team. Our admin tools record which conversations staff open.

5. Photos, videos, stickers and GIFs

5.1 What you send in a chat

A photo or video you send in a chat is uploaded to our storage at Amazon Web Services and delivered to the people in that conversation over a content delivery network.

• We remove it from our servers after 7 days. That is an automatic rule on the storage itself, not a promise someone has to remember to keep.
• Your phone keeps its own copy of what you send and receive, and so does everyone else's phone in that conversation. That is why an old photo still opens for the people who were there, while a phone that joins later will not find it.
• If a message is reported, a copy of its picture or video is kept for up to 90 days so the report can be reviewed. See section 6.

Media is fetched over a web link with a long random file name. Anyone holding that link can open the file, so treat it the way you would treat any link you were sent: do not put anything in a chat that you would mind being passed on.

5.2 Pictures that are not chat

Your profile picture, recipe and post photos, group and challenge pictures, photos of meals and run route maps are part of the thing they belong to, so they are not on the 7 day clock. They stay while that profile, recipe, post, group, challenge, meal entry or run exists, and they go when it is deleted, or when you delete your account.

A photo of a meal is kept with the entry in your food log for as long as that entry is there. The app has no button for removing a single meal entry today, so in practice a meal photo stays until you delete your account, which removes it along with the rest of your food log. It is also sent to Google's Gemini service to be read, which is described in section 4.3. If you want a particular meal photo gone before then, write to yotam@fitext.com.

These pictures are fetched over web links too, and the same applies as in 5.1: anyone holding the link can open the file. That includes the route map or photo on a card posted in a challenge's chat.

One more honest detail. A photo of a scale, a photo that was read but never logged, and the route map of a run you deleted at the end instead of saving are not tied to an entry our deletion can find, so today they are not removed when you delete your account. We are fixing that. Until then, write to yotam@fitext.com and we will remove them.

One exception on the account side: a group or challenge picture belongs to the group or the challenge rather than to you, so if you created one and then delete your account, the group or challenge carries on under a new owner and keeps its picture. See section 8.

5.3 Stickers and GIFs

We do not host stickers or GIFs, and we do not copy them. A sticker in a Fitext chat is a pointer to KLIPY, and every phone that displays it fetches it from KLIPY at that moment. See section 4.3 for what KLIPY sees.

6. Reporting and moderation

You can report a message, a person, a group, a post, a recipe, a workout or a challenge from inside the app, and you can block someone, which stops their messages reaching you.

When you report a message:

• The report records the message itself, who sent it, which conversation it came from, and who reported it, so a person at Fitext can look at it and decide what to do.
• If the message had a photo or a video, a copy of that file is kept for up to 90 days, so that the evidence does not disappear under the normal 7 day rule while the report is still being handled.
• You can only report a message in a conversation you are actually part of.

We keep reports, and the blocks people have set, even after an account is deleted. Deleting a report would erase a complaint somebody else is relying on, and deleting a block would silently reconnect two people who chose to be apart.

7. How long we keep things

• Your account and profile: for as long as your account is open.
• Your activity records (runs, workouts, meals, weights, steps): for as long as your account is open, because they are your history.
• Messages: until you delete your account, unless they are removed sooner (a card that shared something its owner has since deleted is removed, for example). Removing a chat from your inbox hides it for you only: your messages stay for the other people in it, and there is no way to unsend one. Your synced chat with Lia also stays until then, because the app has no way to delete it.
• Chat photos and videos: 7 days on our servers. Up to 90 days if the message was reported. Indefinitely on the phones that already received them.
• Other pictures (profile, posts, recipes, workouts, groups, challenges, run maps): while the thing they belong to exists.
• Photos that belong to no entry (a photo of a scale, a photo that was read but never logged, the route map of a run you deleted at the end): today these are not removed when you delete your account. See section 5.2.
• Meal photos: with the entry in your food log, which today means until you delete your account. See section 5.2.
• Reports and blocks: kept after deletion, for safety. See section 8.
• Backups: we take backups of our database so that a failure does not lose everybody's data. The routine ones are kept for about a week and then replaced. We also hold a small number of one-off archival snapshots, taken before major maintenance, and those are kept until we retire them, which can be a long time. So a record you deleted can still sit inside a backup until that backup is discarded. We never use a backup to bring a deleted account back, and if we ever had to restore one after a disaster, we would apply the deletions again.

8. Deleting your account

There are two ways to do it. They end in the same erasure, but they do not start at the same moment, so we describe each one.

8.1 In the app, which takes effect at once

Open Settings from the inbox toolbar, tap Delete account, and confirm. Your account closes there and then. You are signed out, nobody can message you or find you in the app, and your email address is released immediately, so you could sign up again with it if you ever wanted to. The erasure itself follows and is finished within 30 days, and normally within minutes.

One thing can take longer. If something you made is still being used by other people, such as a workout that a live challenge is being scored against, it is held until that challenge ends and then deleted, so nobody is left competing against something that has vanished. Your account stays closed and unreachable throughout.

8.2 On the web, with no login and no reinstall

Use our account deletion request page. This route works differently, and the difference matters: the page records a request, it does not close the account by itself. Anyone can type anyone's address into a public form, so a person at Fitext checks the request first. Your account stays open and usable until that check is done, and the deletion is carried out within 30 days of your request. From the moment it is actioned, everything in 8.1 applies.

The page answers the same way for every address, so it cannot be used to find out who has an account. If you want your account closed this minute and you still have the app, use the in-app route.

8.3 What is deleted, and what is kept

Two things we want to be straight about. A group or a challenge you created does not disappear when you leave: ownership passes to another member so that the people still in it keep what they built. And other people's phones hold their own copy of your conversations. We remove your messages from our servers and ask the app on their phone to drop them too, but a device that never comes back online, and anything anyone saved or screenshotted outside Fitext, is beyond our reach.

9. Your rights and choices

• See what we hold: ask us and we will send you a copy.
• Correct it: most of it you can edit yourself in the app, in your profile and settings.
• Delete it: see section 8. You do not have to ask anyone's permission and you do not have to give a reason.
• Object or restrict: ask us to stop using your information in a particular way.
• Take it with you: ask for your data in a portable form.
• Notifications: turn them off in your phone's settings, or mute a conversation in the app.
• Location: revoke the permission in your phone's settings. Runs will still time you, they just will not map you.
• Photo library: Fitext does not ask to read it. Your phone's own picker hands the app only the photos you choose.
• Food analysis and barcode lookups: decline the consent prompt, and those features stay off.

To exercise any of these, write to yotam@fitext.com. We answer within 30 days. There is no charge, and we will not treat you differently for asking.

10. Security

• Everything the app sends travels over an encrypted connection (HTTPS and secure websockets). The app refuses unencrypted connections outright.
• Passwords are stored as bcrypt hashes. We cannot read your password, and neither can anyone who takes a copy of the database.
• Our database is encrypted where it is stored, and so are the files in our storage.
• Our application servers are not reachable directly from the internet; traffic passes through a gateway that terminates the encryption.
• Access to production systems is limited to the people who need it.

No system is perfectly secure, and we will not pretend otherwise. If we ever discover a breach that puts you at risk, we will tell you and the relevant authority as the law requires. Keep your password to yourself, and tell us if you think someone else has it.

11. Children and age

Fitext is not for children under 13, and we do not knowingly collect anything from them. We ask for your date of birth when you sign up. If you live somewhere that sets a higher minimum age for agreeing to online services on your own, which is up to 16 in parts of the European Economic Area, that higher age applies to you.

If you are a parent or guardian and you believe a child has given us information, write to yotam@fitext.com and we will delete the account and its data.

12. Where your data is processed

Fitext is run from Israel. Our application servers and our database run in Amazon Web Services in Frankfurt, Germany. Uploaded pictures and video are stored in Amazon Web Services in the United Arab Emirates and delivered worldwide through a content delivery network, which means a copy may be cached near whoever is viewing it.

The European Commission recognises Israel as providing an adequate level of data protection, which is the legal basis for information moving there. Where information goes somewhere without such a decision, which includes the region our pictures are stored in, the transfer is covered by the standard contractual clauses in our provider's data processing terms. By using Fitext you understand that your information is processed in these places.

13. EEA and UK users

If you are in the European Economic Area or the United Kingdom, the GDPR gives you the rights listed in section 9, plus the right to complain to your national data protection authority. Our legal bases are:

• Performing our contract with you: your account, your content, your messages, and the features you asked for.
• Your explicit consent: health and fitness data, which is a special category under Article 9, and location while you track a run. You can withdraw consent by turning the feature off or deleting your account, and that does not undo what was lawful before.
• Our legitimate interests: keeping the service safe, dealing with abuse and reports, and keeping the app working. We have weighed these against your rights and think they are fair.
• Legal obligation: when the law requires us to keep or hand over something.

For anything GDPR related, write to yotam@fitext.com.

14. California residents

If you live in California you can ask what personal information we collect and why, ask for a copy, ask us to correct it, and ask us to delete it. We do not sell your personal information and we do not share it for cross-context behavioural advertising. We will not discriminate against you for exercising these rights. Send requests to yotam@fitext.com, and we will answer within 45 days.

15. Changes to this policy, and how to reach us

If we change something that matters, we will say so in the app or by email, and we will move the date at the top of this page. Continuing to use Fitext after a change means you accept the updated policy. The current version always lives at fitext.com/privacy-policy.html.