Frelia Privacy Policy

In this policy, "your phone" means the device you use Frelia on. If you use Frelia on a computer or in a web browser, the same rules apply to that computer or browser.

1. Where your data is read from and where it goes

This is the complete list. Anything not in this table stays on your phone.

Every connection the app makes over the internet uses HTTPS. As with any internet request, a service your phone connects to directly can see your phone's internet (IP) address.

Frelia's food-search server and live-tracking server run on Google Cloud in the United States. Neither stores your searches or your position (sections 6 and 7). The website and its early-tester list are hosted by Cloudflare (section 14).

2. What stays on your phone

Frelia keeps your data in its own private storage on your phone. This includes:

• Cycle and wellbeing (most sensitive): period dates, estimated cycle phases, symptoms, flare-ups, daily check-ins, life events and recovery days. Used to adapt training suggestions, protect your streak on period and recovery days, and show cycle insights. Frelia is not a contraceptive or medical tool. This data is never placed on a home-screen widget and is never sent to Frelia.
• Activity: workouts, GPS routes, pace, distance, elevation, heart rate, steps, training plans and routines.
• Food and water: your food diary, saved foods, energy and macro targets, nutrient estimates and water. If allergen and eating-preference settings are shown in your version of the app, they are stored on your phone too and never sent anywhere.
• Body and profile: your display name, date of birth, height, weight readings, progress photos, goals and experience levels.
• Safety contacts: the names and phone numbers you type in for trusted contacts. Frelia does not read your phone's contacts.

How it is protected: your data is protected by your phone's own app sandbox, storage encryption and screen lock. Frelia does not add a separate layer of encryption to the database on your phone, so keep your phone locked. Your backup passphrase and any WebDAV password are kept in your phone's secure key storage (Keychain on iPhone, Keystore on Android).

Phone backups: on Android, Frelia turns off Google's automatic app backup and device-to-device transfer, so the system never copies your Frelia data to Google. On iPhone, if you use Apple's iCloud Backup or back up your iPhone to a computer, Apple includes app data in that backup, including Frelia's. That backup is controlled by your Apple settings and Apple's privacy policy, not by Frelia.

3. Health Connect and Apple Health

Frelia asks for access only when you choose to connect, and only reads. It never writes, edits or deletes anything in Health Connect or Apple Health. On Android, Frelia requests these read permissions:

On iPhone, Frelia asks Apple Health for read access to steps, active energy, total energy and workouts, and, separately and only when you import your cycle history, menstrual flow.

What a cycle history import reads and keeps: Frelia reads up to two years (730 days) back. From menstrual flow records it uses only the calendar day and whether it was a flow day; days marked as spotting or no flow are skipped, and flow intensity is not stored. On Android it also reads Health Connect's menstruation period records, which give a period's start and end dates. From these Frelia works out your period start and end dates and stores only those, on your phone.

4. Location, the recording notification and sensors

• When location is used: Frelia uses GPS to record outdoor workouts, and your current position when you plan a route. It asks for location only "while using the app" and never asks for background location (ACCESS_BACKGROUND_LOCATION).
• While recording: on Android, Frelia runs a foreground service (foregroundServiceType="location") so your route keeps recording when the screen is locked, and shows an ongoing notification with your time and distance. Recording starts when you start a workout and stops when you finish or discard it.
• Last known position: Frelia remembers your most recent position on your phone so maps open in the right place. "Delete my data" removes it.
• Bluetooth heart-rate sensors: if you pair a heart-rate strap or watch that broadcasts heart rate, Frelia reads it during a workout. The connection is directly between your phone and the sensor.
• Battery level: read only to include it in live tracking while you share a link, so the person following knows if your phone is running low.

5. Camera, photos and label reading

Frelia uses the camera only for features you start yourself:

• Barcode scanning: the barcode is read on your phone. Only the barcode number is then looked up online (section 7).
• Nutrition label reading: you photograph a label and the numbers are read on your phone. The photo is held only in the app's private cache and is deleted as soon as it has been read. It is never saved to your photo gallery and never uploaded.
• Progress photos: you can attach up to three photos to a weight reading, from the camera or your photo library (a copy is kept inside Frelia). They stay on your phone. They are never uploaded, never included in an export or a backup, and "Delete my data" deletes them.

Label reading (and barcode reading on Android) uses Google's ML Kit, which runs on your phone. According to Google, ML Kit may send Google basic technical information, such as device model, app version and performance figures. It does not send the photo or the text it reads.

6. Safety check-in, SOS and live tracking

