Privacy Policy

Effective date: October 18, 2026
Last updated: October 18, 2026
Publisher: Fresh Pineapple LLC, a Wyoming limited liability company
Contact: [email protected]

Ola Wellness is a food, fasting, activity, sleep and cycle diary/log that lives on your iPhone. This policy says what the app does with your information, in plain words, and it is written to be checked against the app rather than trusted on its own. The short version:

• There is no account. We do not know who you are, and we have no server that holds your diary/log.
• Your data stays on your phone unless you choose one of the features below that send something out, each of which is off until you turn it on and says exactly what it sends and what we keep.
• If you share food photos or dictated meals, we keep a copy for up to 90 days to improve food recognition and our food database, tied to a random code and never to your name, your diary/log or Apple Health. You can delete what you shared at any time from Settings.
• If you turn on Kai, the chat assistant, each question you ask goes with a summary of your recent days to an AI model so it can answer. Our server never keeps that summary. It keeps your question and Kai's answer (and any photo you attach) for up to 90 days, tied to the same random code, to check and improve Kai, and you can delete them at any time from Settings.
• Ola is for adults 18 and over. We don't knowingly collect anything from anyone younger (section 4).
• We do not sell data, show ads, use trackers, or share anything for marketing. Health data is never used for advertising or for improving our food database, and is never stored in iCloud by the app.

1. What the app stores on your phone

Everything you log — foods, meals, water, weight, workouts, fasts, sleep, period days, notes, goals and settings — is kept in a database inside the app's own storage on your iPhone. It is protected by your device passcode and Apple's file protection like any other app data. We cannot see it, and it is not sent to us.

The app also keeps a small summary of today's rings (calories, steps, sleep, fast) in a shared container on the phone so its Home Screen widgets and Live Activity can draw it. That summary never leaves the device.

Backups

The app writes automatic backup files inside its own storage, and you can choose a second folder in the Files app to receive copies. Backups contain your whole diary/log, including data read from Apple Health, so:

• the in-app backup folder is marked so that iCloud device backup does not copy it;
• the app refuses an iCloud Drive folder as a backup destination and will say why;
• an export you make and share yourself goes wherever you send it — that is your choice, and outside the app's control.

Backups and exports are ordinary files. Anyone with the file can read it. Treat them as you would a copy of your diary/log.

2. Apple Health

If you turn on Apple Health in Settings, the app asks iOS for permission and you choose, type by type, what it may read. The app can read:

• steps, active energy, walking and running distance, and workouts
• weight
• water
• sleep
• menstrual cycle data

It uses these only to fill in the rings and cards you see, credit activity toward your calorie budget, track your cycle and draw your charts. Health data is processed on your phone and is not sent to us or to anyone else, with one exception you choose: if you turn on Kai (section 3d), the daily totals in its summary, some of which come from Apple Health (steps, sleep, weight, active energy credited), go with each question you ask it so it can answer. Our server passes the summary on and does not keep it. Kai's answers are kept for up to 90 days (section 3d), and an answer can repeat some of those numbers ("you slept 6 h 10 m"); they are used only to check and improve Kai, then deleted. Health data is never used for advertising or marketing, never sold, and never stored in iCloud by the app.

If you separately turn on write-back, the app writes weight, water, dietary energy and period days that you logged in Ola Wellness to Apple Health, so the Health app and other apps you allow can see them. It never writes sleep, steps or activity. You can turn write-back off at any time in Settings, and you can revoke any Health permission in the Health app or in iOS Settings; the app keeps working without it.

Data from a Garmin, Oura, Apple Watch or other device reaches the app only through Apple Health, under the same permissions.

3. The four features that send something off your phone

Each is off when you install the app. Each is a separate switch in Settings → Food lookup, and each can be turned off again at any time, which stops the sending immediately. Nothing else in the app talks to the internet, except an estimate you ask for inside one of them (3b-iii).

Who receives it. What a feature sends goes only to the companies named in that feature's section below (OpenRouter and Google for photos, voice and Kai; Open Food Facts, USDA FoodData Central and FatSecret for online lookups), and to the company we rent our server from, and only to run the feature you turned on. We only use providers whose terms protect your data at least as well as this policy does.

3a. Look up foods online

When on, searching for a food or scanning a barcode sends only the words you typed or the barcode number to nutrition databases so the app can show you matching foods:

• Open Food Facts (a non-profit; data under the Open Database Licence) — privacy
• USDA FoodData Central (United States Department of Agriculture) — contacted directly by the app, with a free API key you can add yourself — privacy
• FatSecret — reached through a relay server we operate (see 3c) — privacy

