Privacy Policy

Lurnex, Inc., a Delaware corporation (“we”, “us”), makes Logr and is responsible for the personal data described here. This policy covers the Logr app for iPhone and Android and this website, getlogr.app.

For anything about your data, write to support@getlogr.app.

Logr is built to work in a basement with no signal, so it keeps your data on your phone first. We cannot see anything in this section.

• Your setup answers: your first name, age, gender, goal, experience, body weight, equipment, training days and workout length, the areas where you have pain, and the emphasis and cardio you asked for. Your phone uses them to build your plan, and they are never uploaded.
• Your height, body-weight log, and the photo and bio in Profile.
• Your ranks, level, streak and plans, which are calculated on your phone.
• Your training log, for as long as you don’t have an account.
• Reminders and the workout card on your lock screen, which your phone schedules and shows by itself.
• Files you import from other apps, which are read on your phone; the workouts in them join your training log.

Your first name leaves the phone only if you join the feed, where it fills in your display name; you can change it before you save. If you back up your phone to iCloud, Google or a computer, the backup can include Logr’s data, under your control and Apple’s or Google’s terms.

Some of Logr needs a server, and some of it needs another company. Each row says what is sent, when, and what for.

Your account

If you create one: your email address, and your password, which is stored only in hashed form. With Sign in with Apple: the identifier Apple gives us, the email address Apple shares (which can be a private relay address) and, the first time, the name you choose to share. With Sign in with Google, on Android: the identifier Google gives us, your email address and your name. We use them to sign you in and keep your data together.

Your training log

While you are signed in: your finished workouts (times, titles, notes, and each set’s weight, reps, time, effort and warm-up mark), your routines and the exercises you created. They are copied to our servers when you sign in and each time you open the app, so the log is kept with your account. A workout in progress is not. If you edit or delete a workout after it has been copied, our copy is not updated; it stays until you delete your account.

The feed

If you join it: your feed profile (display name, bio and picture), what you post (titles, text, photos, videos and the workout you attach), your comments, reactions, follows, blocks and reports. See who can see what.

Notifications

If you turn on feed notifications: your device’s push token, with the app version and build environment, so we can tell you about activity such as a comment on your post. The notification, including the other person’s name and the first words of a comment, is delivered through Apple or, on Android, Google’s Firebase Cloud Messaging. Training reminders are scheduled by your phone and involve no server.

Purchases

If you subscribe: Apple or Google takes the payment, and we never see your card. RevenueCat receives the purchase from the store, including the product, price, currency, country, dates and transaction identifiers, linked to a random ID or, once you sign in, your account ID, along with basic device and app details. RevenueCat passes these events to our server, which keeps a log of them. We use them to know whether you have Pro and, through the advertising measurement described below, to measure subscription conversions.

Refund requests

If you ask Apple for a refund, Apple can ask us for information about the purchase. RevenueCat answers for us. It tells Apple that the purchase was delivered, whether a free trial or information about Pro was offered before you bought, and our preference on whether to refund. That preference is based on how much you used Logr, for example how often you opened the app and how many workouts you logged. Apple uses this together with its own information to decide; Apple makes the decision. It handles the information under its own privacy policy, and you can ask Apple for access to or deletion of it at privacy.apple.com. This sharing is on by default and is part of using Logr. You can turn it off at any time in the app, under Profile → Help and support → ⓘ → Privacy Policy → “Share usage with Apple for refunds”. After that, we no longer answer Apple’s requests about your purchases.

Advertising measurement

AppsFlyer measures which ads lead to installs, free trials, subscriptions and purchases. It receives app and device details, IP address, an AppsFlyer device identifier and, on an iPhone, the vendor identifier, the price and currency of a trial, subscription or purchase, and, when you sign in, your account ID. On an iPhone, with your App Tracking Transparency permission, it can also use your advertising identifier (IDFA); on Android, it uses your phone’s advertising ID unless you have deleted it. AppsFlyer shares these conversions with the ad network that showed you the ad — today TikTok — so it can measure and improve its campaigns. When you decline tracking on an iPhone, IDFA is not used, but AppsFlyer may still match an install to an ad statistically, from details such as the time, IP address and device model, and share the result with that network. TikTok’s own measurement SDK is also part of the app, for installs that report through it rather than AppsFlyer; it receives the same kinds of events and details. We do not send workout contents, body details, session recordings or your email address to advertising partners. You can change tracking permission in iOS Settings → Privacy & Security → Tracking, and delete your advertising ID in Android Settings → Privacy → Ads.

Usage events

