Data: Account: email, display name, @handle, profile photo, bio, sign-in provider ID (Apple or Google), account creation time
Where it comes from: You; Apple/Google when you sign in with them. Sign in with Apple may give us a private relay email
What we use it for: Create and secure your account, show your profile, support
Legal basis (EU/UK): Contract
Data: Age confirmation (that you're 13 or older; we don't collect your birth date or birth year)
Where it comes from: You at sign-up or first launch
What we use it for: Enforce the minimum age of 13, apply under-18 protections where we know a user is under 18 (friends-only default, no featuring, no search indexing, excluded from nearby alerts to non-followers and from heat-map inputs)
Legal basis (EU/UK): Legal obligation; contract
Data: Terms acceptance: version accepted and when
Where it comes from: Your acceptance
What we use it for: Prove consent; ask you to re-accept after material changes
Legal basis (EU/UK): Legal obligation; legitimate interests
Data: Your Content: Shots (photos, caption, chosen spot, camera/lens/ISO/shutter/aperture and capture time you share), comments, likes, follows and follow requests, reviews, spot/studio submissions, trips and shared trips
Where it comes from: You
What we use it for: Provide social features and display your content to people allowed to see it
Legal basis (EU/UK): Contract
Data: Spot submissions ("Pin a new spot"): the map pin you confirm, the address you type or confirm, the spot name, type and tips, and the date you accepted the Content License
Where it comes from: You
What we use it for: Review the spot and, once approved, publish it with its pin and address. Pending spots are never shown to other users
Legal basis (EU/UK): Contract
Data: Photo GPS coordinates (the location saved in a photo you add)
Where it comes from: Your photo file, read on your device
What we use it for: Read on your device to suggest a pin you then confirm. The photo itself is re-encoded without GPS/EXIF location before upload, and our servers strip it again. The coordinates are sent separately and stored privately, linked to your account, used only to verify that a submitted photo was taken at the spot and for moderation. Never shown publicly. Deleted with the photo, or when you delete your account.
Legal basis (EU/UK): Legitimate interests (verifying submissions and preventing abuse)
Data: Precise device location (while using the app)
Where it comes from: Your device, with permission
What we use it for: Center the map, show distance and near-me results, suggest the nearest spot. Sent to our servers or to Google only as part of a search request. Not stored with your account. Used in memory only for "Near you" lists
Legal basis (EU/UK): Consent
Data: Approximate city, province/state and country (never exact coordinates)
Where it comes from: Your device location, if you allow it
What we use it for: Center the map and suggest nearby spots when location is off. Stored with your account. Updated at most daily. Deleted when you delete your account
Legal basis (EU/UK): Consent
Data: Rough area for nearby-post alerts (a ~5 km area cell, never exact coordinates)
Where it comes from: Your device, if you turn on nearby alerts
What we use it for: Send "someone posted near you" alerts. Updated at most daily. Deleted when you turn the alert off or delete your account
Legal basis (EU/UK): Consent
Data: Rough area for aurora alerts (a 1° latitude/longitude grid cell, about 111 km north–south, stored with your push preferences) and your saved spots
Where it comes from: Your device (if you allow location) and the spots you saved
What we use it for: Tell you when the aurora may be visible near you or your saved spots. We keep the cell so our server can check the forecast for your area without knowing where you are exactly. Updated when your area changes. Deleted when you turn aurora alerts off, revoke location for aurora alerts (we then use saved spots only), or delete your account
Legal basis (EU/UK): Consent
Data: Saved items, lists, settings (units, map type, notification preferences, quiet hours, privacy settings)
Where it comes from: You
What we use it for: Sync across devices, apply your choices
Legal basis (EU/UK): Contract
Data: Push token (Expo/Apple push token)
Where it comes from: Your device, if you allow notifications
What we use it for: Send notifications you chose
Legal basis (EU/UK): Consent
Data: Notification inbox (likes, comments, follows, requests, nearby posts, moderation notices)
Where it comes from: Generated by activity
What we use it for: Show your notifications
Legal basis (EU/UK): Contract
Data: Feed signals: who you follow, posts you liked, commented on, saved, opened, hid or spent time on, topics of interest, which posts you've already seen (7 days)
Where it comes from: Your use of the feed
What we use it for: Rank the For You feed (see §4)
Legal basis (EU/UK): Legitimate interests (EU/UK: you can use the Following feed instead)
Data: Anonymous usage statistics (if analytics is on): spot viewed, saved, listed or posted; trip planned, saved or shared (number of stops only); feed impressions
Where it comes from: App events
What we use it for: Improve features; build the aggregated activity heat map. Stored with no account ID, name or device location. Uses a daily-changing hashed identifier. Area = the spot's ~5 km cell. Deleted after 90 days. Not recorded if analytics is off or the account is a limited/under-16 account
Legal basis (EU/UK): Consent
Data: Firebase Analytics (app) and Google Analytics 4 (website)
Where it comes from: SDK / gtag on the website
What we use it for: App and site usage statistics, crash and performance signals. In the app, these statistics may be linked to your LensScape account ID.
Legal basis (EU/UK): Consent
Data: Moderation data: reports you file or receive, reasons, automated safety-filter results (Google Cloud Vision SafeSearch), actions taken, appeal messages
Where it comes from: You, other users, filters
What we use it for: Keep the community safe, enforce rules, comply with law
Legal basis (EU/UK): Legitimate interests; legal obligation
Data: Purchases: plan, status, trial and renewal dates, store transaction IDs. Card details are handled by Apple or Stripe; we never see full card numbers. Web checkout may collect your email and billing country
Where it comes from: Apple via RevenueCat; Stripe
What we use it for: Grant Pro, prevent fraud, accounting and tax
Legal basis (EU/UK): Contract; legal obligation
Data: Advertising data (free users): device advertising ID (IDFA) only if you allow tracking, IP address, ad interactions, rewarded-ad completions
Where it comes from: Google AdMob SDK
What we use it for: Show and measure ads; non-personalized ads if you decline tracking or consent
Legal basis (EU/UK): Consent (personalized ads); legitimate interests (non-personalized/contextual)
Data: Device, log and security data: IP address, device and OS type, app version, timestamps, crash logs, rate-limit counters
Where it comes from: Automatically
What we use it for: Security, abuse prevention, debugging
Legal basis (EU/UK): Legitimate interests
Data: Support messages
Where it comes from: You
What we use it for: Answer you
Legal basis (EU/UK): Legitimate interests
•
Other users and the public: content you post, based on your visibility (public or friends-only), your profile, and your public trips. Public content can appear on lensscapeapp.com and in search engines. Under-18 and friends-only profiles are not indexed.
•
Service providers (processors) that act on our instructions:
◦
Google (Firebase, Google Cloud): Auth, Firestore, Storage and Cloud Functions in the US (us-central1); Cloud Vision SafeSearch; Firebase Analytics; Google Analytics.
◦
Google Maps Platform: your search text, map area and coordinates for search, details, photos and parking. We don't attach your account. Google's privacy policy applies.
◦
Apple: Sign in with Apple, App Store payments, MapKit/Apple Maps, push delivery.
◦
Expo (650 Industries): push notification delivery.
◦
RevenueCat: in-app subscription status, linked to your LensScape user ID.
◦
Stripe: web checkout and billing.
◦
Vercel: website hosting; processes IP addresses and request logs.
◦
OpenWeather: spot coordinates for weather. We don't send your account.
◦
NOAA SWPC: we download public aurora and Kp forecasts. We don't send NOAA your account details.
◦
OpenAIP: spot coordinates for airspace lookups. No account information is sent.
◦
FOSSGIS/OSRM: trip stop coordinates and your IP (see §3).
◦
These providers must protect personal information at least as well as this policy does and use it only to provide their service to us (App Store guideline 5.1.1(i)).
•
Advertising partner: Google AdMob receives device and ad data as described in §2.
•
Legal and safety: to comply with law or valid legal process, protect people from harm, report child exploitation, enforce our Terms, or defend legal claims.
•
Business transfer: if LensScape is sold or merged, under this policy's protections, with notice to you.
•
We removed openrouteservice (HeiGIT) as a routing provider. Trip data is no longer sent to it.