Privacy Policy

TripSignal Drive Privacy Policy

Effective Date: August 25, 2026
Last Updated: August 25, 2026

This Privacy Policy explains how Morgan Brothers Entertainment LLC (“Morgan Brothers Entertainment,” “we,” “us,” or “our”) handles information in connection with TripSignal Drive.

TripSignal Drive is designed primarily as an on-device driver decision-support tool. Trip-offer information is processed locally on the user’s device. Limited subscription, licensing, device-verification, and support information may be processed remotely as described below.

1. Core Privacy Principle

TripSignal Drive processes trip-offer information locally on the user’s device.

Trip-offer information, TripSignal calculations, TAKE / MAYBE / SKIP recommendations, locally generated offer journals, screenshots, OCR-derived offer content, and local technical diagnostics are not automatically transmitted to Morgan Brothers Entertainment LLC or uploaded to the TripSignal licensing backend.

TripSignal Drive does transmit limited subscription and device-verification information to TripSignal’s licensing service when required to verify paid access, enforce licensing rules, prevent unauthorized use, and protect the service.

Licensing information is separate from trip-offer information.

The licensing backend is designed not to receive trip-offer fares, pickup or destination information, screenshots, OCR text, Accessibility-derived offer content, TAKE / MAYBE / SKIP recommendations, internal offer reasons, or route information.

We do not sell personal information or trip-offer information.

2. Information Processed Locally

TripSignal Drive may process information visible in a supported rideshare or delivery offer, including:

• offered fare or estimated earnings;

• pickup time and distance;

• trip time and distance;

• service or trip type;

• visible pickup or destination information;

• visible route or stop information;

• other information displayed as part of the offer;

• information derived from OCR or Accessibility processing;

• calculated TripSignal metrics; and

• TripSignal TAKE / MAYBE / SKIP recommendations.

This information is used on the device to interpret supported trip offers, calculate metrics, apply user-selected rules, and present driver guidance.

Morgan Brothers Entertainment LLC does not automatically receive this trip-offer information.

3. Android Accessibility Service

On Android devices, TripSignal Drive may use Android Accessibility Service after the user voluntarily enables it and provides the required consent.

TripSignal Drive uses Accessibility Service to access visible information from supported rideshare or delivery offer screens so that the app can interpret the offer and calculate TripSignal guidance.

Depending on the supported offer and device state, this may include visible text and values such as fare, pickup information, time, distance, trip information, service type, and destination or route-related information displayed on the screen.

TripSignal Drive may also use supported Android screenshot or visual-recognition functionality as part of its local offer-processing system.

TripSignal Drive does not use Accessibility Service to:

• automatically accept rides;

• automatically reject rides;

• tap ride-offer buttons on the driver’s behalf;

• send messages;

• communicate with passengers or customers;

• autonomously modify another application;

• autonomously control Uber, Lyft, or another rideshare or delivery platform; or

• make the driver’s final ride decision.

The driver always makes the final decision.

Accessibility-derived trip-offer information is processed locally and is not sent to the TripSignal licensing backend.

The user can disable TripSignal Drive’s Accessibility access at any time through Android system settings.

4. OCR and Visual Processing

TripSignal Drive may use local optical character recognition (“OCR”), screenshot, or visual-processing functionality to interpret visible trip-offer information when supported by the device and app configuration.

OCR-derived offer content and screenshots used for TripSignal offer processing remain local to the device unless the user deliberately chooses to provide a file to Morgan Brothers Entertainment LLC, for example when requesting technical support.

TripSignal does not automatically upload OCR-derived trip-offer text or offer screenshots to the TripSignal licensing backend.

5. Driver Settings

TripSignal Drive may store settings selected by the user, including settings such as:

• minimum fare;

• earnings-per-hour thresholds;

• earnings-per-mile thresholds;

• service-time assumptions;

• operating assumptions;

• sound or voice preferences;

• display preferences; and

• Standard or other available TripSignal feature settings.

These settings are stored locally on the user’s device unless a future version expressly discloses otherwise.

They are not part of the TripSignal licensing request.

6. Standard Last Offer

TripSignal Drive Release 001 maintains a local Standard Last Offer state.

The Standard Last Offer may include locally stored information such as:

• platform;

• product or service type;

• TripSignal TAKE / MAYBE / SKIP decision;

• internal reason data;

• effective dollars per mile;

• effective dollars per hour;

• pickup percentage;

• fare;

• pickup time and distance;

