Privacy Policy

Effective date: October 18, 2026
Last updated: October 23, 2026
Publisher: Fresh Pineapple LLC, a Wyoming limited liability company
Contact: contact@freshpineapple.co
Mailing address: 5830 E 2nd St, Ste 7000, Casper, WY 82609, USA (our registered agent)

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.
• Our server keeps nothing you send for food photos, dictated meals or Kai unless you turn on a separate switch, Help improve Ola. It is off by default and no feature needs it. If you turn it on, we keep food photos and dictated meals 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. Kai's questions and answers are never kept. You can turn it off and delete what you shared at any time from Settings.
• The AI model never trains on what you send. Photos, dictated meals and Kai go to Google Gemini through OpenRouter, and every request is set so that it can only reach Google's own endpoints. OpenRouter keeps nothing after answering. Google may keep a request for a limited time to check it for abuse of its rules, which it calls safety retention (section 3).
• Food facts help build our own food database. While any online feature is on, the app shares facts about packaged foods: barcode, brand, name, the label's numbers, serving sizes and corrections people make. These are sent without your install code, kept with nothing that links them to you, and never include your diary/log, photos, words or Apple Health data. The facts themselves are never published; rows about products built from many of them may be, and corrections to Open Food Facts products go back to Open Food Facts. You can switch this off in Settings (section 3e).
• 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 your question, Kai's answer or that summary; the AI model doesn't train on them, though Google may keep them for a limited time for safety checks (section 3). With Help improve Ola on, our server keeps only a photo you attach, for up to 90 days, as with any food photo.
• 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, and the AI model answers without training on it, though Google may keep the request for a limited time for safety checks (section 3, Who receives it). 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 Apple's own services that check the app is genuine and whether you subscribe (3c and section 8), an estimate you ask for inside one of the features (3b-iii), and, while at least one of them is on, the food facts described in 3e. With all four off, nothing of yours leaves your phone.

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; the public search engines in 3d for Kai's food searches; 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. Every request to the AI model is set so that OpenRouter may send it only to Google's own Vertex AI endpoints, never to another company serving the model, and only to endpoints that never train on what you send. OpenRouter keeps nothing after answering. Since October 18, 2026, Google requires that it may keep requests to its Gemini models for a limited time to check them for abuse of its usage policies, which it calls safety retention. Google does not say how long, and does not use them to train its models. We cannot turn this off and still use Gemini. Our server refuses to start if it is pointed at any other model or company, so this can't change without this policy changing first (section 13).

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) — reached through the same relay server (see 3c), which holds the key, so there is nothing to set up — 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. By default, nothing: our server passes the photo on to answer your request and does not keep it. If you turn on Help improve Ola (a separate, optional switch in Settings → Food lookup, also offered when you first allow photos), 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 passes the picture to Google, which answers without training on it and may keep it for a limited time for safety checks (section 3, Who receives it). Their own terms also apply: OpenRouter privacy · Google privacy. 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: nothing by default. With Help improve Ola on, 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 exactly as they handle photos (3b). 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 exactly as they handle photos (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, and your meal names;
• your cycle and symptoms, only if you also turn on Let Kai see my cycle (Settings → Food logging). It is off by default, has its own consent screen, and goes off whenever Kai does. Then Kai also gets your life stage, the day and phase of your cycle, when your next period is expected, your cycle lengths over the last year, and the last two months of flow days, symptoms and the notes on them;
• 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), which passes a short search phrase to public search engines such as Google, Bing and DuckDuckGo. The AI model writes the phrase and is told to use only a food or product name. Our server refuses to send a phrase that mentions health, body figures, conditions or medicines, but the check works on words, so don't ask Kai to search for anything about yourself. No code, address or other identifier goes with the phrase. 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 never keeps your questions, Kai's answers or the summary of your days, whatever your settings. If you turn on Help improve Ola and attach a photo, a resized copy (location removed) is kept for up to 90 days, exactly as in 3b, and Delete my shared food data removes it sooner. Questions and answers kept under this policy's earlier wording, before October 19, 2026, are deleted within 90 days of being sent, or sooner with Delete my shared food data. OpenRouter and Google handle each request exactly as they handle photos (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. Kai can't tell you whether a food is safe for an allergy or free of an ingredient; always read the product's label (see our Terms of Use, section 5A).

3e. Food facts for Ola's food database

We're building our own food database, so that Ola depends less on outside food services. A database is made of facts about foods, and a packaged food's facts are the same whoever scans it. So, while at least one online feature is on, the app shares:

• products: for a packaged food with a barcode or a brand that you log from Open Food Facts or USDA, a label Ola read for you, or a food you created with a barcode: the barcode, brand, name, serving size and the nutrition numbers per serving;
• corrections: when you change the calories or nutrients of such a food, or a portion that photo, voice or Kai guessed, the field, the old number and the new one;
• missing barcodes: a barcode no source had, on its own.

What is never in a food fact: your name, the random install code, any other identifier, your network address, the time (only the day is kept), which meal or day you ate it, how much you ate, your notes, photos, words you said, anything from Apple Health, or any food without a barcode or brand (so a home recipe is never shared). Results from FatSecret are never shared as products.

How it's sent. Facts wait on your phone and go in small batches at most once a day at a random time, so a batch can't be tied to a meal. They are sent without your install code. The server checks that the request comes from a genuine copy of the app (3c), uses your network address and the app's security pass only to apply limits, in memory, and then keeps only the facts, each with the day it arrived. A phone sends an identical fact at most once a year, so the facts don't show how often anyone eats a food. Because they aren't about a person, we keep them with no time limit.