Foods you choose are saved to your phone. Nutrition content from FatSecret that its terms do not allow us to keep is removed from the phone within 24 hours unless you logged it.

Your diary/log, weight, Health data and identity are never part of a search. Search words are used only to find foods, so please don't type personal health details into the search box.

3b. Recognize food from photos

When you turn this on, the app first shows you a consent sheet and needs your agreement. After that, when you take or choose a photo on the camera screen, the app:

1. shrinks the picture and removes its location tag;
2. sends it to a server we operate (see 3c);
3. that server passes it to a third-party artificial-intelligence model — Google Gemini, accessed through OpenRouter — which returns a list of food names and rough portion sizes.

What we keep. Our server keeps a copy of the resized photo, with its location tag already removed, for up to 90 days, together with the list of foods the model returned and a random code the app makes on your phone. The code is not an account and is not linked to your name, your diary/log or anything from Apple Health; it exists so that you can ask us to delete what your phone shared (Settings → Food lookup → Delete my shared food data). We use the copy to improve food recognition and to build and check our food database, as other food apps do, and then delete it. What we learn from a photo — a food's name, a typical portion, the numbers printed on a label — may be kept after that, with nothing linking it to you. We do not sell these copies or give them to anyone else.

OpenRouter and Google handle the picture in order to answer the request under their own terms, which we do not control: OpenRouter privacy · Google privacy. Read them if this matters to you, and leave the feature off if you would rather no photo left the phone.

Calories and nutrients never come from the photo. They come from the food database or, for a food no database has, from an estimate you ask for (see 3b-iii). You confirm every item and portion before anything is logged. Photos are never used to identify you.

3b-ii. Log food by voice

When you turn this on, the app first shows you a consent sheet and needs your agreement. After that, when you press the voice button and describe a meal, the app:

1. turns your speech into text on the phone, using iOS's on-device speech recognition. The recording is never stored and never leaves the device. If your iPhone or language cannot do this on the device, the feature says so and does nothing rather than send audio away;
2. shows you the text, which you can edit;
3. only when you tap Find foods, sends that text to the same server as photos (see 3c), which passes it to the same model — Google Gemini, accessed through OpenRouter — to pick out the foods and amounts you named.

What we keep. As with photos, our server keeps the text, the foods returned and the random install code for up to 90 days, to improve how meals are understood and to grow our food database, then deletes them. OpenRouter and Google handle it under their own terms, linked above. Calories and nutrients never come from what you said. They come from the food database or, for a food no database has, from an estimate you ask for (see 3b-iii). You confirm every item and portion before anything is logged.

3b-iii. Estimates, only when you ask

When no food database and no web search has a food from a photo, a dictated meal or Kai, the app offers to estimate it. Nothing is sent unless you tap Estimate. The first time, the app tells you what will be sent and asks you to confirm; after that it remembers your answer. When you tap it, the app sends only the food's name and, if the photo suggested one, a weight to the same server (see 3c), which passes them to Google Gemini, accessed through OpenRouter, for a typical serving's calories and nutrients. No photo, diary/log, Apple Health data or anything else about you is sent. The request carries the random install code described in 3b, used only to apply the daily limit.

What we keep. Nothing: our server keeps no copy of the food's name or of the estimate, only a count that an estimate was made. OpenRouter and Google handle the request under their own terms, linked in 3b.

The estimate opens labelled as an estimate. You can change the name, the serving and every number, and it reaches your diary/log only when you tap Log. It is never added to the food database, and the entry stays marked as an estimate.

3d. Kai, the chat assistant

Kai answers questions about your own numbers ("why did my weight jump this week?"), and finds foods the app doesn't have yet. When you turn it on, the app first shows you a consent sheet and needs your agreement. After that, each time you ask Kai something, the app sends to the same server as photos (see 3c), which passes it to Google Gemini, accessed through OpenRouter:

• your question and the conversation so far;
• a summary of your recent days: about two months of daily calories, protein, carbs, fat, fiber, steps, sleep, water and fasting against your goals, your weigh-ins from the last 90 days, your goal, the notes you wrote on your days and weigh-ins, the last week of meals by name, your meal names, and, if you track your cycle, your cycle and symptoms;
• a photo, only when you attach one, resized with its location tag removed.

The summary contains no name, account, email or device identifier. It includes totals that came from Apple Health, which is the exception described in section 2.

To answer, Kai may look a food up in the app's own food list, in the online databases in 3a (only if "Look up foods online" is on), or on the web. A web search runs on our server through a search service (SearXNG) that passes only the search words, usually a food or product name, to public search engines. When nothing has a food, Kai offers an estimate instead (see 3b-iii). A food Kai finds is labelled with where it came from, and goes into your diary/log only when you tap Log. Kai cannot change your diary/log or the food database by itself.

