What Luvya is
Luvya is a general wellbeing app for iPhone and Android. It creates gentle daily and weekly plans for self-care, sleep, calm, movement, mindfulness, routines, nutrition, confidence and everyday balance, and adapts them through check-ins. It's made by Appex s.r.o., a small company in Košice, Slovakia.
It is not a medical service. Luvya is not a medical device and doesn't provide medical advice, diagnosis, treatment or therapy. It doesn't monitor anyone's condition and can't recognise an emergency. In a crisis or emergency, contact local emergency or crisis services right away.
What's in the app
- A chat with Oakie to start. Onboarding is a short, friendly chat with Oakie the oak leaf instead of a long form.
- Weekly plans. A new week arrives on Monday, with a focus, weekly targets and daily tasks. The next week is prepared ahead.
- Today. One highlight ("If you only do one thing") and a short list of tasks.
- Habits that grow. One or two anchor habits get steady practice; once one sticks, it shows up less often, and you decide when to retire or swap it.
- A note for you. Now and then, a short personal note on the week, only when there's something specific to say. You can turn these off by saying they don't help.
- Check-ins. Optional questions about pace, what to lean into, what you liked and didn't, plus a free note. The options are drawn from your own week.
- Moments. Occasional short screens such as "How are you, right now?" and "A gentle look back".
- Insights. A shared library of short articles, filterable by topic, with favourites.
- Companions and looks. Oakie the leaf and a cast of paper mascots, and three looks (Airy, Warm and Glow) that change colours but not layouts.
- Reminders. Personal reminders that arrive at the right moment, and never too many.
- Invitations. Personal codes that extend the free trial for both people.
The division of labour
The core design decision: the model writes, and code decides. A language model is good at turning a person's context into warm, specific text. It's not a good place to keep long-term state or to choose how much to ask of someone. So those parts are ordinary, testable code.
| Decided by code | Written by Gemini |
|---|---|
| Whether next week simplifies, holds steady or progresses, from real task completions and your requested pace | The tasks, descriptions and wording for that week, within that direction |
| Which days must exist, computed on the server in your time zone | What fills each of those days, and the day's emoji |
| The long-term spine: main goal, 4-week arcs, focus areas, anchor habits, and how far any of them may change | Proposed updates to that spine, which code accepts only within the limits below |
| The lifecycle of each habit, from your completions and your answers to the in-app habit question | How a habit is carried out and phrased this week |
The rules, specifically
- Asking for an easier pace always simplifies the next week.
- A largely unfinished week simplifies: fewer or shorter tasks and nothing new. Two in a row reduce it further, to the anchor habits and at most one light task a day.
- A strong week earns at most one small new challenge, never more.
- A request for a harder pace is honoured gently, and not right after a missed week.
- Weeks generated ahead of time never add extra load, so progress can't stack up unseen.
- The main goal stays put. Focus areas change only at the end of a 4-week arc, with at most one anchor habit swapped per arc. The progression level moves at most one step a week.
Where Gemini is used
| Job | Personal data in the request |
|---|---|
| Oakie's replies in the onboarding chat, when a reply is needed | Yes: your onboarding answers |
| Writing the weekly plan | Yes: see the list below |
| Reviewing each new week for quality, and for safety when you've mentioned a condition or injury | Yes: the new week and what you wrote about conditions and limitations |
| Turning check-ins into priorities that carry across weeks | Yes: check-in answers and notes, reflections, earlier priorities |
| Short reflections after check-ins and in moments | Yes: recent check-ins, reflections and an activity summary |
| Finding, checking and categorising Insights articles, reviewing their images, and generating an image as a last resort | No |
What goes into a plan request
Your goals and approach; energy and stress in your own words; typical day and free time; anything you wrote about health conditions or limitations; diet, allergies, injuries and equipment; favourite and avoided activities; preferred name and city if you gave them; time zone; check-in answers and notes; carried-over priorities; and a summary of what you completed.
These requests contain no email address, account ID, device identifier or payment information. Requests and responses are stored in your account so plans can be checked and problems debugged. See the Privacy Policy for more.
What happens to the output
- Responses must follow a fixed JSON schema.
- Each one is checked on the server: every expected day present, no duplicates, no empty days. Anything that fails is retried and doesn't become your plan.
- A second review pass looks over every new week. If you mentioned a health condition or injury, activities that may not suit it are replaced, and sentences that promise safety or medical effects are removed.
- If generation keeps failing, the app shows a real error with a way to contact us rather than an endless spinner.
Using the model responsibly
- Medical boundaries. The prompts tell the model not to diagnose, recommend treatment or medication, or make medical claims, and to keep to general suggestions that point to a qualified professional for medical questions. Instructions lower the risk but can't remove it, and that's reflected in our Terms of Use.
- No open-ended chat. The only conversation is the onboarding chat with Oakie, which stays on the onboarding questions and calls the model only when a reply is needed. Everything else is structured plans and short texts from defined inputs.
- Proportionate use. Generation runs once a week for accounts with access. Accounts without access are skipped. Duplicate runs are prevented, manual recovery requests have an escalating cooldown, and simpler jobs use a lighter model.
- Prompts under version control. System prompts live in a versioned file in the repository and are uploaded from there.
Known limits
- Suggestions can be inaccurate or unsuitable. You decide what's right for you.
- Luvya doesn't detect crises or emergencies.
- Personalisation is only as good as what you share, and notes are interpreted by a model that can misread them.
Data, in short
- Our main database and server functions run in EU regions on Google Cloud (Firebase).
- No ads in the app, and we don't sell personal information.
- Identifiers kept for preventing trial abuse are stored as keyed hashes.
- Everything else, including what stays after you delete an account, is in the Privacy Policy.
Gemini is a product of Google. Luvya is an independent app and isn't endorsed by or affiliated with Google.