Tracking Technologies
A closer look at the services that support LaneTrax, and the technologies used for measurement and communications.
The services below support the LaneTrax iOS app, its authentication and discount websites, backend, and communications. Our static landing page has no login, advertising pixels, or analytics trackers. The information processed by each service depends on the features you use and the service's role. See our Privacy Policy for information about retention, sharing, and your rights.
Data Flows lists service endpoints and domain families used by our integrations. An asterisk denotes subdomains. The list is not exhaustive; destinations vary by feature, region, and service configuration.
The information listed includes examples supplied by the App and our websites. Service connections can also involve IP addresses, device and App information, installation identifiers, and information generated by the relevant SDK. The combination depends on the integration and your use of the service; not every provider receives every category described on this page.
Service Operations
These services support accounts, infrastructure, support, subscriptions, and message delivery. A service can support more than one purpose; this grouping does not mean it receives only operational information.
| Service | Description | Data Flows | Information processed |
|---|---|---|---|
| Firebase Hosting | Serves our websites and routes authentication-recovery and discount requests to backend functions. |
|
IP addresses, requested URLs, browser and request headers, and connection information. Depending on the page, URLs may include a sign-in recovery identifier, discount code, campaign parameters, or language choice. |
| Firebase Authentication | Authenticates users and manages access to LaneTrax accounts, including email-link sign-in. |
|
Account identifiers, email addresses, sign-in provider information, authentication tokens, and email sign-in action links. |
| Google Sign-In | Allows users to sign in with a Google Account and authenticate their LaneTrax account through Firebase. |
|
Google account identifiers, sign-in tokens, and profile information made available through the sign-in flow, such as name and email address. |
| Cloud Firestore | Stores account, session, and bowling records in a U.S. multi-region database. |
|
Account and session identifiers, profiles, shot results, trajectories, preferences, and record metadata; temporary sign-in recovery records used by the authentication website. |
| Firebase Realtime Database | Synchronizes active-session state between connected devices using a database in U.S. Central. |
|
Active-session identifiers, device identifiers and names, timestamps, and recent-shot state. |
| Google Cloud Storage | Stores replay media, diagnostic images, and replay metadata in U.S. Central, EU multi-region, and Asia multi-region buckets. Recovery-copy retention is described in the Privacy Policy. |
|
Compressed replay clips with available audio, diagnostic lane images, detailed replay JSON, and account/session identifiers in object references. Replay storage supports storefront-based selection and a user-changeable server setting. |
| Cloud Functions | Runs backend operations for authentication, discount lookups, subscriptions, referrals, document generation, support, and security checks. |
|
Operation-specific account, session, transaction, referral, request, and device-integrity information; email sign-in and recovery requests and discount codes. |
| RevenueCat | RevenueCat manages purchases, subscriptions, and access to paid features. |
|
Purchases and entitlements; account ID, email/name, analytics and attribution identifiers, notification token, and configured attributes are supplied by the App. |
| Intercom | Intercom provides customer messaging and support. |
|
Account ID, email/name, account creation date, notification token, custom properties, support messages, and shared analytics events. These events can include diagnostic fields and content references. |
| Customer.io | Customer.io delivers email, push notifications, and messages within the App, processes App events, and measures message engagement. It also delivers authentication emails. |
|
Account ID, email/name/language, account creation date, custom properties, device/push information, an advertising identifier when available, and shared events including diagnostics and content references. The notification extension supports message delivery and measurement. Engagement information includes email opens and link interactions; no landing-page tracker is used. Authentication email delivery uses the recipient's email, sign-in link, request time, and language. Sign-in links are excluded from click tracking. |
| Cobrowse | Cobrowse enables live support sessions that you approve. |
|
Account ID, email, display name, device identifier and hardware model identify your App installation for support, independently of approval for screen viewing. An approved session can expose the App view and camera preview while the lane selector is shown. This screen access is used to provide live assistance. |
| Sign in with Apple | Allows users to authenticate with their Apple Account. |
|
Apple sign-in identifiers and tokens, and name and email information made available through the sign-in flow. |
| App Store In-App Purchase | Processes purchases and subscriptions through StoreKit. |
|
Products, purchases, subscription status, and signed transaction information. |
| Firebase Cloud Messaging | Registers the App installation for push messaging, associates its Apple push token, and processes notification-receipt events. |
|
App installation identifiers, messaging registration tokens, Apple push tokens, App/device information, and notification event information. |
| Apple Push Notification service | Delivers notifications to the user's device. |
|
App/device notification tokens and notification payloads. |
| App Attest | Helps validate App instances and protect sensitive operations. |
|
App-instance key identifiers, attestation information, challenges, and assertions. |
Analytics and Diagnostics
Usage measurement, crash reporting, and communications measurement have different purposes and may involve different information. Customer.io's message measurement is included in its entry under Service Operations.
| Service | Description | Data Flows | Information processed |
|---|---|---|---|
| Google Analytics | Google Analytics measures App usage and events. Its retention settings are described in Section 6 of the Privacy Policy. |
|
Account ID, custom user properties, and shared events covering use, purchases, diagnostics, geometry, and account-linked content references. |
| Firebase Crashlytics | Firebase Crashlytics collects crash reports and diagnostics to help resolve failures. |
|
Account ID, properties, nonfatal errors, and camera, session, or device context. |
| Firebase Performance Monitoring | Firebase Performance Monitoring measures the speed and reliability of App operations. |
|
Traces for sessions, shots and PDF operations; identifiers, timings, frame rates, counts and errors. |
Advertising and Attribution
We use event information to measure how people discover and use LaneTrax, evaluate campaigns, and improve advertising performance. Shared events may include usage and purchase activity, lane coordinates, shot-processing and performance information, errors, and references to video, JSON, or diagnostic images. These references may contain account and session identifiers. A content reference is distinct from the recording itself but may still link the event to a person or session.
| Service | Description | Data Flows | Information processed |
|---|---|---|---|
| Meta SDK | Meta uses App events for advertising measurement and, where configured, targeting and personalization. Its role varies by activity; see Section 5 of the Privacy Policy. |
|
Shared events and their diagnostic/content-reference parameters, app activity and conversion events. |
| AppsFlyer | AppsFlyer connects installations and App events with advertising campaigns and referral links. OneLink carries discount-page referrals through installation and into the App. It processes covered end-user information on our behalf and can pass information to partners we configure; those partners' uses are separate. |
|
Shared events, account ID used as the customer identifier, attribution and deep-link information. Discount installation links include discount codes and campaign parameters. Following a OneLink also involves connection and device/browser information and can support attribution before sign-in. |
| TikTok iOS SDK | TikTok measures App events and advertising campaign results. |
|
Shared events, account ID, display name and email supplied to the SDK. |
Your Choices
You can manage app tracking, camera, microphone, and notification permissions in your iOS settings. Your tracking permission does not control all analytics, diagnostic, or account-related processing. Wherever you live, you can request access, correction, deletion, or the training opt-out using the request process in Section 9 of the Privacy Policy. That section also explains how to exercise applicable rights to object to processing, opt out, or withdraw consent.
The Replays setting controls new replay recording/export, not every diagnostic upload or analytics event, and does not cancel previously queued uploads. Audio depends on microphone permission. Cobrowse live support requires explicit approval.
Use the unsubscribe link in marketing emails to stop receiving them. Your email software may let you block remote images; doing so does not prevent all link interaction measurement. Storage, retention, and deletion are explained in Section 6 of the Privacy Policy.
Read Section 4 of the Privacy Policy for more about these technologies.