Ship's Blog and sharing — who can see what
Last updated Sat Jul 11 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
Two features show your voyage to people outside the crew: the Ship's Blog and passage share links. Both are opt-in, and both are under your control. Here's exactly who sees what.
The short version
Nothing is public unless you publish it. No blog exists until you create one; no share link exists until you make one; your logbook, crew list, and live position are never public by default.
Ship's Blog
The blog is a public website for your boat at /boats/your-address — you pick the address (it starts from the boat name, and you can change it).
- Only PUBLISHED posts are visible. Drafts are yours alone until you hit publish.
- Position is a snapshot, not a feed. When you publish a post, it captures that moment's position, passage label, and day number — permanently, even if your logbook changes later. The blog never shows where you are now, only where you were when you posted.
- Each post carries your words and up to a handful of photos; the blog page shows your title, tagline, template, and logo — nothing else from your account.
- Post in port about where you were, not underway about where you are, if boat security is on your mind. A three-day delay on posts costs nothing and tells nobody your current anchorage.
To take something down: unpublish the post (back to draft) and it's gone from the public page.
Passage share links
A share link is a private URL for a specific passage — made for shore crew, not the public. Anyone with the link sees the passage's track, latest synced position (with its age), and status. Control them from the passage page:
- Revoke any link at any time — it dies immediately.
- Links can carry an expiry date — good for a delivery where the owner needs eyes for two weeks, not forever.
- Make separate links for separate people; revoking the surveyor's doesn't cut off your family.
- The float plan email sends the pilotage plan as a revocable link too — not an attachment that lives forever in someone's inbox.
What is never public
Your logbook entries, crew names, contacts, maintenance records, stowage, papers, billing — none of it has a public surface. Shore-brief emails go only to the recipients you ticked, and every brief carries an unsubscribe link.
The privacy checklist before a passage
- Blog: happy with the address and what's published?
- Share links: right people, expiry set where it makes sense?
- Brief recipients: current list, nobody stale?
Three minutes, done. Questions about a specific exposure? Ask — privacy questions jump the queue in spirit if not in code.