Privacy Policy
For new accounts, this version applies from sign-up, from Wednesday 14 October 2026. For existing accounts, it takes effect on Monday 23 November 2026; until then, the current version applies.
1. Who we are and what this notice covers
Handover is operated by Helmwise (Pty) Ltd. Helmwise (Pty) Ltd is registered in South Africa under company number 2026/258092/07. Its registered office is Flat 601, Dunhof Flats, 12 Hall Road, Cape Town, Western Cape, 8005, South Africa. Contact our Information Officer, Charl Dettmer, at hello@thehandover.app about privacy or your information.
This notice explains how information is handled in the Handover website, phone app and optional WhatsApp Capture service. It describes the service after the private AI launch. Reading or using the service is not, by itself, consent to every use of personal information described here.
For vessel records, the organisation or person deciding why the records are kept is normally the controller, called the responsible party under South African law. Helmwise processes those records on the customer's instructions. A customer may itself act for another controller. Your vessel administrator can help identify the responsible organisation; contact us if you need help.
Helmwise is responsible for its own purposes, including administering customer relationships, billing records, service security, support, product updates by email and optional product analytics. Our Data Processing Agreement governs processing on a customer's behalf. Choosing an AI supplier does not by itself change these roles.
2. Information we receive
We receive information you provide when you create an account, join a vessel, submit content, connect WhatsApp, buy a subscription or contact us. We also receive information from vessel administrators, other authorised users, payment services and the devices used to access Handover.
Account and vessel information includes names, email addresses, roles, crew membership, vessel names, rotations, access arrangements and subscription status. Billing records include purchase details and payment status. Payment providers handle payment credentials under their own arrangements. Your choice about Handover update emails, made at sign-up and in Settings, is stored with your account.
Vessel content includes typed notes, transcripts, photos, documents, contact and library details, AI-generated suggestions, reports and associated metadata. Content can concern crew, guests, suppliers and other people who do not have an account.
Technical information includes account identifiers, device and browser details, IP addresses, diagnostic events and security logs. If you say yes to Help improve Handover, it also includes product interactions (section 10). Error reports can contain contextual information from a failed operation. We do not promise that every diagnostic event is free of personal information.
WhatsApp Capture receives the messages sent to our number from a connected phone, together with the sender's number and message metadata. Handover keeps a record of each message (section 9). Optional weather and location features use the location supplied or selected for that feature. Permission to use a device's microphone, camera or location is controlled separately through the device.
3. Why information is used
We use account and service information to provide access, organise vessel records, transcribe and sort notes, extract information, generate reports, deliver requested messages and provide support. We use billing information to administer purchases and refunds, and technical information to secure, troubleshoot and improve the service.
For processing under our own control, we use account and purchase information to perform our contract where you are the contracting individual. For an organisation's staff and contacts, account administration and support instead rely on our legitimate interests in delivering and managing the organisation's service, balanced against people's rights. We do not treat your employer's contract as a contract with you.
Tax and accounting records are processed to meet applicable legal obligations. Security and fraud prevention rely on our legitimate interests in protecting the service and its users, and on any applicable legal duties. Handling disputes relies on our legitimate interests in establishing and defending legal claims. On the website and the updated phone app, optional product analytics, and the device storage it needs, rely on your consent, which you give by saying yes when Handover asks (section 10). Older phone versions send usage statistics without asking; from 23 November 2026 we discard those statistics when they arrive. Counts sent from our own servers rely on our legitimate interests in running and improving the service, balanced against people's rights. Where consent is required, it is obtained separately and can be withdrawn for future processing.
Product updates by email. We send product updates only to people who chose them: by leaving the "Send me Handover updates" box ticked when they signed up, or by saying yes when Handover asked in the app. Every update has an unsubscribe link that works in one click, with no sign-in. Settings has a "Handover updates" switch, and a reply of "stop" is honoured. Where you said yes in the app, we rely on that consent. Where you left the box ticked at sign-up, we rely on our legitimate interest in telling the people who use Handover about it. You can object or unsubscribe at any time (section 13). Password, account, billing and legal notices are not product updates. We send them whether or not you have turned updates off.
For vessel records processed on instructions, the responsible organisation determines the lawful grounds and gives the relevant notices. It must also meet any additional requirements for health information, children's information or other specially protected data. Those requirements belong to the controller. Helmwise allowing the information into the service does not meet them. Helmwise remains responsible for its own legal obligations.
Providing the account information needed to identify and authenticate you is necessary to provide an account. Optional content and features are your choice, subject to your organisation's instructions. Some features cannot work without the information they process.
4. AI on your vessel
AI is selected for the vessel, rather than separately for each crew member. Qualifying paid access includes a vessel subscription, a subscription covering the vessel, or an active crew member's qualifying Pro, Team or Vessel access. Eligible trials, passes, access codes and paid-through periods can count. Consequently, a crew member with a Free account can use private AI while working on a qualifying vessel.
Qualifying vessels use our private AI service, which Tinfoil, Inc. (United States) runs on sealed servers. Vessels without qualifying access normally use OpenAI for text, images and voice transcription, in the app and on WhatsApp. OpenAI is used through its API, not the consumer ChatGPT product.
When qualifying access ends, including when a trial, pass or the last qualifying crew entitlement ends, subsequent requests normally use the standard providers. A specifically enabled private-AI vessel remains private until that setting is removed. Where available plan information leaves eligibility uncertain, requests may remain private until that uncertainty is resolved. A failure to read the routing settings is different: the request stops unless the vessel has a separate private-only setting. It is not sent to standard AI because of that failure.
Private AI protects the AI processing step. Tinfoil, Inc. runs it on sealed servers: protected computing hardware designed to prevent its operators and hosting companies from reading content during inference. Before Handover sends anything, it checks the server's attestation, a signed proof of what the server is running. If that check fails, nothing is sent through that connection. This is not a guarantee against every possible security failure.
Tinfoil states that it does not use AI inputs or outputs to train models and that it keeps no prompts or replies after answering. One qualification applies. Temporary data derived from requests can remain in protected hardware memory as a prompt cache. Its published design has no fixed expiry. Entries are displaced as memory is needed, or cleared when the hardware restarts. Handover supplies vessel-specific cache keys for applicable requests. This is not a promise of immediate erasure of every content-derived value. Tinfoil keeps usage metadata, including request counts, token counts and timestamps. That is separate from request content.
Handover does not use your recordings or vessel content to train general-purpose AI models, identify speakers or score crew performance. OpenAI states that it does not use API inputs or outputs to train its models. It keeps text and image requests and replies for up to 30 days for abuse monitoring (longer only where the law requires it or to protect the service or others from harm), and does not keep voice recordings sent for transcription. Provider-specific information is available through the supplier links below.
If private processing fails, Handover does not automatically send the request to a different AI provider. For certain text-model failures, it can retry once on another model at the same private provider. Photo processing and voice transcription have no enabled second-model backup. Failed requests may require another attempt or manual entry.
Before text goes to any AI service, Handover replaces recognised private details, such as names, numbers and addresses, with placeholders, and puts them back in the answer. A boat admin can switch this off. How We Use AI, section 6, explains what it covers and what it can miss.
Handover still handles your content before and after the private AI step and stores the resulting records. Hosting, storage, emails, diagnostics, analytics, billing and WhatsApp transport do not become private AI services. See How We Use AI for feature details and the limits of masking.
5. Who can see vessel records
Authorised users can access records according to their vessel membership and permissions. Administrators manage access for their organisation. Helmwise personnel and suppliers may process information where necessary to operate, secure or support the service, subject to access restrictions and confidentiality obligations. Sharing or emailing a report gives its recipients a separate copy outside the app's access controls.
We do not sell personal information. We do not use product analytics to evaluate individual crew performance or provide employers with individual productivity scores. Operational records may still identify who submitted information and may be visible to authorised colleagues.
6. Providers and other recipients
The services below receive information for the stated purposes where the relevant feature is used. A service can act on our behalf for one purpose and under its own responsibility for another. The Data Processing Agreement covers the processing performed on a customer's behalf. Provider terms do not replace our responsibilities to you.
| Service | Purpose and information involved |
|---|---|
| Supabase | Authentication, database and file storage, including accounts and saved vessel records. Infrastructure includes AWS. |
| Tinfoil, Inc. (United States) | Private AI inference on sealed, attested confidential-computing servers, for eligible or specifically enabled vessels and Helmwise's private test vessel; submitted AI content and service usage metadata. |
| OpenAI (United States) | Standard text, image and voice transcription, in the app and on WhatsApp; the content needed for those requests. OpenAI keeps text and image requests and replies for up to 30 days for abuse monitoring (longer only where the law requires it or to protect the service or others from harm), and does not keep voice recordings sent for transcription. |
| Resend | Account messages, invitations, support-related messages, requested report delivery and product updates to our own users; addresses and message content. Resend states that it stores customer data in the United States. |
| Twilio and the WhatsApp Business Platform operated by Meta/WhatsApp | Optional WhatsApp message transport; messages, media, phone numbers and delivery information. WhatsApp also has its own relationship with its users. Twilio keeps messages and media for 7 days, and deleted text can stay in its backups for up to 30 more days (section 9). |
| Vercel | Website hosting, request handling and performance measurement; network information and data processed through hosted services. Our website servers run in the EU (Dublin, Ireland); content delivery and other Vercel services may involve other locations. |
| PostHog | Optional product analytics through PostHog's United States service. The website and the updated phone app start it only after you say yes; statistics from older phone versions are discarded from 23 November 2026 (section 10): an account-linked identifier, the actions taken in the app, approximate country and region worked out from the internet address (which is then discarded), and app, device and browser details. Session replay, automatic click capture and in-app surveys are disabled. Our servers also send PostHog technical counts and timings that are not linked to a person and do not depend on your choice. We have turned off PostHog's use of our analytics to train its own AI models. PostHog's separate AI analysis features remain enabled; when we use them, analytics data, including identifiers, can be processed by PostHog's AI providers. This is separate from the AI processing of vessel content in section 4. PostHog is certified under the EU-US Data Privacy Framework. |
| Sentry | Error and performance diagnostics for the website, the phone app and our servers; technical events and potentially contextual information associated with an error. Website error reports go to Sentry's United States service. |
| Airtable (Formagrid Inc., United States) | Administration of access arrangements; relevant names, email addresses and access-code information. Airtable's Data Processing Addendum provides EU and UK Standard Contractual Clauses. |
| Open-Meteo | Weather and location lookup features; requested locations and associated network request information. |
| Paddle and any app store used for purchase | Payment, tax, fraud prevention and purchase administration; purchase information. Their own terms and privacy notices apply to their independent activities. |
We may also disclose information to recipients you or your organisation select, professional advisers under confidentiality duties, or authorities where disclosure has a valid legal basis. Any business transfer involving personal information must preserve applicable protections and notice obligations.
Supplier privacy information: https://tinfoil.sh/privacy ; https://developers.openai.com/api/docs/guides/your-data ; https://supabase.com/privacy ; https://www.twilio.com/en-us/legal/privacy ; https://www.whatsapp.com/legal/privacy-policy . Contact hello@thehandover.app for the processing details relevant to your vessel.
7. Countries and international transfers
Helmwise operates from South Africa. Our main database and our website servers are in the EU (Ireland). Suppliers also process information internationally, including in the United States, where our AI, analytics, error-reporting and email providers are based. A database location does not establish where every supplier, support operation or AI request processes information. Private AI does not mean local-only or South Africa-only processing. Tinfoil, Inc. processes in the United States and in other locations named in its agreement with us.
Crew records that boats keep in Handover reach Helmwise in South Africa under the EU Standard Contractual Clauses and, for UK information, the UK Addendum. Both are built into our Data Processing Agreement with each boat. When you give us your own details, for example for your account or billing, and the GDPR applies to that processing, it applies to us directly. Our suppliers outside Europe are covered by the EU-US Data Privacy Framework or Standard Contractual Clauses; the Data Processing Agreement, Schedule 3, lists those that handle boat records, and section 6 lists the rest. We also meet South Africa's own transfer rules. Accepting this notice is not a substitute for those safeguards.
Contact hello@thehandover.app for the countries and safeguards applicable to your information and a copy of relevant safeguards, with legally permitted redactions to protect confidential information.
8. Storage, audio and deletion
Saved vessel records, transcripts, reports and photo attachments are retained while needed for the customer's use of Handover and handled on the customer's authorised instructions. Archiving a record does not delete it. Closing one crew member's account does not automatically delete the organisation's shared records or another person's information.
When you save items captured through the Handover web app, Handover keeps the saved details and information about their source. This can include a short excerpt, the file name, and an email's sender, subject and date. When a saved item came from a PDF or Word document attached to an email, its source also keeps that email's sender, subject and date. We also keep an identifier used to recognise an email you have already added. These details follow the retention and deletion rules for saved vessel records.
The Handover web app does not save the original dropped email file, CSV file or extraction-only picture as an attachment. A dropped PDF or Word document is different, including one read out of an email's own attachments: when you save a suggested new item from Drop that supports document attachments, Handover attaches a copy of the whole original document. That copy can contain information beyond the extracted item. Credential entries do not receive document attachments. Adding details or a note to an existing Library entry does not attach the original document. Handover tells you if a document could not be attached. Photos you deliberately attach elsewhere remain with their records.
After a valid account-deletion request, we delete the account information from active systems within 30 days, subject to applicable legal retention requirements. Customer-requested deletion of vessel records follows the Data Processing Agreement. We verify authority and explain any relevant restriction; we do not use account closure to override another person's rights.
Handover does not keep raw voice recordings as a saved note, attachment or audio archive. The phone app may retain a pending recording on the device while offline or after an unsuccessful upload, until the workflow completes or the recording is discarded. The saved transcript remains. This statement does not describe copies held by a messaging or transcription provider.
Images used solely for contact or library extraction are not retained by Handover as standalone import images after processing. Images deliberately saved as attachments, including WhatsApp capture photos, are different: they remain with their records. Removing a photo or permanently deleting a capture removes normal product access; storage cleanup must also deal with unreferenced files, shared references and any older files requiring review.
Our database provider takes a backup every day and keeps each backup for 7 days, in Ireland. Backups are held separately from normal use and are deleted when the 7 days end. Information we have deleted from our live system can therefore remain in a backup for up to 7 more days. If a backup is restored, valid deletion instructions are applied again.
Error reports are kept for up to 90 days.
We request deletion of detailed product-analytics records when you delete your account, or after your account or device has not been used for 12 months. PostHog advises allowing about two weeks to remove the records, followed by about two more weeks for its backup copies to expire. Individual requests can require earlier deletion.
Analytics recorded on the website before 9 October 2026 can include internet addresses, a more detailed estimated location, and details we no longer collect: boat names, the file names of imported photos, error message text, note identifiers, exact due dates, and the text of buttons and links clicked. You can ask us about this information, or ask us to delete it, at hello@thehandover.app.
Other security and diagnostic records are retained for the period needed to detect and investigate incidents; support records while the request and any associated dispute remain relevant; and billing records for applicable accounting, tax and claims requirements. We must limit each category to what is needed for its purpose and review it for deletion. Contact us for the applicable schedule or progress of a deletion request.
Suppliers keep some copies for set periods. OpenAI keeps text and image requests and replies for up to 30 days for abuse monitoring (longer only where the law requires it or to protect the service or others from harm), and does not keep voice recordings sent for transcription. Tinfoil keeps no prompts or replies, apart from the prompt cache described in section 4. Twilio keeps WhatsApp messages and media for 7 days. Deleted message text can stay in Twilio's backups for up to 30 more days. Deleting a Handover note does not erase a copy already delivered to another person, or one a supplier is still holding within those periods.
9. WhatsApp Capture
WhatsApp Capture operates for connected numbers and eligible access. Messages pass through WhatsApp/Meta and Twilio before Handover receives them. Private AI starts at the later inference step; it does not extend to that message transport. The app provides an alternative capture route that does not pass through WhatsApp and Twilio.
What Handover keeps. For each message, Handover keeps a message record in its database. The record holds the original text (or the caption of a photo), the sender's phone number and the link to any photo or voice file. It also holds the time, the outcome and the identifiers that tie the message to a vessel and a crew member. The note saved from the message is separate. It stays with the vessel's records (section 8). Handover does not keep the voice file (section 8).
What the clean-up clears, and when. The clean-up covers every WhatsApp message. Messages that arrived before it was switched on were cleared in one go when it started. For each message:
- Once Handover has replied, it clears the text, the media link and all but the last two digits of the number from the record. This happens when the message has been saved, answered or skipped, or after the third failed retry.
- An hourly clean-up clears anything still uncleared after 24 hours.
- What remains holds no message content: a reference number, the outcome, times, the identifiers for the vessel and crew member, and the last two digits of the number. It is deleted 30 days after the message arrived.
- When a sole owner deletes a vessel workspace, these records are deleted with it.
The clean-up does not touch the saved note, the record of the phone you connected, or database backups. The connection record keeps the full number until your account or the boat's workspace is deleted. The log of connecting and disconnecting keeps it until the boat's workspace is deleted, or until you ask us to delete it. Backups follow the 7-day cycle in section 8.
Twilio and WhatsApp. Twilio keeps its copy of each message and its photo or voice file for 7 days. Deleted message text can stay in Twilio's backups for up to 30 more days. Disconnecting a number stops further capture from it. It does not delete earlier notes. Copies held by WhatsApp/Meta, copies on your own device and messages already delivered to other people are outside Handover's deletion controls.
10. Cookies, analytics and diagnostics
Needed to run Handover. Authentication cookies and similar storage maintain sign-in and other necessary service functions. Error reports (Sentry) help us find and fix faults and keep the service secure. There is no switch for these in the app, because we cannot keep Handover working and safe without them. You can still object to error reporting by emailing hello@thehandover.app; we will stop unless we have a strong reason to continue, and we will explain that reason.
Help improve Handover (your choice). On the website and the updated phone app, optional product analytics (PostHog) is off until you say yes when Handover asks you to help improve it. Until you say yes, no product-analytics identifier is stored on your device. If you say yes, we see which features are used, whether actions succeed or fail and how long they take, the app version and device type, and the approximate country and region your connection comes from. Signed-in activity is linked to a pseudonymous account identifier, not your name or email address. You can change your answer at any time in Settings, under Privacy. Handover works the same either way. The website asks before analytics starts. The phone app asks from its next version. An older phone app sends usage statistics without asking, linked to the pseudonymous account identifier; from 23 November 2026 we discard them when they arrive.
What analytics does not include. Analytics accepts only approved fields and values. It does not include your notes, transcripts, photos, files or their names, names, email addresses or boat names. This applies to the website and to the phone app from version 1.1.5. Page addresses are reduced to the app's own page names, and where you came from is not recorded. We do not use analytics to follow where individual crew members are. Records linked to an account can be traced back to that account, so we treat them as personal information.
Counts from our own systems. Our servers also send PostHog simple counts and timings, such as how long a voice-note transcription took. They are sent from our servers, store nothing on your device, and are not linked to your name, email address or account. They do not depend on your analytics choice.
Handover does not record session replay of your screen interactions and does not show in-app surveys. Optional analytics, and the device storage it needs, start only after you say yes. A privacy notice or continued use of the service is not that consent. You may contact us to object to processing based on legitimate interests and to ask about the analytics information linked to your account. Browser controls can restrict storage, although blocking essential storage can prevent sign-in.
11. Security and incidents
We use access controls, vessel-scoped database policies and encrypted network connections to protect information. These measures reduce risk; they do not make every system or recipient inaccessible to authorised operators, or guarantee absolute security.
We will notify affected customers of personal-data breaches as required by our Data Processing Agreement and applicable law, and notify individuals or regulators where required. We do not require you to waive your legal rights because internet services involve security risks.
12. Children and sensitive information
Handover accounts are for adults aged 18 or over. Vessel records can incidentally contain health information or other specially protected information, and information about children. Handover is for vessel operations and handover records, not healthcare, diagnosis, treatment or deliberate health-data processing. The responsible organisation must have a lawful basis, meet any additional conditions and provide the relevant notices before submitting information about others. Submit only what is necessary. Helmwise providing the service does not supply those conditions or remove its own legal obligations. Do not upload identity documents, medical histories or credentials merely because the service can accept them.
13. Your rights and complaints
Depending on the applicable law, you may request access, correction, deletion, restriction or portability; object to relevant processing; withdraw consent; and complain to a regulator. These rights have legal conditions and exceptions. We will respond within the applicable legal deadline and explain any permitted extension or refusal. We may need proportionate information to verify identity or authority.
For vessel records, we normally assist or refer the request to the responsible organisation. We will not require you to obtain its permission before exercising rights against Helmwise for processing under our own control. Contact Charl Dettmer at hello@thehandover.app.
Handover update emails. You can object to Handover update emails at any time, without giving a reason. Use the unsubscribe link in any update (one click, no sign-in), turn off "Handover updates" in Settings, or reply "stop". We stop. This does not affect password, account, billing or legal notices.
Handover's AI suggestions are for human review. They are not used by Helmwise to make solely automated decisions with legal or similarly significant effects about people.
You can complain to the South African Information Regulator at https://inforegulator.org.za/ or, where applicable, your local data protection authority. UK residents can contact https://ico.org.uk/ . You do not have to complain to us first.
14. Changes
We will keep this notice current and explain material changes through appropriate communications. Where a change needs consent, customer authorisation or advance notice, updating this page alone does not provide it. The Terms and Data Processing Agreement explain contractual notices and objections.