ESAC Public Pilot Privacy Notice

This notice applies to the production-backed ESAC public pilot. The separate training demo uses synthetic browser-local records and should not be used for real personal information.

Information collected

The pilot may collect account identifiers, contact details, company and voyage particulars, application decisions, communications, timestamps and audit events. Crew onboarding and check-in may also collect crew identity particulars, passport or MSIC evidence, live check-in photographs, precise location, device registration and submission information.

Crew app location and permissions

After a crew member approves voyage tracking at boarding, the ESAC Crew app collects precise location data to create that voyage's GPS route and requested heartbeats even when the app is closed or not in use. The same voyage approval covers later check-ins, heartbeat requests and Normal, Enhanced or Coast Guard sampling changes for that voyage. Location is not used for advertising.

On Android, the app requests foreground location first and requests only access that is still missing. Android 11 and later require the crew member to enable background location through the app's system Location settings. The app uses the system camera or photo picker only when the crew member chooses to capture or select required evidence; the Android app does not request its own camera permission. Device push registration may continue if visible notification permission is declined so authorised operational data messages and receipt processing are not silently disconnected.

Purpose and access

Information is used to operate, secure, test and improve the ESAC workflow; investigate faults or misuse; and support assessment by the applicant and an assigned PGSA. Access is restricted according to account role and application assignment. Identity documents, check-in evidence and voyage locations are not intended for public access.

Storage and disclosure

Pilot application data is stored in a separate production Supabase environment in Singapore and the website is delivered through Cloudflare. Information may be processed by those infrastructure providers and may be disclosed where required by law or necessary to investigate a security incident.

When an authorised Customer, PGSA or Administrator opens an ESAC voyage-tracking record, Google Maps may supply a compact contextual route image using up to 100 sampled canonical vessel-track coordinates. If the authorised user expands the map, the Google Maps interactive service receives the recorded route coordinates and all coordinate-bearing vessel heartbeat positions needed to display a direct marine line and heartbeat dots without vehicle routing. The PGSA and Administrator Crew status map may also send the latest authorised position for each registered crew tracker so that device-status markers can be displayed. Crew names, contact details, tracker diagnostics and authority history are not sent to Google Maps; those records remain inside the portal's restricted Technical details. Google also receives ordinary connection and device information. ESAC route records remain in the Maresac and Supabase systems. If Google Maps cannot load, the portal displays the authorised records using a locally rendered plot. Google Maps use is subject to the Google Maps terms and Google Privacy Policy.

Retention and deletion

Identity documents and check-in photographs or precise location records are retained only while needed for the relevant voyage, security review, incident handling or a legal obligation, and are reviewed for deletion when an ESAC is closed. Account and application records are retained while needed for the pilot, security and audit. You may request account closure, access or correction. Some immutable audit events may need to be retained, but personal information that is no longer required will be deleted or de-identified where practicable and legally permitted.

Your choices

Crew onboarding and Check-in are optional during the pilot. Do not upload passports, MSIC cards, face photographs or other sensitive documents unless the pilot interface specifically requests them and you are authorized to supply them. Crew can pause voyage tracking without withdrawing the voyage approval, revoke tracking access for the phone, or change location and notification access in Android settings. Declining background location prevents later background collection but does not prevent access to the app's other available features.

Contact

Privacy, access, correction and deletion requests: odysseus69@scyllancharybdis.com.