Security

Security & privacy

Survey data is some of the most valuable information your organisation holds. GeolantisNEO keeps it private to your organisation, stored in a known region and recoverable — and this page explains how.

Key highlights

  • Private by default

    Your projects and features belong to your organisation. You decide who can see and edit them.

  • Stored in Europe

    Survey data, photos and files are stored in Frankfurt. Account, contact and billing details stay in the EU.

  • Two-factor sign-in

    Protect your account with a one-time code from an authenticator app.

  • Recoverable

    The production database can be restored to any point in the last 7 days.

Infrastructure

Managed cloud platforms
GeolantisNEO runs on established managed cloud platforms — Supabase for the database, sign-in and file storage, Vercel for the web apps. We operate no servers of our own.
Locked-down database
The production database refuses direct network connections by default. When an engineer needs access, it is opened for that one address for the task and closed again straight after.
Encryption
All traffic to GeolantisNEO is encrypted with HTTPS (TLS). Data is encrypted at rest by our database provider, and passwords are stored only as salted hashes — never in plain text.

Access control

Permissions enforced at every layer
Roles and project permissions are checked in the app, in the API and in the database itself. Row-level security keeps each organisation’s data separate, even if a request bypasses the app.
Sign-in
Users can add two-factor authentication with any authenticator app.

Backup and continuity

Point-in-time recovery
The production database is continuously backed up and can be restored to any moment in the last 7 days.
Monitoring
Our services are monitored around the clock, with current status published at status.geolantis.com. Application errors reach our engineering team automatically.

Software development

Reviewed and tested changes
Every code change goes through a pull request and automated tests — including database security tests — before it can be released.
Controlled database changes
The database schema changes only through versioned migrations, and every new table is protected by row-level security in the same change that creates it.
Staged releases
Changes run on a preview and a staging environment first. Releasing to production is a separate, deliberate step.

Report a security issue

If you believe you have found a security vulnerability in GeolantisNEO, please tell us with details and steps to reproduce it at support@geolantis.com