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
March 30, 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.
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 a mix of on-device settings, account-backed dashboard data, 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 the account and session information needed to authenticate you, and Timli stores a saved dashboard snapshot in Clerk publicMetadata.
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, analytics, weather, and transit lookups.
Account authentication and account-backed dashboard storage.
If you sign in, Clerk processes account details such as your email address, authentication or session data, and the saved dashboard snapshot that Timli stores in Clerk publicMetadata.
Clerk 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.
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