Back to site

Privacy Policy

Last updated: 17 October 2026

Helmwise (Pty) Ltd

An updated version applies to new accounts from 14 October 2026, and to existing accounts from 23 November 2026.

1. Introduction

Handover is operated by Helmwise (Pty) Ltd, a company registered in South Africa, registration number 2026/258092/07 (“Helmwise”, “we”, “us”, “our”). This Privacy Policy explains how we collect, use, store, and protect your personal information when you use the Handover application.

Handover is a voice-first capture and handover reporting tool for superyacht crew. You record voice notes, type text notes, and use guided import workflows for library items. The app organises that information into structured handover reports for your vessel. This notice explains information handling. Reading it or using Handover does not, by itself, provide consent to every processing activity described here.

Business postal address: 12 Hall Road, Sea Point, Cape Town, 8001, South Africa. Contact Charl Dettmer at hello@thehandover.app about privacy or your information.

2. Data We Collect

  • Account information: your email address, name, and role when you sign up.
  • Voice recordings: temporarily uploaded for transcription. Handover does not keep raw audio as a saved, replayable note or long-term audio archive. Pending device copies and provider processing have separate lifecycles. See Section 4.
  • Capture content: the text of your notes, including transcribed voice notes, AI-generated classifications, and any metadata you add (department, priority, status).
  • Uploaded files and images: photos attached to captures, plus documents, screenshots, and photographed cards or notes that you choose to upload for template analysis, library imports, contact extraction, or report customisation.
  • Vessel information: vessel name, rotation dates, crew roster, and configuration settings.
  • Usage analytics: product usage data collected via PostHog. On the website, this only runs if you say yes. The Handover phone app does not ask this question yet. Handover's servers also send PostHog simple counts and timings; these are not linked to you or your account. Where analytics is on, a browser or device identifier can distinguish visits before sign-in. Signed-in activity is associated with a stable, pseudonymous account identifier. This information is not necessarily anonymous. See Section 12 for details.

Handover can store photo attachments with normal handover items. Access to each photo follows access to the note it belongs to. Handover also supports camera and image-library imports in specific workflows such as library imports, contact extraction, and report logo upload. For library and contact extraction flows, the selected image is used transiently to extract structured details and is not retained by us as a standalone stored image after extraction.

3. How We Use Your Data

  • Transcription: voice recordings are sent to a third-party transcription provider, OpenAI, to convert speech to text. Handover does not keep the recording as a saved audio note. Pending device recordings and provider copies have separate lifecycles (see Section 4).
  • AI classification: capture text is sent to OpenAI's API (not the consumer ChatGPT product) to classify captures into departments, priorities, and report sections. OpenAI states that API inputs and outputs are not used for model training by default.
  • AI extraction and import: text that you paste, documents that you upload for structure analysis, and images or screenshots that you upload for contact or library import may be sent to OpenAI's API to extract structured fields for review. In current library and contact import flows, those images are processed transiently for extraction and are not retained by us as standalone image files after the extraction request completes.
  • Report generation: your captures are assembled into PDF and DOCX handover reports.
  • Email delivery: handover reports and account emails (signup confirmation, password reset, invitations) are sent via Resend.
  • Product improvement: we use product analytics to understand how Handover is used and to improve the product. We do not use analytics to score individual crew performance.

4. Voice Recordings

Voice recordings are used for transcription. Handover does not keep raw audio as a saved application record, replayable attachment or long-term audio archive. A recording waiting on a phone for upload or retry is a separate temporary copy. Transcripts and resulting notes can remain as saved vessel records.

Handover does not use your recordings to train general-purpose AI models or identify speakers. In the standard service, audio is sent to OpenAI's transcription API. OpenAI states that API inputs and outputs are not used for model training by default. Deepgram previously provided transcription but is no longer used for new requests. Historical requests remain subject to the arrangements in effect when they were made. Messaging and AI providers have their own processing lifecycles. No-training settings and deletion are different controls.

5. Crew Privacy

