Privacy
Last updated October 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 holdsno address, no coordinate and no customer identifier, only the metadata needed to meter, alert and debug.
The nearest thing to an exception, stated plainly. Our geocoding cache stores a coordinate against a SHA-256 of the address, so the same address is not sent to a third party twice. The address itself is not kept. The hash is a lookup key, not a copy. Entries expire after thirty days. The cache is shared across all customers and is linked to no account.
Decision traces, which record why an answer came out the way it did, hold the steps and the reasoning (which territories were considered, which rule decided) and no address and no 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 or by password. If you set a password we keep only a salted, slow hash of it, never the password itself. 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.
- Your IP address. Signing in and the demo form keep a salted one-way digest of the caller's address to stop one machine requesting a thousand sign-in emails. It cannot be turned back into an address, it is never shown to anyone, and it is deleted with the record it belongs to, within the hour for a sign-in.
AI assistants
You can connect an AI assistant such as Claude or ChatGPT to MapLogics by signing in from it. This section covers what that connection can reach and what we keep about it.
What a connected assistant can read
When you connect one, you choose the organisation it works in and whether it may only read or may also prepare draft changes. It acts as you, so it can never see or do more than your role in that organisation allows, and if your role changes, the connection changes with it. With read access it can check addresses and read that organisation's territories, locations, rules, drafts, usage and decision log. With draft access it can also change the unpublished draft and add locations. It cannot publish anything.
What we receive, and what we do not send anywhere
We receive what the assistant sends when it uses one of our tools: the tool's name and its arguments, such as an address to check or the ZIP codes for a new territory. We never receive your conversation with the assistant. An address sent to be checked is handled exactly like one sent to the API: used to decide and not stored. Anything an assistant adds to your configuration, such as a new location and its address, is kept as part of your configuration, the same as if you had added it yourself.
We do not send your organisation's data to Anthropic, OpenAI or any other AI company ourselves. The assistant fetches what you, or the assistant working for you, asked for, and what it does with the answer is covered by your agreement with that company. AI companies are not on our list of third parties below because we do not share data with them; you do, by connecting.
What we store about a connection
- The assistant's registration: the name it gave itself (for example "Claude"), the web addresses it asked us to send you back to after signing in, and when it was last used. For one day we also keep a one-way digest of the network address it registered from, to limit how many registrations one machine can make.
- The connection itself: who connected it, in which organisation, the access you chose, how you signed in, when it was connected and last used, and when and why it ended.
- Its access tokens, stored only as one-way hashes, never in a form that could be used. An access token lasts an hour and a refresh token 30 days.
- Draft changes an assistant makes, recorded in the audit log under your name with the assistant named beside them.
Disconnecting
Open Settings in the MapLogics app and find Connected AI clients. Disconnecting deletes the connection's tokens at once, so the assistant's next request is refused. Organisation owners and admins can disconnect any member's assistant, or stop allowing AI assistants in their organisation altogether, which disconnects every one of them.
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 |
| AI assistant access tokens | Until they expire (1 hour, or 30 days for a refresh token), or deleted at once when you disconnect |
| A disconnected AI assistant connection | 30 days after it ended, so you can see who ended it and when |
| An AI assistant registration that never completed a sign-in | 30 days |
| Your configuration | Until you delete it |
| Demo requests | 2 years, then deleted |
| Email addresses from the free tools | 2 years. If you unsubscribed, the address is kept so we can keep honouring that |
| The campaign cookie on the marketing site | 90 days |
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.
The unsubscribe line is worth explaining, because it looks like an exception and is the opposite of one. If you ask us to stop emailing you, we keep your address and nothing else: no record of what you looked up, where you came from, or which tool you used. We keep the address because it is how we recognise that you asked. Deleting it would mean that the next time you used one of the free tools we would have no idea you had ever left, and could start emailing you again.
Who else sees it
We use as few third parties as we can. Today there are three companies.
| Who | What they get | Why |
|---|---|---|
| Cloudflare | All application data | Compute, storage, queues, email delivery, and the Turnstile check on our two public forms |
| 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 and no advertising pixels, and nothing here follows you to any other website.
One cookie is set, and only if you arrive from a link that says where you came from: a search result, a campaign link with utm_ parameters on it, or a link on somebody else's site. It holds the campaign parameters that were already in the URL you clicked, the host of the site that linked to you, and the page you landed on. Not the full referring address, because that can carry a search query or somebody's internal path.
It lasts ninety days and it does join your visits together: if you come back later and then create an account, we can see that the account came from the campaign you first arrived on and from whichever one brought you back. That is what it is for, and it is the only thing it does. There is no identifier in it, nothing that names you, and it is readable only by us, so it cannot be used to recognise you anywhere else. A visit that arrives with nothing to record sets no cookie at all.
Blocking or deleting it costs you nothing. The site works identically without it and no feature depends on it.
One third-party script does run, and only on two pages: Cloudflare Turnstile, on the demo request form and the sign-in form. It is there to tell a person from a script, because both of those forms send email and a bot can otherwise spend our ability to send it. It sees the request and how it was made; it does not set a tracking cookie and is not used to identify you anywhere else. Every other page loads nothing from anyone.
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, emailhello@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, emailhello@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.