Trust
Security and tenant isolation
Renaro is built for multi-tenant operators where passenger PII, booking history, payment state, and fleet records must remain scoped to the correct organization.
- Auth
- WorkOS-backed sessions
- Tenant model
- Explicit org scope
- Database
- RLS-aware operations
- Audit
- Sensitive access evidence
Data isolation is a product feature
Taxi and chauffeur companies hold passenger PII, corporate account details, payment state, and driver records. Renaro treats tenant isolation as a core architecture rule.
- Scope every tenant query and mutation by organization.
- Use authenticated request context and RLS-aware transaction behavior for defense in depth.
- Keep audit trails for writes and sensitive access patterns.
Buyer trust belongs on the landing site
Security pages are not just procurement checkboxes. They help serious operators understand that Renaro is built for production data.
- Explain authentication, tenant boundaries, auditability, and data export posture.
- Link security to corporate accounts, payments, passenger privacy, and integrations.
- Avoid unsupported compliance badges until formal certifications exist.
SEO role
Security and privacy searches support enterprise evaluation and internal stakeholder buy-in.
- The page links to the standalone security page and corporate account content.
- FAQ content answers passenger PII, tenant isolation, and audit questions.
- Structured metadata keeps security content crawlable without login barriers.
Related product paths
Frequently asked questions
Who is Security and tenant isolation for?
This page is for operators evaluating dispatch software that can support live bookings, driver coordination, payments, reporting, and multi-tenant controls without stitching together separate tools.
How does Renaro support evaluation?
Renaro exposes product areas as focused pages, comparison pages, integration pages, and buying resources so operators can evaluate the exact workflow they are trying to improve.
Platform walkthrough
See how Renaro handles your real operating workflow.
Bring a booking scenario, a dispatch policy, a pricing edge case, or a migration concern. The walkthrough should prove how the platform behaves under actual operator pressure.