MTD Developer Logo
New API is in preview! Subject to change. Send feedback to contact@mtd.dev

License for Distribution Requirements

These requirements apply to any application or product that uses MTD Data and is distributed to the general public under the License for Distribution section of the Developer License Agreement and Terms of Use. MTD may update these requirements at any time; it is the Licensee's responsibility to maintain compliance.

1. Platform Design Standards

Applications must follow the current, official design guidelines for their target platform (for example, Apple's Human Interface Guidelines for iOS/macOS apps, Material Design for Android apps, or equivalent guidelines for other platforms). The intent is that apps feel native, predictable, and accessible to riders, not that any particular visual style is required.

2. Ownership and Affiliation Clarity

Applications must make clear to users that they are not an official MTD product and adhere to the requirements in Identification of MTD and MTD Data in the Agreement. Specifically:

  • The app name, icon, and store listing must not imply MTD ownership, endorsement, or official affiliation.
  • The app must include, in an easily discoverable location (such as an About screen or store listing description), the attribution line required by the Agreement: "Data provided by MTD. [App Name Here] not affiliated with MTD"
  • The developer's name or organization must be accurately listed as the publisher in any app store or distribution channel.

3. User Support

Applications must provide users with a clear and functional support channel. At minimum, this means:

  • A support contact (email address, support page URL, or equivalent) that is publicly listed in the app store or distribution channel.
  • Response to user-reported issues within a reasonable timeframe.
  • MTD is not responsible for support of third-party applications and must not be implied as a support contact.

4. Platform Version Compatibility

Applications must remain compatible with operating system versions in active support by their platform vendor. When a new major OS version is released, Licensee must provide an update restoring full compatibility within 90 days of that release. MTD may grant extensions on a case-by-case basis upon written request.

5. Active Maintenance

Licensees are expected to actively maintain their applications. An application will be considered abandoned if any of the following occur:

  • No update has been published in 24 months, or
  • A platform compatibility break (as described in Section 4) has not been addressed within the required timeframe, or
  • The app's support channel (as described in Section 3) has become non-functional and has not been restored within 30 days of MTD's notice.

MTD reserves the right to revoke a Licensee's key upon a finding of abandonment.

6. App Store and Distribution Channel Listing Accuracy

App store listings and any other public-facing distribution materials must accurately represent the application's functionality. Listings must not make claims about data accuracy, real-time reliability, or service coverage that exceed what MTD guarantees under this Agreement. MTD's name may only appear in the listing in accordance with the attribution and affiliation requirements in Section 2 and the main Agreement.

7. Privacy Policy

Any application that collects, transmits, or stores user data — including but not limited to location data, usage patterns, or account information — must maintain a publicly accessible privacy policy. The privacy policy must accurately describe what data is collected, how it is used, and with whom it is shared. The privacy policy must be linked or otherwise accessible from within the application and from any app store listing. MTD Data itself is not user data for purposes of this section; this requirement applies to data the Licensee collects about users of their application.

8. Accessibility

Applications must conform to WCAG 2.2 Level AA success criteria, or the equivalent accessibility standard required by the target platform, whichever is more stringent. The intent is that MTD transit information remains usable by riders with disabilities regardless of which application they use to access it. Licensees are encouraged to test with assistive technologies (such as screen readers) on their target platforms.