Lanturne Privacy Policy
Last updated: 6 August 2026
Lanturne is operated by Technium Foundry LLC ("we", "us"). This policy explains what data Lanturne collects, why it is collected, who else can see it, and how long it is kept.
Contact: support@lanturne.com
Summary
- We collect only what is needed to tell you your parent is all right.
- We keep where she is now, not where she has been. Her most recent position is kept as a single value
- We do not sell data. We do not share it with advertisers. There is no advertising in Lanturne.
- Her watch can only send. It cannot read anything about you and never displays your name.
Who the people are
Lanturne involves two people, and the data rules differ for each.
The account holder — usually an adult child — creates the account, subscribes, and receives alerts.
The monitored person — usually a parent — wears the watch. She does not have an account and does not sign in. Data about her is collected by her watch and shown to the account holder who set up the account.
If you are setting Lanturne up for someone else, you are responsible for telling them it is running and what it does. We provide the plain-language summary above so that conversation is easy to have.
What we collect
From the account holder
| Data | Why | Where it comes from |
| Email address | To sign you in and reach you about your account | Firebase Authentication (Google) |
| Push notification token | So an alert can reach your phone | Firebase Cloud Messaging (Google) |
| Subscription status | To know whether your account is active | Google Play Billing |
| App version and device platform | Attached to support messages so we can help without asking | The app |
| Support messages you write | To answer them | You |
| Data | Why | When |
| Display name and time zone | To show whose events these are, and to know when "9 a.m." is | Entered by the account holder at setup |
| Check-in events | To confirm she is all right | When she taps "I'm OK" |
| SOS events | To raise an alarm | When she presses SOS |
| Fall events | To raise an alarm | When the watch detects a fall |
| Location | So you know where to go in an emergency | Recorded and kept on an SOS and on a detected fall |
| Last known location | So a missed check-in or a silent watch can still tell you where she was | Whenever her watch reports a position. Only the newest is kept — each one overwrites the last, so there is only ever one |
| Watch battery level and wear state | To warn you before the watch stops working | Periodically |
| Liveness signal | To notice if the watch stops reporting | Every 15 minutes |
What we do not collect
- A history or trail of her movements
- Heart rate, blood pressure, sleep, steps, or any health or fitness measure
- Contacts, photos, messages, call logs, or microphone audio
- Any advertising identifier
Who else sees it
We use these providers, and only these:
| Provider | What they process | Why |
| Google — Firebase Authentication | Email address | Sign-in |
| Google — Firebase Cloud Messaging | Push token, alert notification | Delivering alerts |
| Google Play Billing | Purchase and subscription status | Taking payment |
| DigitalOcean | All data, at rest, in our database | Hosting |
We will disclose data if legally compelled to, and where we are permitted to tell you, we will.
How long we keep it
Events are kept for as long as the account exists. This is deliberate. A caregiver may need to look back over months to see when a parent's routine changed, and a record that has been quietly pruned cannot answer that.
The liveness signal is summarised to one entry per day after 30 days, because the raw signal carries no meaning beyond "the watch was on".
When you delete your account, we delete the account, the monitored person's profile, and all associated events. Backups are overwritten on their normal cycle, within 35 days.
Your rights
Wherever you live, you may:
- See what we hold about you and the person you monitor
- Correct anything wrong
- Delete the account and everything in it
- Take a copy in a machine-readable format
- Object to processing, or ask us to restrict it
If you are in the EEA or UK, our lawful basis is contract — we cannot provide the service without this data — except for support messages, which are legitimate interest. If you are in California, we do not sell or share personal information as the CCPA defines those terms, and we do not discriminate against anyone who exercises their rights.
Security
Device tokens and pairing codes are stored as SHA-256 digests, never in the form they were presented. Session tokens are held in the Android Keystore. Traffic runs over TLS. Location and credentials never appear in our logs.
No system is perfect. If we discover a breach affecting you, we will tell you and the relevant regulator within the time the law requires.
Children
Lanturne is not for anyone under 18 and we do not knowingly collect data from children. If you believe a child's data has reached us, email support@lanturne.com and we will remove it.
Changes
If we change this policy in a way that materially affects you, we will tell you in the app before it takes effect. The date at the top always reflects the current version.