Security at the gangway.
No one boards until they’re cleared. The search rules follow the ISPS level you set.
You control each ISPS level.
You decide what happens at Levels 1, 2 and 3, from automatic check-in to a mandatory search of every visitor. Raise the active level the moment port risk or the threat changes.
A typical setup. Each level’s search frequency, ID checks and restricted access are yours to define in the admin. Change the active level and every crew phone hears it, instantly. What the Code itself asks for is set out in the ISPS Code explained.
Nobody boards until they are cleared.

The check-in, in the order a visitor meets it. And what happens for guests.
The vessel is named, the level in force is stated, and the visitor is told they may be asked for identification and to submit to search. Access is granted at the Master’s discretion, and the screen says so before a single field is filled in.
Heads of department are listed with photo, rank, and whether they are aboard or ashore. The host’s phone gets the arrival with the visitor’s name and photo. The visit is filed under the host who took it.
The kiosk holds the check-in and alerts the right crew member by push or WhatsApp, with name and photo. A 4-digit PIN, set in the admin, clears the hold. If nobody is at the gangway, the visitor can call for assistance from the screen.
The crew member signs as search officer and records the ID they verified: passport, driving licence, government, company or work ID. Who searched, when, and the outcome, on the visitor’s record. Agreements are signed on the iPad before boarding and kept with it.
Company, host and whether a search was carried out, per visitor, with the ones who have left below. It exports as a PDF: visitor, came in, left, searched by, and both signatures.
The owner’s party do not go through visitor sign-in, an agreement or a photo. They carry a name, a cabin, a date of birth and a document, and they are counted on the muster roster like anyone else aboard.
Add the fields your flag or port actually asks for: nationality, passport expiry, joining port. Or import the whole manifest from a spreadsheet.
And email, for the office. The admins who opt in get a note when a search is triggered or completed, an agreement is signed, a flagged visitor appears, or someone is still aboard at day’s end.
The vessel owns its data.
UK and EU GDPR
The vessel is the data controller. Muster App Ltd is the processor.
UK data residency
Crew and visitor data is stored and processed in AWS’s London region.
Encrypted in transit and at rest
TLS 1.3 in transit, AES-256 at rest. Photos and IDs stored encrypted.
SOC 2 aligned controls
Access control, audit logging and change management modelled on the SOC 2 framework.
You control retention
Keep records as long as you need. Delete any visitor whenever you want.
Right to erasure
If a visitor asks to be forgotten, wipe their record, photo and agreement in the admin.
The detail is in the privacy policy.