Security and compliance
Most of what your crews record can't be collected a second time. This page lays out how FieldTap stores it, who can see it, and how it's backed up.
How backups work
The database is snapshotted daily by the hosting platform. Separately, we take our own encrypted copy every day and store it in a different cloud account in a different region. Losing either one still leaves you with the other.
Managed daily snapshots
Nightly Postgres logical backups kept by the managed database platform, with point-in-time restore on customer-tier plans.
Encrypted offsite copies
A daily pg_dump, encrypted with AES-256 (GPG) before it leaves our side and stored in S3 in a separate cloud account with Object Lock turned on. Someone who got into the primary account still couldn’t delete them.
Separate region and keys
The offsite bucket is in a different region from the primary database, and the encryption passphrase is stored apart from the cloud credentials.
Need a copy of your encrypted dump or a custom retention policy? Get in touch.
Start free trialRegulations
How FieldTap supports the regulations our customers most often work under.
| Regulation | Scope | How FieldTap helps |
|---|---|---|
| NHPA Section 106 | Cultural resources | Append-only activity log, fillable state forms such as DPR 523, locked records for defensible documentation |
| NEPA / CEQA | Environmental review | Structured field forms, photo documentation with GPS, an activity log of who changed what for environmental impact assessments |
| ARPA | Archaeological site protection | Site data kept inside your organization, role-based access, time-limited photo links |
| OSHA 1910 / 1926 | Workplace safety | Daily monitoring forms, inspection records with timestamps, approval workflows for safety sign-offs |
| GDPR | EU data privacy | Data portability (full export), right to deletion, encryption at rest and in transit, role-based access control |
| CCPA | California data privacy | Data access and deletion rights, no sale of personal information, transparent data collection practices |
How we handle security
Most of our access control lives in the database, not the app. Row-level security decides who can read a record, the audit log is append-only, and photos are only served through time-limited links.
We review our security practices and audit dependencies on a regular basis. We're working toward SOC 2 Type II certification but don't have it yet.
If you need a compliance statement for your organization or have questions about any of this, contact us.
Report a vulnerability
If you've found a security issue, please tell us privately first. We'll confirm it and fix it as fast as we can.
Contact us