• trip time and distance; and

• the path to the associated local screenshot.

The Standard user interface does not display the internal reason as a visible Reason field.

The Standard Last Offer is limited to one current retained offer.

A newer valid Last Offer replaces the previous retained Last Offer.

The Standard Last Offer and its associated capture are retained for up to approximately 24 hours, subject to normal app operation and storage availability.

TripSignal Drive provides a Clear Last Offer function that removes the Standard Last Offer state and its associated retained capture.

Clear Last Offer does not necessarily delete other separate operational journals or diagnostic files described below.

7. Local Operational Offer Journals

TripSignal Drive Release 001 includes a local operational offer journal used for product operation, technical evidence, and troubleshooting.

The journal may contain structured information relating to completed TripSignal offer processing, including information such as:

• timestamps;

• TripSignal decision identifiers;

• presentation-session identifiers;

• ingestion source;

• Uber or Lyft platform attribution;

• fare;

• pickup and trip time and distance;

• calculated time, distance, dollars-per-hour, and dollars-per-mile values;

• pickup percentage;

• TripSignal TAKE / MAYBE / SKIP recommendation;

• internal reason;

• technical parser or source classifications;

• audio and overlay request/outcome information;

• screenshot or capture references; and

• parsed summary or route/destination-related information.

These operational journal records are stored locally on the user’s device.

They are not automatically uploaded to the TripSignal licensing backend.

Release 001 may maintain:

• daily structured offer-journal JSONL files;

• daily structured offer-journal CSV files;

• a rolling structured offer journal containing up to approximately 1,000 recent records;

• a latest-offer structured record; and

• local presentation-event journal files.

Daily offer-journal files are subject to automatic deletion after approximately 30 days.

The rolling journal is limited by record count and may retain up to approximately 1,000 recent records.

The latest structured offer record is overwritten when a newer record is written.

Current Release 001 source does not establish a separate automatic age-based deletion rule for the local presentation-event journal.

These local operational records are not a centralized TripSignal analytics database.

8. Local Diagnostic Information

TripSignal Drive may create short-term local technical diagnostic records used for troubleshooting offer processing, parser behavior, overlay behavior, audio behavior, and application performance.

Local diagnostics may include technical information such as:

• timestamps;

• app package and version;

• device manufacturer and model;

• Android API level;

• OCR enabled state;

• technical ingestion source;

• source package;

• parser-rejection reason;

• parser invocation state;

• parsed offer metrics;

• evaluator metrics;

• TripSignal decision;

• technical reason;

• audio or overlay dispatch state;

• OCR fallback information;

• offer-screen state; and

• overlay timing or latency information.

Release 001 diagnostic files are short-retention local files. The current implementation uses approximately a four-hour diagnostic retention window, a limited rotating file set, and file-size rotation.

These diagnostic files remain local to the device and are not automatically transmitted to Morgan Brothers Entertainment LLC or the TripSignal licensing backend.

9. Screenshots and Captures

TripSignal Drive may create local screenshots or captures in connection with supported Last Offer or diagnostic functionality.

The Standard capture store is limited to one retained capture and a maximum retention period of approximately 24 hours.

Screenshots remain local to the user’s device unless the user deliberately exports or sends them.

Morgan Brothers Entertainment LLC receives a screenshot only if the user voluntarily provides it, for example by attaching it to a support communication.

10. No TripSignal Cloud Offer Database

TripSignal Drive does not require a separate TripSignal cloud account for its core offer-processing functionality.

TripSignal does not maintain a centralized TripSignal cloud database containing the user’s trip offers, local offer journal, screenshots, OCR-derived offer content, pickup or destination information, or TAKE / MAYBE / SKIP recommendation history.

TripSignal does maintain limited server-side licensing and subscription-verification records as described below.

Licensing records are separate from local trip-offer data.

11. Google Play Purchases and Subscriptions

On Android, purchases and subscriptions are processed through Google Play.

Morgan Brothers Entertainment LLC does not directly receive or store the user’s full payment-card information for purchases processed by Google Play.

Google processes marketplace, billing, and payment information under Google’s own terms and privacy policies.

TripSignal Drive uses Google Play Billing to determine purchase ownership and to support subscription activation and verification.

12. Licensing and Subscription Verification

TripSignal Drive uses a TripSignal-operated licensing service to verify subscriptions and enforce licensing rules.

When licensing verification is required, the Android app may send limited information to the TripSignal licensing service, including:

