Authenticated access
Only authenticated users and explicitly scoped machine credentials can change hosted data. AtlasTrack validates standards-based OIDC identities, and production rejects local-development identity tokens.
Security and trust
Travel visibility should never mean uncontrolled access.
AtlasTrack uses authenticated, organization-scoped controls, optional team-restricted traveler access, and hardened hosted infrastructure to protect travel data. This page distinguishes implemented safeguards from deployment responsibilities and roadmap items.
Posture reviewed August 2, 2026
Available today
Controls built into AtlasTrack
Scoped travel access
Travel records and mutations are scoped to the selected organization. Business administrators can keep organization-wide visibility or explicitly restrict regular members to their own and assigned Team travelers; owners and administrators retain global oversight.
Restricted database exposure
Application data is not exposed directly to browsers. AtlasTrack reaches Postgres through a private server connection, enables row-level security, and removes application-table privileges from browser-facing database roles.
Safer external imports
Server-side feed fetchers validate approved HTTPS destinations, block local, private, and metadata addresses, re-check redirects, limit response size and timeouts, and avoid exposing feed tokens in client errors.
Transport and browser hardening
Production uses HTTPS, requires SSL for its Supabase database connection, and sends HSTS, anti-framing, MIME-sniffing, referrer, permissions, and content-security headers.
Security-aware engineering
Route-policy regression tests, static analysis, dependency auditing, secret scanning, container scanning, pinned build inputs, and non-root backend containers are part of the repository's verification workflow.
Data handling
Purpose-limited by design
AtlasTrack processes account, travel, workspace, Team-assignment, and operational security information to provide and protect the service. It does not sell personal information. Depending on the organization's selected policy, active members may see organization-wide travel or only travelers assigned through Teams. Live-location sharing uses a separate authorization boundary.
Information is retained while an account or workspace is active and as reasonably needed for security, backups, legal obligations, and disputes. Permanent account deletion removes active data. AtlasTrack's production operating requirement is for protected backup copies to age out within 30 days unless longer retention is legally required; provider retention and deletion-aware restore controls must be verified for each production deployment. Access, correction, export, and deletion requests can be sent to support.
Clear status
Implemented, configurable, and planned
Swipe horizontally to compare every status and explanation.
| Capability | Status | What that means |
|---|---|---|
| OIDC sign-in and organization roles | Implemented | Hosted identity validation and owner/admin/member authorization paths are present. |
| Team-restricted traveler access | Implemented | Business owners/admins can assign traveler subjects separately from Team viewers and managers and explicitly enable restricted visibility. |
| Security event logging | Implemented | AtlasTrack records a limited set of structured security events for investigation without copying arbitrary request metadata into those logs. |
| Central log retention and alert routing | Deployment setup | Render exposes service logs; durable retention and security alert destinations must be configured for each deployment. |
| Backups and point-in-time recovery | Deployment setup | Production operators must configure and verify provider retention, deletion-aware restores, and the 30-day backup aging requirement. |
| SSO and SCIM provisioning | Planned | Not currently offered as an AtlasTrack administration capability. |
| Customer administrative audit API | Implemented | Business owners and administrators can search and export covered workspace-scoped administrative events. A dedicated app UI, all-mutation coverage, periodic retention proof, and external aggregation remain planned. |
| SOC 2, ISO 27001, or government authorization | Not claimed | AtlasTrack does not currently claim these certifications or authorizations. |
Vulnerability disclosure
Report a suspected vulnerability or incident.
Send a concise description, affected URL or feature, reproduction steps, and potential impact. Do not include live credentials, private traveler data, or destructive proof.
Please avoid privacy violations, service disruption, social engineering, and accessing data beyond what is needed to demonstrate the issue. AtlasTrack will review good-faith reports and coordinate a reasonable disclosure timeline, but does not claim 24/7 monitoring or a fixed response SLA.