TripIQ Beta Privacy Policy

Purpose

TripIQ is an Android ride-request analysis tool for rideshare drivers. It helps estimate whether a supported ride request meets your standards by calculating hourly value, per-mile value, and a GO, MAYBE, or NO GO result.

Screen Capture and OCR

When Real-Time Mode is active, TripIQ uses Android screen analysis only after you approve the Android permission prompt for that session. TripIQ reads visible screen frames so it can identify and analyze supported ride-request screens.

TripIQ performs text recognition on the device using Google ML Kit Text Recognition. TripIQ does not create or save a screen-recording video.

In the current beta, TripIQ does not upload screenshots, screen frames, OCR images, or OCR text to TripIQ-operated servers.

Ride-Request Information

TripIQ may process ride-request details visible on supported screens, including fare, pickup time, pickup distance, trip time, trip distance, platform label, other visible request text where applicable, calculated hourly value, calculated per-mile value, and the resulting GO, MAYBE, or NO GO decision.

The current beta keeps same-day dashboard aggregates locally, such as offer counts, decision counts, and value totals by platform. TripIQ does not maintain a full persistent ride history in the current beta.

Location

The current beta does not request precise location, approximate location, or background location access.

Local Diagnostics

TripIQ may store local diagnostic logs to help troubleshoot beta issues. These logs may include raw and normalized OCR text, calculated ride values, parser details, lifecycle and recovery events, app version, device model, Android version, memory details, screen-analysis status, and related troubleshooting information.

Local daily diagnostic log files are cleaned up after approximately 30 days.

TripIQ includes a diagnostic capability for OCR PNG and TXT artifacts, but that artifact saving is disabled in the current beta.

Diagnostic Sharing

The current beta does not automatically upload diagnostic logs and does not include an in-app diagnostic sharing path. If you manually send diagnostic files to support, review them first and remove or avoid sending passenger names, complete pickup or dropoff addresses, account credentials, private screenshots, or other unnecessary personal information.

Preferences and Local Storage

TripIQ stores local preferences and operating state, including onboarding completion, decision thresholds, diagnostic logging mode, Real-Time Mode recovery state, overlay position, process session identifiers, a short lifecycle event buffer, and same-day dashboard summary values.

Android Backup and Device Transfer

TripIQ stores diagnostics, ride-analysis information, preferences, and dashboard statistics locally on the device. TripIQ is configured to prevent its app data from being included in Android cloud backups or Android device-to-device transfer extraction.

Third-Party Services and SDKs

The current beta uses Google ML Kit Text Recognition for on-device OCR. The current beta does not include analytics, advertising, crash-reporting, or TripIQ telemetry SDKs.

Data Retention and Deletion

Same-day dashboard aggregates reset by date. Local diagnostic logs are cleaned up after approximately 30 days. You can also remove locally stored TripIQ data by clearing app storage or uninstalling TripIQ through Android settings.

Android Permissions

TripIQ uses display-over-other-apps permission to show the result overlay, foreground-service capability so Real-Time Mode can continue while active, and Android screen analysis permission for user-authorized screen capture during an active Real-Time Mode session.

Security Limitations

TripIQ stores beta diagnostics and app data locally on your device. Device security, screenshots taken outside TripIQ, files you manually share, and manufacturer-specific transfer behavior outside standard Android backup and extraction settings may be outside TripIQ's control.

Children

TripIQ is intended for rideshare drivers and is not directed to children.

Future Changes

TripIQ may introduce additional optional features in the future. If a new feature materially changes how information is collected or used, this policy and applicable Google Play disclosures will be updated before the feature is enabled.

Contact

Questions about this policy can be sent to support.tripiq@gmail.com.