Last updated July 20, 2026

Data security

Your map and field data stays yours.

Data protection pillars

Customer ownership

You retain ownership of data you upload and sync.

Encryption

Protected in transit and at rest.

Access control

RBAC and least-privilege defaults.

API security

Authenticated API access with rotatable credentials.

Encryption in transit

All customer-facing endpoints require TLS. Internal service communication uses encrypted channels.

Encryption at rest

Sensitive customer data at rest is encrypted using industry-standard algorithms on managed storage services.

Access control

Administrative and customer access is governed by role-based permissions. Default roles follow least-privilege principles.

Role-based access control (RBAC)

Teams, territories, and admin functions can be scoped to specific roles. Account owners manage user provisioning and deprovisioning.

Multi-factor authentication (MFA)

MFA is available for qualifying enterprise accounts. We recommend enabling MFA for all administrative users.

Password security

Passwords are hashed using strong algorithms. Minimum complexity requirements apply. Password managers are encouraged.

API authentication

API access requires authenticated credentials. Keys should be stored securely, rotated periodically, and never embedded in client-side applications.

Secret management

Production secrets are stored in secure configuration systems with restricted access. Secrets are not committed to source control.

Session security

Sessions use secure cookies with appropriate expiration. Suspicious login activity may trigger additional verification.