We do not try to work out who a food fact came from, and the facts stay with us. They are kept on our server (3c). We never publish them as they arrived, and we would give them to anyone else only after that recipient agreed in writing to keep them deidentified and not to try to work out who they came from.

What we may publish. We use the facts, combined with facts from many people, to build and check Ola's food database. The database is made of rows about products: a barcode, brand, name, serving size and nutrition numbers. A row never carries a date, a count of how many people logged the product, or anything about who did, and a row is shown to anyone else or published only once at least three separate facts agree on it. We may use these rows in the app, publish them and license them to others.

Open Food Facts. Part of the database starts from Open Food Facts' data, which they share under the Open Database Licence. That licence requires changes to their data to be shared openly, so corrections to Open Food Facts products are published under that licence and sent to Open Food Facts from Ola's own account. Only product rows, as above, are shared: never anyone's individual fact. Anyone may use those rows on the licence's terms, which is why nothing in them can point to a person. Open Food Facts handles what it receives under its own privacy policy.

Turning it off. Settings → Food lookup → Share food facts is on by default; turn it off and nothing more is sent. Facts already shared can't be found again, because nothing links them to you.

3c. The relay server

Requests to FatSecret and USDA, 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 the barcodes you search for, except as the food facts described in 3e. To avoid asking USDA the same thing twice, and to keep search working when USDA is unavailable, it keeps USDA's answers on the server for up to a year, filed under a one-way code made from the search words rather than the words themselves, with nothing about who searched. An answer is refreshed from USDA after 30 days;
• stores, only with Help improve Ola on, and only for up to 90 days, the shared photos and dictated words described in 3b and 3b-ii and photos attached in Kai (3d), in files readable only by the server's own account, with the random install code and the foods returned. It never stores a Kai question or answer;
• keeps the food facts described in 3e, with nothing that identifies you;
• 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, no IP address and no link to any kept photo or words, so nothing in it can be traced to you, and it may be kept after the 90 days;
• never keeps the summary of your days sent with each Kai question;
• runs Kai's web searches through a search service on the same server, which sends only the search phrase on to public search engines (3d);
• 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 proof that each request comes from a genuine copy of the app. The server checks this with Apple's App Attest, which tells it that the request comes from an unmodified copy of Ola on a real iPhone, and then gives the app a short-lived pass to show with each request. The pass holds a random code for that copy of the app (not for you) and whether Ola Pro is active; the server neither stores nor logs it. Copies of the app that we test with use a shared access token instead. Neither says anything 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 (or, for copies of the app that App Attest has vouched for, against a scrambled form of that copy's App Attest 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 in section 3 (only with Help improve Ola on), 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 and words 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 training of AI models. We don't collect, use or sell personal data to train large language models, and the AI model we use doesn't train on what you send (section 3). Photos and words kept under Help improve Ola are used to test and tune how we ask the model, not to train one.
• 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 or dictated meals with us, email contact@freshpineapple.co and we will delete them; the person can also delete them at once from Settings → Food lookup → Delete my shared food data (section 6).

The website, and Do Not Track

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.

Do Not Track. Neither the app nor the website tracks you over time or across other sites and apps, and we don't allow anyone else to collect information about your activity across sites through Ola. So Ola does nothing different when your browser sends a Do Not Track or Global Privacy Control signal: there is no tracking to turn off.

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. Only if you turn on Help improve Ola, photos and dictated words you send (including photos attached in Kai) are kept by our server for up to 90 days and then deleted automatically. Food facts (3e) are kept with no time limit because nothing in them links to you.
• Delete what you shared: Settings → Food lookup → Delete my shared food data asks our server to delete every photo and dictated meal your phone has shared, and starts a new random install code. The server also deletes everything older than 90 days by itself. OpenRouter keeps nothing after answering. Google may keep a request for a limited time for safety checks (section 3); that copy is Google's, and we can't delete it for you.
• 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 and dictated meals 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, Let Kai see my cycle, Share food facts 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. For the features that use our relay server (photo, voice and Kai), the app also sends Apple's signed subscription record to the server, which reads it to see whether Ola Pro is active and then discards it; it is not stored or logged, 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 contact@freshpineapple.co, 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.

If anyone asks us for information about a person's reproductive or sexual health, we will disclose it only if a valid order from a court with authority over us requires it, we will challenge requests we believe are not lawful where we can, and we will tell the person first unless the law forbids 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. The AI model is reached only through the Google Vertex AI endpoints described in section 3.

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 live in Washington, Nevada, Connecticut, California, the European Economic Area, the United Kingdom or another place whose law gives you rights over health or personal data, you can also ask us to confirm what we hold about you, give you a copy along with a list of every company we shared it with and how to contact them, correct it, delete it, or stop using it, and you can withdraw any consent you gave. Email contact@freshpineapple.co. Because there is no account, include your phone's install code (Settings → Food lookup → Install code; tap it to copy) so we can match what it shared. We answer within 45 days; if we need more time we'll tell you why, and take no more than 45 days more. If we turn your request down, you can appeal by replying "appeal" to our answer: we decide an appeal within 45 days and, if we still say no, tell you how to complain to your state's attorney general or data-protection authority. There's no charge, and we won't treat you differently for asking.

Our Consumer Health Data Privacy Policy sets out the same information in the form Washington's My Health My Data Act and Nevada law ask for.

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
5830 E 2nd St, Ste 7000
Casper, WY 82609, USA
contact@freshpineapple.co
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.