What procurement teams ask before buying field SaaS
1. How is data isolated between organizations?
2. What roles and permissions exist?
3. Are audit trails complete and tamper-evident?
4. Where is data stored and encrypted?
5. Can we pass a security review?
Scootee's security architecture
- **28 PostgreSQL tables** with organization_id scoping
- **50+ RLS policies** enforcing tenant isolation at the database level
- **Four roles** — employee, sales_manager, director, admin
- **Supabase Auth** — email/password, OTP, JWT tokens
- **approval_history** — IP address, user agent, timestamps on every decision
- **Zod validation** on all API endpoints
Privacy by design
GPS capture activates only during shift sessions employees explicitly start. Location data is encrypted in transit and at rest. Employees can access their own tracking records. Organizations configure retention policies per enterprise agreement.
See Security & Compliance and [Security page](/security/).
Why field operations SaaS security differs from consumer apps
Consumer GPS and expense apps store user data in shared infrastructure with minimal access controls. Enterprise field operations SaaS processes:
- **Employee location trails** during work sessions — sensitive personal and operational data
- **Financial records** — expense claims, receipt images, approval decisions
- **Procurement data** — purchase orders with vendor pricing and contract terms
- **Organizational hierarchy** — employee bands, compensation rules, territory assignments
Procurement teams evaluating field SaaS must verify tenant isolation, role-based access, audit completeness, and encryption — not just feature checklists.
Scootee security architecture deep dive
Database-level tenant isolation
28 PostgreSQL tables scoped by organization_id with 50+ Row Level Security (RLS) policies enforcing tenant isolation at the database layer — not application-layer filtering that single coding errors can bypass.
Role-based access control
Four roles control platform access:
| Role | Access scope |
|---|---|
| employee | Own shifts, expenses, and tracking records |
| sales_manager | Team visibility, approval authority |
| director | Organization-wide dashboards, high-value approvals |
| admin | Full configuration and user management |
Authentication and session security
Supabase Auth provides email/password, OTP, and JWT token authentication. Session management enforces token expiration and secure credential storage on mobile devices.
Approval audit trails
approval_history records IP address, user agent, timestamp, and approver identity on every expense and procurement decision — satisfying SOC 2, internal audit, and regulatory compliance requirements.
API validation
Zod schema validation on all API endpoints prevents injection attacks and malformed data from entering the database — defense in depth alongside RLS policies.
Procurement security review checklist
Enterprise buyers should verify:
1. Data isolation — RLS policies at database level, not application layer only
2. Encryption — Data encrypted in transit (TLS) and at rest
3. Access controls — Role-based permissions with least-privilege defaults
4. Audit trails — Complete, tamper-evident decision records
5. Data residency — Storage location compliance with regional regulations
6. Privacy design — GPS capture limited to explicit shift sessions
7. Employee data rights — Access to own tracking and expense records
8. Retention policies — Configurable per enterprise agreement
Security & Compliance Scootee addresses each requirement through architecture documented for procurement review.
Privacy by design for location data
GPS capture activates only during shift sessions employees explicitly start — not personal time. Location data encrypts in transit and at rest. Employees access their own tracking records. Organizations configure retention policies per enterprise agreement.
This privacy-by-design approach satisfies GDPR, CCPA, and global labor law requirements while providing operations teams the visibility they need during active work periods.
Multi-tenant security across field operations modules
Security architecture spans all platform modules uniformly:
- [GPS Live Tracking](/platform/gps-live-tracking/) — Location trails organization-scoped
- [Expense Intelligence](/platform/expense-intelligence/) — Claims and receipts tenant-isolated
- [Distance Engine](/platform/distance-engine/) — Mileage rollups per organization
- [AI PO Extractor](/platform/ai-po-extractor/) — Procurement documents tenant-scoped
- [Approval Engine](/platform/approval-engine/) — Decision records with complete audit trails
- [MobiTraq Alerts](/platform/mobitraq-alerts/) — Discrepancy data organization-isolated
Unified security architecture eliminates the risk of deploying best-in-class point solutions with inconsistent data isolation standards.
Global B2B enterprise deployment
contact Scootee serves global enterprises with distributed field workforces. Security architecture supports multi-country deployment with organization-scoped data isolation regardless of workforce geographic distribution. Enterprise pricing and deployment scoping via — no public pricing tiers.
Frequently Asked Questions
How does Scootee isolate data between organizations?
28 PostgreSQL tables with organization_id scoping and 50+ Row Level Security policies enforce tenant isolation at the database level — ensuring no cross-organization data access regardless of application layer behavior.
What roles and permissions does Scootee support?
Four roles: employee (own records), sales_manager (team visibility and approvals), director (organization-wide access and high-value approvals), admin (full configuration). Employee bands add expense limit and policy differentiation.
Is GPS location data encrypted and privacy-compliant?
GPS capture activates only during explicit shift sessions. Location data encrypts in transit and at rest. Employees access their own records. Organizations configure retention policies per enterprise agreement — satisfying GDPR, CCPA, and global privacy requirements.