LightScout
LocationsBlogAboutGet the App
Home/Privacy Policy

Privacy Policy

Last updated: 2 October 2026

Introduction

LightScout ("we", "our", or "us") operates the LightScout mobile application and the website at lightscout.app. This policy explains how we collect, use, and protect your information.

Information We Collect

Location data: When you use location-based features, the app accesses the location you choose or permit and sends it to our service providers to generate a photography guide. Location details may form part of a guide you save to your account. You can control device location permission in iOS Settings.

Camera and experience preferences: Your selected camera type and experience level are used to personalise guides and may be sent to our service providers as part of a guide request.

AI Scout requests and Google Gemini: To create a Scout, LightScout sends Google Gemini the place you choose, which can include its name or address, precise coordinates and search area; the Scout type, date, time and time zone; your camera type and photography experience; your language and measurement settings; and weather, sunrise, sunset, sun direction, golden-hour and blue-hour details calculated for that place and time. Google services also receive the authenticated account identifier needed to process the request through the Firebase and Google Cloud authorisation route; that identifier is not embedded in the text prompt given to the model. The Scout prompt does not include your name or email address. Google Gemini uses these details to create the photography plan you requested.

In LightScout 2.7.0, LightScout asks for explicit permission before the first such request. Choosing Not now lets you continue browsing. Withdrawing permission in LightScout Settings blocks new Google Gemini requests; Scouts you already saved remain available. Withdrawal cannot recall a request that has already been sent or delete provider-held records by itself.

Purchase information: In-app purchases are processed by Apple through the App Store. We do not collect or store payment details.

Website waitlist: If you join the weekly-report or Android waitlist, we store the email address you submit and the page source in Supabase so we can send those updates. You can unsubscribe from an email or ask us to delete the address.

Website analytics: We use Cloudflare Web Analytics to measure aggregate website traffic, such as pageviews, referrers, browser or device category, and approximate country. We also count accepted App Store button-action requests from the homepage and two selected articles through Cloudflare's existing website request analytics. These counters use fixed page, button-placement, source and campaign categories, with test traffic kept separate. They add no cookies, browser storage or visitor identifiers, send no full referrer, and honour Do Not Track and Global Privacy Control. Cloudflare receives the network information needed to deliver and secure website requests. We do not send email addresses, precise locations, account identifiers, or free-text search terms to website analytics.

App analytics and attribution vary by app version. LightScout 2.5.0 (build 9), which may remain installed after a later version is released, uses AppsFlyer's standard iOS SDK for App Store attribution. After sign-in, this version supplies the LightScout account identifier as the AppsFlyer customer user ID, may collect AppsFlyer installation identifiers and Apple's advertising or vendor identifiers when available, records the new-account, completed-scout and completed-purchase conversion signals, and passes the AppsFlyer identifier to RevenueCat. This build did not disable AppsFlyer integrated-partner sharing before the service started. We therefore treat its User ID, Device ID and Product Interaction data as linked and used for advertising attribution and measurement. It is not used by LightScout to personalise advertising.

LightScout 2.6.0–2.7.1 use AppsFlyer Strict for bounded App Store attribution. They do not send the raw LightScout account identifier to AppsFlyer, disable advertising-identifier and vendor-identifier collection for AppsFlyer before start, and block AppsFlyer integrated-partner sharing. Product analytics uses a server-issued pseudonymous identifier and bounded product events rather than an account identifier, location, report or free-text values.

Purchases and Device ID in LightScout 2.6.0 and later. RevenueCat administers subscriptions, one-time credit packs, entitlements and purchase restoration. Its iOS SDK independently sends Apple's vendor identifier (IDFV) as a Device ID with its backend requests for purchases and App Functionality. Removing the app's former AppsFlyer-to-RevenueCat forwarding does not mean that RevenueCat receives no device identifier. We do not use this RevenueCat identifier for cross-company tracking.

Optional app analytics in LightScout 2.7.0–2.7.1: LightScout keeps Firebase Analytics and AppsFlyer collection off unless you choose Share usage analytics. If allowed, these services may receive app-use events; device and app information, including approximate location derived from network information; purchase and subscription events; camera type; photography experience; and an app-scoped account identifier. We use this information to understand activation, reliability and marketing effectiveness. Scout content, selected places, searches and precise coordinates are not included in these analytics events. This choice does not affect app features or purchases.

