A plain-language look at how Nimbus-FM protects your account and data — written to be accurate, not to sound impressive.
Last updated August 17, 2026
The database takes automatic backups with point-in-time recovery — if something goes wrong (a bad migration, an accidental bulk change), it can be restored to a specific moment, not just the most recent daily snapshot.
Inside the application itself, deleting a record — an employee, tenant, lease, and similar — doesn't destroy it immediately. These are soft-deleted: removed from view right away, but recoverable rather than gone, which is a second layer of protection against an accidental delete.
Passwords are never stored in plain text, and never stored in a form that could be "decrypted" back to the original — they're hashed with bcrypt, a one-way, industry-standard hashing algorithm built specifically for passwords. Even someone with direct access to the database cannot recover a user's actual password from what's stored.
Access follows least privilege. Company owners have full access by default; every employee account is granted its own specific, individually-toggled permissions instead of one all-or-nothing "admin" switch — for example, whether they can see every work order in the company or only the ones assigned to them, whether they can reassign a technician, or whether they can manage billing.
Every edit, delete, and access-level change across the company — updates to properties, leases, work orders, employees, clients, and equipment; permission changes; administrators added or removed — is recorded with who did it and when, and is reviewable from Settings. Viewing it is its own permission, so it's not automatically visible to every employee. It currently shows the most recent 100 events per company, with no pagination or export yet.
Nimbus-FM never sees or stores your card details. Checkout runs entirely on Stripe's own hosted payment page — card numbers go directly to Stripe, not through our servers. Stripe is PCI DSS Level 1 certified (the highest level in the payments industry) and SOC 2 Type II compliant.
Nimbus-FM is multi-tenant — many companies share the same application and database. Every single query is scoped to the logged-in user's own company, so one customer's properties, work orders, tenants, and employees are never reachable from another customer's session. This isn't just a design intention: it's covered by automated tests that specifically try to access another company's data and confirm it's rejected.
The third parties that process data on Nimbus-FM's behalf, and why:
We don't sell customer data to anyone, and we don't share it with these providers beyond what's needed to run the service.
Ordinary business data isn't field-level encrypted. Names, phone numbers, addresses, and work order text are stored as plain text in the database (protected by the access controls and encrypted connection above, but not individually encrypted at rest) — standard for this type of application, but worth being precise about.
No formal third-party security audit, penetration test, or SOC 2 report for Nimbus-FM itself. Render, our infrastructure provider, holds its own independent SOC 2 Type II certification — but that covers Render's platform, not an audit of our own application code and processes. This page reflects what's actually implemented in the code, not an independent certification.
No guaranteed Canadian data residency. Render doesn't currently offer a Canadian region, so infrastructure runs in the US. If that's a hard requirement for your organization, email us and we'll talk through it.
No formal, published incident response plan yet. See "Reporting a Concern" below for how to reach us if something comes up.
If you believe you've found a security issue, please email support@nimbus-fm.com with details. We'll respond and take it seriously.