The Digital Round
Security & Privacy

Built secure for maritime environments

DigitalRound's offline-first architecture is designed to minimise cyber risk in connectivity-constrained environments. Here's exactly how your data is handled, protected, and controlled.

🔒 Local-first, no cloud required
🔐 TLS 1.2+ in transit
📡 Offline-first (no cloud required)
⚓ IMO MSC.428 aligned
🇪🇺 GDPR ready
🏭 Air-gapped deployment available
🗃️

Local-first data storage

All data lives on the vessel's device by default. Cloud sync is optional — disabled means nothing leaves the vessel. Ever.

🔑

You own your data

DigitalRound never uses your operational data for AI training, benchmarking, or any commercial purpose. Export it anytime. Delete it on request.

🛡️

Minimal attack surface

A system that operates offline can't be remotely compromised while disconnected. Offline-first is good security architecture, not just a connectivity feature.

⚓ IMO MSC.428(98) — Cyber Risk Management

IMO Resolution MSC.428(98) requires maritime operators to include cyber risk management in their Safety Management System. Port State Control inspectors are increasingly checking for evidence of cyber hygiene.

DigitalRound supports MSC.428 compliance in three ways: (1) offline-first architecture reduces attack surface; (2) role-based access control limits blast radius if a device is compromised; (3) immutable timestamped audit logs provide evidence of maintenance activities for SMS documentation. Air-gapped deployment is available for operators requiring complete network isolation.

🗃️ Data Storage & Privacy
Where is our vessel's maintenance data stored?
By default, DigitalRound stores all data locally on the vessel's device (tablet or laptop). The local device is the primary data store. Cloud sync is entirely optional and only occurs when the vessel has internet connectivity and sync has been explicitly enabled by an administrator.

For operators with strict data sovereignty requirements, DigitalRound can be deployed in a fully local mode where no data leaves the vessel network under any circumstances.
Do you store our operational data on your servers?
Only if cloud sync is enabled. In that case, encrypted rounds data, work orders, and exception logs synchronise to our cloud infrastructure. Identifying information (vessel name, company) is configurable — operators may choose to pseudonymise it.

Operators requiring full data isolation can deploy DigitalRound in on-premises mode (Enterprise tier), where all data stays within the vessel or company network and never touches our infrastructure.
Who owns the data?
The operator owns all data, always. DigitalRound does not use operational data for AI model training, benchmarking, competitive analysis, or any commercial purpose without explicit written consent. Data can be exported in full at any time (CSV and PDF formats) and deleted on request.
How long is data retained?
Data is retained for the duration of the subscription. Enterprise customers may specify a custom retention policy. On subscription termination, data export is provided within 30 days, after which it is securely deleted from any cloud infrastructure.
🌐 Network Security
What happens when the vessel has no internet connection?
The app functions identically offline. All reads and writes go to the local database. No network calls are attempted. This is not a degraded mode — it is the primary design. An offline vessel running DigitalRound has zero external network exposure for that application.
What ports and protocols are used for sync?
Cloud sync uses HTTPS (TLS 1.2+) on port 443 exclusively. No unusual ports or protocols are required. Standard outbound web filtering rules are sufficient — no additional firewall exceptions are needed for most vessel network configurations.
Does the app require any inbound connections?
No. All sync is initiated outbound from the vessel. No inbound connections, no open ports on the vessel's network, no remote access required by DigitalRound.
🔑 Authentication & Access Control
How do crew members authenticate?
DigitalRound supports:
  • PIN authentication — fast, works offline, designed for engine room use
  • Password authentication — for higher-security requirements
  • Role-based access control — crew, supervisor, and admin roles with distinct permissions
  • SSO integration (Enterprise) — SAML 2.0 / OAuth 2.0 compatible with major identity providers
What happens if a tablet is lost or stolen?
Be straight with your fleet on this one: application-level encryption at rest is not implemented today, and there is no remote wipe. A lost tablet is protected by the device's own controls, not by ours. So enabling device-level encryption (standard on all modern Android/iOS) and a minimum 6-digit device PIN is not a recommendation here, it is the control. Set a LOOP PIN on every crew account as well — an account with no PIN opens on a single tap. Encryption at rest and remote wipe are in build.
Can we restrict data access by crew role?
Yes. Role-based access control allows administrators to configure exactly which data and screens are available per role. Typical configuration: crew can log rounds and view open work orders; supervisors can view historical trends and all exceptions; administrators manage templates and user accounts.
🔒 Encryption
How is data encrypted?
  • Data at rest: not encrypted today. Rounds data is held in the app's local database and its preferences store, on the device or the hub PC. Encryption at rest is in build.
  • Data in transit: TLS 1.2+ for all sync communications — never transmitted in plaintext
  • Integration credentials (for example the ship's mail account): held in the application's preferences store in plaintext. Moving them to the platform keystore is in build. Crew PINs are stored unhashed.
  • API keys and credentials: Never logged, never exposed in error messages or debug output
🤖 LOOP AI Data Handling
Does LOOP send maintenance data to third-party AI providers?
In offline mode: No data leaves the device. LOOP operates entirely locally using a local model — zero external calls.

In online mode: If cloud AI features are enabled, queries are processed by our AI provider (Anthropic). Only the specific query and minimal relevant context are sent — not bulk historical data. This data is governed by Anthropic's enterprise data usage policy, which prohibits training on customer data.

Operators who require strict data isolation can configure LOOP to operate in local-only mode permanently, regardless of connectivity.
Is LOOP's AI trained on our vessel's data?
No. LOOP accesses your rounds history and manuals as a reference at query time — it does not train on your data or incorporate it into any model. Your data is read-only context, not training material.
🇪🇺 GDPR & Compliance
Is DigitalRound GDPR-compliant?
For EU-based operators: crew personal data (names, user IDs) can be configured to use pseudonymous identifiers. Data subject access requests and deletion requests can be fulfilled on request. A Data Processing Agreement (DPA) is available for Enterprise customers. We do not sell personal data to third parties.
Can we get documentation for a security review or IT audit?
Enterprise customers can request: penetration test summary (under NDA), security architecture overview, data processing agreement, and incident response policy. Contact [email protected] for enterprise security review requests.

Security questions before evaluating?

We're happy to walk through the architecture with your IT team or DPA before the pilot.

Book a Call → Email Us