Optional app analytics in LightScout 2.7.2 builds with “Share usage analytics”: LightScout keeps Firebase Analytics disabled in this version. If you choose Share usage analytics, the app sends app-use events, app information, purchase and subscription events, camera type and photography experience to PostHog's EU service and keeps the existing optional AppsFlyer Strict attribution behaviour. PostHog receives no session replay or screen auto-capture, Scout content, searches, place details, location or precise coordinates. PostHog geoIP processing is disabled. Events before sign-in may be connected to later activity only through a random, server-issued analytics identifier; this is not your LightScout account ID, and no prior Google Analytics or pre-consent event export is joined to it. Firebase Crashlytics and the authenticated Firebase/Google route used for AI Scout generation remain separate from optional product analytics.

You can withdraw this choice at any time in LightScout Settings. In 2.7.2, withdrawal stops future PostHog uploads, drops unsent PostHog events queued on the device, cancels local uploads, resets the analytics correlation state and does not require account deletion. It cannot recall an event already sent or an upload already accepted by a provider. Refusing analytics remains in force across upgrades; an old accepted decision must be renewed under the optional “Share usage analytics” control in Settings. For 2.7.0–2.7.1 choices, the version-specific Firebase behaviour described above applies. Contact support@lightscout.app for a broader data-rights request.

Earlier aggregate builds with “Help improve LightScout”: This setting is on by default, including before sign-in. An earlier explicit refusal remains off after an upgrade. The app measures feature use, activation, purchase-flow outcomes, return visits and reliability solely to improve LightScout. Each installation calculates ordered onboarding, activation and purchase funnel progress; daily, weekly and monthly feature reach; sessions; daily returns through 90 days and weekly returns through 12 weeks; and repeat successful Scout use. Results include bounded performance ranges, app version/build, plan, photography preferences and controlled feature/outcome categories. The device retains only the summary state needed for these calculations, not an action history or analytics identifier. Observation windows renew after 90 days on the next relevant use and distinguish initial from continuing measurement. Calendar-period summaries are replaced when the period changes. This includes existing installations after an upgrade and is not a count of new downloads or identified people.

Counts pass through LightScout's endpoint hosted by Supabase before reaching PostHog's EU service. The endpoint does not forward the device's IP address, cookies, account credentials or device headers to PostHog, and does not log analytics request contents. Supabase necessarily receives network information to deliver and secure the request. PostHog receives population statistics with person-profile creation and geoIP processing disabled. We use these statistics solely to assess and improve the app; we do not construct individual behavioural profiles or join these statistics to account, advertising or purchase records. Existing individual data from earlier builds remains subject to the earlier disclosures and deletion process.

Statistical contributions are grouped by UTC day, release channel, cohort or calendar period and controlled categories. They go through LightScout's first-party relay to PostHog's EU service. No account or installation identifier, device fingerprint, session identifier, searches, selected places, Scout content, photographs or locations enter this statistical transport. Delivery references prevent duplicate uploads and are not reused across statistical rows. The relay does not forward client IP addresses, cookies or request headers; PostHog person profiles and geoIP processing are disabled. Unsent contributions remain bounded and expire after at most 14 UTC days. The figures describe how installations use the app; LightScout cannot open an installation's activity history or join these contributions to account, advertising or other-service data. Earlier counter builds calculated only fixed day-1, day-7 and day-28 cohorts. Earlier builds that offered a separate Device usage analytics choice could send retained installation histories after permission; the later statistical builds stopped that mode and discarded its unsent events. An existing deletion reference remains locally available in Settings for requests about previously sent data and is never used for new collection. Device backups can carry local statistical state and preferences. Turning off Help improve LightScout stops future statistics, clears unsent contributions and local calculation state, and does not affect features or purchases. It cannot recall an upload already accepted by a provider.

Earlier builds with a separate Detailed app journeys setting: This separate setting is off until you choose to turn it on. Once enabled, the app sends bounded feature, onboarding, Scout, paywall, purchase-flow and reliability events directly to LightScout's PostHog EU project with a random installation identifier. PostHog can use that identifier to calculate ordered journeys and return visits for opted-in installations. Events include controlled categories, subscription tier, app version/build and App Store or TestFlight channel. They do not include your LightScout account ID, name, email, photographs, searches, selected places, Scout content, precise coordinates, raw errors or flow identifiers. The SDK can also send the anonymous identifier and app/device context in configuration requests after opt-in. Automatic screen and tap capture, session replay, surveys, push events and error capture are disabled. PostHog person profiles and geoIP enrichment are disabled. Because this stream goes directly to PostHog, PostHog receives the network information needed to deliver the request; the relay's IP and header exclusion described above applies only to basic statistics. This information is used to improve the app, not for cross-company advertising tracking.

