Privacy policy
Last updated 31 Oct 2026
In short:
- If you are a seafarer, your agency decides what is kept about you and why. CrewBerth stores it for them. Ask your agency first; we will help them answer.
- Crew data is stored in India. It is never sold, never used for marketing or to train AI models, and never shown to another agency.
- Three jobs pass through providers outside India: email, WhatsApp reminders, and reading a scan. Section 7 lists them.
- An agency can delete a seafarer at any time, and their certificate scans go with them.
- Questions or complaints: email hello@crewberth.com or WhatsApp +91 77108 93634.
1. Who we are
This policy explains how Rajkumar Tamilselvan, trading as Revoric Labs (GSTIN 32AXJPT8222B1ZN), 3rd Floor, Jos Annex, MG Road, Kochi, Kerala 682016, which runs CrewBerth (“we”, “us”) handles personal data in CrewBerth, the crew compliance software at crewberth.com. It is written for India’s Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and the rules made under it.
To reach us about anything in this policy, email hello@crewberth.com or WhatsApp +91 77108 93634.
2. Two roles: processor and fiduciary
CrewBerth holds two kinds of personal data, and our role is different for each.
- Crew data. A manning agency puts in details of its seafarers: who they are, their certificates and scans, and their sea service. For this data the agency is the Data Fiduciary: it decides what to collect and why, gives each seafarer its own privacy notice, and records their consent. We are its Data Processor: we hold and process the data only to provide CrewBerth to that agency, on its instructions and under our Terms of Service. The agency’s notice, not this policy, is what tells a seafarer how their data is used.
- Our own customers’ details. For the people who hold a CrewBerth login at an agency, people who write to us, and visitors to this website, we are the Data Fiduciary, and this policy is our notice to you.
3. Crew data we process for agencies
What is held
- Identity and contact: full name, INDOS number, CDC number, rank, date of birth, phone number, email address, and any notes the agency’s staff add.
- Certificates: the type (CoC, CoP, STCW courses, medical fitness certificate, passport and others), grade, number, dates of issue and expiry, issuing authority, and a scanned copy where the agency adds one. A medical fitness certificate can reveal health information, and a passport scan carries its photograph and details.
- Sea service: sign-on and sign-off dates, vessel, flag, rank, and whether the seafarer sailed as a trainee.
- Availability: when the seafarer is next available, and a short note.
- Consent: when and how the seafarer agreed to the agency’s notice, which version of the notice, and any withdrawal.
- Reminders and uploads: which certificate reminders were sent and whether sending worked (the phone number itself is not copied into this record), the upload links made for the seafarer, and the scans they send in through them.
- Placement and billing records: the principals and vessels the agency crews for, its vacancies, and the manning-fee invoices it issues to principals, which can list the seafarers placed.
Where it comes from
The agency’s staff type it in or import the agency’s own spreadsheet. A seafarer can also send a renewed certificate through an upload link their agency sends them; it waits for the agency’s staff to check it before it becomes part of the record. If an agency asks us to set CrewBerth up from its existing sheet, we load the sheet for the agency and then delete the copy it sent us.
What it is used for
Only to provide CrewBerth to the agency that entered it: showing it to that agency’s staff, working out renewal dates, voyage checks and Seafarers’ Welfare Fund contributions, sending the morning renewals email to its staff, sending WhatsApp reminders to its seafarers if the agency has turned them on, reading a scan into a form when its staff ask, and producing its reports and invoices.
We look at an agency’s crew data only to set CrewBerth up for it, to answer its support requests, or to keep the service running and secure, and then no more than the task needs.
We do not sell crew data, use it for marketing, or use it to train AI models. We do not show one agency’s data to another agency or to anyone else, except the providers in section 7 as their job requires, or where Indian law obliges us to (for example, a lawful order of a court or authority). If that happens we tell the agency, unless the law forbids it.
4. Your details, when you use CrewBerth or contact us
For the data in this section we are the Data Fiduciary.
Agency staff with a login
- Your name, email address, the agency you belong to, and your role there (owner, admin or staff).
- Your password, which our sign-in provider stores only as a one-way hash. We never see it.
- Settings you choose, such as whether you get the morning renewals email, and which renewal alerts you have already seen.
- Which sections of CrewBerth you open each day, such as Seafarers or SWFS: one record per section per day, with no IP address, device or page content.
- When you sign in, and the technical records our providers keep to run and protect the service: IP address, browser type, and the pages requested.
Your login is created by us or by your agency’s owner or admin, who give us your name and email address. We use these details to let you in, to send the emails the service needs (invitations, password resets, and the morning renewals email, which you can switch off under Account), to support you, to see whether CrewBerth is being used and where to help, and to keep CrewBerth secure.
People who contact us
If you write to us by email or WhatsApp, we use your name, contact details and what you write to reply, to arrange a demo or a setup, and to follow up on that conversation.
Billing
For an agency that pays for CrewBerth: its name, address and GSTIN, and the name and contact details of the person who handles payment, to invoice it and to keep the tax records the law requires.
Website visitors and the demo
crewberth.com has no analytics, advertising or tracking. Our hosting provider keeps technical logs of requests (IP address, browser, page) to run and secure the site. The demo at crewberth.com/demo opens a shared sample agency whose seafarers are made up; it asks nothing about you, and nothing can be saved in it.
6. Where the data is stored
CrewBerth’s database and certificate scans are stored in India, in our database provider’s Mumbai region, and the application runs on servers in Mumbai. Our backup copies are kept on an encrypted computer in India (section 8).
Three jobs pass the data they need through providers whose servers may be outside India: sending email, sending WhatsApp reminders, and reading a scan. Section 7 says exactly what each one receives. The DPDP Act allows personal data to be processed outside India unless the Central Government restricts transfers to a country; we will stop using any provider in a country it restricts.
7. Who else handles it
We use these providers to run CrewBerth. Each receives only what its job needs and handles it under its own terms with us, which require it to keep the data secure and to use it only to provide its service.
Supabase
Database, certificate scan storage and sign-in.
What it receives: everything in CrewBerth: crew records, certificates and their scans, staff logins.
Where: India (Mumbai, on Amazon Web Services).
Vercel
Runs the CrewBerth website and its scheduled jobs.
What it receives: pages and data as they pass between your browser and the database; technical request logs.
Where: India (Mumbai) for the app; Vercel’s global network delivers pages.
Resend
Sends CrewBerth’s emails: the morning renewals email, team invitations and password resets.
What it receives: staff names and email addresses; in the renewals email, seafarers’ names and ranks, their certificates and expiry dates, and the vessel they are on.
Where: United States.
Meta (WhatsApp Business Platform)
Sends certificate reminders to seafarers from the agency’s own WhatsApp number, only if the agency turns reminders on.
What it receives: the seafarer’s phone number and name, the agency’s name, the certificate and its expiry date, and a link to send in a renewed copy.
Where: Meta’s data centres, outside India.
Google (Gemini API)
Reads a certificate scan into the certificate form, only when a staff member asks it to.
What it receives: the scan or photo of that one certificate.
Where: Google’s data centres, which may be outside India.
Before a new provider receives crew data, we email every agency’s owner at least 30 days ahead, so an agency that objects can leave first.
8. How long it is kept
- Crew data: for as long as the agency keeps it in CrewBerth; the agency decides. Its staff can delete a seafarer at any time, which deletes their record, certificates and certificate scans, sign-ons, consent record, upload links and reminder history. Invoices already issued keep the names printed on them, because an invoice has to stay as it was issued.
- Upload links stop working after 30 days or 5 uploads, whichever comes first, or as soon as the agency revokes them. A scan the agency turns down is deleted at once.
- When an agency leaves CrewBerth: we keep its data for 30 days so it can ask for a copy, then delete it from the database, file storage and our backups.
- Backups: we keep a nightly backup copy of agency data, including certificate scans, on an encrypted computer in India, in a folder no other user of that computer can open. Each nightly copy is kept for 30 days, and a scan deleted in CrewBerth is removed from the backup 30 days later, so deleted data leaves our backups within 30 days. We use a backup only to recover the service.
- Staff logins: while you have one. If your agency removes you, your access ends at once; the login itself (your name and email address) and its record of sections opened stay so the agency can add you back, and we delete them when you ask or when the agency leaves CrewBerth.
- Messages from people who contacted us and did not become customers: up to two years after our last exchange.
- Billing and tax records: as long as Indian tax law requires, currently up to eight years.
- Technical logs: for our providers’ standard periods.
9. How it is protected
- Each agency’s data is kept apart inside the database: every record belongs to one agency, and the database itself refuses to show it to anyone outside that agency (row-level security). Automated checks try to cross that line, and are run against the live database whenever the access rules change.
- Certificate scans are kept in private storage and opened only through links that expire within an hour.
- Data is encrypted in transit (HTTPS) and at rest by our database provider.
- An upload link is a long random code, and we store only a scrambled (hashed) copy of it. It shows only the agency’s name, the seafarer’s first name and the certificate asked for, never what is on file.
- The demo holds only made-up seafarers, and the database refuses any change made from it.
- Administrative access to CrewBerth’s systems is limited to the people who run it, and used only for the purposes in this policy.
No system is perfectly secure. If we learn of a personal data breach affecting crew data, we tell the affected agency without undue delay, with what we know and what we are doing about it, so that it can inform the Data Protection Board of India and the people affected, as the DPDP Act requires of it. If a breach affects our own customers’ details, we inform the Board and you ourselves.
10. Your rights
If we are the Data Fiduciary for your details (you hold a login, you wrote to us, or you visited this site), you can:
- ask for a summary of the personal data we hold about you and what we do with it;
- ask us to correct, complete, update or erase it;
- withdraw any consent you have given, as easily as you gave it;
- nominate someone to exercise these rights for you if you die or become unable to;
- raise a grievance with us, and then with the Data Protection Board of India.
To do any of these, email hello@crewberth.com or WhatsApp +91 77108 93634. We answer within 30 days, and may first need to confirm who you are. Erasing your details does not remove what the law requires us to keep, such as tax records.
If you are a seafarer, your agency is the Data Fiduciary for your crew record. Send your request to the contact named on its privacy notice. If you write to us instead, we pass your request to your agency and help it answer; we do not change an agency’s records without its instructions.
11. Children
CrewBerth is software for businesses and is not meant for anyone under 18. An agency that enters the details of a trainee under 18 must first have the verifiable consent of their parent or lawful guardian, as the DPDP Act requires (see our Terms of Service).
12. Grievance officer and complaints
For a question or complaint about personal data in CrewBerth, email hello@crewberth.com or WhatsApp +91 77108 93634. We resolve grievances within 30 days.
If you are not satisfied with our answer, you can complain to the Data Protection Board of India. If your concern is about your crew record, raise it with your agency first.
13. Changes to this policy
We post any change here with a new date. If a change affects crew data or takes away a right this policy gives you, we email every agency’s owner at least 30 days before it takes effect.