Security
Effective Date: November 4, 2026
Solvara Labs LLC · Austin, Texas
Security contact: security@opsvara.com
This page summarizes how Solvara Labs LLC ("Solvara Labs," "we," or "us") protects the data our customers keep in the Opsvara platform (the "Service"), and how to report a security issue. The commitments that apply to customer data are set out in our Data Processing Agreement (https://opsvara.com/dpa).
1. How We Protect Your Data
1.1 Separation of Customer Accounts
Every request to the Service is scoped to the signed-in user's own company account. One customer cannot see another customer's records. Our support staff's own sign-ins do not work against customer accounts; they reach an account only through the support access described in Section 1.5.
1.2 Encryption
All traffic to the Service is encrypted with TLS, and the web application uses HTTP Strict Transport Security. Our database (MongoDB Atlas) and file storage (Amazon S3) are encrypted at rest. Stored integration credentials, such as QuickBooks connection tokens, are additionally encrypted by the application with AES-256-GCM.
1.3 Sign-In and Passwords
Passwords are stored only as bcrypt hashes. Sign-in is locked for fifteen (15) minutes after five (5) failed attempts, API requests are rate limited, sessions expire, and deactivating a user blocks their access immediately.
1.4 Permissions in Your Account
Each user has a role, such as administrator, office, or field worker, that controls which screens and actions they can reach. Your administrators decide who has which role.
1.5 Support Access by Our Staff
Our support staff can sign in to your account only after your company opens a support window (for 24 hours, 3 days, or 7 days). Each session lasts at most thirty (30) minutes, your administrators are emailed when it starts, and every change made is logged. A restricted emergency-access path, available only to Solvara Labs' owner, is logged and notified in the same way.
1.6 Payments
Card and bank details are entered directly into Stripe, a PCI DSS Level 1 payment processor, and never pass through or rest on our servers. We keep only Stripe references and the last four digits.
1.7 AI Features
Only the data needed to answer a request is sent to our AI provider. We do not use your data to train or fine-tune any AI model, and our AI providers are contractually prohibited from training on it.
1.8 Location Data
The mobile app collects a technician's location only in the foreground, only while they are clocked in, and only if they opt in and your company has turned the feature on. The live location record is deleted when they clock out.
1.9 Treatment Records
Treatment and chemical application records are retained for the life of the account and protected against deletion.
1.10 Backups
Our database runs as a three-node replica set with automated backups. We verify backups monthly and test restoring them quarterly.
1.11 Service Providers
We use a small set of service providers to run the Service, each under a written agreement. The full list, with what each one does and where, is at https://opsvara.com/subprocessors.
2. If Something Goes Wrong
If we confirm a security breach affecting your data, we will notify your account administrators without undue delay and in any event within seventy-two (72) hours of confirming it. We will tell you what happened, what data was affected, what we are doing about it, and who to contact, and we will keep you updated as we learn more.
3. Reporting a Security Issue
If you believe you have found a security vulnerability in the Service, please email security@opsvara.com with a description of the issue, the steps to reproduce it, and how we can reach you. We will acknowledge your report, keep you informed as we investigate, and let you know when it is fixed.
We will not pursue legal action against anyone who reports a vulnerability to us in good faith and follows these guidelines:
Give us a reasonable time to fix the issue before telling anyone else about it.
Do not access, change, or delete data that does not belong to you. If you come across someone else's data, stop, and tell us.
Do not degrade or disrupt the Service, and do not use automated scanning that sends a high volume of requests.
Do not use social engineering, phishing, or physical attacks against our staff, customers, or offices.
Test only against an account you own or have permission to use.
We do not currently offer a paid bug bounty. Our machine-readable security contact is published at https://opsvara.com/.well-known/security.txt.
4. Questions
For security questionnaires or to request a signed copy of our Data Processing Agreement, email support@opsvara.com.
Last Updated: November 4, 2026 | Version: security-v1 | Solvara Labs LLC | Austin, Texas | security@opsvara.com