Crew privacy is a founding principle of Handover. We limit the use of crew identity to providing, securing, supporting, and improving the service.

  • Handover does not use product analytics to evaluate individual crew performance or productivity.
  • Signed-in product activity may be linked to a stable, pseudonymous account identifier in PostHog. We do not use this information to score individual performance or productivity.
  • Vessel admins can see crew names solely for the purpose of handover coordination (e.g. assigning rotations, sending handover reports). This access is limited to what is necessary for operational handover management.
  • We will never sell, share, or expose individual crew data to vessel owners, management companies, or any third party for performance evaluation purposes.

6. AI-Processed Content

Capture text, summary prompts, uploaded template documents, pasted library text, and uploaded library import images or screenshots may be processed by OpenAI's API for classification, summary generation, structure extraction, and OCR-style field extraction. OpenAI states that API inputs and outputs are not used for model training by default.

Text-based AI workflows can be protected by our vessel-level “AI privacy protection” setting, which performs best-effort, pattern-based redaction of common personally identifiable information before text is sent to OpenAI. This protection may not identify every name, identifier, or sensitive detail, and it does not mask audio before transcription or visible information contained inside uploaded images. Audio and image imports are processed as submitted. In the current library image-import flows, those images are used only to extract fields for review and are not retained by us as standalone stored images after extraction.

Important: AI-generated outputs — including classifications, summaries, and report content — are informational only and do not constitute professional advice. You rely on AI-generated content at your own risk. Users must review all AI-generated content before relying on it or including it in official handover documentation.

7. Data Storage and Security

Supabase provides the application's database, authentication and file storage, hosted on AWS infrastructure in Ireland. Other providers process information for hosting, AI, messaging, analytics and diagnostics. Not every copy is held only in Supabase. Within the app, access follows authentication, vessel membership and permissions for the record. Authorised Helmwise personnel and service providers may also need restricted access to operate, secure, support or maintain the service. Handover is not end-to-end encrypted against Helmwise.

  • All connections use HTTPS/TLS encryption in transit.
  • Passwords are securely hashed using industry-standard algorithms.
  • Library PIN codes are hashed with bcrypt.
  • Row-level security ensures strict data isolation between vessels.

Breach notification. In the event of a security breach that compromises your personal information, we will notify the Information Regulator (South Africa) and affected users as soon as reasonably possible after becoming aware of the breach, in accordance with Section 22 of the Protection of Personal Information Act (POPIA).

While we implement reasonable technical and organisational measures to protect your personal information, no method of transmission over the internet or electronic storage is completely secure, and we cannot guarantee absolute security. You acknowledge that the provision of the Handover service necessarily involves the transmission of your data to the sub-processors listed in Section 9, and that you accept this as an inherent and necessary part of the service.

8. Data Retention

  • Captures: retained for as long as your account is active and your vessel continues using the service.
  • Voice recordings: not kept as saved audio records in Handover. Pending device recordings and supplier copies are separate (see Section 4).
  • Uploaded import images: screenshots and images from the camera or photo library that are sent for contact or library extraction are processed transiently for the request and are not retained by us as standalone import files after extraction, unless you separately save the resulting structured content in the product.
  • Stored photo attachments: retained with the capture they belong to. Archiving a capture does not delete its photos. Removing an individual photo or permanently deleting its capture removes it from normal product access. Eligible unreferenced files are then handled by protected storage cleanup; older files, shared files, backups, or files requiring manual review may be retained for longer.
  • Account data: deleted upon request. You may request deletion of your account and all associated data at any time by contacting hello@thehandover.app. After account closure, personal data is deleted within 30 days, except where we are required or permitted to retain it under applicable law, for example, to comply with a legal or regulatory obligation, to establish, exercise, or defend a legal claim, or to resolve an outstanding billing dispute. Where retention is required, we retain only the minimum data necessary for that purpose and for no longer than is necessary.
  • Backups: database backups are rotated according to Supabase's standard backup and retention policy. Analytics and diagnostic records have separate retention and deletion processes. Contact us about information linked to your account. Closing a crew account does not necessarily delete shared records controlled by the vessel's organisation.

9. Third-Party Sub-processors

We use the following third-party services to operate Handover:

