Privacy

What AYRLI knows about you.

Last updated 21 October 2026. AYRLI is early software and this page changes when the app does.

The short version

Location is used for three things: noticing when you arrive at and leave your gyms, recording the route of a run or walk while you are recording one, and one-off readings when you check in by hand or look for a gym. Gym visits are stored as times, not coordinates. A run’s route is stored, and only you can see it.
Your sessions are visible to the people in your crews. That is the point of the app. Your posts and stories go to your friends and crews unless you choose otherwise.
Your measurements, progress photos, workout log and run routes are private to you. Apple Health is off unless you turn it on, is read-only, and adds nothing without your yes.
There are no ads and no third-party analytics or tracking SDKs, and nothing is sold to anybody. The app does keep its own error reports and a short list of usage counts, in its own database.
Your data sits in a database in Sydney. A few named services handle specific pieces of it, and they are listed below.
You can delete your account, and everything in it, yourself, from inside the app.

Who you are dealing with

AYRLI is operated by Perpetuate Life Pty Ltd (ABN 53 689 899 894, ACN 689 899 894), a company registered in Queensland, Australia, and built in Brisbane. That company is responsible for your information under the Australian Privacy Principles. On this page, “AYRLI” and “the developer” mean it. It is a small team with no marketing department. For anything on this page — a question, a correction, a complaint, or a request for your data — use the contact form. What you send through it is stored in AYRLI’s database and forwarded to the developer by email.

Location: exactly what happens

AYRLI asks for the "Always" location permission, which is the strongest one iOS has, and it is fair to be suspicious of that. Here is everything it does with location.

Checking in at the gym

The app registers a geofence — a circle of between 50 and 500 metres — around each gym you have added. iOS watches those circles, not the app. When you cross into one, iOS wakes AYRLI in the background and hands it one fact: "entered". When you cross out, it hands it "exited". The app turns those two facts into a session with a start time and an end time.

A gym visit is stored as a gym and a time, never a coordinate. The geofence does not keep a trail of where you went.
The gym’s pin is a coordinate, and it is one you choose. If you add a gym and tap “use my current location”, that reading is saved as the point the check-in circle is drawn around. You can move the pin or type an address instead.
Your crew can be told you have arrived. If you are still at the gym five minutes after crossing in, your crew-mates can get a notification saying so. They are told which session, not where you are.
If you say no to "Always", check-in still works. AYRLI shows a check-in button instead. Tapping it takes a single position reading and sends it to the server to confirm you are actually at the gym; that reading is answered yes or no and is not stored.

Recording a run or walk

This is the one place AYRLI follows you, and only while you have asked it to. When you start a run or walk, the app takes a position reading every couple of seconds — including with the phone locked in your pocket, which is what background location is needed for. iOS shows its blue location indicator the whole time. It stops when you end the run.

The route is saved. When you finish, a simplified version of the route is stored against your account, along with distance, time, moving time and kilometre splits.
Only you can see the route. The database lets the owner of a route read it and nobody else — not your crew, not your club, not your friends. Your crew sees that you did a run or walk and how far and how long, the same as any other session.
It leaves only if you send it. If you make a share card from a run and share it, the card carries the map. It shows the whole route, including where you started — so if a run starts at your front door, so does the card.
Deleting your account deletes every route, by name, in the same step as everything else.

One-off readings

A single reading is also taken when you open the map to set or move a gym’s pin, when you look for clubs near you, and when the run screen first opens, so the map starts where you are. None of those readings is stored. Where one goes to Google to find gyms nearby, it says so below.

What is stored

