Privacy Policy

Last updated: 22 August 2026

Moorlock is active laptop-theft protection: a local agent that locks or shuts your machine down the moment it's taken, plus an optional cloud account for fleet management, evidence, and recovery. This policy explains what personal data the Moorlock service ("we", "us") collects, why, and your rights over it. It covers the cloud service at moorlock.io; the on-device agent is open source and runs locally.

What we collect

  • Account & identity — your email address, optional name, and organisation. Passwords are never stored; we keep only a salted PBKDF2 hash, and passkeys store only a public credential. Optional two-factor secrets are stored to verify your codes.
  • Devices & fleet state — the devices you enrol, their protection posture (armed/triggered/etc.), and event history, so you can manage a fleet and see incidents.
  • Evidence — if you enable it, webcam and screen captures taken at trigger time. These are encrypted at rest.
  • Location — if you enable location, two kinds of position attached to check-ins, trigger, and theft reports: an approximate position derived from your IP address, and (on macOS, if you grant the system location permission) a more precise position from the operating system's Wi-Fi-based location services. Both are encrypted at rest and shown on your dashboard map. You can turn location off at any time in the app.
  • Billing — if you subscribe, your payment is processed by Stripe. We store a customer/subscription reference and plan status; we never see or store your card details.
  • Product analytics — privacy-respecting usage analytics (see "Analytics & cookies").

How your data is protected

Evidence and location are protected with envelope encryption — each organisation has its own data key, wrapped by a server master key. This is notend-to-end encryption: because we support account recovery and fleet access, our servers can decrypt this data. We state that plainly rather than overclaim. Device tokens are hashed at rest, sessions are signed and short-lived, and access is scoped so one organisation can never read another's data.

Why we process it (legal bases)

  • To provide the service (contract) — accounts, devices, evidence, alerts, and billing.
  • Legitimate interests — securing the service, preventing abuse, and improving the product via aggregate analytics.
  • Consent — optional features you switch on, such as evidence capture and location.

Who we share it with

We use a small number of processors and service providers, and never sell your data:

  • Cloudflare (infrastructure) — hosting and the Worker runtime, our database (D1), encrypted object storage for evidence (R2), key-value storage, and edge delivery. Cloudflare also sends our transactional emails (verification, password reset, alerts) via its email service.
  • Stripe (payments) — subscription billing. Card details go directly to Stripe; we never see or store them.
  • PostHog (analytics) — product analytics, hosted in the EU and proxied through moorlock.io so your browser never calls a third-party analytics domain. Only loads with your consent (see below).
  • ipwho.is (IP geolocation) — when you enable location, the agent queries this service to turn an IP address into an approximate city. Precise location, when enabled, comes from your own device's operating system, not a third party.
  • CARTO & OpenStreetMap (map tiles) — the dashboard map loads background map imagery from CARTO (built on OpenStreetMap data). Your browser requests map tiles from CARTO for the area shown; no account data is sent — only the standard tile coordinates any web map requests.

These providers act as our processors under data-processing terms, except Stripe and the map/geolocation providers, which are independent controllers for the limited data they receive. We choose providers that support GDPR-compliant processing.

Analytics & cookies

Strictly necessary: we set one essential cookie to keep you signed in. It carries a signed session token, is never used for tracking, and needs no consent. Your browser also stores small preferences locally (such as theme and language); these never leave your device.

Analytics (consent-based): we use PostHog to understand which features are used and where people get stuck. Analytics are off until you accept them in the cookie banner — until then PostHog sets no cookies and captures nothing. You can change your choice any time via Cookie settings in the footer. We use no advertising or cross-site tracking cookies, and session recording is disabled.

Retention

Account and device data is kept while your account is active. Evidence and location tied to an incident are kept until you resolve or delete the incident, or delete your account. When you delete your account we remove your personal data, except where we must retain limited records (e.g. billing) to meet legal obligations.

Your rights

Depending on where you live (including under the UK/EU GDPR), you have the right to access, correct, export, or delete your personal data, to object to or restrict certain processing, and to withdraw consent for optional features at any time. To exercise any of these, email privacy@moorlock.io. You also have the right to complain to your local data protection authority.

International transfers

Our infrastructure runs on Cloudflare's global edge and may process data outside your country. Where required, transfers rely on appropriate safeguards such as standard contractual clauses.

Changes

We'll update this policy as the service evolves and revise the date above. Material changes will be highlighted in the product or by email.

Contact

Questions or requests: privacy@moorlock.io.