Your business runs on its data, so protecting it is part of the product, not an add-on. Here's how SitRep keeps it safe.
Data protection
- Encrypted in transit. All traffic uses HTTPS (TLS 1.2 or newer), with HTTP Strict Transport Security. Connections to the services we use are encrypted too.
- Encrypted at rest. The database, uploaded files, and backups live on encrypted storage. On top of that, every stored password-like secret (bank access keys, mailbox keys, payment processor keys, integration keys, and two-factor secrets) is individually encrypted with AES-256-GCM, and only the last four characters are ever shown back.
- Passwords are stored only as salted hashes. Sign-in sessions are random tokens stored only as hashes.
- Sensitive employee records (such as Social Security numbers and license numbers) are encrypted, limited to owners and admins, logged every time they're viewed, and never sent to AI services.
- United States hosting. The Service and its backups are hosted in U.S. data centers.
Backups
- Automatic, encrypted backups every day, kept for 30 days.
- Encrypted copies are also kept off-site, in the United States.
- The off-site copies are locked for 30 days after they're written: until the lock ends, nobody can change or delete them, including us.
- Restores are tested regularly, by restoring a backup and checking it against the live data.
Access control
- Two-factor sign-in is required for every owner and admin, for our own staff, and for anyone who links a bank account. Any business can require it for everyone.
- Roles and permissions. Each person gets a role (owner, admin, office, sales, driver, field tech) and only that role's access, adjustable per person. Every page, action, file, and document checks permissions on the server, and automated tests fail the build if one doesn't.
- Company separation. Every record belongs to one company, and nothing can read across companies.
- Support access is your choice. Our staff can enter your account only while your owner has support access switched on, and every page and action during a visit is recorded.
- Account protection. Repeated failed sign-ins lock a login temporarily. Removing a team member ends their sessions at once.
Payments and bank data
- We never hold your money. Payments go to your business through your own processor.
- Card details are entered into the processor's secure fields and never touch our servers.
- Bank connections through Plaid are read-only: no money can be moved through them.
Messaging safeguards
- Automated messages only go out between 9 AM and 6 PM in the recipient's local time.
- STOP replies are honored automatically.
- New connections that can reach customers start in a test mode until an owner switches them live.
Software security
- Every library is locked to a known version and updated on purpose, never automatically.
- Critical and high-severity issues are fixed or mitigated within 7 days; medium within 30 days.
- Servers install security updates automatically, accept administrative access by key only, and expose only web ports.
- Changes ship only after the full automated test suite passes.
Vendors
We use well-known providers with recognized security programs, and connect each with the least access that works. The list is in our Privacy Policy.
If something goes wrong
We follow a written incident response plan: contain the problem, assess what was affected, notify affected businesses without unreasonable delay and as the law requires, recover from clean backups, and review what happened so it doesn't happen again.
Your data, your control
- Export everything at any time.
- Cancel on your own, with 90 days of read-only access to take your data with you.
- See Data deletion for how deletion works.
Reporting a vulnerability
If you believe you've found a security issue, please email steven@sitrepcrm.com with the details and steps to reproduce it. Please give us a reasonable time to fix it before sharing it, and don't access other people's data, disrupt the Service, or run automated scans against it. We won't take legal action against good-faith research that follows these guidelines, and we'll keep you updated as we fix it.