Data Security
Your data, handled with care.
Most clients ask some version of “who can see my data, and where does it go?” Here’s how we approach it.
Data Security & Storage
- Your private database at the core. You own it.
- Encrypted in transit (TLS) and at rest.
- Role-based access and logging matched to the project.
- Isolated per-client deployment.
- Backups and recovery procedures defined in scope.
- Portable: export and handoff on the agreed schedule.
Where does your data live?
It depends on the project—usually a cloud database such as Azure SQL or PostgreSQL in a region you specify, or on your own servers if on-premises hosting is required. Either way, you own it.
Encryption—at rest and in transit
For projects with a managed database, encryption at rest and TLS are part of the standard architecture unless your environment requires an equivalent control. The exact controls are documented in the project scope.
Access control and audit logs
Role-based access means people see only what they need. A field technician does not need access to a full landowner database, while a manager may need summaries without raw records. When auditability is in scope, sensitive actions are logged for review.
Government and federal contracts
We can build on FedRAMP-authorized cloud infrastructure such as Azure Government or AWS GovCloud and structure a deployment around the requirements identified during discovery. Full FedRAMP authorization is an organizational process, not something a single contractor delivers.
Sensitive and private data
Private landowner records, PII, or health data shape the architecture from day one: what gets encrypted, who has access, what gets logged, and how data is handled when a user leaves the project.
Backups and recovery
Managed database projects include a backup and recovery plan defined in scope. Snapshot frequency, retention, restore documentation, and recovery testing are matched to the workload and support tier before launch.
Questions about your specific setup?
Tell us what you’re working with — landowner records, federal data, PII — and we’ll walk through how the architecture would protect it.
