---
title: "Security and data · Supaferry"
description: "How the platform is built and run, in the terms a procurement officer or a data protection lead asks about."
url: https://supaferry.com/legal/security
language: en
---
# Security and data

Last updated: 5 October 2026

How the platform is built and run, in the terms a procurement officer or a data protection lead asks about.

## Architecture

- Web application with a server-side API; the database is never exposed to the browser.
- Every request is validated at the boundary with schemas shared by server and client.
- The back office fails closed: without configured credentials it answers 503, never open access.
- Public endpoints are rate limited; booking creation is idempotent so a dropped connection never creates a duplicate.
- TLS everywhere; HTTP redirects to HTTPS.

## Isolation and access

- One database per operator, hosted in the EU.
- Row-level security enabled with no public policies: only the server, under its service credential, reads or writes.
- Named accounts with roles per state or office (admin, agent, boarding officer, finance, auditor) in the government package.
- Staff access at SupaSailing SL is limited to named engineers, logged, and used for support on request.

## Backups and continuity

- Daily database backups by the hosting provider, retained 7 days, plus a mirror to a second provider.
- Export of every table on demand, in CSV, so the operator always holds its own data.
- Restore tested before go-live for each operator.

## Audit

Every booking, payment, cancellation, voyage and settings change is written to an audit log with the actor and the time, visible in the back office and exportable.

## Payments

Card data is never stored or seen by Supaferry. A real gateway uses its own hosted or tokenised fields; the demonstration gateway only simulates outcomes. Cash payments are recorded by receipt number.

## Incident response

Security reports: legal@supasailing.com. We acknowledge within two business days. Personal data breaches are handled as described in the privacy policy, including notification to the AEPD within 72 hours where required.