• Safety check-in and SOS: if you are overdue on a check-in or stop moving unexpectedly during an outdoor activity, Frelia shows a countdown and then prepares a message with your name and a Google Maps link to your last known position. You send it yourself through your phone's share sheet, to a contact you choose. Frelia does not send it through any server.
• Live tracking links: during a recorded activity you can choose to share a live-tracking link with someone you trust. Only while you are sharing, your position, GPS accuracy, speed, direction, distance, battery level, display name and any route you are following are sent to Frelia's live-tracking server (live.frelia.health) so the person with the link can follow you. The link contains a random code that cannot be guessed (128-bit); anyone who has the link can follow your activity until sharing ends.
• What the live-tracking server keeps: the current activity, in memory only. It never writes it to disk and never logs your position, the link code or your name. It forgets the session 5 minutes after you finish, after 30 minutes without an update, or after 2 hours at most, and you can stop sharing at any time.
• The page your contact opens: the live-tracking page loads its map from OpenStreetMap and its map software from unpkg.com, in your contact's browser.

7. Online food search and barcode lookups

Foods you have already saved are found on your phone without going online. Before your first online lookup, Frelia explains what will be sent and asks you to agree. When you search online or look up a barcode:

• What is sent: the words you searched for or the barcode number, and your food database region and language, so the results are foods you can buy. No name, no account, no location, and nothing from your diary, health or cycle data.
• FatSecret, through Frelia's food-search server: your search goes first to a small server run by Frelia (api.frelia.health), which passes it to FatSecret and returns the results. FatSecret sees Frelia's server, not your phone. Frelia's server does not record what you search for. It holds your phone's IP address briefly in memory to limit how many requests one address can make, and does not write it to disk or to its logs.
• Open Food Facts as a backup: if FatSecret has no result, or is unavailable, your phone sends the search or barcode directly to Open Food Facts, which can see your phone's IP address.
• Search suggestions while typing: off unless you turn it on in Settings → Data & Privacy. When on, the letters you type in food search are sent through Frelia's server to FatSecret as you type, to suggest foods.
• Saving a result: a food you look up is kept on your phone only if you choose to save it.

8. Maps, routes and elevation

• Map tiles: to draw a map, the app downloads map images (tiles) for the area on screen from Stadia Maps, or from OpenTopoMap if you choose that style. The provider can tell roughly which area you are looking at. Offline map packs are downloaded from Stadia Maps and stored on your phone; "Delete my data" removes them.
• Route suggestions and place search: when you ask for a route or search for a place, your start point (and, for some routes, a point along the way), the length you asked for, and any place name you type are sent to OpenRouteService. The route screen tells you this before you pick a start point.
• Elevation correction (off unless you turn it on): if you turn on "Correct elevation using terrain data", a simplified copy of each saved run's GPS route, including where it starts and ends, is sent to Stadia Maps once, after you save the run, to correct GPS altitude noise. With it off, nothing extra is sent.

9. Optional encrypted backup

Backup is optional and off unless you turn it on. When you use it:

• Encrypted on your phone first: your data is encrypted on your phone (AES-256-GCM) with a key made from a passphrase you choose, before anything is saved or uploaded. The passphrase and key stay in your phone's secure key storage and are never sent to Frelia or to the storage provider.
• Where it goes: only to a place you choose: a backup folder on your phone (removed if you uninstall Frelia), a backup file you save or share yourself, or a WebDAV server you specify (such as your own Nextcloud), reached over HTTPS with a password kept in your phone's secure key storage. Backup to Google Drive and iCloud is planned and will follow the same rules. Frelia does not run a backup server and never receives your backup.
• What is in it: all your Frelia data, including cycle and wellbeing data, except progress photos. A few details are visible without the passphrase: the date and time the backup was made, its size, how many records it holds, and its format version. On a WebDAV server, backups go in a folder named with a random code for your phone.
• Who can read it: without your passphrase, nobody can read the backup, including Frelia, Google, Apple or your storage host. If you forget your passphrase and your phone is lost, the backup cannot be recovered by anyone.
• Deleting backups: "Delete my data" removes your passphrase, your backup settings, your WebDAV password and the backups kept on your phone. It cannot reach backup files you saved elsewhere or files on your WebDAV server; delete those there if you no longer want them. Your storage provider's own terms and privacy policy apply to files you keep there.

10. Payments and subscriptions

• Who handles payments: purchases are made through Apple's App Store or Google Play, and are processed by Apple or Google under their own terms and privacy policies. Frelia never sees or stores your card details.
• Subscription status: Frelia uses RevenueCat to check which subscription you have. RevenueCat receives an anonymous, randomly generated app user ID and your purchase records from Apple or Google. Frelia does not send RevenueCat your name, email address or any other details about you, and has turned off device-identifier collection.
• No health data: no health, cycle, location, food or workout data is ever sent to Apple, Google or RevenueCat for payments.
• On your phone: the app keeps a copy of your subscription status so Premium features work offline. "Delete my data" clears it; it does not cancel a subscription, which you manage in your App Store or Google Play account.

11. Home-screen widgets

• What they show: if you add a Frelia widget to your home screen, it can show today's water, energy and macros, steps, your week's training, your next workout, or your check-in energy. Anyone who can see your home screen can see what your widgets show; remove a widget at any time to hide it.
• No cycle data: no cycle or reproductive health data, and no symptoms, are ever placed in a widget.
• On your phone only: widget information is written to your phone's local storage for the widget to read. It is not sent anywhere. Logging water or energy from a widget saves straight into Frelia on your phone.