• the TripSignal Android package name;

• Google Play product or subscription identifier;

• Google Play purchase token;

• a TripSignal device-binding identifier;

• TripSignal version code;

• TripSignal version name; and

• applicable subscription or base-plan identifier.

The device-binding identifier is derived by the app from Android device information for the purpose of licensing and device-binding enforcement.

The TripSignal licensing service verifies subscription status using Google Play’s server-side subscription-verification systems.

The purchase token is received by the licensing service for verification. Persistent TripSignal licensing records use cryptographic fingerprints rather than storing the raw purchase token as the licensing-record identity.

Persistent device-binding records likewise use cryptographically transformed device identifiers.

Sanitized TripSignal licensing logs use shortened cryptographic token and device fingerprints rather than raw purchase tokens or raw device-binding identifiers.

TripSignal licensing requests do not include trip-offer fares, pickup information, destination information, screenshots, OCR-derived offer text, Accessibility-derived offer content, TripSignal recommendations, internal offer reasons, or route information.

13. Server-Side Licensing Records

TripSignal Drive maintains server-side licensing records required for subscription verification, licensing enforcement, fraud prevention, security, device binding, support, and service operation.

These records may include information such as:

• cryptographic purchase-token fingerprint;

• cryptographic device-binding fingerprint;

• product identifier;

• subscription or base-plan identifier;

• first binding time;

• last verification time;

• entitlement expiration time;

• app version code;

• support reference information;

• linked or superseded licensing state;

• released licensing state;

• licensing reset information;

• previous-device information;

• device-transfer state; and

• related licensing timestamps and status information.

These records do not contain the user’s TripSignal offer journal or trip-offer content.

14. One-Device Licensing

TripSignal Drive may enforce a one-entitlement / one-active-device licensing rule.

A valid Google Play entitlement may be bound to one active physical device at a time.

An attempt to use the same entitlement on another physical device may be rejected by the licensing service.

The licensing system may periodically re-verify subscription status and device-binding state.

Temporary network, Google Play, Google Cloud, or TripSignal licensing-service availability issues may temporarily prevent or delay verification.

15. Cloud Licensing Logs

TripSignal’s licensing backend creates operational logs for licensing, security, and troubleshooting.

These logs may include:

• licensing outcome;

• licensing status;

• shortened cryptographic token fingerprint;

• shortened cryptographic device fingerprint;

• TripSignal version code;

• server processing time information; and

• subscription/base-plan identifier.

These operational logs are not trip-offer analytics.

The licensing backend is designed not to log raw trip-offer content.

16. Google Cloud Services

TripSignal’s licensing service uses Google Cloud infrastructure, including server and database services, to operate subscription verification and device binding.

Google Cloud may process or store licensing information on behalf of Morgan Brothers Entertainment LLC as a service provider.

Trip-offer information and local offer journals are not uploaded to this licensing infrastructure through the Release 001 licensing path.

17. Support Communications

If a user voluntarily contacts us at:

support@tripsignal.app

we receive the information the user chooses to include in that communication, which may include:

• email address;

• message content;

• screenshots;

• diagnostic files;

• offer-journal files; or

• other information voluntarily attached by the user.

We use support information to respond to the user, investigate the reported issue, provide support, protect the service, or resolve licensing problems.

Support information is not sold or used for targeted advertising.

Users may contact us at the same address with privacy or deletion questions.

18. Data Sharing

Morgan Brothers Entertainment LLC does not sell TripSignal user data.

We do not sell trip-offer information, recommendations, screenshots, local journals, or licensing information to advertisers or data brokers.

Information may be processed by service providers where necessary to operate the app and licensing system, including Google Play and Google Cloud.

Information may also be disclosed where reasonably necessary to:

• comply with applicable law, legal process, or governmental requests;

• enforce our rights or Terms of Service;

• detect or prevent fraud, abuse, or security incidents;

• protect users, Morgan Brothers Entertainment LLC, or third parties; or

• complete a corporate transaction where legally permitted and subject to appropriate protections.

19. Advertising and Tracking

TripSignal Drive does not use trip-offer information for targeted advertising.

TripSignal Drive does not use local trip-offer journals, screenshots, OCR-derived offer content, pickup or destination information, or TripSignal recommendations to create advertising profiles.

TripSignal does not sell this information to advertising networks or data brokers.

Licensing-related device information is used for subscription verification, security, fraud prevention, and device-binding enforcement, not advertising.

