How FluxOps protects your buildings and your data
FluxOps is designed so that no job is dispatched without a person's approval, no customer can see another's data, and every approval, assignment, and mute is on record.
Who can dispatch a job?
Only a person on your team, with an explicit tap, or a not-to-exceed rule that person set. FluxOps never dispatches on its own.
What can a contractor see?
Only the one job they were sent: the site, the unit, the problem, and the amount. The link works for that job and that role only, expires, and can be revoked by you at any time. Contractors never touch your account or your other sites.
Is my data separate from other customers'?
Yes. Every record is tied to your organization and access is enforced at the database level, not just in the app. Your users see only the sites you give them.
What is audited?
Every approval, decline, assignment, mute, and mute override, with who did it and when. The record can't be edited after the fact.
How are alarm emails and contractor notes handled?
As untrusted input. FluxOps reads them to fill in fields; they never trigger an action on their own.
How do I report a security issue?
Write to security@fluxops.app. We acknowledge every report within two business days.
Questions
Where is data hosted?
In the United States, with a managed database provider.
Is there single sign-on?
Not in this version. Email and password with invitations only; there is no public sign-up.
Can I export my data?
Yes, on request today; self-service export is planned.
Start with one location. Add the rest when it earns it.
Flat $15 per site per month. Unlimited users. Contractors never pay. Your first location is free, for as long as you want.