Privacy
What we hold about you, why, who else ever sees any of it, and how to have it removed. Written to be true rather than to be long.
Last updated 6 October 2026.
Who is responsible
CENTRAFOX CONSULTING LLC, 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, United States, provides CREWWIZE and is responsible for the personal data held by the service at cloud.crewwize.com. Write to service@crewwize.com about anything on this page.
For anything about your data, write to service@crewwize.com. We have not appointed a data protection officer, because the law does not require one of us.
Because CENTRAFOX CONSULTING LLC is not established in the European Union, it has appointed a representative under Article 27 GDPR: Martin Högl, Franklinstr. 14, 10587 Berlin, Germany, service@crewwize.com. You may contact the representative instead of, or as well as, us.
We decide ourselves why and how this data is used, so we are its controller — not a processor acting for a vessel's owner. The one exception is a draft: a name an officer puts on a crew list before asking the person, for which that officer and we are joint controllers.
A vessel's appliance is a different matter: it is the owner's machine, aboard their boat, and what it holds — the logbook, the crew list of that boat — is held by the owner and never by us.
What we hold, and why
- Your account — name, email address, and your passkey's public key or a hashed password. To let you sign in and to write to you about your account — to provide the service you asked for (Art. 6(1)(b) GDPR).
- Your crew profile — what you choose to enter about your sailing. To show it to the people you sail with (Art. 6(1)(b)).
- For finding crew — the skills you rate, the certificates you enter, when you are free, what you are looking for and your life-aboard wishes, all optional. The officers of vessels and voyages you share, and of a voyage you asked to join, may see them on that voyage's list of possible crew; you can limit that to the vessels you are standing crew of. If you join the crew listing — off until you agree to its sentence, which we keep with its date — the officers of a voyage published as seeking crew may see the same answers on its list, but only for a leg you said you are free for and only when you accept its cost arrangement; leaving deletes the agreement. A voyage's officers may pin you to its short list, which holds the pin and, at most, the date they noted contacting you — nothing else, never a note — and which is deleted when the vessel opens the voyage. You are not told when you are on a list; ask us and we will tell you which short lists hold you. Basis: providing the service you asked for (Art. 6(1)(b)); for the crew listing, your consent (Art. 6(1)(a)).
- Emergency information — an emergency contact and notes for a first responder, both optional, held only with your recorded consent and deleted when you withdraw it. Readable by the officers of a vessel you are sailing on, while that voyage is planned or running. We do not ask for medical data.
- Vessels, voyages and memberships — which boats you own or sail, in what role, and on which voyages. That is what the service is (Art. 6(1)(b)).
- Moments and pictures copied ashore from a voyage under that voyage's consent, and chat messages with the pictures, PDFs, videos and voice messages sent in them. Chat is not end-to-end encrypted: the service can read what it stores, and says so. A picture sent from the chat page is redrawn by your browser first, so its location never reaches us. Basis: providing the service (Art. 6(1)(b)).
- Purchases — which plan you hold and until when. Card details never reach us; Stripe holds them. Basis: the contract (Art. 6(1)(b)) and tax law (Art. 6(1)(c)).
- Technical records — sign-in times and the address a request came from, kept for security for 30 days — our legitimate interest in keeping the service secure (Art. 6(1)(f)).
We hold no analytics, no advertising identifiers and no location history. A vessel's position is shared with her community only if her owner switches that on, and only the latest one is kept.
Only your name and email address are needed for an account; everything else is optional.
Your pitch
A short text you write about how you can contribute to a crew — at most 600 characters, one general version and, if you like, one for a particular vessel or voyage. It is shown as plain text to the officers who already see your matching answers, and to nobody else. No program reads it to score or rank you. It never goes to a vessel and is never written into a logbook. We hold it because you asked us to (Art. 6(1)(b) GDPR), until you delete it, the vessel or voyage it was written for is deleted, or your account is.
Names an officer puts on a crew list (drafts)
The owner, captain, chief boat officer or mate of a vessel may put a person on her crew list before asking them. We call this a draft. It holds the person's first and family name, optionally an email address and a mobile number, and the role the officer has in mind. The person has not been contacted and has agreed to nothing.
- Who sees it: the vessel's officers. The name and the word draft also reach the vessel's own crew list aboard. The email address and the mobile number never leave our server.
- Who is responsible: the officer who entered it and we, as joint controllers (Art. 26 GDPR). The basis is the officers' legitimate interest in planning who will sail (Art. 6(1)(f)).
- Our arrangement: the officer decides whom to enter; we run the service, keep the address and number on our server, and answer every request about a draft. You may use your rights against either of us.
- Telling the person: a draft causes nothing to be sent. We do not write to somebody who has agreed to nothing (Art. 14(5)(b)); the person is told when an officer invites them — the invitation names the vessel and the person who invited them, and links to this page.
- How long: until an officer deletes it, or the person accepts an invitation made from it — then it becomes their own account and the mobile number the officer typed is deleted. A draft nobody has changed or invited for twelve months is deleted automatically, and the officer who entered it is told.
- If you are on a list as a draft and want to be removed, write to service@crewwize.com: we tell you which vessel holds you and delete the draft.
Your emergency page and first-responder links
On Emergency you may keep one or more emergency contacts — a name and a telephone number, and optionally an email address — and a note for a first responder in your own words. Both are optional. We ask for no medical data, but if you mention a health fact in your note, that is health information, which the law treats as a special category of data.
Nothing here exists until you tick: I consent to CREWWIZE storing my emergency contacts and my note for first responders, which may include information about my health, and showing them to the officers of the voyages I am on and to first responders I or they share a link with. I can withdraw this consent at any time on this page, which deletes the record. We keep that sentence and the date. The basis is your explicit consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR). Withdrawing deletes the note and the contacts and closes every open link at once; aboard they go at each vessel's next connection. Withdrawing does not make what happened before unlawful (Art. 7(3)).
- Who can read it: you; the skipper and mate of a voyage you are enrolled on and the vessel's captain, chief boat officer and mate, while that voyage is planned or under way — a vessel's owner who holds no role aboard cannot; the vessel itself, for the current or next voyage, so it can be read at sea, released aboard when the voyage closes; and a first responder you or those officers name.
- On officers' phones: the skipper's and mates' phones keep a dated copy taken from the vessel, so it can be read in a power outage. It is dropped when the voyage closes, when the phone is released or signs out, and at checkout; a phone that never reconnects keeps it until then.
- First-responder links: one link per named responder, read-only, lasting 24 hours by our server's clock and revocable earlier; stored on our side only as a cryptographic hash; at most ten a day per person making them. Anybody holding the link can read the record until it expires or is revoked, including somebody it was forwarded to. The record appears only when the responder presses Open the record; that opening is recorded with the responder's name and organisation as the person who made the link typed them, and our server's time.
- When a link is first opened: you are told in the app and by email, and each emergency contact with an email address receives one plain message saying your record was opened — with nothing from your record and no link to it. We send no text messages.
- The record of openings is kept 12 months from each opening, also after you withdraw consent, so that we can show who opened the record and when (Art. 6(1)(f) and Art. 5(2) GDPR).
If somebody named you as their emergency contact, we hold your name and telephone number, and your email address if they gave it. We use it only to show to the people who may read their record, and — your email address only — to send you one message the first time a first responder opens it. We never write to you otherwise and never share your details, and we delete them when the person removes you, withdraws consent or deletes their account. Basis: the consent of the person who named you, and the legitimate interest in reaching you in an emergency (Art. 6(1)(f)). Ask us what we hold, or object, at service@crewwize.com.
Where a vessel last said she was, and her timeline
- Her last position: if a vessel's own navigation instruments report a position, her appliance sends us the most recent one when it connects. We keep one, replace it each time, and show it with the time we received it. A phone's position is never sent. Her owner and her crew list see it; followers only if her owner switches that on, which is off by default. It is not AIS and not live tracking, and we never show who is aboard beside it. Basis: the contract for the crew (Art. 6(1)(b)), the owner's legitimate interest for followers (Art. 6(1)(f)).
- Following a vessel: we keep that you follow her. Her owner sees how many followers she has, never who.
- Posts: a vessel's owner and captain may post text and one picture, signed with their name and role at the time. A picture's location data is removed before it is stored. The author can edit or delete a post; the owner can delete any post on her timeline.
- Moments: pictures from a voyage that its crew already copied ashore are shown to that vessel's crew; followers see them only if the voyage's officers switch that on. Anybody aboard may ask that a picture is not copied ashore at all.
- Her story: lines measured by CREWWIZE and lines that are the owner's claim, each labelled; people are counted, never named.
A copy of your data, and deleting your account
A copy. On Account settings you can download what we hold about you as one zip file, with your own pictures. Of other people it contains names only. You confirm it is you with your password or a sign-in in the last ten minutes; once an hour at most. Not in it: logbook entries (the vessel's record, readable on her pages), the text of chat messages (readable in the chat), card details (we never hold them), and an officer's short list or another person's watch wish about you, which are their notes (Art. 15(4) GDPR). The file is in a structured, machine-readable format, so you can take it elsewhere (Art. 20).
Deleting your account. On Account settings, after a page that says exactly what goes and what stays. What goes: the account and every credential and session; your profile, matching answers, pitch and photograph; your emergency record with its contacts, links and openings; your documents; drafts you created and invitations you sent; your place on every crew list and every voyage still being planned; your posts, story lines, pictures copied ashore with you as author, and follows; your chat account. A CREW PRO subscription stops renewing.
- What stays: every logbook entry written under your name, because a signed log that could be edited would be evidence of nothing; what you wrote in chat, which is the other people's correspondence too; a picture somebody else took; voyages a vessel already opened or closed; Stripe's invoices; and, where somebody else's record points at you, a row shown as Former member with no address and no credential.
- Proof of consent: for three years after the deletion we keep which documents you agreed to, their versions and when — filed under a one-way code of your former account number, with no name and no address (Art. 7(1) GDPR).
- Backups: a deleted item stays in an encrypted backup until that backup is removed — at most about 13 months (see below).
- When we must refuse: if you own a vessel that still has other people on her crew list, the page tells you what to do first.
How long we keep what
- Account, profile, matching answers, pitch, photograph, documents, emergency record: until you delete them or the account. Availability windows expire on their own end date.
- Officer's short list naming you: deleted when the vessel opens that voyage.
- Draft on a crew list: at most 12 months after it was last changed or invited.
- Invitation: until accepted, declined, withdrawn or expired — 14 days.
- First-responder link: 24 hours. Record of its openings: 12 months.
- Vessel's last position: one, replaced on each report. Voyage track copied ashore and mirrored logbook entries: as long as the vessel's account exists.
- Posts, story lines, pictures copied ashore: until their author or the vessel's owner removes them, or the account is deleted.
- Chat messages and attachments: as long as the conversation exists. Chat send counter: 8 weeks.
- Mail delivery records (that a message left, or was refused, never its content): 12 months. Address look-ups when inviting (who looked and when, never the address): 30 days.
- Security logs with sign-in times and request addresses: 30 days. Cloudflare keeps its own under its terms.
- Proof of consent after deletion: 3 years.
- Purchases and plan: while the account exists; Stripe keeps invoices under tax law.
- Backups: encrypted with a key that is not on the server. Database: seven nightly copies on the server, and up to twelve monthly copies kept offline for restore drills. Pictures and chat attachments: a full copy once a year plus the changes since, older ones deleted once the new full copy is checked — so a deleted item is gone from every backup within about 13 months.
Who else ever sees any of it
- OVH hosts the server. The data on it is on an encrypted volume whose passphrase is not on the machine.
- Cloudflare carries the web traffic to the server.
- Stripe takes payments and holds the card details, and may act as the seller of record for a purchase.
- Link (Stripe), as seller of record of CREW PRO and VOYAGE, receives your name, email address and country for the purchase.
- The emergency contacts and first responders you or your officers choose, as described above.
- Outside the European Union: we are a US company and our server is in the United States. Data you give us directly needs no transfer mechanism. Where a service provider above receives personal data, we rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses.
- Nobody else. Mail is sent by our own server with no relay. We sell nothing to anybody, and there is no data broker, advertising network or third-party script anywhere in the service.
Your rights
Write to service@crewwize.com. If you are in the European Union or the United Kingdom, the GDPR gives you these rights:
- Access to what we hold about you (Art. 15), its correction (Art. 16) and its erasure (Art. 17).
- Restriction of what we do with it (Art. 18), and a portable copy (Art. 20).
- Objection to anything we do on the basis of legitimate interest (Art. 21).
- Withdrawing a consent at any time, for the future.
- A complaint to a data protection authority (Art. 77).
No decision about you is made automatically. Crew matching suggests and never decides; an officer chooses (Art. 22).
One thing cannot be deleted, and we would rather say so here than after you ask: a logbook entry you wrote aboard stays in that vessel's log, with the name it was written under. The log is a signed chain kept by the boat, and a record that could be edited afterwards would not be evidence of anything. Deleting your account removes the account; it does not rewrite a ship's history.
We keep your data while you have an account and delete it when you close it, except what is listed under how long we keep what.