Legal

Terms of Use

Effective 17 July 2026. These terms cover the Kuramap website, its data, and the public Kuramap API. By using them, you accept what follows.

The short version

  • Take the data and use it, commercially or otherwise — just credit Kuramap. It is published under CC BY 4.0.
  • Use the API within its rate limits, and don’t present Kuramap as an official or legal source. It isn’t one.
  • The data is provided as-is. We work hard to be accurate and we publish our own gaps, but we make no warranty.

Who you are dealing with

Kuramap is an independent, unincorporated civic project — not a company. There is no registered legal entity behind it; it is run by a private individual, reachable at [email protected]. Nothing on this site should be read as implying a corporate body, an official mandate, or any endorsement by a government institution.

Data licence

Kuramap’s published data — the region hierarchy, representatives, terms, and the API responses that serve them — is licensed under the Creative Commons Attribution 4.0 International licence (CC BY 4.0). You are free to copy, redistribute, adapt and build on it, including commercially, provided you give appropriate credit.

How to attribute

Include a credit like this, with the link intact:

Contains data from Kuramap (https://kuramap.euxven.com), licensed under CC BY 4.0.

Upstream sources have their own terms

Kuramap builds on public sources — boundary geometry from geoBoundaries and register data published by the IEBC among them — and those carry their own licences and attribution requirements, which travel with the data. If you redistribute the boundary geometry in particular, credit the upstream source as well as Kuramap. The data page sets out each source and the licence that applies to it.

The licence for this project’s source code is a separate matter and is not settled by these terms.

Using the API

The public API is read-only and free to use, within limits that exist so one caller cannot degrade the service for everyone else. The API documentation describes the current rate limits and quotas, and returns 429 with a Retry-After header when you exceed them.

Please don’t:

  • circumvent rate limits or quotas — for example by rotating keys or spreading requests across addresses to evade them. If you need more headroom, ask;
  • share, resell or publish your API key; it identifies your usage and you are responsible for what is done with it;
  • present Kuramap as an official, authoritative or legal source of Kenyan electoral or administrative boundaries, or imply that it is endorsed by the IEBC or any government body. It is an independent project, and the authoritative record is the one the relevant institution publishes;
  • misrepresent the data — including presenting our coverage gaps as complete, or attributing altered data to Kuramap without saying you changed it (CC BY 4.0 requires you to indicate modifications);
  • use the service to break the law, or in a way that endangers a person named in the data.

We may rate-limit, suspend or revoke a key that is causing harm to the service. Where it is practical to reach you first, we will.

No warranty

The site, the API and the data are provided as-is, without warranty of any kind, express or implied — including any warranty of accuracy, completeness, fitness for a particular purpose, or uninterrupted availability.

We take accuracy seriously and we publish our known gaps rather than hide them — the data page records what is missing or unreconciled. But civic data changes, records disagree, and mistakes happen. Do not rely on Kuramap for a legal, electoral or official purpose: verify against the responsible institution’s own record. To the fullest extent permitted by law, we are not liable for loss arising from your use of, or reliance on, this data.

Found something wrong? Please tell us at [email protected] — corrections are welcome and are the main way this gets better.

Changes to these terms

We may update these terms; if we do, we will change the effective date at the top of the page. Material changes will be called out on the page rather than made quietly, and the full history is public in our source repository. Continuing to use the site or API after a change means you accept the updated terms.

See also our Privacy Policy.