Encryption in Transit and at Rest
TLS in transit and encryption at rest by our hosting providers, plus application-level encryption of MFA secrets, payment tokens and signing keys.
Your maritime data includes crew records, certificates, contracts and operational records. This page sets out how we protect it; the binding version is the Data Processing Agreement every customer accepts.
Recognized as an innovative and scalable company under Spain’s Startup Law (Ley 28/2022) by ENISA — Ministerio de Industria y Turismo.
SupaMaritime and SupaSailing are brands of SupaSailing S.L.
Every feature designed to protect your business — without compromise.
TLS in transit and encryption at rest by our hosting providers, plus application-level encryption of MFA secrets, payment tokens and signing keys.
Application servers in Paris. Databases in London (UK adequacy decision) for Ferry, Merchant and Agent, and in Frankfurt for Guild. The sub-processor list is published.
Role-based access scoped by organisation and vessel, row-level security in the database and server-side checks on every request that reads customer records.
Security events and administrative access by our staff are logged where the module supports it.
Managed PostgreSQL databases backed up daily and kept for 7 days. Uploaded files mirrored daily, with deleted files kept for 90 days.
Every request that reads a customer's records is checked on the server, on top of the database's row-level policies.
Export your data as CSV, JSON or XLSX and your files in their original format, self-service or on request. Switching and erasure follow the EU Data Act terms in our contract.
MFA is available to every user, with an authenticator app, email or SMS code depending on the module.
We target 99.5% monthly availability, excluding announced maintenance. It is a target, not a guarantee, unless your order form includes service credits.
In Ferry and Merchant: hours of rest checked against MLC and STCW limits, crew certificates with expiry alerts, and ISM, ISPS and drill records.
A GDPR Data Processing Agreement is part of the terms every customer accepts, with Standard Contractual Clauses for sub-processors outside the EEA.
Each module runs on its own database; inside a module, organisations are kept apart by row-level security.
We do not claim certifications we do not hold. These are the commitments written into the DPA and General Terms every customer accepts.
An Article 28 GDPR agreement, with Standard Contractual Clauses for sub-processors outside the EEA. Published at supasailing.com/legal/dpa.
If a personal data breach affects your data, we notify you without undue delay and in any event within 48 hours.
You, or an independent auditor you appoint, can audit our compliance once every 12 months with 30 days' notice.
Export at any time, at least 30 days to retrieve your data after the contract ends, and no fee for switching or export.
We do not run our own data centres. The service runs on managed infrastructure, and every provider is listed with its purpose and location.
Databases, authentication and file storage run on Supabase (hosted on AWS), application servers on Hostinger in Paris, and DNS, TLS and encrypted backup storage on Cloudflare. Their certifications belong to them, not to us.
View the sub-processor listSend us your questionnaire (SIG, CAIQ or your own). We answer it from the DPA and its technical and organisational measures.