Logr sends PostHog events such as “workout finished” with its counts of exercises and sets and its duration, “paywall shown”, or which way you signed in. Each event comes with device and app details (such as model, system version, app version and language) and an approximate location PostHog derives from your IP address, and is linked to a random ID or, once you sign in, your account ID. Events never contain body details, names or anything you type. We use them to see which parts of Logr work and where people get stuck.

Session recordings

We record app sessions with Amplitude, to see where the app confuses people or breaks. A recording is a video of that session: every screen you saw, everything you tapped, and everything you typed or entered — including the setup screens where you give your age, gender, height, weight and pain areas. Nothing in a recording is hidden or blurred, with one exception: the camera picture in the body scan is never recorded. A recording also carries Logr’s own diagnostic messages from that session. Recordings are filed under the same ID as your usage events, so once you sign in they are linked to your account. You can ask us to delete them at any time.

Plan import

If you bring in a programme you already have: the text you paste, up to 8,000 characters, and any screenshots of it you add are sent to our server at getlogr.app and read by Google’s Gemini model, which turns them into a plan. We don’t store the text or the screenshots. Our server holds your IP address in memory for a short time to limit how often the feature can be used.

Custom exercises

When you name an exercise of your own, the name and your app language are sent to our server at getlogr.app. Google’s Gemini model fills in its equipment and muscles, and OpenAI’s image model draws a picture of it in Logr’s style. Nothing else about you is sent, and we don’t store the name. The picture is saved on your phone only. Our server holds your IP address in memory for a short time to limit how often the feature can be used.

Exercise animations

The first time you open an exercise, its animation is downloaded from the content delivery network that stores it. Like any download, the request shows that network your IP address.

Support

If you write to support@getlogr.app: your email address and what you write. An email started from the app also includes your app and system versions. We use it to help you.

We use your data only for what each row says, to keep Logr secure and free of abuse, and where the law requires it. Advertising measurement uses the limited identifiers and conversion data described above. Cross-company tracking depends on your permission where required.

The feed is the one part of Logr other people see.

• Your feed profile, posts, comments and reactions are visible to everyone signed in to Logr, except people you have blocked or who have blocked you. There is no private or followers-only mode yet.
• A workout you attach to a post shows its date and start time, duration, sets, volume, exercises and streak. Nothing else from your training log is shared.
• Photos and videos are stored at unlisted web addresses. Anyone who has an address can open the file, even without Logr, so treat what you post as public.
• Photos are redrawn before they are uploaded, which removes their location and camera details. Videos are not: if your phone recorded where a video was filmed, that stays in the file.
• Who follows whom is visible only to the two people involved. Your blocks and reports are visible only to you, and nobody is told who reported them.

You can delete a post or a comment at any time. It leaves the feed straight away and its text is erased; what remains, such as a post’s workout summary, is kept out of sight until you delete your account.

Leaving the feed, from your feed profile, deletes your posts, comments and profile and keeps your account and training log. Your reactions, follows and blocks stay until you delete your account.

Some of what you tell a training app is about your body. The details most likely to count as health information (the areas where you have pain, your body weight and height, your gender and age) stay on your phone and are never uploaded.

Your training log reaches our servers only if you have an account, and only so that it is kept with your account. If you write health details into a workout note, they travel with the note, so keep notes to what you are happy to store with us. We never use your training data for advertising, and never sell it.

Where data protection law asks for a legal ground, these are ours:

• Providing what you asked for (our contract with you): your account, keeping your training log, the feed, purchases, refund requests (consent given through this policy, which you can withdraw with the switch in the app), the notifications you turned on, plan import and support.
• Your consent: push notifications and advertising tracking where required. You can withdraw these permissions in your phone’s settings. Withdrawing permission does not affect processing that already took place.
• Our legitimate interest in understanding and improving Logr and keeping it secure and free of abuse: usage events, session recordings, rate limits, handling reports, and delivering exercise animations. You can object to these at any time; see your rights.
• Legal obligations, such as keeping business records or answering a lawful request from an authority.

These companies process data on our behalf, under contracts that bind them to our instructions and to protecting it:

Supabase

Our database, sign-in, file storage and server functions. The database runs in Zurich, Switzerland.

RevenueCat

Subscription status and purchase records. United States.

AppsFlyer

Install attribution and advertising conversion measurement. Operated by AppsFlyer Ltd.

AppSprint

Apple Ads campaign attribution and subscription revenue measurement, using app and device identifiers, Apple attribution data and purchase events forwarded by RevenueCat.

PostHog

Usage events. United States.

Amplitude

Session recordings. United States.

Google

Reading the programmes you import and filling in the exercises you create from their names, through Vercel’s AI Gateway, and delivering notifications on Android through Firebase Cloud Messaging. United States.

OpenAI

Drawing pictures of the exercises you create, through Vercel’s AI Gateway. United States.

