Privacy
Last updated August 2026
MapLogics decides what should happen at an address. That means addresses pass through us, so this page is specific about which parts we keep, for how long, and which parts we deliberately throw away.
Who we are
MapLogics provides the service described on this site. For data your organisation loads into MapLogics, you are the controller and we are the processor: you decide what goes in, we process it to answer your questions. For your own account details, we are the controller.
What we store, and what we do not
Your configuration
Territories, locations, services, rules and published versions. This is the substance of what you build, and it is kept until you delete it or close your account. Published configuration is immutable by design: a decision made last year still points at the version that made it, so past versions are retained rather than overwritten.
Addresses you send to be resolved
An address is used to geocode and decide. The record we keep of the request holds no address, no coordinate and no customer identifier — only the metadata needed to meter, alert and debug.
One exception, stated plainly. Our geocoding cache keeps the provider's normalised form of an address for thirty days, stored against a SHA-256 of it rather than the address itself, so the same address is not sent to a third party twice. That cache is shared across all customers and is not linked to any account.
Decision traces, which record why an answer came out the way it did, do contain the coordinate. They expire on a window set by your plan.
Your account
Your email address, which organisations you belong to, and your role in each. Sign-in is by emailed link, so we hold no password. Sessions expire after 30 days of inactivity and 90 days regardless.
We record security events on your account — sign-ins, address changes, signing out everywhere — with the country a request came from and nothing more identifying. No IP addresses, no device fingerprints, no user agents. You can read that log yourself in Settings.
What we never store
- Passwords. There are none.
- Payment card details.
- API keys or webhook signing secrets in readable form in logs or audit records.
- IP addresses against your account activity.
How long we keep it
| What | Kept for |
|---|---|
| Request metadata for metering and debugging | 90 days |
| Decision traces | Per plan, then expired |
| Geocoding cache entries | 30 days |
| Batch inputs and outputs | 30 days |
| Audit records of configuration changes | 2 years |
| Sign-in links | 15 minutes, single use |
| Your configuration | Until you delete it |
These windows are enforced by a job that runs continuously, not by a policy somebody remembers to apply. Longer or shorter windows can be set per organisation.
Who else sees it
We use as few third parties as we can. Today there are three.
| Who | What they get | Why |
|---|---|---|
| Cloudflare | All application data | Compute, storage, queues and email delivery |
| US Census Geocoder | The address being geocoded | Turning an address into a coordinate. No account identifiers are sent. |
| OpenStreetMap Nominatim | The address being geocoded | Used when the primary geocoder cannot place an address. |
This site runs no analytics, no advertising pixels and no third-party scripts of any kind. There is nothing to consent to, which is why you were not asked.
Where it lives
On Cloudflare's network, which is global. Data may be processed in any region Cloudflare operates in, including outside your own country. If you need processing confined to a particular region, ask before you rely on it, because we cannot currently guarantee it.
Your rights
You can ask what we hold about you, correct it, export it, or have it deleted. Most of it is already visible to you in the application. For anything else, email hello@maplogics.com and we will answer within 30 days.
Where your organisation is the controller and the data is your customers', those requests should come through your organisation rather than direct to us, and we will help you answer them.
Security
Details of how the system is built are on the trust page, including what is not built yet. If you find a security problem, email hello@maplogics.com. We would rather hear from you than not.
Changes
If this page changes in a way that affects what we do with your data, we will tell account owners by email before it takes effect rather than only updating the date at the top.