20. Data Retention

Different categories of information have different retention characteristics.

Local Last Offer and Captures

• Standard Last Offer: up to approximately 24 hours.

• Standard retained capture: maximum one capture and up to approximately 24 hours.

Local Offer Journals

• daily structured offer-journal files: approximately 30 days;

• rolling journal: up to approximately 1,000 records;

• latest structured offer record: overwritten by a newer record;

• presentation-event journal: no separate automatic age-based deletion rule is established in Release 001.

Local Diagnostics

Local diagnostic files use short retention of approximately four hours together with file rotation and storage limits.

Server-Side Licensing Records

Server-side licensing records may remain after a subscription expires, a device changes, or a binding is released or superseded.

Current Release 001 licensing source does not implement a general automatic application-level deletion or TTL for every licensing record.

Morgan Brothers Entertainment LLC may retain licensing records for as long as reasonably necessary to:

• operate and secure the licensing system;

• prevent fraud and abuse;

• enforce one-device licensing;

• investigate subscription or device conflicts;

• provide customer support;

• resolve disputes;

• comply with accounting or legal obligations; and

• maintain service integrity.

21. Data Deletion

Users control local TripSignal application data on their device.

Depending on the data category, users can remove local information by:

• using Clear Last Offer for the Standard Last Offer and its associated capture;

• clearing TripSignal Drive app storage through Android system settings;

• deleting separately exported files; or

• uninstalling TripSignal Drive.

Clear Last Offer does not delete the separate operational offer journal or all technical diagnostic data.

Clearing the app’s storage or uninstalling the app normally removes app-private local TripSignal data, subject to Android system behavior and any files the user separately exported or saved.

Users may contact:

support@tripsignal.app

to request information about or deletion of server-side information controlled by Morgan Brothers Entertainment LLC.

Deletion requests may be subject to information that must reasonably be retained for security, fraud prevention, legal compliance, accounting, dispute resolution, or protection of the service.

Deletion of licensing records may affect TripSignal’s ability to verify an existing entitlement or resolve past licensing conflicts.

22. Security

TripSignal Drive is designed so that trip-offer processing remains primarily on the user’s device.

Communication between TripSignal Drive and the TripSignal licensing service uses secure HTTPS transport.

The licensing system uses cryptographic fingerprints for persistent purchase-token and device-binding records.

Sanitized operational licensing logs use shortened cryptographic fingerprints instead of raw purchase tokens or raw device-binding identifiers.

TripSignal’s licensing backend is separate from local trip-offer processing and is designed not to receive trip-offer fares, pickup or destination information, screenshots, OCR content, recommendations, internal reasons, or route information.

No technical or organizational security measure can guarantee absolute security.

Users should also protect access to their device, Google Play account, email account, screenshots, exported files, and any diagnostic information they choose to share.

23. Children’s Privacy

TripSignal Drive is intended for adult rideshare and delivery drivers.

The app is not directed to children under 18.

Morgan Brothers Entertainment LLC does not knowingly use TripSignal Drive to collect personal information from children under 18.

24. Third-Party Platforms and Services

TripSignal Drive may operate alongside third-party applications and services, including rideshare, delivery, Android, Google Play, and Google Cloud services.

Morgan Brothers Entertainment LLC does not control the privacy practices, software, availability, interfaces, or policies of those third parties.

Users should review the applicable privacy policies and terms of the services they use.

25. Independent Product; No Affiliation

TripSignal Drive is developed and operated independently by Morgan Brothers Entertainment LLC.

TripSignal Drive is not affiliated with, endorsed by, sponsored by, authorized by, or operated in partnership with Uber Technologies, Inc., Lyft, Inc., or any other rideshare, delivery, transportation, or gig-work platform.

Third-party names and trademarks belong to their respective owners and are used only to identify compatible services or explain app functionality.

26. Changes to This Privacy Policy

We may update this Privacy Policy when TripSignal Drive functionality, data practices, marketplace requirements, security practices, or applicable law change.

An updated policy will display a revised Effective Date.

When required, we will provide additional notice.

If a future version changes what information is transmitted, remotely stored, shared, or retained, this Privacy Policy and applicable Google Play Data Safety disclosures will be updated to reflect the changed processing.

27. Contact

Morgan Brothers Entertainment LLC
TripSignal Drive

Email: support@tripsignal.app

Website: https://www.tripsignal.app

© 2026 Morgan Brothers Entertainment LLC. All rights reserved.