Emergency card

WatchKeeper — offline quick reference

Works with NO signal (on a device where the app has loaded before)

• Opening the app and reading anything you loaded in the last 30 days
• Posting log entries, fish log, VHF log, incidents, plan notes, and watch shifts — these queue on the device and survive a reload
• Ticking Procedures checklists (stored on the device)

Queues automatically — no action needed

• Queued entries syncing to the server (happens by itself when signal returns)
• Shore briefs and arrival notices — sent from the server on schedule, from your last synced data, even while you're dark

Needs live signal, full stop

• Sign-in on a NEW device
• Weather, tides, AIS, Skipper AI
• Photo uploads, crew invites, billing changes

Rules of thumb

• Do not sign out and do not clear the browser while offshore — a fresh sign-in needs a connection.
• Keep logging normally offline; the queue syncs by itself when signal returns.
• Check Settings → Pending writes to see what's still queued — “Retry all” forces a sync attempt.
• Shore crew worried? Your shared passage link shows the latest synced position and when data last arrived.

Reaching support

• Email: support@watchkeeper.me — works from any satellite mail client (Iridium GO, Starlink, SSB winlink). Plain text is fine.
• Status, text-only: support.watchkeeper.me/status.txt
• Answered within 1 business day — sometimes longer if James is offshore too.
• Include if you can: boat name, app email, what you did, what you expected, what happened.

WatchKeeper is a logbook, not a safety system. For emergencies use your EPIRB, DSC radio, and local SAR — never wait on an app or an email.