Security That's Engineered In, Not Bolted On
Tenant isolation at the database layer. MFA at the authentication layer. Audit logging at every layer. Certificate pinning on every mobile device. This is how a platform earns enterprise trust.
Core Security Pillars
Tenant Data Isolation
Each organization operates within defined data-access boundaries, with role-based permissions and database-enforced protections. Access rules are applied at the data layer, not only in the application.
Designed to keep each organization's records within its own boundary.
Dual-Layer Role-Based Access Control
Application roles determine which dashboard a user sees. Staff role codes determine which modules are accessible within that dashboard. Priority hierarchy ensures admin-tier roles override staff-level restrictions. Promotion to management auto-grants admin access; demotion auto-revokes it.
Role definitions across dedicated portals, from Platform Owner and Admin through Director, Manager, Ops Manager, Supervisor, HR, Training Admin, Employee, Client, and Applicant.
Multi-Factor Authentication
Mandatory TOTP MFA for platform owners and admin roles. Configurable tenant-level enforcement for employees. Administrator sign-in is restricted to approved company accounts, and clients, employees, and administrators use separate sign-in paths.
Auth segmentation ensures no credential confusion between user tiers.
7-Year Audit Trail
Platform audit logs record administrative and cross-organization actions, including who acted, what was affected, which organization was involved, and a severity classification.
Audit logs: 7 years. API usage logs: 2 years. Auth logs: 90 days.
PII Isolation & Data Protection
Compensation data is excluded from non-administrative views. Disciplinary records are restricted to authorized administrators and the affected employee. Sensitive fields are withheld from general views.
Sensitive personal data is visible only to roles that need it.
Tenant-Scoped Identity Validation
Requests are checked against both the user's identity and their membership in the organization. Platform administrator authority is recognized through a controlled, audited process.
Sensitive data is reachable only through controlled, permission-checked access paths.
Session & Device Control
Every session is monitored. Every device is validated. Every context switch is audited.
- Active session monitoring with IP tracking, user agent logging, and session expiration
- Login lockout tracking for failed admin login attempts with configurable thresholds
- Device trust management with forced logout capabilities across all active sessions
- Authorized administrative access into an organization is shown with a visible context indicator and recorded in the audit log
- Separate sign-in paths for clients, employees, and administrators
Mobile Security Hardening
Most operations happen on phones, not desktops. Field devices are secured with the same rigor as the platform itself.
Jailbreak / Root Detection
Device compromise checks verify secure lock screen and detect jailbroken/rooted devices before granting platform access. Compromised devices are blocked.
Secure Token Storage
Authentication tokens stored in Keychain (iOS) and Keystore (Android) via dedicated Capacitor plugin. Tokens never stored in plaintext or accessible to other apps.
Certificate Pinning
Configured pinned domains with version tracking prevent man-in-the-middle attacks on all mobile API communications. Pinned certificates rotate with app updates.
Geofence Enforcement
GPS verification on every clock-in/out, DAR entry, and patrol checkpoint scan. Guards operating outside site geofence boundaries trigger real-time supervisor alerts.
Security Governance
Documented policies and procedures that demonstrate enterprise-grade security posture to your clients and their auditors.
Vendor Risk Assessments
Documented risk assessments for all sub-processors, including Supabase (database), Stripe (payments), Resend (email), Mapbox (geolocation), hCaptcha (bot protection).
Incident Response Runbook
Severity levels (SEV0–SEV3) with defined triage steps, containment protocols, communication procedures, and post-incident review requirements.
Log Retention Policy
Formal retention schedules enforced at the infrastructure level: 7 years for audit logs, 2 years for API usage, 90 days for authentication events.
