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 the data is protectedDEVICE → TRANSIT → STORE → AUDITDEVICEField tablet, cached recordsEncrypted at rest (AES-256), biometric unlockTRANSITAPI calls over TLS 1.3Certificate pinning, perfect forward secrecySTORESupabase on AWS, row-level securitySensitivity classes: Public, Restricted, Confidential, ProtectedAUDITAppend-only ledgerEach create, edit, approval and export, with user and timeCOMPLIANCE & INFRASTRUCTURESOC 2 Type II hostingAES-256TLS 1.3Daily off-site backupsAWS Region: USPoint-in-time recovery
Location confidentiality
GPS coordinates, georeferenced photos and site locations stay inside your organization unless you choose to share them. Photos are served through signed, time-limited URLs, so there are no permanent links to pass around. A public data share is the one exception, and it stays off until a project manager turns it on.
Restricted projects
Mark a project Restricted and only its team can see it. Its records and photos stop syncing to everyone else's devices, owners and admins have to add themselves to the team, which is logged, and it can't be shared publicly.
Audit log
The audit log is append-only and can't be edited or deleted. It records record creation, edits, status changes, approvals, rejections (with the reason given), photos, team changes and exported files, so you can show who changed what when a reviewer or client asks. Offline work is logged when it syncs.
Role-based access
There are five organization roles and four project roles, so access can follow how your team is actually organized (project managers, field leads, technicians, read-only viewers). Row-level security policies apply to every database table, so the database itself refuses access, not just the UI.
Encryption at rest and in transit
All data is encrypted at rest with AES-256 and in transit with TLS 1.3. That covers field records, GPS coordinates, photos, EXIF metadata and audit logs. Photos sit in private storage that requires authentication and are only served through time-limited signed URLs.
Authentication
OAuth 2.0 authentication with HTTP-only cookie sessions. Passwords require a minimum of 10 characters with uppercase, lowercase, and numeric complexity. Support for multi-factor authentication and single sign-on for organizations that require them.
Upload validation
Uploads are checked on both the client and the server against an allowlist of image types (JPEG, PNG, WebP, HEIC, TIFF), with a 25 MB size limit and filename sanitization. Files are stored under randomized paths so they can't be enumerated. Executables are rejected.
Exporting your data
FieldTap exports CSV, Excel, Word, PDF, GeoJSON and KML. You can export everything at any time, and the formats are open ones that hold up for long-term archiving and client deliverables.
Infrastructure
Hosting includes automatic HTTPS, DDoS protection and a global edge network. The database is managed PostgreSQL with automated daily backups, point-in-time recovery and network isolation. Every HTTP response sends security headers: HSTS with preload, X-Frame-Options DENY, strict content type enforcement and a restricted permissions policy.
Offline data
Records kept on the device for offline use are held in secure on-device storage. When the device reconnects, records sync over TLS with field-level merging. If two people edited different fields, both edits are kept. If they edited the same field, the conflict is flagged for review instead of one edit silently overwriting the other.
Backup and recovery
Daily automated database backups, with point-in-time recovery going back up to 7 days. Backups are encrypted and stored in a separate availability zone, so after a failure the data can be restored to any point inside that window.
Integrations
Integrations with ArcGIS Online and Google Drive use OAuth 2.0 with short-lived access tokens that refresh automatically. Outbound webhooks are signed with HMAC-SHA256 so your endpoint can verify each payload. Integration tokens are encrypted at rest and scoped to the minimum permissions needed.

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.

Daily
automated snapshots
AES-256
GPG-encrypted offsite
2 regions
primary and offsite
Append-only
audit ledger
Layer 1

Managed daily snapshots

Nightly Postgres logical backups kept by the managed database platform, with point-in-time restore on customer-tier plans.

Layer 2

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.

Layer 3

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.

Least-privilege write keys
The backup uploader can write new objects but can’t delete existing ones, so leaked credentials couldn’t be used to wipe old backups.
Restore tests
On a regular schedule we decrypt a backup and restore it into a throwaway Postgres instance to make sure it actually works.
A copy on request
Ask and we’ll send you a current encrypted dump of your organization’s records. There’s no fee for it.

Need a copy of your encrypted dump or a custom retention policy? Get in touch.

Start free trial

Regulations

How FieldTap supports the regulations our customers most often work under.

RegulationScopeHow FieldTap helps
NHPA Section 106Cultural resourcesAppend-only activity log, fillable state forms such as DPR 523, locked records for defensible documentation
NEPA / CEQAEnvironmental reviewStructured field forms, photo documentation with GPS, an activity log of who changed what for environmental impact assessments
ARPAArchaeological site protectionSite data kept inside your organization, role-based access, time-limited photo links
OSHA 1910 / 1926Workplace safetyDaily monitoring forms, inspection records with timestamps, approval workflows for safety sign-offs
GDPREU data privacyData portability (full export), right to deletion, encryption at rest and in transit, role-based access control
CCPACalifornia data privacyData 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