What we collect, and what we deliberately do not.
A plain-language summary of how LiftLine AI handles your information and protects it, with what the app actually sent in the last 30 days.
We collect what the app needs to work and to get better, and we say exactly what that is. We do not sell it, we do not show ads, and we do not track you across other companies' apps or websites.
What we do not collect
- No analytics, advertising, or crash-reporting code from anyone else. The app sends its own usage events to our database — which screens and features you open, never your location or what you say to Liftie — and you can turn them off in Settings › About & support.
- No session replay, no advertising identifier, no ad network, no ads.
- No fingerprinting, no cross-site or cross-app tracking, and no IP-based geolocation.
- No sale of data, no data brokers, no ad-tech recipients.
- No access to your microphone, device camera, contacts, calendar, or health data. Photos you share are picked with Apple's picker, so the app never reads the rest of your library.
- Location is read only while the app or the web page is open. Nothing tracks you in the background.
- We do not train any model on your data.
What the app actually sent in the last 30 days
The kinds of usage event the iPhone app sent us in the last 30 days, and how many of them carried a location, counted from the events themselves.
Live figures load in your browser.
Where your location goes
Your exact location stays on your phone, where it finds the nearest lifts and puts you on the map. These are the only ways anything about it leaves.
- Pro alerts
- With Pro or Max, Alerts on, and notifications and location allowed, the app sends which resort you are at and your nearest lift, so an alert is about the right mountain. Only the latest is kept, it is deleted when you turn alerts off, and coordinates are never stored.
- Routes
- When you plan a route from where you are, or Home and the map show routes and suggested runs from where you are, your location goes to our route server for that request. It is not stored; the server's technical log notes at most the lift or run a route started from.
- Usage events
- Each one says whether you are at a mountain, yes or no, worked out on the phone. Never a location.
- On the web
- If you turn on nearby-lift alerts, your browser works out which lift you are close to and tells our server, and the alert arrives through your browser's push service.
- Crowd reports
- A report carries the lift, the value, the time, and your account ID. No coordinates.
Everyone else who sees anything
Liftie, the route planner and alerts run on our own server in the United States, so no outside AI company receives your chats. Everyone outside who receives anything is below.
| Service | What it receives | Why |
|---|---|---|
| Supabase | Your account, profile, preferences, trips, the photos you share, crowd reports, favourites, Liftie notes and feedback, usage events, entitlements, and authentication events. | Our database, authentication, storage, and server functions, in the United States. |
| Apple | On iOS: your purchase and subscription, the notifications we send you, and Sign in with Apple if you use it. The app also asks Apple Maps for places and drive times in a trip, and WeatherKit for the weather at a resort. | Purchases, notifications, sign-in, place search, and weather. |
| Your sign-in, only if you choose Sign in with Google. | Sign-in. | |
| Resend | Your email address, your first name, and the contents of the message. | Sending account and service email. |
| Stripe | Billing details for the few older web subscriptions that are still running. The web sells nothing new. | Payments for those subscriptions. |
| Apple and Google push services | If you turn on web notifications: the notification itself, which carries no name, email, or account identifier of yours. | Delivering a notification while our site is closed. |
| YouTube | Your IP address and device details when a webcam plays, because the video streams from YouTube, which may set its own cookies. | Live webcams. |
| The resorts | Your IP address when a webcam image loads, because it loads from the resort's own server. | Webcam images. |
| Esri and Amazon | Your IP address and the part of the map on screen, when map imagery and terrain load. | The map. |
| AWS | Ordinary web server logs, including your IP address, and the app's requests as they pass through our gateway to our own server. | Web hosting, and the gateway that connects the app to our server. |
| Discord | Operational alerts from our collection service — crowd counts only, and no user identifiers of any kind. | Knowing when collection breaks. |
Webcams and the people in them
We count people in lift lines on public resort webcams, using a vision model on our own computer. For each frame we count we keep a head count, a confidence and a timestamp. We also keep some frames to train and check the counter. We never identify anyone: there is no face recognition and no attempt to work out who is in a picture.
If you think you appear in a frame we have kept, write to Lucas@liftlineai.app and we will look.
Your controls
You can use Snowcat without signing in. In the app you can delete your account (Settings › Profile › Delete account), turn off usage data (Settings › About & support), and read or delete what Liftie remembers (Settings › Liftie AI). For a copy of your information, a correction, or anything else, write to Lucas@liftlineai.app. We will help wherever you live.
How access is enforced
- Everything travels over encrypted connections.
- Access to your data is enforced by row-level security rules in the database itself, so a request for someone else's row is refused by the database rather than by our application code.
- Session tokens are stored in the iOS Keychain. Payment card details never touch our systems.
- The administrative key that can bypass those rules exists only on our collection machine and in our server environment. It is never in the website, the app, or anything you download.
- The database is backed up on a short rolling schedule so an accident is recoverable.
The key the website and app use to reach our database is publishable by design and visible in the browser on purpose. Access control is the row-level security policy, not the secrecy of that key.
We are a very small operation. We hold no security certification and have not had a third-party penetration test, and we will not imply otherwise. If a breach affects your personal information we will tell you and the relevant authorities as the law requires, without unreasonable delay.
Reporting a vulnerability
Write to Lucas@liftlineai.app. We will read it, act on it, and not pursue anyone who reports a problem responsibly and gives us a reasonable chance to fix it before disclosing it.
- Useful in a report
- What you did, what happened, and roughly when. A proof of concept helps but is not required.
- Please do not
- Access, modify, or delete data that is not yours; run automated scanning that degrades the service for other people; or test social engineering against anyone.
- Machine-readable
- https://liftlineai.app/.well-known/security.txt