Tenant isolation
Production customers receive isolated data stores per organization. Your locations, people, and operational records do not share a database with other groups.
Security
Restaurant BOH data — schedules, wages, vendor spend, compliance records — deserves the same rigor as your financial systems. Here is how Luminix handles it today.
Production customers receive isolated data stores per organization. Your locations, people, and operational records do not share a database with other groups.
Role-based permissions limit what each user sees — GMs to their store, owners to roll-up views. Sensitive HR fields require explicit permission keys.
TLS in transit for all product traffic. Sensitive HR fields (wages, bank details, tax identifiers) encrypted at rest with application-level encryption.
Authentication uses httpOnly session cookies in the product app. No third-party ad tracking in the operator workspace.
Sensitive mutations in HR, finance, inventory, and payroll emit domain events and audit rows — so leadership can reconstruct who changed what.
Customer operational data is hosted in United States regions. Marketing site and transactional email use standard US subprocessors documented in customer agreements.
Compliance roadmap
We are building toward SOC 2 Type I readiness as customer count grows. Ask on your demo for our current security packet, penetration test status, and incident response process.
Subprocessors
Questions? privacy@luminixops.com or Office@luminixops.com
← Back to resourcesWe will cover access model, encryption, audit trails, and integration boundaries for your group.
From $119 / location / month · Free 60–90 day pilot
See connected modules in your operation
Book a demo — we map Luminix to your locations, tier, and rollout timeline.