What we keep. Our server keeps each question you ask and Kai's answer to it (with any foods it suggested) for up to 90 days, with the random install code described in 3b and nothing that names you, so we can check and improve Kai's answers. Then they are deleted automatically. An answer can include your own numbers, such as a weigh-in, a day's calories or last night's sleep, some of which may have come from Apple Health. The summary of your days sent with each question is not kept. If you attach a photo, a resized copy (location removed) is kept for up to 90 days in the same way, exactly as in 3b. Delete my shared food data removes all of it sooner. Phones whose owner agreed to Kai before this was added (consent version 1) have Kai switched off until they read the new wording and agree again; nothing from their chats was kept. OpenRouter and Google handle each request under their own terms, linked in 3b.

On your phone. Your chats are saved on your phone so you can pick them up later, with the photos attached to them. You can delete each past chat, and Delete all local data clears them all.

Kai is not a doctor and doesn't give medical advice; it's told to suggest talking to a clinician when a question is medical.

3c. The relay server

Requests to FatSecret, to the photo and voice model, and from Kai go through a small relay server that Fresh Pineapple LLC operates on a server rented from a hosting company. It exists so that the API credentials for those services are not inside the app. The relay:

• holds no accounts and no diary/log;
• does not store search terms or barcodes;
• stores, only for the photo, voice and Kai features and only for up to 90 days, the shared photos and dictated words described in 3b and 3b-ii and Kai's questions and answers described in 3d, in files readable only by the server's own account, with the random install code and the foods returned;
• separately keeps a log of how each request went, used to compare AI models: which model, how long it took, counts, and the food names that came back. It holds no photo, no words you typed or said, no Kai question or answer, no install code and no IP address, so nothing in it can be traced to you, and it may be kept after the 90 days;
• also receives, if you attach a photo in Kai, that photo, which is kept in the same way. The summary of your days sent with each question is not kept;
• runs Kai's web searches through a search service on the same server, which sends only the search words on to public search engines;
• keeps only brief operational logs (time, request type, and success or failure), with no IP addresses, search words, photos or messages in them. They are kept for troubleshooting for no more than two weeks and are not used to identify anyone;
• requires an access token, which the app sends with each request. The token is shared by copies of the app and proves a request came from it; it says nothing about who you are.

Fair-use limits. Kai, photo logging and voice logging have daily limits (and Kai an hourly one), so that one stuck or misused copy of the app cannot use up the service for everyone. They are set well above how people normally use the app. If you reach one, the app tells you when the feature will be ready again; search, barcode scanning and logging by hand are never limited. To apply them, the relay counts requests against the random install code, in memory, for up to a day, and can also count requests from one network (IP) address; the counts are never written to disk. We may change the limits.

4. What we do not do

• No account, sign-in, or profile.
• No advertising, no ad networks, no ad identifiers.
• No third-party analytics, crash reporting, or usage tracking. The app contains no third-party analytics or tracking code, and does not request permission to track. The only things we keep about how the app is used are the shared photos and words and Kai's questions and answers in section 3, and a server log of request outcomes with no personal content.
• No sale or rental of personal data, and no sharing of it except with the providers named in section 3, only to run the feature you turned on. We do not "sell" or "share" personal information as California law defines those words, including for cross-context behavioral advertising. Shared photos, words and Kai chats are not sold or handed to anyone else.
• No use of Health or fitness data for advertising, marketing, or data-mining, and no storage of it in iCloud by the app.
• No use by anyone under 18. Ola is for adults 18 and older, or the age of majority where you live if that is higher, as our Terms of Use require, and it is rated 18+ in the App Store. It is not directed at children or teenagers, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has shared photos, dictated meals or Kai chats with us, email [email protected] and we will delete them; the person can also delete them at once from Settings → Food lookup → Delete my shared food data (section 6).

5. Permissions the app asks for, and why

• Apple Health — to read the types in section 2 and, only if you enable write-back, to write the types listed there.
• Camera — to scan barcodes (processed entirely on the phone) and, only if photo recognition or Kai is on, to photograph a meal or a nutrition label.
• Photo library — only when you choose a picture for photo recognition or Kai; the app uses the system picker and sees only the picture you pick.
• Microphone and speech recognition — only while you hold the voice button to describe a meal, and only if voice logging is on. Recognition happens on the phone; the audio is not stored or sent.
• Notifications — for the reminders you switch on (meals, water, weigh-in, fasting). They are scheduled on the phone; no push server is involved.

Every permission can be declined or revoked in iOS Settings; the app continues to work without it.

