Security

Security and data handling

What KnockAtlas stores, how it is protected, who can reach it, and how it is deleted. Written to be read by a security team, not by a buyer.

Last reviewed 30 August 2026 · Marz Technologies LLC · California entity B20260357358

Architecture and hosting

KnockAtlas runs entirely on Cloudflare: Workers for application code, D1 for the relational store, R2 for lead media and backups, and KV for session and rate-limit caching. There is no separate application server, VM, or container to patch, and the platform beneath the application maintains SOC 2 Type II and ISO 27001 attestations.

Encryption

Tenant isolation

Every query that touches customer data is scoped by organisation identifier, and that scoping is applied in one place rather than repeated per route — so a new endpoint inherits the boundary instead of having to remember it. Role scoping sits on top: a rep sees their own book, a manager their team, a director their region.

The boundary is exercised, not assumed: adversarial tests that attempt cross-organisation reads and writes run as part of an ongoing security review programme, and the isolation model is documented for customer security teams on request.

Identity and access

CapabilityStatus
Email and password authentication, PBKDF2-hashedAvailable today
Role-based access: rep, manager, director, organisation ownerAvailable today
Bot protection on sign-in and invitation acceptanceAvailable today
Administrative sessions expire in 24 hours; step-up re-authentication on destructive actionsAvailable today
Sign-in alerting on administrative accountsAvailable today
TOTP multi-factor for director and administrator rolesIn development
SAML 2.0 and OIDC single sign-on, with SCIM provisioning and deprovisioningCommitted as a condition of any enterprise pilot, before the first employee account is created. Scoped against Microsoft Entra ID.

We do not expect an enterprise to federate its workforce into a password database, and we are not asking anyone to.

Independent assurance

Audit logging

Administrative and data-affecting actions are recorded to an append-only audit log: lead imports, territory and ZIP assignment, role changes, invitations, exports, and control-plane operations. Each entry carries the actor, the organisation, the action, and a timestamp.

Location data

KnockAtlas records position only at the moment a representative logs a door outcome. It does not track between doors, does not run a background location service, and produces no movement trail.

FieldPurpose
Latitude and longitude at dispositionConfirms the knock happened at the address it was recorded against
TimestampOrders activity and supports rhythm analytics
Reported accuracy radiusDistinguishes a confident fix from a poor one rather than discarding it

Position is visible to the representative who recorded it and to their management chain. It is not exposed between peers, and managers themselves are not location-tracked by the product.

Deletion and portability

Sub-processors

Two, and we will give 30 days' written notice before adding a third.

Sub-processorPurposeRegion
Cloudflare, Inc.Application hosting, database, object storage, CDN, access controlUnited States
ResendTransactional email — invitations, password resets, security alertsUnited States

Deployment

KnockAtlas installs from the browser. There is no app-store distribution and no mobile device management enrolment, so putting it on a managed device estate requires no action from your endpoint team. Details are in the IT Deployment Brief below.

Evaluation documents

The full Security Overview and IT Deployment Brief are provided to evaluating organisations on request — they are confidential documents, handled the way we handle everything else. Write to security@knockatlas.com and they are sent the same business day, no call required. Role manuals are provided during onboarding and inside the application.

Questions a document does not answer: contact us.