Your account	Your email address and password, or your Apple ID, which is how you sign in. Sign-in by mobile number is built and will be switched on after release: when it is, we text a code to your number, one number can hold one account, and this page will say so before it is on. Handled by Supabase Auth; a password is stored hashed and AYRLI never sees it. Your number is never shown to other people and is never used for marketing. If an account is suspended for breaking the rules, a one-way hash of its number is kept so it cannot be used to sign up again, even after the account is deleted.
Your profile	Your handle, display name, full name, a short bio, your profile photo and cover photo, who can see your profile, your weekly session target, which crews and clubs you are in and your role in them, and your notification and privacy choices.
Getting in	The invite code you came in on, if any, or your request for one. If you chose “Join the AYRLI list” to get in, that you agreed, when, and the exact sentence you agreed to — so AYRLI can email you news. You can get off the list through the contact form.
Sessions	Start and end time, length, which gym, whether it came from the geofence or you added it by hand, the type (full, run, walk, rehab, recovery, cardio), what you were training, which plan it came from, where it happened (gym, home, physio or elsewhere), a distance if it has one, a title if you give it one, and a note if you write one.
Runs and walks	For one you recorded in the app: the route, distance, elapsed and moving time, kilometre splits, and a count of the GPS readings that were thrown away as inaccurate. For one you added from Apple Health: its route, distance and times.
Apple Health offers	Only if you turn Apple Health on: the runs and walks found there, each with its start and end, type, distance and energy burned, and whether you added it or said no. See Apple Health.
Workout log	Exercise names, sets, reps, weights, what kind of set it was, and personal bests.
Measurements	Whatever you choose to log: weight, body fat, chest, waist, hips, shoulders, arms, thighs, calves, neck — with the date, and any target or goal you set.
Progress photos	The photo, the date, and which pose it is.
Plans and schedule	The workout plans you make or save, which days they are on, days you skip, crew sessions you say you are going to, and events you put on or sign up for. If you submit a plan to the shared shelf and it is approved, it is shown to everyone with you named as its author.
Posts and stories	Your photos and captions, the club a post is tagged with, a song if you add one (its title, artist, artwork and preview link from Apple’s catalogue), likes and replies, posts you save, and who viewed your stories.
Messages	What you write in crew, club and direct chats, and any photo you send in one.
Friends and safety	Who you have sent a friend request to, who has sent you one, who accepted, who you have blocked, and reports you have made.
Music	Only if you connect Spotify: the track you are playing, its artist and artwork, and when you last played something. One row, replaced each time — not a history.
Notifications	Your phone’s push address (an Expo push token), and notifications queued for you until they are sent.
Errors and usage	See Errors and usage below.

Health information

Measurements, progress photos, a session labelled rehab, anything you write in a session note, and workouts read from Apple Health are health information, and Australian privacy law treats them as sensitive. They are stored because you put them in or asked for them to be read, and nothing in the app shares them anywhere unless you specifically say to.

Apple Health

AYRLI can add the runs and walks you record on a watch or another app. It is off until you turn it on, with the Apple Health switch in You → Account, and iOS then asks which permissions to give.

What it reads, and only reads. Workouts and their routes. AYRLI never writes anything to Health and does not ask for permission to.
What it keeps. Of the workouts it finds, only runs, walks and hikes of 10 minutes or more are kept, starting from the fortnight before you turned it on. Each one is saved to your account as an offer: when it started and ended, what kind of workout it was, the distance and the energy burned. No route is saved at this stage.
Nothing is added unless you say so. Each offer is shown on Today, and it only becomes a session if you tap Add. Then its route is read from Health and saved the same way as a run recorded in AYRLI — visible to you and nobody else — and the session itself is seen by your crew like any other run or walk. If you say no, that is remembered and it is never offered again.
What it is used for. Showing you your own training, and nothing else. Health data is not used for advertising or marketing, is not sold, and is not shared with any third party.
Turning it off. Switching it off in AYRLI stops it reading. Runs you already added stay. To take the permission away completely, change it in the Health app. Deleting your account deletes the offers and every route along with everything else.

Voice set logging

You can say your sets out loud instead of typing them. AYRLI asks iOS to turn your speech into words on the phone; the audio is never recorded or uploaded by AYRLI. The words are then sent, through AYRLI’s server, to Anthropic’s API, which reads them into exercises, sets, reps and weights. Along with the words go the sets you have already logged in that session, so “same again” means something. Your name and account are not part of that request. AYRLI keeps the sets that come out of it, not the transcript. If that service cannot be reached, the phone reads the words itself and asks you before saving anything.

iOS shows its own sentence on the speech permission — that speech data is sent to Apple to process requests. That sentence is Apple’s, and AYRLI cannot change it. What AYRLI does is ask for on-device recognition, which iOS honours by failing rather than quietly sending audio off the phone.

Who can see what

This is enforced in the database itself, rather than by the app remembering to be careful. The rules are:

