Who we are
LILO is built and operated by Martin Jansson, Ullevålsveien 9A, 0161 Oslo, Norway. For privacy questions, write to support@lilo.fit.
We are based in Norway. The European General Data Protection Regulation (GDPR) applies to LILO through the EEA Agreement, alongside the Norwegian Personal Data Act.
Who this policy is for
LILO has two kinds of users: the trainers who run their coaching business on the platform, and the clients they coach — plus standalone clients who use LILO on their own, with no trainer. We handle data differently in each case, so this policy is split accordingly.
If you’re a trainer
What we collect. Email, name, avatar, timezone, language preference, and role. Your subscription status (active, trial, expired) and your Stripe customer ID. Stripe Connect payout details if you sell session packages. Server logs and usage counters used for AI rate limits and abuse prevention.
How we use it. To run your account, deliver the service you signed up for, bill the subscription, send transactional email (verification codes, receipts, critical notices), provide support, and keep the platform secure.
Legal basis. Performance of our contract with you (running the service), our legitimate interest in security and fraud prevention, and legal obligations such as bookkeeping.
Your rights. You can access, correct, export, or delete your data, and object to processing based on legitimate interests. You can delete your account yourself under Profile → Delete account in the portal (see Delete account); for anything else, contact support@lilo.fit. You also have the right to lodge a complaint with Datatilsynet, the Norwegian Data Protection Authority.
If you’re a client added by a trainer
Your trainer invited you to LILO so they can coach you in one place instead of across spreadsheets and chat apps. Here is what they collect about you and what you can do.
What’s collected about you. Your name, email, phone, goal, the notes your trainer takes about you, where you are in their pipeline, the messages you exchange with them, calendar events, the programs they assign you, and your session bookings and balances. If you use the LILO mobile app, also: weight, sleep, steps, heart rate, body composition, and calorie/nutrition logs — and, if your trainer uses check-ins, your check-in answers and any progress photos you add (below).
Check-ins. Your trainer can send you short check-in forms — for example a weekly one. We store the questions, your answers, and a log of the numbers you give over time so you and your trainer can see trends. Some answers are about your health: how you rate your stress, energy and sleep quality, how well you followed your plan, and any body measurements (weight, body fat, waist and similar), which are also added to your body-measurement history. Free-text answers are stored as you write them. Your trainer can also record a check-in on your behalf, for example during a session.
Progress photos. A check-in can ask for progress photos of your body. You choose whether to add them. They are stored in private file storage in the EU, filed under your own account — they are never public and never sent to an AI service. You can always see and delete your own photos. Your trainer can see them only while your photo-sharing consent is switched on in the app: withdraw it and their access ends immediately, in the database and in file storage. Deleting your account deletes your photos.
Health data. Check-in answers about your body and wellbeing, body measurements and progress photos are health data — a special category under GDPR Article 9 — like the other health logs above. They are processed only with your explicit consent: you give it when you choose to answer or add a photo, and for photos also through the separate sharing consent, which you can withdraw at any time.
What you pay through LILO. If you buy session packages from your trainer, your card and billing address are processed directly by Stripe. LILO never stores your card number.
Who decides how this is used. Your trainer is the data controller for the data they store about you in LILO. To exercise your rights — access, rectification, erasure, export, objection — start with your trainer. They can remove you from their client list inside LILO. You can delete your own account from the mobile app (see Delete account). Exports are done on request: write to support@lilo.fit and we’ll send you a copy. If your trainer doesn’t respond, contact us and we’ll help.
What your trainer agreed to. When trainers sign up they commit to informing clients about how LILO is used and to obtaining any consents required by law, especially before turning on AI features or syncing health data.
If you use LILO without a trainer
LILO also supports standalone use: you can create a client account directly, with no trainer attached, to track your own workouts, weight, sleep, and meals in the mobile app.
Who decides how this is used. When you use LILO on your own, there is no trainer in the loop — LILO is the data controller for your account data.
Legal basis. Running your account (profile, login, subscription) relies on performance of our contract with you. Health and body data — weight, body composition, sleep, heart rate, and nutrition logs — is special-category data under GDPR Article 9, so we only process it on the basis of your explicit consent. Nothing is collected until you choose to log it: each entry you make in the app is your instruction to store that data for the sole purpose of showing it back to you, and you withdraw that consent by deleting the entries or your account. We never use standalone health data for anything else, and no trainer can see it unless you later share it (see above).
Your rights. You can correct your data, withdraw consent, and delete your account directly from the app — there’s no trainer to go through first. For access or an export, write to support@lilo.fit and we’ll send you a copy on request. You also have the right to lodge a complaint with Datatilsynet, the Norwegian Data Protection Authority.
If you later connect with a trainer, or a trainer invites you, this section stops applying to the data you choose to share with them — see “If you’re a client added by a trainer” above.
Operational data we control directly
Some data we keep regardless of which side of the platform you sit on: server logs, IP addresses captured for authentication and abuse prevention, login events, AI usage counters used to enforce rate limits, and security telemetry. We are the controller for this operational data, and we keep it for as long as it’s useful for security and no longer.
AI features and Google Gemini
LILO uses Google Gemini for two distinct features — one on the trainer side, one on the client side. They send different kinds of data to Google for different reasons, so we describe them separately.
Trainer-side coaching insights and routine drafts.
For the AI coaching insights and suggested routines LILO shows trainers, names are stripped before data leaves our server. Clients are referred to as Client 1, Client 2, Client 3, and only exercises, numbers, and relative dates are sent. Real names are mapped back into the response on our side after Gemini answers. When a trainer asks a follow-up question, the question is sent as typed, except that the names of the trainer’s clients are swapped for those same placeholders on our server first. Cached results are refreshed after six hours and kept until they are regenerated or the account is deleted.
Client-side meal scanning (LILO PRO).
Clients on LILO PRO can tap Scan meal in the mobile app to photograph their plate. The photo is sent directly to Google Gemini, which returns the detected foods and estimated portion sizes as text. The user reviews and edits the result before any food is logged.
The legal basis for the meal-scan flow is performance of contract: meal scanning is part of the LILO PRO service the user subscribed to, and each scan is actively initiated by the user.
Sub-processors
The companies that help us run LILO and the data they handle:
We update this list when sub-processors change. If you would like advance notice of material changes, write to support@lilo.fit.
Data residency & transfers
Primary data storage and authentication run inside the European Union. Some sub-processors (Stripe, RevenueCat, Google Gemini, Google Fonts, Firebase, Apple/Google, and Vercel’s global edge) involve transfers outside the EEA. Those transfers are covered by the European Commission’s Standard Contractual Clauses and the supplementary measures the relevant providers publish.
Retention
We keep your data for as long as your account is active. When an account is closed, we delete personal data within thirty days, except for records we are required to keep — principally accounting records, retained for the period set by the Norwegian Bookkeeping Act (typically five years).
Cached AI outputs are refreshed after six hours and kept until they are regenerated or the account is deleted. Server logs are rotated on a rolling window kept short enough for security review and no longer.
Children
LILO is built for adults. We do not knowingly create accounts for anyone under eighteen.
Changes to this policy
When this policy changes in a way that materially affects you, we will notify you at least thirty days before the change takes effect, by email and through an in-product banner. Smaller clarifications are reflected by updating the date at the top of the page.
Contact
Questions, requests, complaints — write to support@lilo.fit. We aim to respond within five working days.