Provider
Purpose
Infrastructure
Supabase
Database, authentication, file storage
AWS
OpenAI
Voice-to-text transcription, text classification, summaries, document structure extraction, image understanding for optional WhatsApp Capture, and transient image/text library imports
—
Resend
Transactional email delivery
—
Twilio
WhatsApp message transport, inbound and outbound (optional WhatsApp Capture feature)
—
Vercel
Web application hosting and page-speed measurement; website servers in Dublin, Ireland
—
PostHog
Product analytics linked to account or device identifiers, with approximate country and region; on the website only after you say yes, and the phone app does not ask yet; server-side counts and timings are not linked to you or your account; separate AI analysis features may use additional providers
—
Sentry
Error and performance diagnostics, including technical events and potentially personal context from a fault
US service

10. Data Sharing

We do not sell, rent, or trade your personal data to any third party. Service providers described in this policy and their own sub-processors may handle information for the purposes described here, including the separate analytics AI features explained in Section 12.

We may disclose your information if required to do so by law, court order, or other legal process, or if we believe in good faith that disclosure is necessary to protect our rights, your safety, or the safety of others.

11. International Transfers

Your data may be processed outside of South Africa by our sub-processors, as indicated in Section 9. Where data is transferred internationally, we ensure that appropriate safeguards are in place to protect your data in accordance with applicable data protection laws, including the Protection of Personal Information Act (POPIA).

12. Cookies and Tracking

  • Essential cookies: Handover uses essential authentication cookies (Supabase session tokens) required for the application to function. These cannot be disabled.
  • Analytics: we use PostHog for product analytics. On the website, this only runs if you say yes when Handover asks you to help improve it. Until you say yes, your browser sends no usage data to PostHog and stores no analytics identifier. You can change your answer at any time in Settings, under Privacy. If you say yes, it measures feature use, workflow steps, outcomes and timings. Before sign-in, a browser or device identifier can distinguish visits. After sign-in, product activity is linked to a stable account identifier. Website custom event fields are filtered to approved categories, counts and outcomes, excluding names, email addresses, vessel names, original filenames, note text, recordings, photos and uploaded document contents. These controls do not make the remaining identifiers or event history anonymous. The Handover phone app does not ask this question yet: it sends usage statistics and links them to your account identifier once you sign in. Handover's servers also send PostHog simple counts and timings, such as how long a voice-note transcription took; these are not linked to you or your account. We do not use analytics for crew performance evaluation.
  • No advertising cookies: Handover does not use advertising or marketing cookies. The PostHog product analytics described above are used only to operate and improve Handover.

Location estimates. Under the settings introduced on 9 October 2026, new website analytics events retain approximate country and region derived from the internet connection; client IP addresses are discarded from stored events after processing. IP-based location is an estimate, not proof of a person's or vessel's exact position. Events can remain linked to an account or device even when a report shows only geographic totals. Earlier analytics history includes IP addresses and more detailed estimated location; the new settings did not erase that history. Other hosting, security and diagnostic systems can still process IP addresses.

Website controls. Automatic click capture, in-app surveys and PostHog session recording are disabled. Analytics page addresses use recognised app routes with record identifiers replaced; query strings, fragments, referrers and marketing campaign or advertising-click identifiers are removed from those URL fields. The phone app also collects usage events, with controls separate from the website.

Analytics and AI. We have disabled PostHog's optional use of anonymised, aggregated analytics to train its own AI models. Its separate AI analysis features remain enabled. When we use those features, relevant analytics data, including identifiers, can be processed by PostHog's additional AI providers. This is separate from AI processing of vessel content.

Error reports. Sentry receives error and performance diagnostics to help investigate faults and reliability. Reports can include the error description, operation or page, app and device details, timings and context from the fault, including personal information. We do not describe every report as free of customer content. Our website reports use Sentry's US service. Error reporting is separate from product analytics and is not used to assess crew performance.

13. Children's Privacy

Handover is not directed at children under 18 years of age. We do not knowingly collect personal information from minors. If we become aware that we have collected data from a child under 18, we will take steps to delete that information promptly.

14. Your Rights

Under the Protection of Personal Information Act (POPIA) and, where applicable, the General Data Protection Regulation (GDPR), you have the following rights regarding your personal data:

  • Access: request confirmation of whether we hold personal data about you, and a copy of that data.
  • Rectification: request correction of inaccurate, misleading, or incomplete personal data.
  • Erasure: request deletion of your personal data.
  • Portability: request a machine-readable copy of your data.
  • Objection: object to the processing of your personal data on reasonable grounds, including the right to object at any time to the processing of your personal data for the purposes of direct marketing.
  • Automated decision-making: request that you not be subject to a decision based solely on automated processing that has legal or similarly significant effects on you. Handover uses AI to classify and summarise captures, but these outputs are informational and are not used to make decisions of this kind.