Vercel

Hosting this website and the servers for plan import and custom exercises. United States.

Resend

Delivering sign-in emails. United States.

Spaceship

Our support mailbox. United States.

Apple provides Sign in with Apple, App Store payments, aggregated ad attribution and the delivery of notifications under its own privacy policy, and receives the refund-request information described above. Google provides Sign in with Google and Google Play payments under its own. Advertising partners, today TikTok, receive conversion data through AppsFlyer or TikTok’s own SDK for attribution and campaign optimization, as described above. They process that information under their own privacy policies.

Beyond these companies, we share data only with the people you choose on the feed, with authorities where the law requires it, and, if Logr is ever sold, with the buyer, who would be bound by this policy. We would tell you before that happened.

Lurnex, Inc. is a company in the United States, and so are several of the companies above; our database itself is in Zurich, Switzerland. Data protection law in the United States is not the same as in the EU, the UK or Switzerland.

Where the law of those places requires a safeguard for personal data that reaches the United States, we rely on the EU–U.S. Data Privacy Framework, its UK Extension and the Swiss–U.S. Data Privacy Framework where the recipient is certified under them, and otherwise on the European Commission’s standard contractual clauses, with the additions UK and Swiss law require. You can ask us for the details of these safeguards.

• Account, training log, feed content and notifications: until you delete them or your account. Deletion takes effect on our database at once; copies in its backups are overwritten on the backup cycle.
• Usage events and session recordings: only as long as they help us improve Logr, and never beyond the retention periods set with PostHog and Amplitude.
• Advertising measurement: for as long as needed to measure and improve our campaigns, subject to provider retention settings and applicable deletion requests. You can contact us about these records.
• Purchase records: while you have a subscription, and afterwards for as long as the law requires us to keep business records.
• Reports: as long as we need them to handle the report and protect people, which can outlast the account involved.
• Push tokens: until you turn notifications off, sign out, or Apple or Google tells us a token is no longer valid. A log of which notifications were sent, identified only by a random ID, is kept for troubleshooting.
• Support emails: as long as we need them to help you and to keep a record of what we agreed.
• Plan import text and screenshots: not kept at all.
• Custom exercise names sent to our server: not kept at all.

You can ask us to:

• tell you what data we hold about you, and send you a copy;
• correct data that is wrong;
• delete your data, or stop using it while a question about it is settled;
• give you the data you provided in a machine-readable format, to take elsewhere;
• stop using your data for usage events, session recordings or anything else we do on the ground of our legitimate interest;
• withdraw a consent you gave, which does not affect what happened before.

Write to support@getlogr.app. We may ask you to confirm a request from your account’s email address, so that your data doesn’t go to someone else. We answer within 30 days, and we don’t charge for it.

You can also complain to a data protection authority: in the EU and the EEA, the one where you live or work; in the UK, the Information Commissioner’s Office; in Switzerland, the Federal Data Protection and Information Commissioner.

You can make these requests wherever you live, including in the United States, and we answer them the same way.

Delete your account in the app, under Profile, Account and data, Delete account, or ask us to delete it if you can’t open the app. We then delete your account, your training log, your feed profile and everything you posted, your comments, reactions, follows and blocks, the reports you made, your notifications and push tokens, and the photos and videos you uploaded. The app also removes your training data from that phone.

Some records stay, because we need them or because they are not only yours: purchase records at RevenueCat and in our purchase log, reports other people made about your content, and the log of sent notifications. Advertising measurement records, usage events and session recordings already collected are not deleted automatically; they stay linked only to an ID that no longer belongs to an account, and we delete them if you ask.

Deleting your account does not cancel a subscription: cancel it in Google Play or in your Apple ID settings. Deleting the app removes everything Logr stored on that phone.

Logr is not meant for children under 13, and we don’t knowingly collect their data. If you believe a child under 13 has given us personal data, write to support@getlogr.app and we will delete it. Anyone under 18 needs a parent or guardian’s permission to use Logr (see the Terms of Use).

Data travels between the app, our servers and our providers encrypted. Our database lets each account read only its own training log, and posts only as described above. Passwords are stored only in hashed form. No system is perfectly secure; if a breach puts your data at risk, we will tell you and the authorities as the law requires.

getlogr.app sets no cookies and uses no analytics, advertising or tracking tools. Vercel, which hosts it, processes your IP address and the pages you request in order to deliver them and keep the site secure, and keeps those logs for a short time.

When Logr changes what it collects or who handles it, we update this policy first and change the date at the top. If a change matters to you, we will tell you in the app before it takes effect.

Questions, requests or complaints about your data: support@getlogr.app. Lurnex, Inc. is responsible for Logr and for this policy.