Only you	Your run and walk routes, your Apple Health offers, your workout log (apart from new personal bests, below), your measurements and targets, your progress photos, your schedule and your saved posts. Who viewed your story is shown to you and nobody else.
Your crews	Your sessions — that you trained, when, for how long, at which gym, what you called it and how far, if it was a run — and the crew feed, which includes a new personal best (the exercise and the weight). The crew sessions you say you are going to, and when you arrive at the gym for one. Session rows also hold your note: the app never shows one person’s note to anybody else, but treat it as readable by your crew.
Your friends	Whether you are training right now and at which club, when you were last active, and — if you have connected Spotify — what you are playing or last played.
Your clubs	Other members of a club you have joined can see you in its member list and leaderboard: whether you are training there now and how many sessions you have done there. Each club has its own setting for whether they see your real name and photo — everyone, friends only, or nobody, in which case you appear as “Member” and still count toward who is training. You choose it when you join and can change it in that club’s settings.
Your profile, posts and stories	One setting decides all three. Friends (the default) means your accepted friends and anybody in a crew with you. Public means anybody signed in to AYRLI. Private means nobody, and nobody new can send you a friend request. Replies under a post have the same audience as the post. Changing the setting changes it for everything you have ever posted. A story disappears from view after 24 hours.
Messages	The people in that chat: your crew in a crew chat (a new member sees only what was said after they joined), the members of a club in a club chat, and the two of you in a direct chat. Messages are stored on AYRLI’s server, not end-to-end encrypted.
Anyone signed in	Anybody with an AYRLI account can find you by typing the start of your handle, and will see your handle, display name and profile photo in the result — whatever your profile setting. A public plan you wrote shows your name. Nothing about you is shown on the web: there is no web view of anybody’s profile or training.

A block works both ways and beats every setting above: the two of you stop seeing each other in crews, clubs, search, the feed and stories, and neither of you can message the other.

Private mode

If you would rather a crew not know it is you, private mode replaces your name and photo with a generated alias — "Ghost 47" — for everyone in that crew. Your sessions, your presence and your streak all keep counting. The people who still see the real you are you and anyone whose friend request you accepted. The crew owner and admins get no back door.

A note about photos

Progress photos, post photos, story photos and photos sent in chat are kept in private storage, and each can only be fetched by the people allowed to see the thing it belongs to. Your profile photo and cover photo, a crew’s cover photo and a club’s cover photo are different: they sit in public storage, so anyone who has the exact URL can load them without signing in. The URLs are long and are not published anywhere, but they are not secret. Do not put anything in a profile photo you would mind a stranger seeing.

Share cards

The share-card editor builds the picture on your phone. Photos and clips you pick from your library are used there and are not uploaded. Filters, and the optional face retouch, run on the phone using Apple’s own image frameworks; nothing about your face is uploaded or stored. A card in progress is saved on the phone so you can come back to it. The finished card goes only where you send it from the iOS share sheet.

Errors and usage

AYRLI has no third-party analytics, crash reporting, advertising or tracking SDKs. It does keep two small records of its own, in its own database:

Error reports. When something in the app fails, it records what failed, where in the app, the app version and iOS version, and which account it last happened to. Identical errors are grouped and counted. The first time a new kind of error appears, the developer is emailed a description of it. What you were typing is never part of a report.
Usage events. Five moments are noted against your account: signing up (with your handle — the developer is also emailed when somebody new signs up), starting a session (whether it came from a plan, its type and where), logging a set (which exercise and what kind of set), making a post (whether it had a photo and whether it was tagged to a club), and sending a message (that one was sent — not what it said). They are used to count how much the app is used.

Neither is shared with anybody. When you delete your account, both stop being linked to you: the counts stay, the account they pointed to does not.

Notifications

Some notifications are scheduled by your own phone, with no server involved: reminders before a session, a nudge to review a session, and the check-in and check-out banners.

Others are about what other people did, so they have to come from a server. If you allow notifications, the app stores your phone’s push address, and AYRLI sends notifications through Expo’s push service and Apple’s for: a new message in one of your chats (with a preview of the message), a friend request, a like on your post, a crew-mate checking in for a session you are going to or arriving at the gym, being added or invited to a crew, and a few things about plans and invite codes. Likes, check-ins and arrivals can each be switched off in the app’s notification settings, and all of them can be switched off in iOS Settings.

Who else touches your data

Each of these gets only the piece described, and only when you use the feature it belongs to.

