Privacy Policy
Last updated
This Privacy Policy applies to CA DMV Test: California Permit, NY DMV Test: New York Permit, WA DMV Test: Washington Permit, NJ Driver, FL DMV Test: Florida Permit, TX DMV Test: Texas DPS Permit, and the usdmv.app website. The apps require no registration or login and have no user accounts. Practice records are stored locally, while usage events and other data described below are sent to network services, including Firebase and AdMob.
Developer and privacy contact
The developer responsible for the apps covered by this Privacy Policy is Flownet Tech LLC. Our developer name on Google Play is FLOWNET TECH. For privacy questions, contact [email protected].
- FL DMV Test: Florida Permit —
app.usdmv.fl— [email protected] - TX DMV Test: Texas DPS Permit —
app.usdmv.tx— [email protected]
The addresses above provide app-specific support for FL and TX; [email protected] is the general website and privacy contact. Coverage by this policy does not indicate store availability in every region or on every platform.
| Data | Handled by | Why |
|---|---|---|
| Saved practice records and settings | Local app storage; see analytics below | The app works offline |
| Payment details | Apple / Google | Subscription and one-time purchase billing — we never see your card |
| App usage and crash reports | Firebase (Google) | Fix bugs and see which features get used |
| Advertising data, available identifiers and device info | Google AdMob | Show ads to users on the free tier |
| Optional question feedback | Flownet Tech LLC | Investigate reported question issues; email is optional |
Information the app does not request
Core study features do not require your name, postal address, phone number, email, or card details. The apps do not request precise GPS location, contacts, photo-library, or microphone access. There is no app password because there is no account. Email and notes are optional when you submit question feedback.
No account, offline study and local data
Questions, explanations, and practice records are stored on your device; core study features work offline. Saved practice records are not uploaded to our servers. Related usage events are collected as described under Firebase below. Analytics, crash reports, ads, purchases, and feedback use network services; going offline does not delete data already sent or guarantee that queued events will not be sent when you reconnect. Local data can be removed using the operating system’s app-data or app-removal controls, where available; backups are managed separately by your operating system. Clearing local data does not delete feedback or data already sent to our servers or SDK providers. There is no app account or account-deletion feature, and we currently do not provide a dedicated request process for deleting server-side data.
Subscriptions and purchases
VIP plans include weekly and monthly subscriptions and a one-time lifetime purchase through the Apple App Store or Google Play, subject to store availability. Those stores process payments and hold your billing details. The app receives purchase status to unlock VIP features; analytics includes purchase events (such as plan, amount and currency) and membership status. Purchases are managed through your Apple ID or Google account; we do not receive your card details. Active VIP access removes in-app ads but does not disable Firebase Analytics or Crashlytics, or guarantee that the advertising SDK stops all data processing.
Firebase (analytics and crashes)
Firebase Analytics and Crashlytics are enabled in release builds to understand feature use and diagnose failures. Analytics handles app-instance identifiers, device and app information, and approximate location derived from IP. Usage events include app opens, screen views, practice type and answer correctness, exam scores and duration, language, VIP status, subscription type, and purchase events. Crashlytics handles installation identifiers, crash stack traces, app and device state, and diagnostic logs; Analytics events may also appear as crash breadcrumbs. These data are sent to Google even though the apps have no user accounts.
Depending on platform permissions and SDK configuration, Analytics may also process available advertising or vendor identifiers. Advertising uses of Analytics data depend on Google account integrations and data-sharing settings; removing in-app ads does not change those settings.
Question feedback
Feedback is sent only when you submit a report. It includes a random report ID, question ID, state, language, issue category, selected answer (if any), app version and build, platform, VIP status, submission time, and a randomly generated device identifier stored locally and reused for feedback. Notes and email are optional; you can report an issue without an email address. Reports are sent over HTTPS to our feedback service and stored in a Cloudflare D1 database to investigate question issues. Stored reports include the context listed above and any email or notes you choose to provide. If you provide an email, the app remembers it locally for later feedback. Analytics records submission events, the issue category and whether an email was provided; those events do not include the email or note text. Avoid including sensitive personal information in notes.
Ads (Google AdMob)
The free tier shows Google AdMob ads. Google documents SDK collection and sharing of IP addresses (used to estimate approximate location), available device identifiers, app and ad interactions, and diagnostics for advertising, analytics, and fraud prevention. Identifiers depend on the platform and permissions, including Android advertising ID and app set ID where available. The apps do not track you across other companies’ apps or websites. The iOS apps do not request App Tracking Transparency authorization or access IDFA. Firebase and AdMob still process the data described in this policy. Active VIP access removes in-app ads but is not a sale/sharing opt-out or a switch to disable all SDK data processing.
The apps currently have no European advertising-consent dialog, consent-preferences screen, in-app sale/sharing opt-out switch, or age-based ad-request flags for minors. We do not promise that minors receive only non-personalized ads.
Sale, sharing and available controls
We do not sell personal information for money. Advertising-related disclosures can nevertheless qualify as sale or sharing under applicable privacy laws, including sharing for cross-context behavioral advertising under California law. See Do Not Sell or Share My Personal Information for current controls and their limitations.
Teens and children
The apps are study aids for teenagers and adults preparing for driver knowledge tests and are not directed to children under 13. FL and TX specifically target ages 13–15, 16–17, and 18 and older. This intended audience does not mean that age-based ad controls are implemented.
This website
Your language and theme choices are kept in your browser’s local storage. Our hosting provider, Cloudflare, processes website requests and may handle IP addresses, user agents, requested URLs, and security and traffic data. Pages also load Google Fonts, which sends requests to Google with network and browser information such as your IP address and user agent. There are no advertising cookies on this site, and we do not share website data for advertising. Website browser preferences do not change app SDK settings.
Your choices
Your operating system may offer advertising and tracking controls; available options depend on your device and system version. These controls do not disable every form of analytics or diagnostics. Active VIP access removes in-app ads. You can use the core practice features offline and choose whether to submit feedback or include an email address.
The limitations described here do not limit rights you may have under applicable law.
Provider privacy information
- Firebase — Privacy and security
- Firebase Analytics — Data collection
- AdMob — Android data disclosure
- AdMob — iOS data disclosure
- Google — Privacy Policy
Contact and changes
Write to [email protected] for privacy questions. We update the date at the top when this policy changes.