12. Things you choose to share

Some features let you send something to another app or person. Nothing is sent until you pick where it goes and send it:

• Workout and recap pictures: cycle details are left off unless you turn them on for that picture. A route outline leaves out the first and last few hundred metres, to help keep places like your home private.
• Challenge codes: a code holds the challenge, the name you chose, one progress percentage, a date and a random tag. It never holds anything about your cycle, symptoms or recovery days.
• Safety messages and live-tracking invites: see section 6.
• Activity files: you can save a workout as a GPX or TCX file, which contains its GPS route.
• Feedback and bug reports: these open a draft email to support@frelia.health in your own email app, with the app version and platform filled in. You can edit it before sending. If you send it, we receive your email address and what you wrote, and use them only to reply and fix problems.

13. Your data: export, import and deletion

• Save a copy of your data: from Settings → Data & Privacy you can export your data at any time as a JSON file saved where you choose. Cycle and wellbeing data is left out unless you tick the box to include it. Progress photos are never included.
• Import: you can bring data in from a Frelia export, a backup, GPX or TCX activity files, or a cycle history file from another app (such as Clue, Flo or a spreadsheet). Imported files are read on your phone.
• Delete my data: Settings → Data & Privacy → Delete my data permanently deletes all your Frelia data on your phone: every diary and record, progress photos, offline map packs, your last known position, trusted contacts, your choices about what may be sent online, your backup passphrase, backup settings and the backups kept on your phone, and the cached subscription status. It cannot be undone.
• Copies outside the app: deletion on your phone cannot reach copies that already exist elsewhere: an export file you saved, something you shared, a backup on your WebDAV server, or an Apple device backup. Those are yours to keep or delete. Frelia holds no copy of your app data on its own servers; the only personal data Frelia stores on a server is the website's early-tester list (section 14), which is separate from the app.

14. Early-Tester Discount List (Website)

Separately from the app, the Frelia website (frelia.health/early-access) offers a form to join the early-tester beta group and discount list. This section covers that list; it does not describe the app itself.

• Collected by: Jarrod Franz, for Frelia.
• What is stored: the email address you submit, your selected mobile platform (Android or iOS), the date and time you submitted it, and which version of the consent wording you agreed to. No name, and no other personal details are collected by the form.
• Purpose: to invite you to the Frelia private beta on your platform (via Google's tester tools or Apple TestFlight) and to send you the early-tester subscription discount when Frelia subscriptions launch. (The early-tester discount code is valid for 3 months from subscription launch; if not claimed within 3 months, it expires.) This list is never used for newsletters or any other marketing.
• Notifications: upon submission, a notification email is sent to support@frelia.health with your submitted email and platform so you can be added to the appropriate beta testing track.
• Where it is stored: Cloudflare D1, a database provided by Cloudflare, our website hosting provider, located in Cloudflare's Oceania region. Cloudflare may still process the request itself through data centres outside Australia, as part of the normal operation of its content-delivery network, even though the database's storage location is pinned to Oceania.
• Your IP address: used momentarily by Cloudflare and by the form itself to prevent abuse (rate limiting) and is never stored.
• Not connected to the app: the app itself remains account-free. This email list exists only on the website's infrastructure and is never linked to any on-device data, activity, or cycle information.
• Never sold or shared: the email list is never sold, rented, or shared with any third party.
• Retention backstop: if Frelia subscriptions haven't launched within 18 months of the early-access form going live, the whole list is deleted.
• Backups: if an entry is deleted - by your request, or by the retention backstop above - it may still exist in Cloudflare's point-in-time backups for up to 30 days before it is gone for good.
• Access and correction: you can ask what is held about you on this list, or have it corrected, at any time.
• Removal: email support@frelia.health at any time and we will remove your address, no explanation needed.

15. Children's Privacy

Frelia is intended for adults aged 18 and over. It is not intended for anyone under 18, and we do not knowingly collect or solicit personal information from anyone under 18. Because Frelia has no accounts and keeps your data on your phone, we hold no personal information to delete; if you believe a child is using Frelia, uninstalling the app or using "Delete my data" removes everything it stored.

16. Changes to this Policy

If we update this Privacy Policy, the revised version will be published here with an updated effective date. If a change affects how health data is handled, we will tell you prominently in the app before it takes effect.

17. Contact Us

If you have any questions, concerns, or feedback regarding this Privacy Policy or your data privacy, please contact us:

• Developer & Maintainer: Jarrod Franz
• Project: Frelia (Women's Running, Fitness & Nutrition)
• Email: support@frelia.health
• Repository: github.com/JarrodFranz/Womens-Fitness-App

© 2026 Frelia. All rights reserved. Built with privacy, dignity, and scientific integrity.