NAVISTEER Privacy Policy
1. Who processes the data
Yannick JEAN-AIMÉE, a sole trader operating under the trade name OCEANS NEXUS, publishes NAVISTEER. He is the controller for processing needed for accounts, the display of profiles and postings, applications, messages, security and operation of the platform. His business address is Tiahura, PK 28.460, côté montagne, Haapiti-Moorea, 98729 Moorea Maiao, French Polynesia. For questions about data: admin@navisteer.app.
A recruiter who receives candidate data determines their own recruitment purposes and is responsible for its use, copies and retention outside NAVISTEER. Solely for operations entrusted by the recruiter and defined in a separate agreement meeting Article 28 of the GDPR, OCEANS NEXUS acts as a processor under the recruiter's documented instructions. OCEANS NEXUS remains the controller for the platform's own processing.
For GDPR questions in the European Union, the designated representative is Euverify Ltd (Ireland), Unit 3D North Point House, North Point Business Park, New Mallow Road, Cork, T23 AT2P, Ireland; gdpr@euverify.com. This representation does not replace OCEANS NEXUS as controller.
2. Data and their sources
We receive data you provide at registration, in your account or in your communications. For a candidate, these include identity and contact details, date of birth, nationalities and work rights, an optional photograph, the reference port, availability, structured professional history, languages, declared qualifications and certificates, applications and messages. The profile's only permanent location is a canonical port; temporary availability may specify another port until it expires. There is no continuous GPS tracking or disclosure of a residential address after unlocking.
For a recruiter, we process the identity and contact details of the account holder or representative, declared information about the organisation, postings, access requests, communications and service rights. Recruiter registration is declarative; it does not certify the person or company. We also process Contact form messages, information needed for authentication, access and security logs, IP addresses needed to prevent abuse, reports and moderation decisions. Data needed for an order and invoice are processed only when purchasing is actually open and a purchase is made.
The training pre-enrollment form collects your name, email address, phone number, optional message, selected training, language and request date. Authorised Navisteer staff use these data to handle your request. They may continue the exchange in a private support thread, without attachments. A pre-enrollment made without an account remains separate from any account using the same email address. A visitor receives a private link after a support reply: access is limited to that request and valid for at most seven days, never beyond the thread’s expiry. Emails announce a reply without copying the conversation text.
NAVISTEER does not request medical data. New uploads of CVs, qualifications or CFBS as permanent files are rejected. A recruiter CV may be generated on demand from authorised structured fields. Schools and courses are publicly browsable; at launch they have no independent account or access to CVs. There is no native mobile app, newsletter or active personalised job alerts at launch.
In each form, fields marked as required are necessary to create the account or carry out the requested action. Without them, that action cannot be completed. Other fields are optional; leaving them blank may limit profile display or certain applications according to criteria selected by a recruiter.
3. Purposes and legal grounds
| Purpose | Legal basis |
| --- | --- |
| Create and manage an account, provide requested functions, post a vacancy, search, apply, communicate and manage authorised access | Performance of the Terms of Use or steps requested before entering into them |
| Optionally prefill a qualification at the candidate's request | Performance of the requested service; manual entry remains available |
| Protect accounts, prevent abuse, investigate reports and ensure continuity | OCEANS NEXUS's legitimate interest in securing a connection service, subject to individuals' rights |
| Issue and retain invoices and supporting records when sales exist | Applicable legal obligations |
| Respond to rights requests and handle incidents | Applicable legal obligations and, for service management, legitimate interest |
Reading this policy and accepting the Terms of Use do not constitute general consent. No marketing consent is requested while those functions remain closed. If optional processing based on consent opens later, the choice will be separate and revocable.
4. Visibility, recipients and application checks
Public pages and the map do not reveal a candidate's contact details or full identity. Access to details requires a session according to role. An authenticated recruiter receives private fields needed for contact only with an active unlocking right and within server-enforced limits. The photograph retains its visibility rule. The PDF used for prefilling, any older CV files, medical data, passwords, sessions, payment information and internal moderation files are not given to the recruiter. Recipients of an application or message see the information needed for that communication. Authorised OCEANS NEXUS and DEVLAB personnel access data only for their duties.
For a posting, the recruiter selects the qualifications, certificates and years of experience required. The engine compares these requirements with declared structured data; a mismatch can block submission of an application for that posting. No professional criterion is imposed by default. Declared or verified status, nationality, visa and the mere expiry of a qualification are not automatic blocking criteria for this engine. The reasons are shown to the candidate, who may correct their profile or request human review and present their views. The recruiter may confirm the block or allow the application with an explanation. Difficulties may be reported to admin@navisteer.app. The check does not decide whether to hire and does not use AI scoring.
5. Optional PDF import of a qualification
At the candidate's request, a qualification PDF can be used to propose six fields: qualification number, holder name, holder reference, issuing authority, issue date and expiry date. The candidate reviews, corrects and confirms the values before they are recorded. This analysis does not verify authenticity, legal validity or equivalence. Manual entry remains possible.
The PDF passes through the API hosted by Railway and a separate temporary store in Amsterdam, then through Vercel AI Gateway and Amazon Bedrock for inference by an Anthropic model in the Europe region. European inference settings do not guarantee exclusively European transit through Vercel. The file and temporary proposals are encrypted; local processing uses temporary memory storage. The flow requires the inference provider not to retain content or use it for training, and does not request content caching. Processing expires after thirty minutes. Objects are erased before confirmed fields are recorded, on abandonment or by cleanup after expiry; a deletion failure suspends new imports until it is resolved, within one hour at the latest. The final technical log, without PDF content or proposals, is retained for seven days. Only confirmed fields become profile data.
6. Providers and processing locations
DEVLAB provides controlled maintenance and operations. Railway hosts the API, PostgreSQL/PostGIS and private storage, including the Tigris object layer in Amsterdam; support access and related processing may occur outside the European Economic Area. Vercel hosts the site, Web functions, map origin and AI gateway; Production functions run in the iad1 region in the United States, and delivery uses a global network. Resend sends Production transactional email; Google Workspace manages the domain's mailboxes. Amazon Bedrock and Anthropic participate only in the optional prefill flow described above. Map resources come from OpenFreeMap and OpenStreetMap/OpenMapTiles data through NAVISTEER's central origin: the browser does not send its NAVISTEER cookies or identifiers directly to the map provider.
To detect and resolve failures, NAVISTEER uses Sentry, in projects whose event hosting is located in the EU region, to monitor technical errors from the API and website only. Before transmission, events are reduced to the error type, static code locations in the stack, HTTP method, environment, software release, timestamp and a technical event identifier. Free-form error messages, page URLs and their parameters, request bodies and headers, cookies, identities and contact details, user documents, screenshots, replays and performance traces are not sent. Browser errors pass through a NAVISTEER relay and API errors leave from the server: Sentry sees the technical address of the sending server, not the visitor's IP address. This diagnostic and continuity processing relies on the legitimate interest described in section 3.
These flows may involve processing or access outside the European Economic Area, particularly in the United States and from French Polynesia; this may also concern Sentry support access and subprocessors despite EU-region event hosting. To learn about the transfer safeguards applicable to your data flow and request a copy of available documents, write to admin@navisteer.app. No payment provider receives order data while purchasing remains closed.
7. Retention and deletion
| Category | Period or criterion |
| --- | --- |
| Active account, profile and structured qualifications | During account activity and while data serve requested functions; warning after 23 months of inactivity, closure and deletion at 24 months without new activity |
| Voluntary closure | Account immediately unusable and profile removed from the active service; shared data needed by the other party anonymised, then deleted on their applicable expiry date |
| Closed applications, conversations and reports | Deletion or anonymisation no later than 24 months after closure or the applicable last exchange |
| Unlocking rights and security audits | 365 days after the event |
| Abuse limiting data | Seven days after the last request in the counter |
| Scrubbed technical error events sent to Sentry | Until the retention period configured for the Sentry projects expires, limited to the time needed to diagnose and correct incidents; earlier deletion where necessary |
| Contact requests, support conversations including those related to a pre-enrollment, and sender details | No later than 90 days after the last message in the thread, unless deleted earlier |
| Abandoned, rejected or unreconciled technical payments, when purchasing opens | No later than 90 days after terminal status or receipt |
| Invoices, credit notes and accounting records, when sales exist | Ten years in an archive separate from ordinary use |
| Temporary prefill files and proposals | Deletion before confirmed fields are recorded; emergency cleanup within one hour; technical log without content deleted after seven days |
Temporary availability expires on the selected date. Copies may remain in backups until the end of their actual rotation; deletions made since a backup must be reapplied before any restoration returns to service. Data that are no longer needed may be deleted earlier, subject to an applicable obligation or active case.
8. Your rights and choices
Subject to applicable conditions, you may request access, correction, erasure, restriction and portability, and object to certain processing. Where consent is the ground for processing, you may withdraw it without affecting prior lawful operations. You may close your account in the service or write to admin@navisteer.app. A proportionate identity check may be requested. For data a recruiter processes for their own recruitment after receiving them, also address your request to that recruiter; OCEANS NEXUS forwards requests relating to operations entrusted to it by the recruiter.
You may complain to the CNIL or another competent supervisory authority. Strictly necessary cookies and technical storage are described in a separate notice; no advertising tracker is active. Any material amendment to this policy will be announced and dated. Publication alone does not require a new acceptance checkbox.
