Your journey is not an advertising profile.

Information stored on your device

Saved routes and Home/Work places, alert preferences, quiet hours and app settings are stored on your device. Live features may send the travel parameters described below to their providers. These details are not sent to Fairlight Apps usage analytics.

Optional product usage counts

In builds that support optional usage reporting, it is off until you choose to share in Settings → Privacy & Analytics. Reporting availability varies by app version; an unavailable switch does not enable reporting. The coarse events can describe opening the app, selecting a tab, resolving a route from live or offline data, creating a saved route, enabling an alert, or a paywall, purchase or restore step. They may include app version, build, platform, a plan label or placement. They exclude station names, search text, journey details, exact location, advertising identifiers and customer identifiers.

Fairlight’s Cloudflare endpoint stores daily aggregate counters by these coarse dimensions, not a per-user event history or IP addresses in the counter database. Network services still process connection information to deliver a request. Turning reporting off stops new events and cancels in-flight requests; it cannot retract counts already received and combined with other usage. AnyTube does not save or replay an event queue. Ads and purchases are separate from the optional usage switch.

Website analytics and hosting

This website sends aggregate page-view and App Store click counters to the same endpoint, unless your browser reports Do Not Track. It sets no analytics cookies and sends no referrer, fingerprint or advertising identifier in the event payload. Cloudflare necessarily processes connection information to deliver and protect the website and endpoint; its infrastructure practices are separate from our aggregate counter database. See Cloudflare’s privacy policy.

Live Transport for London requests

Live line status, stop searches, nearby-stop lookups and journey planning send the query, station identifiers or origin and destination coordinates needed to answer the request to Transport for London. This includes coordinates of a place you select for a live journey. TfL processes those requests under its own terms and privacy practices. Fairlight Apps does not retain those travel parameters in its usage analytics.

Optional Google place search and walking directions

Google Places and Google Directions are used when configured in an app build. Place search can send your typed place or address to Google for suggestions and coordinates. Place-detail requests send place identifiers; walking-direction requests send origin and destination coordinates. These services also receive the connection information needed to answer a request. They are live travel features, not optional Fairlight usage reporting, so switching usage reporting off does not disable a search or directions request you initiate. See Google’s privacy policy.

Advertising

Advertising availability varies by app version. Some builds keep ad serving disabled while provider checks are pending. When enabled, free-tier Google Mobile Ads requests are configured as non-personalised, with Google’s publisher first-party identifier disabled. However, non-personalised does not mean data-free: Google may process approximate location derived from an IP address, app- or device-level identifiers subject to operating-system permissions, advertising interactions, performance, diagnostic and network information to deliver, secure and measure ads.

Advertising choices are separate from the optional usage switch. Where Google requires a privacy-options form, use Settings → Manage ad privacy choices; options may be unavailable in a build that disables advertising. Pro removes ads, not the purchase services needed to verify Pro. See Google’s privacy policy.

Purchases and restoring Pro

Apple processes App Store payments. RevenueCat uses an anonymous app user identifier, product and purchase history, and receipt and entitlement verification information to unlock and restore Pro, prevent fraud and provide purchase analytics. This purchase processing is not disabled by the optional usage switch. AnyTube does not ask for contact details to create a RevenueCat account, and Fairlight Apps does not receive your full card details. See RevenueCat’s privacy policy.

Notifications

If you enable alerts, iOS schedules or delivers notifications according to your choices. Background checks may request current line status from TfL. You can change notification permission in iPhone Settings and route rules inside AnyTube.

Support requests

If you email support, we receive the email address, message and troubleshooting information you choose to send so we can respond. Do not send passwords, card details, unredacted receipts or sensitive travel information. Support email is separate from optional usage reporting.

Retention and deletion

On-device data remains until you remove it, reset the relevant setting or delete the app. Deleting AnyTube does not cancel a subscription and does not erase aggregate counts or records held by Apple, Google or RevenueCat. Fairlight’s counter database has no customer identifier with which to find an individual’s events and does not impose an automatic expiry on the daily aggregate counts. Turning reporting off prevents new events; it does not delete earlier totals. Provider records and infrastructure logs are handled under the providers’ policies. Contact us about access or deletion of identifiable information you have sent directly to support.

Contact

Fairlight Apps · hello@fairlightapps.com