You can turn Detailed app journeys off in Settings. The app then stops capturing these events and discards events still queued on the device along with its stored installation identity. Turning off Help improve LightScout also withdraws this separate choice. Neither action can recall data already accepted by PostHog or stop an upload already scheduled or in flight. The native events are a self-selected sample and are kept separate from the default statistical totals. PostHog does not currently enforce an automatic expiry for these events. LightScout does not link this installation identifier to your account or retain a separate identity mapping solely for analytics requests.

These builds do not start AppsFlyer's individual attribution collection. When product statistics are enabled in an App Store installation, the app registers install attribution through Apple's SKAdNetwork mechanism. Apple controls the privacy thresholds, delays and information included in those postbacks; copies use the configured AppsFlyer receiving endpoint. This is limited install attribution, not cross-app profiling or a user-level marketing journey. Turning off Help improve LightScout stops future counter collection and registration attempts and removes unsent counters. It cannot recall a request or Apple attribution already registered. App features, purchases, account processing, Gemini permission and reliability diagnostics remain separate.

SDK-only builds before LightScout 2.7.5 whose analytics notice mentions screen names, taps and session IDs: These builds use the official PostHog iOS SDK directly, with one optional Help improve LightScout choice. They no longer send the anonymous statistical counters through our Supabase endpoint. Analytics stays off until you accept the current notice. A refusal from either earlier analytics control stays off; earlier acceptance does not automatically authorise the added screen and interaction collection.

After permission, PostHog's EU service receives app opens, backgrounds, installations and updates; named screens; taps, control interactions and repeated taps; and bounded Scout, purchase-flow and reliability events. The SDK includes random installation and session identifiers, app version/build, operating-system and device information, locale, screen dimensions and network type. Control text and selected values are excluded from autocapture; developer-supplied control labels may be included. We do not send photographs, searches, selected places, report content, account IDs, names, emails or raw errors in analytics. Session replay, surveys, push capture and PostHog error capture remain off; person-profile creation and geoIP enrichment remain disabled. PostHog receives the network information needed to deliver direct requests, including SDK configuration requests. This is product improvement, not cross-company advertising tracking.

Turn Help improve LightScout off in Settings to stop new SDK capture and discard locally queued events and the stored installation identity. An upload already scheduled or in flight may complete, and withdrawal cannot recall data already accepted by PostHog. Unsent counters from earlier builds are discarded on upgrade, never converted into SDK event histories. These SDK reports describe opted-in installations, not every installation or identified account. Apple’s aggregate install-attribution registration remains separate and can run before an SDK analytics choice; an explicit analytics refusal stops future registration attempts. It cannot recall attribution already registered. No automatic expiry is currently enforced for PostHog events; we retain the general data-rights contact below and do not create a separate account-to-installation identity mapping.

LightScout 2.7.5 builds with Usage statistics, including builds 135 and 136: Usage statistics is on for a fresh installation. Earlier explicit refusals and withdrawals remain respected. On-device summaries measure onboarding, feature use, purchase-flow outcomes and return visits using the statistical flow and bounded observation windows described above. Anonymous counters pass through LightScout's Supabase endpoint to PostHog in the EU. They do not contain account, installation or session identifiers, photos, searches, selected places, report content, precise locations, advertising attribution or transaction amounts and references. You can turn Usage statistics off in Settings to stop collection and clear unsent counters and local summary state, independently of detailed analytics, and turning off detailed analytics does not turn these statistics off. The two streams are reported separately; anonymous counters are not joined to account or advertising journeys.

LightScout 2.7.5 build 136: detailed analytics and account journeys. In App Store and TestFlight builds, detailed analytics is on by default. LightScout does not show an analytics invitation. You can turn it off at any time in Settings > Help improve LightScout > Detailed analytics and ad measurement; an earlier refusal made in a previous version stays off. While it is on, the official PostHog iOS SDK sends app actions, screens, taps and app/device information directly to PostHog's EU service using random installation and session references. Taps are identified only by developer-defined element identifiers, not on-screen text. Earlier 2.7.5 builds, including build 135, asked you to accept an analytics invitation before this collection began. When you sign in, a random, server-issued account analytics reference joins activity across your devices and can connect earlier permitted anonymous activity on the same installation to that account. PostHog creates a person profile only for an identified account. This reference does not contain your name or email address and is distinct from your sign-in account ID. Signing out resets the SDK identity so later activity can start under a new anonymous identity; switching accounts keeps their identities separate. Developer-defined element identifiers help us understand taps, while on-screen text and selected values remain excluded. Photos, searches, selected places, report content and transaction amounts and references are excluded. Session replay stays off, as do surveys, push capture, PostHog error capture and geoIP enrichment.