Supabase runs the database, the sign-in, the file storage and the small server functions. The project is hosted on AWS in ap-southeast-2, Sydney. Account emails — a password reset, or confirming a changed address — are sent through Supabase Auth.
Apple, if you use Sign in with Apple; for delivering the app through TestFlight or the App Store; for delivering push notifications; for speech recognition (see voice above); for the map on the run screen and run summary, which is Apple Maps; for naming where a run started, which asks Apple’s geocoder about the first point of the route; and when you add a song to a post, for searching Apple’s music catalogue with what you typed and playing its 30-second preview.
Google Maps Platform, in three places. When you search for a gym, what you typed goes to Google, with a 20 km circle around you if the app knows roughly where you are, so the gym down the road ranks first. When you look for clubs near you, your position and a 20 km circle go to Google. When you type a gym’s address, the address goes to Google to place the pin. And when you make a share card for a run, the map behind it is fetched from Google as an image: Google is sent the centre point and zoom of that map, not the route, which is drawn on the phone. Nothing about your training is sent.
Twilio, for sign-in codes: your number, to check it is a mobile rather than an internet or landline number, and to text the code. Nothing else about you is sent.
Anthropic, for voice set logging: the words of what you said, and the sets already logged in that session. Not the audio, and not your name or account.
Expo, for push notifications: your phone’s push address and the text of each notification sent to you.
Resend, which delivers email to the developer: alerts about new errors and new sign-ups (your handle), and messages from the contact form on this website (your name, email address and message).
Spotify, only if you choose to connect it. You approve the connection on Spotify’s own screen, and AYRLI asks for one permission: to read what is currently playing. The sign-in tokens Spotify gives back are kept in your phone’s keychain, not on AYRLI’s server. Disconnecting removes them and clears what your friends see.
Vercel hosts this website.

These are overseas companies, so the pieces listed against them are handled outside Australia. That is the whole list. Nothing is sold, and nothing is shared with anyone for their own purposes.

This website sets no cookies and runs no scripts other than its own. The homepage remembers, in your own browser, which phone frames you picked. The font it uses is served from this domain, not from anyone else’s.

Deleting your account

You can do it yourself: You → Account → Delete account. It asks twice, then happens immediately — there is no waiting period. If you own a crew that still has other people in it, the app will ask you to hand it over to someone first, so nobody’s crew disappears out from under them.

What deletion removes, in one step: your sign-in, your profile, sessions, runs and their routes, Apple Health offers, your workout log, measurements, targets and goals, progress photos, plans and schedule, posts (with the likes and replies on them), the likes, replies and saves you left on other people’s, stories and their view lists, your chat messages, friendships, blocks both ways, reports you made and reports about you, your club and crew memberships, invitations waiting on you, your invite record and place on the list, your push address, what you were playing, notifications queued for or about you, and any private gyms you added. Your files — profile and cover photos, progress photos, and the photos in your posts, stories and messages — are deleted straight after.

What stays, and why: a public club you added stays, because other people train there, but you are no longer attached to it. Crew invitations you sent to other people stay, because the person asked still has a real offer to answer. Error reports and usage counts stay without your account attached, as described above. Messages you sent through the website’s contact form are not part of your account; ask and they go too.

One thing outlasts the request, unavoidably: routine server logs and database backups roll over on their own schedule rather than being edited, so a copy can persist in those for a short time before it ages out.

If you just want out of a crew or a club rather than out of the app, you can leave it in the app and keep your account and your history.

Your rights

Under the Australian Privacy Principles you can ask for a copy of what is held about you, ask for anything wrong to be corrected, and ask for it to be deleted. Use the contact form and it gets done — this is a small app and there is no process to navigate. If you are not happy with the answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

How long things are kept

Your training history is kept for as long as your account exists, because a training app with an expiring history would be useless. Delete your account and it goes.

Children

AYRLI is not built for children and is not offered to anyone under 16.

Security

Everything travels over HTTPS. Reads and writes are checked in the database against who you are, not only in the app, so a bug in the app cannot simply hand your data to the wrong person. Your sign-in token is encrypted on the phone with a key that lives in the iPhone's keychain. None of that makes it perfect — no software is — and if something does go wrong that affects you, you will be told rather than left to find out.

When this page changes

The date at the top moves. If a change means AYRLI would collect something new or share something further, you will be asked before it applies to you.