Legal
Maiaddy Developer Terms
Last updated: 14 July 2026. See also the developer privacy page.
1. Acceptance of these Terms
These Developer Terms (“Terms”) are an agreement between you and Maiaddy Ltd. (“Maiaddy”, “we”, “us”) governing your access to and use of the Maiaddy Developer Platform — the developer console, API keys, the loccode address APIs, the Maimaps SDKs and APIs, Maiaddy ID integration, and the accompanying documentation (together, the “Services”).
By creating a developer account, generating an API key, or otherwise using the Services, you accept these Terms. If you use the Services on behalf of an organisation, you represent that you are authorised to bind that organisation, and “you” refers to that organisation.
2. Accounts and API keys
You sign in to the developer console with a Maiaddy ID. You are responsible for keeping your account credentials and API keys confidential and for all activity that occurs under them. Do not publish secret keys (for example, in public source repositories) except where a key type is expressly designed for client-side use.
We may rotate, suspend, or revoke API keys that we reasonably believe are compromised, abused, or used in breach of these Terms.
3. Acceptable use
When using the Services, you must not:
- use the Services in violation of applicable law or the rights of others;
- interfere with, probe, or attempt to bypass the Services’ security, rate limits, quotas, or metering;
- scrape, bulk-extract, or redistribute map data, the loccode dataset, or other content obtained through the Services beyond what the documentation for your plan permits;
- resell or sublicense raw access to the APIs or SDKs without a separate written agreement with Maiaddy;
- misrepresent your application’s affiliation with Maiaddy or Maimaps.
4. Plans, billing, and quotas
Access to the Services is metered through plans and quotas shown in the developer console’s Billing section. Paid plans are billed as described there at the time of purchase. Usage above your plan’s limits may be throttled or rejected.
We may change plan limits or pricing prospectively; material changes will be communicated through the console or the changelog before they take effect.
5. Telemetry
Collection. The Maimaps SDKs collect limited, anonymized traffic data (“Telemetry”) when an end user interacts with Maimaps-powered maps in your application. Telemetry consists solely of anonymous road-segment identifiers with associated speed values. The end user’s GPS position is converted to a road-segment identifier on the device and is discarded there: coordinates are never transmitted to Maimaps. Telemetry contains no user identifier, account identifier, device identifier, advertising identifier, or any other information that identifies an end user or device, and individual samples cannot be linked into a journey; the beginning and end of every trip are additionally excluded on-device. Maimaps uses Telemetry solely to improve its maps and to power aggregated services such as live traffic.
Your disclosure obligations. You must disclose the collection of Telemetry in your application’s privacy policy or equivalent notice, including a reference to the Maimaps Telemetry notice at https://maps.maiaddy.com/telemetry.
Opt-outs. Telemetry is enabled by default. Two controls exist:
(a) End-user opt-out. The Maimaps SDKs provide a built-in end-user opt-out, accessible from the Maimaps wordmark on every map. You may not remove, obscure, or interfere with this opt-out. If you disable or reposition the Maimaps wordmark using SDK configuration, you must provide end users an equally accessible means to (i) learn that Telemetry is collected and (ii) disable it, for example a settings entry that invokes the SDK’s telemetry opt-out API.
(b) Developer opt-out. You may disable Telemetry for your application entirely via SDK configuration (telemetryEnabled: false). With Telemetry disabled, the disclosure obligations above do not apply.
No circumvention. You may not attempt to re-identify, deanonymize, augment, or intercept Telemetry, nor submit synthetic or falsified Telemetry.
Changes. Maimaps may modify, suspend, or discontinue Telemetry collection at any time. Material changes to what Telemetry contains will be announced in SDK release notes.
6. Your applications and end users
You are responsible for your application, including its compliance with applicable law, platform and app-store policies, and for providing your end users with any legally required notices covering your use of the Services — including the Telemetry disclosure in Section 5.
7. Intellectual property
The Services — including the SDKs, the documentation, map data, and the loccode system — are owned by Maiaddy or its licensors. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable licence to use the SDKs and APIs to build and operate your applications.
Map content may include data from third-party sources provided under their own licences. You must not remove attribution presented by the SDKs, including the Maimaps wordmark, except as SDK configuration expressly allows and subject to Section 5(a).
8. Disclaimers
The Services are provided “as is” and “as available”, without warranties of any kind, whether express or implied. Map, routing, and traffic information are estimates and may be inaccurate, incomplete, or unavailable; do not rely on them in situations where errors could lead to death, personal injury, or significant damage.
9. Limitation of liability
To the maximum extent permitted by law, Maiaddy will not be liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenues, or data, arising from or related to the Services, and Maiaddy’s aggregate liability under these Terms is limited to the amounts you paid for the Services in the twelve months preceding the claim.
10. Suspension and termination
You may stop using the Services at any time. We may suspend or terminate your access to the Services, in whole or in part, if you materially breach these Terms, if required by law, or if continued provision poses a security or operational risk. Where practicable, we will give notice before suspension takes effect.
11. Changes to these Terms
We may update these Terms from time to time. Material changes will be announced through the developer console or the changelog before they take effect. Your continued use of the Services after changes take effect constitutes acceptance of the revised Terms.
12. Governing law
These Terms are governed by the laws of the Federal Republic of Nigeria, and disputes arising from them are subject to the exclusive jurisdiction of the courts of Nigeria.
13. Contact
Questions about these Terms: contact@maiaddy.com.