To exercise any of these rights, contact Charl Dettmer, our privacy contact, at hello@thehandover.app.

15. POPIA Compliance

Helmwise (Pty) Ltd is committed to compliance with the Protection of Personal Information Act, 2013 (POPIA).

  • Our privacy contact is Charl Dettmer, hello@thehandover.app.
  • We process personal information on a lawful basis, including consent and legitimate interest in providing the Handover service.
  • Data subject requests are honoured within 30 days of receipt.

16. WhatsApp Capture

Handover offers an optional WhatsApp Capture feature on paid plans. If you choose to connect a phone number in your account settings, you can send notes to Handover directly from WhatsApp. This feature is off by default and only operates for phone numbers you explicitly connect. Disconnecting a number from WhatsApp Capture in your account settings stops any further capture from it.

Message transport. Messages you send to the Handover WhatsApp number, and the single confirmation reply we send back, are carried by Twilio, our WhatsApp messaging provider (listed in Section 9). Twilio transmits the message between WhatsApp and our servers.

WhatsApp and Meta. WhatsApp is operated by Meta Platforms, Inc. Meta is not a Helmwise sub-processor; your use of WhatsApp is governed by WhatsApp's and Meta's own terms and privacy policy, which apply to your WhatsApp account independently of Handover. We only receive the messages you choose to send to the Handover WhatsApp number.

What we receive. When you message the Handover number from a connected phone, we receive your message content (text, voice note, or image), your WhatsApp phone number, and basic message metadata.

Voice notes. In the standard WhatsApp workflow, voice notes are transcribed by OpenAI. Handover does not keep the recording as a saved audio note. Messaging and AI-provider copies have separate processing lifecycles, as described in Section 4.

Images. Images or screenshots sent over WhatsApp are read by OpenAI to extract a structured note. The original image is stored in Handover as an attachment to that note, visible only to crew who can see the note itself. Deleting the note removes access to the photo in Handover, but the underlying file may remain in protected storage. Please note that an image such as a business card may contain other people's personal information.

Files. On accounts where file capture is switched on, a PDF, Word or Excel file sent over WhatsApp is read inside Handover's private AI, which keeps the file and its text within that private service, as described in Section 6. The file is stored in the boat's protected storage, visible only to crew who can see the item it belongs to. Files up to 15 MB are accepted. A file that cannot be placed on an item waits for a person to choose where it goes, with the caption as its label, and is removed after 14 days if no choice is made. A file that holds a passport or identity document is never turned into a note and never placed on an item; it is set aside for a person to place by hand. The check that recognises such a document runs inside the same private service and keeps nothing. Where the boat's AI is paused, or private AI is not in use on the account, the file waits unread in the same way. After the confirmation reply, Handover clears the original message text and media link from the message log, as described under “Your phone number” below.

Your phone number. To operate WhatsApp Capture we store the phone number you connect and the sender number of the WhatsApp messages we receive, so we can link each message to your Handover account. Within the capture record itself, the sender's number is masked to its last two digits. The underlying message log keeps the full number while processing or retrying a message. After processing finishes and the reply has been attempted, Handover clears the original text and media link from that log and masks the number there. The connected number and linking and audit records are separate, subject to the retention and deletion rules in Section 8.

The resulting capture. The note created from a WhatsApp message is stored in Handover like any other capture (see Section 8). Clearing the original message log does not delete the saved capture. WhatsApp and Twilio copies have their own processing and retention lifecycles.

17. Changes to This Policy

We may update this policy from time to time. The “last updated” date at the top will reflect any changes. Material changes will be communicated via email to the address associated with your account. Continued use of Handover after changes constitutes acceptance of the updated policy.

18. Contact

Information Officer: Charl Dettmer
Email: hello@thehandover.app

If you are unsatisfied with our response to a privacy concern, you have the right to lodge a complaint with the Information Regulator (South Africa):

Information Regulator (South Africa)
Website: inforegulator.org.za