6. Keeping, deleting and taking your data

• Retention: your diary/log stays on your phone for as long as you keep it; we hold none of it. Photos and dictated words you chose to share, and Kai's questions and answers, are kept by our server for up to 90 days and then deleted automatically.
• Delete what you shared: Settings → Food lookup → Delete my shared food data asks our server to delete every photo, dictated meal and Kai question and answer your phone has shared, and starts a new random install code. The server also deletes everything older than 90 days by itself.
• Delete some of it: swipe to delete any entry, meal, workout, fast or note.
• Delete all of it: Settings → Data → Delete all local data removes the database, backups inside the app, Kai's chats, settings and the widget summary from the phone, and asks our server to delete any photos, dictated meals and Kai questions and answers your phone shared. Deleting the app removes what is on the phone; use Delete my shared food data first if you also want the server's copies gone. Copies you exported or saved to a folder you chose are yours to delete.
• Take it with you: Settings → Data → Export local data produces a file containing everything in the app in a documented JSON format, which you can keep, move to another phone, or import into a later version.
• Withdraw consent: turn off Apple Health, online lookup, photo recognition, voice logging, Kai or write-back in Settings at any time. Revoking Health permissions in iOS has the same effect. Turning a switch off stops sharing from then on; to also remove what was already shared, use Delete my shared food data above. If our wording about what we keep ever changes, the app switches these features off and asks you again before sharing anything under the new terms.

7. Security

The database is stored in the app's sandbox under iOS data protection, and is protected by your device passcode, Face ID or Touch ID. All network connections the app makes use HTTPS; the app declares no exceptions to Apple's transport security. The relay server accepts only authenticated requests over HTTPS and holds no personal data beyond the shared items described in section 3. We use reasonable technical and administrative safeguards for what we hold, but no system is completely secure.

8. Ola Pro subscriptions

Ola Pro is bought through Apple's App Store, and Apple handles the payment. We never receive your name, Apple ID, email address or payment details. The app asks Apple, on your phone, whether you have an active subscription so it can unlock Ola Pro; that check does not go through our server, and we keep no record of who has subscribed. Apple gives us only the sales and trial figures it gives every developer in App Store Connect, which do not identify you. Billing, cancellation and refunds are handled by Apple under its own privacy policy and terms.

9. When you email us

If you email [email protected], we receive your email address, what you write and anything you attach, through our email provider. We use it only to answer you and to keep ordinary business records, and we keep it only as long as that needs. Ask us and we will delete it, unless the law requires us to keep it. Please don't send health details we don't need to help you. We don't add anyone to a mailing list.

10. When we may disclose information

The only information we hold is what sections 3 and 9 describe. We may disclose it if the law, a court order or other valid legal process requires it, or where it is needed to protect the rights, property or safety of our users, the public or Fresh Pineapple LLC. If Fresh Pineapple LLC is merged, sold or reorganized, that information may pass to the new owner, who must keep to this policy. Your diary/log isn't part of any of this, because we never have it.

11. Where information is processed

Fresh Pineapple LLC is based in the United States. What you choose to send us, and the providers named in section 3, may be processed in the United States or other countries, where data-protection laws may differ from where you live. We only use providers whose terms protect it at least as well as this policy does.

Links to other companies' sites and services, such as Apple, FatSecret or Open Food Facts, are governed by their own privacy policies.

12. Your rights

Your diary/log is not held by us, so your rights of access, correction, portability and deletion over it are ones you exercise directly on your phone using the tools in section 6. For photos and words you shared, you can delete them yourself from Settings, and the server deletes them after 90 days regardless. If you are in the European Economic Area, the United Kingdom, California or another place with a data-protection law and believe we hold anything about you, email [email protected] and we will respond. We will not treat you differently for asking.

13. Changes

If the app starts sending anything new off the phone, or changes who receives it, this policy will change first, the app will ask you again before doing it, and the "Last updated" date above will move. We will also point out important changes in the app or on our website. Earlier versions are available on request.

14. Contact

Fresh Pineapple LLC
Ola Wellness Support
[email protected]
olawellness.app/support

Ola Wellness is a personal tracking and planning tool. It does not provide medical advice. Check with a qualified healthcare professional before making changes to how you eat or fast.

This website

olawellness.app sets no cookies, runs no analytics or tracking, and has no sign-up forms or mailing list. It remembers whether you chose the Women or Men look in your own browser's storage; that choice never leaves your device. It is hosted by Cloudflare, which handles standard technical data such as IP addresses to deliver and protect the site. Fonts come from Google Fonts and some page code from public code libraries, which also see your IP address when your browser fetches them.