Trust and security
What we do with your data, and what we do not.
MapLogics decides where customer addresses belong, so it sees customer addresses. This page describes how they are handled today — not what we intend to do later.
How it works today
-
Tenant isolation
Every record is scoped to an organisation, and that scope is enforced at the data-access layer rather than left to each query to remember. Cross-tenant access attempts are covered by automated tests that run before release.
-
Addresses are transient by default
A resolve request carries a customer address. The record we keep of the request holds no address, no coordinate and no customer identifier: enough to meter, alert and debug, and nothing that would make it a liability. One exception, stated plainly: the geocoding cache keeps the provider's normalised form of an address for thirty days, keyed by a SHA-256 of it, so the same address is not sent to a third party twice. The cache is shared across all customers and is not linked to any account.
-
We do not treat hashing as anonymising
A hashed address is still a customer address: anyone holding the same address can confirm the match. Where addresses are not needed, they are dropped rather than digested.
-
Credentials and addresses never reach logs
Redaction happens inside the logger, not by asking engineers to remember. API keys, tokens, session cookies and street addresses are stripped on the way in; coarse geography such as region and postal code is kept because it is useful in diagnostics and not identifying alone.
-
API keys are stored hashed
A key is shown once at creation and stored only as a hash. We cannot recover it for you, which is the point. Keys can be rotated and revoked, and last use is recorded.
-
Encryption
TLS in transit everywhere. At rest, data is encrypted by the managed Cloudflare storage services it lives in.
Subprocessors
Every third party that can see customer data, and exactly what each one gets.
| Subprocessor | Purpose | What it receives |
|---|---|---|
| Cloudflare | Hosting, application data, object storage, queues and email delivery. | All application data. |
| US Census Geocoder | Converting an address into a coordinate. | The address being resolved. No account or customer identifiers. |
| OpenStreetMap Nominatim | Fallback geocoding when the primary provider fails. | The address being resolved. No account or customer identifiers. |
What we do not have yet
MapLogics is early. These are the things a security review will ask for that we cannot claim today. We would rather you learn it here than in a questionnaire.
- No SOC 2 report. A readiness assessment is planned. We will not describe ourselves as compliant or aligned with a framework we have not been audited against.
- No single sign-on or SCIM. Authentication today is passwordless email links. SAML and OIDC are on the roadmap and not built.
- No independent penetration test. Scope and remediation process are prepared; the test has not been run.
- No contractual uptime SLA. We publish targets and measure against them, but there is no SLA to sign yet.
- No data residency options. Data lives in Cloudflare's global network. If a contract requires residency in a specific region, tell us before you buy.
Security questions, or something here that does not match what you were told on a call: security@maplogics.com.