Privacy Policy
Sea Ledgers client platform
| Item | Detail |
|---|---|
| Version | 1.0, effective 13 October 2026 |
| Applies to | app.sealedgers.com, the Sea Ledgers client platform and certificate check pages |
| Controller for accounts and certificates | E‑TRON LLC, a Wyoming limited liability company doing business as Sea Ledgers, 2830 W State Road 84, Suite 107, Fort Lauderdale, FL 33312, United States |
| Contact | privacy@sealedgers.com |
| EU representative | Cloudkasten GmbH, Seestr. 20 G, 50374 Erftstadt, Germany |
1. Who we are
Sea Ledgers runs a platform where yacht owners, managers, captains, crew and verifiers keep fuel, voyage and emissions records, and where Sea Ledgers issues carbon neutrality certificates. E‑TRON LLC, a Wyoming limited liability company doing business as Sea Ledgers ("Sea Ledgers", "we") is responsible for the personal data described here. This policy follows the EU General Data Protection Regulation (GDPR), which applies because the platform serves people in the European Union.
Two roles
Controller. For platform accounts, sign-in, security logs, certificates and our own business contacts, Sea Ledgers decides how data is used.
Processor. For the records a client puts into the platform (Logbook entries, onboarding workbooks, documents), the client decides, and Sea Ledgers acts on its instructions under the Data Processing Agreement.
2. What we collect
| Category | Examples | Source |
|---|---|---|
| Account | Email address, organisation, role (owner or manager, captain, crew, verifier), vessels you can access | Your organisation or Sea Ledgers, when you are invited |
| Sign-in and security | Sign-in times, two-step sign-in status, actions taken in the app (audit log), IP address in server logs | The platform |
| Vessel records | Fuel, bunkering, voyages, ports, engine hours, emissions, documents such as bunker delivery notes. These may include names of crew or suppliers. | Your organisation |
| Certificates | Vessel name, IMO number, certificate number, credits retired, registry serial | Sea Ledgers and the carbon registry |
| Messages | Emails you send us | You |
We do not use advertising or tracking cookies. The app keeps your sign-in session in your browser's local storage, which is needed for it to work.
3. Why we use it, and on what basis
| Purpose | Legal basis |
|---|---|
| Provide the platform, run sign-in and keep your role and vessel access | Contract with your organisation |
| Keep records, approvals and the audit log tamper evident | Contract and legitimate interest in record integrity |
| Issue and publicly verify certificates | Contract with the client |
| Security, fraud prevention and incident response | Legitimate interest and legal obligation |
| Regulatory, tax and audit record keeping | Legal obligation |
| Service emails (sign-in links, approvals, certificate notices) | Contract |
We do not sell personal data and do not use it for profiling or automated decisions with legal effect.
4. The public ledger
Approved records and certificates are timestamped on the Hedera public network. Only a fingerprint (a SHA-256 hash), a certificate number and token data are written there. A fingerprint cannot be turned back into the record. No names, emails or vessel records are written to the ledger. Ledger entries are permanent by design.
A certificate check page is public for each certificate, so that a third party can confirm it. It shows the vessel name, IMO number, credits retired and registry serial, and no personal data about individuals.
5. Who we share it with
Sea Ledgers is based in the United States, and so are Supabase, Render and Resend. Platform data is stored in Frankfurt, Germany, and is accessed from the United States by Sea Ledgers staff and, where needed, by these providers. These transfers out of the European Economic Area are covered by the EU Standard Contractual Clauses or the EU US Data Privacy Framework. We use the service providers below, each under a written agreement.
| Provider | Service | Data location | Data involved |
|---|---|---|---|
| Supabase Inc. | Database, file storage, sign-in | Frankfurt, Germany (AWS eu-central-1) | Account data, client records, uploaded files |
| Render Services Inc. | Application hosting | Frankfurt, Germany | All data in transit through the app; request logs |
| Resend Inc. | Sign-in and notice emails | Ireland (AWS eu-west-1) | Email address, email content |
| Hedera network (public ledger) | Timestamps and certificate tokens | Global, public | Fingerprints and certificate numbers only. No personal data. |
We may also share data with the carbon registry to retire credits, with professional advisers under confidentiality, or with authorities when the law requires it.
6. How long we keep it
| Data | Kept for |
|---|---|
| Account | While the account is active, then 12 months |
| Vessel records, approvals and audit log | Contract term plus 10 years, to support regulatory, tax and certificate audits |
| Certificates and ledger fingerprints | Permanently, so the certificate can always be checked |
| Server logs | 30 days |
| Database backups | 7 days, rolling |
7. Security
Data is encrypted in transit and at rest. Access is by invitation only, with email link sign-in and optional two-step sign-in. Every request is checked against your role. Records cannot be edited once approved, and history tables are append only. Files are private and shared only through links that expire after 5 minutes.
8. Your rights
You can ask to access, correct, delete or restrict your personal data, to receive it in a portable format, or object to its use. Where your data sits in your organisation's records, we pass the request to your organisation and help it respond. Some records must be kept for legal reasons, and ledger fingerprints cannot be removed, but they contain no personal data.
Write to privacy@sealedgers.com. We reply within one month. You may also contact our EU representative, or complain to the data protection authority in your EU country.
9. Changes
We will post updates here and tell account holders by email about material changes.
References: GDPR Article 27, https://gdpr.eu/article-27-representatives-of-controllers-not-in-union/
