The organizations that use Vernala protect land, water, and habitat — often forever. We take the security of the records that document that work seriously. This page summarizes how we protect your data today and where we are headed.
Vernala runs a lightweight but disciplined security program: managed cloud infrastructure, database-enforced tenant isolation, least-privilege access, encryption in transit and at rest, tested backups, and a commitment to plain-English disclosure when something goes wrong. As we grow, we intend to pursue independent security attestation and align our controls with recognized frameworks.
Vernala runs on established managed platforms — our application is hosted on Vercel and our database, authentication, and file storage on Supabase, on infrastructure located in U.S. regions. Using managed services means patching, physical security, and infrastructure hardening are handled by teams whose entire business is exactly that, while we focus on the application layer.
Every organization’s records are isolated at the database layer, not just in application code. Every table enforces row-level security with deny-by-default policies, and our automated test suite attempts cross-organization reads and writes — as a real, hostile user — on every schema change. A change that weakens isolation fails the test suite and does not ship.
Access to production systems is limited to the small Vernala team, on the principle of least privilege, and revoked immediately on role change or departure. We do not read customer records except when strictly required for support (with your permission) or to investigate a security incident.
Our database is backed up automatically every day, encrypted. File storage is additionally mirrored nightly to an independent second provider, so no single vendor holds the only copy of your photos and documents. We have tested restoring from these backups — a backup that has never been restored is a hope, not a plan. Finer-grained point-in-time recovery is scheduled to be enabled as customer data grows.
Every code change passes automated checks — including the tenant-isolation suite, secret scanning, and a guard that verifies no server credentials leak into browser code — before it can be deployed. Dependencies are kept current. Independent penetration testing is planned before broad rollout, and we will remediate findings promptly.
If an incident affects your data, we will notify affected customer admins within 72 hours of confirmation, share what we know in plain English, and update you as we learn more.
How we collect and use information is described in our Privacy Policy. We do not sell your data and we do not use conservation records or landowner contact information to train third-party AI models.
If you believe you have found a security vulnerability in Vernala, please email hello@vernala.co with steps to reproduce. We will acknowledge within one business day, keep you posted on our remediation, and credit you in our disclosure log if you would like.
Security questions from prospective customers, current customers, or researchers — email hello@vernala.co.