DriverWatch NYC

DriverWatch NYC may store the TLC license number, TLC plate number, plate state, optional TLC vehicle license number, optional deadline dates, reminder preferences, optional preferred language, and user mode you enter during onboarding or profile setup.

TLC exam candidates may also save an optional TLC application number, exam timeline, and local exam progress. This information is used to run user-requested checks, keep saved reminders, personalize the app, and show prior results.

DriverWatch NYC checks available public TLC, NYC, and related public-data sources for driver active-list status, vehicle active-list status, open parking or camera ticket information, TLC application status for exam candidates, and limited DMV-related public risk signals when a source is available.

Public sources can be delayed, incomplete, unavailable, or changed by the publisher. DriverWatch NYC does not provide government status from TLC or DMV.

Manual checks can be run in the app. When backend monitoring is configured and enabled, DriverWatch NYC may sync minimal monitoring fields to Supabase: TLC license number, preferred language, plate number, plate state, optional TLC vehicle license number, linked anonymous user id, and monitoring-enabled status.

Backend monitoring does not sync TLC application numbers, local exam progress, private portal credentials, or payment credentials. Scheduled checks compare public-data results and create alerts only for meaningful changes.

Push notification text is generic and does not include TLC license numbers, plates, names, raw public records, or private account details.

Vehicle checks use saved plate or vehicle-license details against available public data. Ticket checks use saved plate and state information to look up open parking or camera ticket data and may store a minimal ticket snapshot for change detection.

Deadline reminders are based on user-saved dates or limited public expiration dates where supported. DriverWatch NYC does not process ticket payments, dispute tickets, submit forms, or decide driving eligibility.

Driver Monitor Pro subscriptions and TLC Exam Prep one-time purchases are handled through the App Store or Google Play purchase flow and RevenueCat.

DriverWatch NYC may receive purchase entitlement status from RevenueCat so the app can unlock purchased features. DriverWatch NYC does not collect or store full payment card numbers, bank information, App Store credentials, or Google Play credentials.

DriverWatch NYC may use Supabase for optional anonymous authentication, persisted app sessions, monitoring profile sync, backend check results, alerts, and Expo push tokens when configured.

The app may use Expo services for app runtime features and push notification delivery. The app may use RevenueCat to manage mobile purchase entitlements. These providers process information only as needed to support the app features described in this policy.

DriverWatch NYC does not ask for or collect SSN, TLC UP password, MyDMV password, bank information, tax ID, full DMV abstract, unnecessary location tracking, or private portal credentials.

The app does not scrape TLC UP or MyDMV.

Some profile details, saved deadlines, latest check results, app language, reminder preferences, notification status, Supabase anonymous session data, and exam progress may be stored locally on the device.

If Supabase monitoring is configured, minimal synced monitoring rows, check results, alert events, and Expo push tokens may be retained while monitoring is enabled or as needed to provide the service.

Delete App Data in Settings calls the delete-user-data backend function with the current Supabase session when available, deletes only synced rows for that authenticated app session, disables remote monitoring and push rows for that session where available, clears local app data from this device, and restarts onboarding.

If synced deletion fails, local data is not cleared so the user can retry. Purchases, RevenueCat records, App Store or Google Play records, and external public data sources are not deleted.

DriverWatch NYC uses public mobile keys only in the app and keeps server-only Supabase service-role keys, push credentials, Apple keys, Google keys, and RevenueCat private keys out of the mobile app.

Supabase-backed rows are designed to be user-owned with Row Level Security when backend sync is enabled.

DriverWatch NYC is intended for TLC drivers, TLC applicants, and adult users preparing for TLC-related work. It is not directed to children.

This policy may be updated as app features, data sources, providers, or store requirements change. The effective date above should be updated when the policy changes.

For privacy questions or deletion requests, use the support contact listed on the App Store or Google Play listing for DriverWatch NYC.