6.1 General
Mermaid is a digital first mate designed to assist with charter-week planning, boat context, route review, weather context, crew coordination, evidence management, expense settlement, trip replay, anchor monitoring and community information.
Features may be released gradually, limited by plan, region, boat type, operating system, browser, device capability, data coverage, vendor licence, beta gate or safety review. A feature shown in marketing, a prototype, roadmap or screenshot is not guaranteed unless it is included in your active plan or order confirmation.
6.2 Boat and Charter context
The Service may provide boat specifications, dimensions, draft, equipment, images, services, extras, booking data, inspection metadata and base information. This data may come from users, charter companies, manufacturers, brokers, public sources or third parties and may be inaccurate, incomplete or outdated.
Before departure and before relying on any boat-specific setting, the skipper must physically verify the vessel, draft, air draft, safety equipment, engine, batteries, navigation instruments, ground tackle, chain markings, emergency equipment and all other material characteristics. A selected boat profile does not prove that the actual boat matches the database entry.
6.3 Route planning and route review
The Service may present route corridors, stopover options, comfort-versus-speed preferences, weather lookahead, warnings, draft context and uncertainty. A route is an informational suggestion, not a clearance, pilotage plan or assurance of safe passage.
A route may omit or misstate hazards, restricted areas, separation schemes, traffic, bridge clearance, cables, underwater works, seasonal rules, currents, tide, sea state, local buoyage, temporary notices, military zones, environmental restrictions, port closures or rapidly changing conditions. The skipper must independently prepare and continuously monitor a legally compliant passage plan.
6.4 Weather presentation
Mermaid may fuse, transform or display baseline forecasts, gust layers, field tiles, coverage labels, source age and fallback data. Weather and sea conditions can differ materially from forecasts and can change faster than data refreshes. Coverage may degrade or be unavailable.
Users must check official marine forecasts, warnings, local observations and appropriate professional sources immediately before and during a voyage. Source-age, fallback and uncertainty notices must not be ignored. Mermaid does not issue official weather warnings and has no duty to monitor a voyage.
6.5 Anchorages, marinas and points of interest
Information about anchorages, ports and marinas may include seabed, shelter, depth, facilities, ratings, comments, images and community-derived observations. Such information is contextual only. It does not confirm legal permission, holding, swinging room, water depth, chart datum, underwater obstruction, mooring condition, availability, booking, opening hours or suitability for the current vessel and conditions.
Users must verify official charts, pilot books, port or marina instructions, local anchoring restrictions, protected-area rules, weather, tide, seabed and actual conditions. Community ratings are subjective and may not reflect current safety.
6.6 Anchor Alarm
The Anchor Alarm may assist with guided anchoring, chain or scope calculations, a wind-biased or smart swing area, local alarms, notes, photographs, logbook entries and optional remote sharing. It is supplementary and cannot guarantee that dragging, drift, collision, grounding or another dangerous condition will be detected or communicated.
Its operation depends on the device, positioning hardware, GPS accuracy, operating-system background limits, permissions, battery, power-saving mode, network, browser or PWA support, push services, email delivery, user settings, sensor quality and correct setup. False alarms and missed alarms are possible.
The device kept onboard with the skipper is the primary alarm device. Crew PWA push notifications and email fallback are remote conveniences only. A Crew User’s acknowledgement may suppress repeat notices on that Crew User’s device for a limited period, but it must not silence the onboard alarm. SMS is not included unless expressly stated in the Service.
The skipper must maintain a proper anchor watch appropriate to the circumstances, independently verify the anchor position and scope, and keep the onboard device powered, audible and correctly configured. Do not leave a vessel unattended merely because the Anchor Alarm is active.
6.7 Crew Ops and safety briefings
The Service may assist with crew lists, invitations, safety briefing workflows, practical tips, photographs, signatures and acknowledgements. These tools organise evidence and communication; they do not deliver certified training, verify comprehension, satisfy every flag-state or charter-company requirement, or transfer responsibility from the skipper.
The skipper must tailor the briefing to the vessel, crew, route, conditions and applicable law; demonstrate safety equipment where appropriate; supervise minors and inexperienced crew; and confirm actual understanding. A stored signature or acknowledgement records an interaction but is not conclusive proof of informed consent, competence, legal compliance or absence of negligence.
6.8 Cash kitty and expense settlement
The cash kitty feature may record expenses, participants, currencies, proposed transfers and paid/unpaid status and may generate a final statement. It is an administrative calculation tool only. Mermaid does not hold, transmit, exchange or settle funds, operate a bank account, provide credit, act as payment institution, escrow agent, accountant or debt collector, or guarantee payment.
Users must verify amounts, participants, exchange rates, tax treatment and settlement instructions. Currency conversion may use a displayed rate or user-selected settlement basis and may not match a bank or card rate. Payment disputes remain between the relevant users. A “paid” marker is a user-entered status, not independent confirmation of payment.
6.9 Check-in, check-out, inspections and evidence
The Service may provide boat-specific offline drafts, issue tracking, previous-issue continuity, photographs, AR-guided assistance, a two-dimensional fallback and future human-confirmed AI suggestions. These are documentation aids, not a marine survey, damage appraisal, condition warranty or acceptance by a charter company, insurer or owner.
The user must conduct an appropriate physical inspection, follow the charter provider’s procedures, report issues through required official channels and obtain acknowledgement where needed. AR alignment, computer vision, metadata and issue suggestions can be wrong. A user must confirm every issue before submission.
Users must have lawful authority to take and upload photographs, avoid unnecessary images of people or sensitive documents, and preserve original evidence where needed. Export packages and checksums support integrity but do not guarantee admissibility, completeness or legal effect.
6.10 Logbook and trip replay
Mermaid’s local-first logbook may record routes, points, metrics, anchoring events and weather enrichment and may sync an optimised server projection for account continuity. The higher-fidelity local record may differ from the server projection. Device loss, storage cleanup, permission changes or failed sync can result in data loss.
Unless applicable law or a competent authority expressly accepts it, the Mermaid logbook is not the vessel’s mandatory official logbook, voyage data recorder or accident record. Users must keep any records required by flag, port, charter, employment, insurance or safety law through appropriate means.
6.11 NMEA and instrument enrichment
Optional NMEA or instrument features may read compatible data. Users must connect devices only where authorised and safe, and must not interfere with certified navigation equipment, wiring, networks or warranties. Raw NMEA debug capture is intended to remain local and short-lived; ordinary sync uses normalised or optimised points. Product-improvement contribution upload is disabled unless a separate account-level opt-in and technical gate are enabled.
Instrument data may be delayed, mislabelled, corrupted, duplicated or unavailable. Mermaid is not a substitute for directly reading, maintaining and cross-checking onboard instruments.