Privacy at RigMinds

Job browsing is public. You can read the verified feed and every individual job page without signing in and without creating any account record.

When you sign in with Google, RigMinds stores:

• Your email address and authentication ID, held by the authentication system so your account works. RigMinds does not receive your Google password.
• Your worker profile if you create one: name you type, roles, years of experience, country, work authorisation, rotation preferences, camp preference, target rate, availability and any credentials you add.
• The job IDs you save.
• Application records you create yourself: job title, employer, location, status, dates and your own notes.

This data exists so your matches, saves and application tracking follow you across devices. It is not sold and is not sent to employers.

If you choose to import a PDF or Word résumé, the file is read inside your browser to suggest worker-profile fields. You see the suggested details before anything is saved. RigMinds does not upload or store the original résumé file.

Only the profile details you approve are saved to your account. Version 1 does not accept photographs or scanned pages.

RigMinds records first-party product events (for example: a page was viewed, a job page was opened, an employer link was clicked, a profile was completed) to understand whether the product works. Events carry a random session identifier, and your user ID when you are signed in.

Event properties are limited to a fixed allowlist: job ID, employer, country, source type, route, referring host, campaign parameters and a coarse match band. Email addresses, names, credentials, notes, employment history and any free-text you write are never sent to analytics. Résumé-import events may include only the file type and number of fields found—not the file name or its contents. There are no third-party advertising or tracking scripts.

From your account page you can view the email you signed in with, download a JSON export of your profile, saved jobs and application records, and delete that RigMinds data. Deletion removes those rows permanently and cannot be undone.

Analytics events are aggregated operational records and are not part of the personal export; they are not readable by accounts and are handled separately as described above.

Profile, saved jobs and application records are kept until you delete them. Job postings in the public feed are kept while they remain active and verified.

Personal tables use row-level security in the hosted database: every read and write is checked against your authenticated user ID, so one account cannot reach another account's rows. Public job data is read-only for everyone. Analytics events can be written by the app but cannot be read back by browsers.

RigMinds links you to the employer's own careers site. When you follow that link, the employer's website and privacy practices apply. RigMinds does not submit applications for you and does not pass your profile to employers.

This is version 1 of the RigMinds privacy disclosure and will be updated as the product grows. See also the terms of use.