LightScout 2.7.5 build 136: advertising measurement. In production App Store installations, the same Detailed analytics and ad measurement setting controls AppsFlyer's standard iOS SDK, which measures installs, sign-ups, completed Scouts and fresh verified purchases. Purchase events include the purchase amount and currency when available. This client measurement does not send renewals, refunds, restored purchases, pending or cancelled payments. The AppsFlyer SDK does not start or send data in sandbox or TestFlight installations. We use these signals to measure how advertising brings people to LightScout and whether it leads to use of the app and purchases. AppsFlyer receives the app/device and network information needed to provide this service. LightScout does not request Apple's App Tracking Transparency permission and does not track you as Apple defines tracking. AppsFlyer runs without Apple's advertising identifier (IDFA) and vendor identifier (IDFV), LightScout sets no customer or account ID in AppsFlyer, and LightScout blocks AppsFlyer from sharing individual-level data with advertising partners. Advertising networks such as Meta and TikTok receive only Apple's aggregated, privacy-preserving campaign measurement (SKAdNetwork and AdAttributionKit), not data about individual users. LightScout no longer adds advertising-source or campaign details to PostHog events. These restrictions apply to AppsFlyer; RevenueCat's independent purchase-related IDFV use remains as described above. Earlier 2.7.5 builds, including build 135, required you to accept an analytics invitation first and made individual-level AppsFlyer features depend on Apple's tracking permission.

Earlier refusals and withdrawals stay off after upgrading to build 136. Before a detailed analytics choice is made, an App Store installation may register aggregate install attribution directly with Apple; when AppsFlyer starts, the SDK takes over management of Apple attribution. Turning off detailed analytics and ad measurement stops new PostHog SDK and AppsFlyer collection and discards locally queued detailed events, pending advertising events and identity state, and clears the local hashed purchase-dispatch history; this does not turn the independent Usage statistics setting on or off. Neither control can recall requests already sent, attribution already registered or data already accepted by a provider. Detailed PostHog reports describe accounts and installations with detailed analytics on, separately from the statistical population. The retention and data-rights information below continues to apply.

App reliability diagnostics: In normal production releases, LightScout uses Google Firebase Crashlytics independently of the optional usage-analytics choice. Crashlytics receives crash reports and bounded non-fatal diagnostics used to find and fix reliability problems. These reports can include stack traces; app version; device model, architecture and operating-system details; relevant process, memory and storage state; a Crashlytics installation or session identifier; and developer logs or fixed diagnostic fields associated with the failure. LightScout's custom account diagnostic is limited to a fixed processing stage and bounded error type; it does not deliberately add your name, email address, Scout prompt, selected place or precise coordinates. Crash and Other Diagnostic Data are linked and used for App Functionality, not advertising or cross-company tracking. Firebase states that Crashlytics keeps crash stack traces and associated installation identifiers for 90 days before starting removal from live and backup systems. Withdrawing optional usage analytics or deleting your LightScout account does not itself recall Crashlytics reports already sent. Contact support@lightscout.app for a broader data-rights request.

Ideas, Suggestions and Feedback

In versions with the “Help shape LightScout” invitation on Home and in Settings, you can send optional feedback without signing in or providing an email address. The form sends your message, feedback category, whether you opened it from Home or Settings, app version and build, operating-system version, platform and language/region setting to our shared feedback service hosted by Neon. A random submission reference prevents duplicate messages when a send is retried; it is not an account or device identifier. We use this information to understand suggestions, investigate problems and decide how to improve LightScout. The form does not automatically attach your LightScout account ID, email address, device identifier, Scout content or location. Please avoid including personal information in your message.

Drafts stay on your device when you close the form or a send fails. They are removed after a confirmed successful submission or when you choose Discard draft. Accepted feedback has no automatic expiry and remains in Neon until we delete it. Because feedback is not linked to your LightScout account, deleting your account does not delete these messages. If you contact us about a submitted message, provide enough detail to help us find it; we cannot locate anonymous feedback from an account ID alone.

The anonymous form has no reply channel, so we cannot reply individually through it. Feedback helps shape our plans, but we cannot promise to build every suggestion. We do not send feedback text or submission references to our product-analytics services or use them for advertising tracking. As with any network request, Neon receives the network information needed to deliver and secure the service.

How We Use Your Information

We use the information described above to provide, secure, measure and improve LightScout, including the version-specific attribution described above. We do not sell or rent personal data, and we do not use it to personalise third-party advertising. Build 9's attribution sharing is disclosed above. LightScout 2.6.0–2.7.4 block AppsFlyer integrated-partner sharing or keep the AppsFlyer SDK off, as described for each version. In 2.7.5 build 136, LightScout blocks AppsFlyer sharing of individual-level data with advertising partners and does not request Apple tracking permission.

