Legal
Privacy Policy
How we handle data in the TheMapZone developer console and across the Tiles, Routing and Places APIs — what we collect, why, how long we keep it, and what you can ask us to do with it.
- Version
- 2026-07
- Effective
- 2026-07-01
- Last updated
- 2026-09-10
1. Who this covers
This policy applies to TheMapZone (“TheMapZone”, “we”) and to two groups of people whose data reaches us in different ways:
- Console users — developers and account owners who register at console.themapzone.com to manage applications, API credentials, usage and invoices. We are the controller of this data.
- Your end users — the people using your app, whose requests reach our APIs through your credentials. We process that data on your behalf, as described in section 7.
A dashboard account is for managing the platform. Your applications authenticate separately with API credentials, and those two paths produce different records, which is why they are described separately below.
2. Account data
When you register, we collect and store:
| Data | Source | Why we need it |
|---|---|---|
| Full name | You, at registration | Identifying the account holder |
| Email address | You, at registration | Account confirmation, password reset, service and billing notices |
| Username | You, at registration | Signing in and attributing actions in the console |
| Password | You, at registration | Authentication. Stored only as a one-way hash — we cannot read it |
| Account type | You, at registration | Business and individual accounts differ in what we must record |
| Organisation name and industry | You, business accounts only | Invoicing and understanding how the platform is used |
We record that you accepted the Terms of Service and Privacy Policy, along with the version you accepted (currently 2026-07) and when. We do not buy account data, and we do not enrich your profile from third-party sources.
3. API request data
Every call your application makes to Tiles, Routing or Places passes through our edge gateway, which records what is needed to authorise the request, count it against your quota and bill it. For each request that means, in general terms:
- The credential and application the request was made with, and the platform identifier it came from (your registered Android package, iOS bundle or web origin).
- Which service and endpoint was called, when, the response status and how long it took.
- The originating IP address, used for abuse prevention, rate limiting and geographic routing.
- Request parameters necessary to serve the call — for Routing and Places this includes the coordinates, addresses or search terms you send us, because we cannot compute a route or resolve a place without them.
Location inputs are the most sensitive data we handle. We use them to answer the request you made, to diagnose faults, and to protect the service. We do not sell them, we do not use them to build advertising or marketing profiles, and we do not attempt to identify the individuals behind them.
4. Console usage data
When you use the console itself we keep server logs of page requests, including IP address, browser user agent, timestamp and the pages viewed, plus a session cookie so you stay signed in. The session cookie is strictly necessary and is not used for tracking or advertising. We do not run third-party advertising or cross-site tracking on the console.
5. Billing data
For paid accounts we hold the billing profile you enter, the invoices we issue, your metered usage for each period, payment references you submit when claiming a payment, and the payment status we record after verifying it. Where card or bank details are involved, they are handled by our payment provider — we receive confirmation and a reference, not the full instrument.
6. Why we process it
| Purpose | Basis (UK/EU GDPR) |
|---|---|
| Providing the console and the APIs you asked for | Performance of a contract |
| Metering usage, issuing invoices, collecting payment | Performance of a contract |
| Rate limiting, quota enforcement, fraud and abuse prevention | Legitimate interests |
| Diagnosing faults and keeping the service reliable | Legitimate interests |
| Service and security notices about your account | Performance of a contract |
| Keeping accounting and tax records | Legal obligation |
| Optional product updates and marketing email | Consent — withdrawable at any time |
7. Your end users
When your app calls our APIs, we act as a processor for the request data you send. That arrangement has obligations on both sides.
What we commit to: processing that data only to deliver, secure and bill the service; not using it for our own unrelated purposes; keeping it under the safeguards in section 10; and deleting or returning it as described in section 9.
What is yours to do: you are responsible for having a lawful basis to send us your end users' data, for telling them about it in your own privacy notice, and for honouring their rights in your app. We have no relationship with your end users and usually cannot identify them, so we will refer their requests to you.
Do not send us special category data (health, biometric, religious or political data, or precise location tied to an identified person) unless we have agreed it in writing first. Our APIs are not designed for it.
8. Who we share with
We do not sell personal data. We share it only with providers who process it on our behalf, under contract and only for the purpose stated:
| Provider | Role | Location |
|---|---|---|
| Cloudflare, Inc. | Edge delivery, DDoS protection and API gateway | Global edge network |
| TheMapZone | Application hosting, database and email delivery on infrastructure we operate directly | Operated by us |
We may also disclose data where the law requires it, to enforce our Terms, or to protect the rights and safety of our users and the public. If we are compelled to hand over your data we will tell you, unless we are legally barred from doing so. If the business is sold or reorganised, data may transfer with it, and this policy continues to apply until you are notified otherwise.
9. How long we keep it
| Record | Retention |
|---|---|
| Per-request API logs | 90 days |
| Aggregated usage counters (for your own charts and quotas) | 25 months |
| Invoices and accounting records | 7 years, as tax law requires |
| Account data after you close the account | Deleted within 30 days, except records we must keep |
Aggregated usage counters are kept longer than raw logs because they are what your usage history and invoices are built from. They are counts, not request contents.
10. Security
All traffic to the console and the APIs is encrypted in transit with TLS. Passwords are stored only as one-way hashes. API credentials are shown in full once, at the moment they are issued, and are stored so they cannot be read back afterwards — which is why rotating a credential replaces it rather than revealing it. Access to production systems is restricted to staff who need it.
No system is immune. If a breach affects your data we will notify you and any regulator we are required to inform, within the deadlines that apply to us. To report a vulnerability, write to security@themapzone.com rather than filing it in a public tracker.
11. Your rights
Depending on where you live, you can ask us to:
- Give you a copy of the personal data we hold about you, in a portable format.
- Correct data that is wrong or incomplete — most account fields you can edit yourself in the console.
- Delete your data, where we have no overriding obligation to keep it.
- Restrict or object to processing we base on legitimate interests.
- Withdraw consent for marketing email, at any time, without affecting your service.
Write to privacy@themapzone.com and we will respond within one month. We may ask you to verify your identity first — we are not going to hand your account data to someone who merely claims to be you. If you are unhappy with our answer you can complain to your local data protection authority.
12. International transfers
Our edge network serves requests from the location nearest your users, so API traffic is processed in multiple countries by design. Where data leaves its country of origin we rely on appropriate safeguards, such as standard contractual clauses or an adequacy decision. Ask us at privacy@themapzone.com if you need the specifics for a particular region.
13. Children
The console is a developer tool for people aged 16 or over, and we do not knowingly collect data from children. If you believe a child has registered an account, tell us and we will remove it.
14. Changes
When we change this policy we update the version and date at the top of this page. For changes that materially affect your rights we will email the address on your account and, where the law requires it, ask you to accept the new version before you continue using the service. Previous versions are available on request.
15. Contact
TheMapZone
Privacy: privacy@themapzone.com
Support: support@themapzone.com
Security: security@themapzone.com
We handle privacy requests by email so they reach the right people directly. If you need a postal address for a formal or regulatory request, ask at privacy@themapzone.com and we will provide one.
Questions about this document? Write to privacy@themapzone.com. This page describes the TheMapZone developer console and APIs operated by TheMapZone.