Timli keeps public PATH tools open, offers optional signed-in dashboard features, and tries to be specific about what data stays on your device versus what is shared with service providers.
Effective date
March 30, 2026
Last updated
October 11, 2026
This notice applies to www.timli.app, timli.app, their localized routes, and legacy livepathtracker.com traffic during the transition. It covers public PATH tools plus signed-in dashboard features for PATH, HBLR, and MTA riders. This notice also covers Timli Pro commute boards, subscriptions, and billing support.
Timli is the current product name. The official web address is www.timli.app; timli.app redirects there, and you may still see livepathtracker.com during the transition. Support remains available at livepathtracker@gmail.com.
The service handles on-device settings, account-backed dashboard and Pro board data, subscription and billing records, station reports, location signals, analytics events, and transit lookup data.
Timli stores most guest-state preferences in your browser so the app can remember how you use it between visits.
If you sign in, Clerk processes your account and session information. Timli stores your saved dashboard settings and Pro access status in Clerk public metadata, and Pro commute boards in Clerk private metadata.
Stripe hosts Checkout and the Customer Portal for payments, invoices, payment-method updates, and subscription management. Payment details entered on those pages go to Stripe; Timli does not store raw card numbers or security codes.
If you report police or crowding at a PATH or HBLR station, Timli records the transit system, station identifier, and report time set by our server.
Precise geolocation is requested only when you enable local weather or the closest-station feature.
We collect usage and diagnostics data so we can understand how the app performs and which features riders actually use.
The app has to send selected route or stop identifiers through its APIs to load arrivals and alerts for the dashboard.
We use the providers below to run sign-in, Pro subscriptions, station reporting, analytics, weather, and transit lookups.
Account authentication, saved dashboard and Pro board storage, and Pro access status.
Clerk processes account and session information, saved dashboard settings in public metadata, Pro commute boards in private metadata, and Pro access status and expiry. It also stores the account self-deletion setting used during billing.
Clerk privacy policyStorage for temporary station reports and separate durable Timli Pro billing records, accessed through Timli servers.
Station report records contain transit system and station identifiers, report times, and temporary hashed account identifiers, without your name or email. Billing records separately contain account and Stripe Customer identifiers, checkout and plan identifiers, and request-retry records. Billing records are not anonymous station reports.
Hosted subscription checkout, payment processing, invoices, and the Customer Portal.
Receives your Timli account identifier and the contact, billing, and payment information you provide on Stripe-hosted pages. Stripe sends Timli subscription and payment events so we can manage Pro access. Timli does not store raw card details.
Stripe privacy policyPrivacy-focused website analytics.
Receives pageview-level analytics such as page URL, referrer, and browser or device metadata used to measure site traffic.
Plausible data policyProduct analytics for feature usage and app behavior.
Receives event names and properties such as locale, app version, transit mode, station count, QR campaign parameters, feature usage, and some selected station or route identifiers tied to your interactions.
OpenPanel privacySite traffic and performance analytics.
Receives aggregated usage and performance data such as page views, referrers, browser, operating system, device category, and geography-derived analytics under Vercel's service.
Vercel analytics privacyWeather data provider used only when weather is enabled.
When you turn on weather, your browser sends latitude and longitude directly to Open-Meteo to retrieve current weather conditions.
Open-Meteo termsPublic PATH arrival and alert data.
Timli servers request public PATH arrivals and alerts from Port Authority endpoints. These requests do not include your account data or precise device location.
PATH official websiteHBLR station metadata and schedule or arrival data for signed-in HBLR riders.
Timli servers send requested HBLR stop identifiers and standard server or network metadata needed to retrieve HBLR station or schedule and arrival data.
NJ Transit websiteConfigured backend used to fetch signed-in MTA metadata, arrivals, and route-scoped alerts.
Timli servers send selected route IDs and station IDs to the configured Transiter backend to load route catalogs, stops, arrivals, and alerts for your MTA cards.
Transiter projectTimli uses localStorage and sessionStorage to remember app preferences such as dashboard choices, QR visit history, banner dismissals, and update-dismissal state on your device.
If you use account features, Clerk may use essential cookies or similar session technologies to keep sign-in working. We do not use your personal information for cross-context behavioral advertising, and we do not load third-party ad network tags on this page.
Retention depends on whether the data lives in your browser, with an account provider, or with analytics or infrastructure vendors.
Preferences stored in localStorage or sessionStorage remain until you clear site data, overwrite the setting, or your browser removes the data.
Saved dashboard metadata in Clerk remains until you change it, delete the account, or ask us to delete account-backed data.
Billing account-to-customer links and billing-request retry records have no automatic expiration. Canceling Pro does not automatically delete these records or your saved boards. Processed Stripe event identifiers expire after 30 days. Stripe retains its own payment and invoice records under its policies. Contact support to request review or deletion of account-linked billing data.
The latest report for each station expires from live storage after 30 minutes. A fresh report replaces it and starts a new 30-minute period. Hashed account identifiers used for submission limits expire after five minutes. These periods apply to live application storage; infrastructure logs and backups follow provider policies.
Timli does not retain precise geolocation on its own servers. Weather lookups may be logged by Open-Meteo under its own policies.
Analytics and infrastructure records are retained according to vendor settings and our operational or security needs.
You can use core PATH features without an account. You also have browser-level controls and can email us about account-backed data.
To make an access, deletion, or correction request, email us at livepathtracker@gmail.com and include enough detail about the account or device context for us to verify the request.
Timli does not knowingly sell personal information or use personal information for cross-context behavioral advertising.
Timli is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information through the service, email us and we will work to remove it.
We may update this notice as features, providers, or legal obligations change. When we do, we will update the last-updated date on this page and revise the effective date when needed.
For privacy questions, California requests, or account-backed data requests about Timli, email:
livepathtracker@gmail.com