Data Storage and Security

Account data, saved guides, credits, and website waitlist submissions are stored using Supabase. Guide requests are processed by our AI and infrastructure providers. We use HTTPS encryption for data in transit and service-level access controls.

In LightScout 2.6.0 through 2.7.1, when analytics collection is enabled and you sign in, LightScout uses a server-issued random analytics identifier to recognise your activity across your devices. It is not your account ID and does not encode it. Activity before sign-in remains app-instance or session based and is not joined to your later account. Google Analytics event data is retained for two months and user data for up to 14 months, with the user-data period reset by new activity. In LightScout 2.7.2 builds with “Share usage analytics”, PostHog stores the bounded individual events described above in its EU project. Earlier aggregate builds with “Help improve LightScout” send the basic counters described above; their separate Detailed app journeys setting enables the narrower native stream. SDK-only builds before 2.7.5 instead send the optional installation-level events described above. In 2.7.5 build 136, detailed analytics, when on, additionally uses the random account reference to connect signed-in activity across devices, and AppsFlyer provides the advertising measurement described above. An earlier refusal keeps it off. Automatic expiry is not currently enforced for PostHog event data. Withdrawal cannot recall data already sent.

Google AI processing: Scout requests are processed through LightScout's authenticated server route and Google Cloud's Vertex AI Gemini service. Google's service terms state that customer data is not used to train or fine-tune AI or machine-learning models without prior permission. Google's published Gemini models cache project-isolated copies of inputs, generated outputs and derived data in memory, not at rest, for up to 24 hours to improve service performance; the production project currently uses this default cache setting. Request-response logging is not configured for the production Gemini model. If Google's automated safeguards flag suspicious activity and the account is within abuse-monitoring scope, Google may retain the flagged prompt for up to 90 days solely to investigate abuse. Google states that this material is not used to train or fine-tune models. LightScout does not promise zero provider retention. Withdrawing in-app permission stops future Scout requests; it does not recall an in-flight request or by itself delete provider-held cache or logs.

Generated Scout responses: LightScout stores each completed generated Scout response in a private account-linked server run record so the same paid result can be returned after a retry, interrupted connection or relaunch. This happens even when you do not separately save the Scout in the app. A restricted service-only quality process may read one response ephemerally for a bounded sample or reported issue; the review interface does not return the account owner or request identity. Generated run responses currently have no separate scheduled expiry and remain until the associated LightScout profile or account is deleted. Deleting the account cascades those private run records. Separately saved Scouts remain subject to the save and deletion controls shown in the app.

Retention and deletion of attribution and purchase identifiers: The verified Google Analytics retention periods stated above are unchanged. We have not destination-verified a custom retention or deletion period for AppsFlyer identifiers or RevenueCat purchase/device mappings, so this policy does not invent one or claim those vendor-held records are immediately deleted. Deleting a LightScout account removes LightScout account data and our active analytics-identity mapping through the documented deletion route; it does not delete Apple's purchase records. We will update this policy after any vendor-side containment, retention or deletion change is separately authorised and verified in its destination.

Third-Party Services

LightScout uses the following third-party services:

  • Apple App Store for distribution and payments
  • RevenueCat for subscriptions, one-time credit packs, entitlements and purchase restoration
  • Supabase for data storage and the app statistics relay
  • Neon for optional anonymous product feedback
  • Google Firebase for Crashlytics, Gemini and (in releases up to LightScout 2.7.1) optional product analytics
  • PostHog's EU service for the build-specific product measurement described above
  • AppsFlyer for the version-specific App Store attribution described above
  • Cloudflare for website hosting, delivery and aggregate website analytics

We use these providers only for the purposes described in this policy and require them, through their applicable service terms and data-processing arrangements, to protect personal data to the same or an equivalent standard. LightScout remains responsible for telling you what is sent and why, obtaining required permission, and responding to data-rights requests we control. A provider may retain or delete data under the specific limits described above and its applicable terms.

Your Rights

You can request deletion of any data associated with your account by contacting us at support@lightscout.app. You can revoke location permissions at any time through your device settings.

You can change Google Gemini permission and the build-specific product-statistics or detailed-analytics setting separately in LightScout Settings. These controls stop future requests or collection; they do not automatically recall data already sent. You can request deletion of your LightScout account in the app and contact support@lightscout.app about provider data-rights requests. Apple purchase records are controlled by Apple and are not deleted when a LightScout account is deleted.

Contact

For privacy-related questions, contact us at support@lightscout.app.

LightScout
LocationsBlogAboutPrivacyTermsPhoto creditsContact

© 2026 LightScout · Photography Field Guide