Privacy Policy
Legal notice covering collection, use, retention, rights, and processors.
Loading…
Trust and Privacy
Coaches and clients share only what consent allows. Human judgement stays central. Opportunity Fit in the founding beta uses built-in analysis — materials are not sent to an external AI provider. This page is a product trust centre — the Privacy Policy and Terms remain the legal sources of truth.
Now available in Finland. Eligible Job Seekers and Career Coaches can subscribe online, with secure payment processing through Stripe. Solo costs €19/month including VAT. Founding Coach costs €59/month excluding applicable VAT. We are preparing to expand across the EU.
Your profile, evidence, plans, and progress live in your workspace. Sharing is optional and selective — not automatic.
Access starts with an invitation and consent choices. You can see what is shared and end access when a relationship should stop.
Orinavis does not make automated hiring decisions, rank candidates, or assign hidden employability scores.
Orinavis does not assign hidden employability scores. Programme or organisation visibility stays consent-aware and role-based — not unrestricted.
Orinavis does not rank people or compare candidates for hiring outcomes. Orinavis does not determine employability or make hiring decisions.
Trust depends on keeping human support and advisory analysis clearly distinct — and never substituting one for the other.
Coaches, advisers, supporters, and you retain judgement, consent choices, and relationship accountability.
Orinavis structures evidence, surfaces fit signals and gaps, and suggests practical actions for review — without ranking people or automating hiring.
Your career evidence, Opportunity Fit reviews, action plans, progress, notes, messages, and bookings stay in your private workspace. Coaches and programmes do not see them by default.
An invitation and consent establish active access for a defined relationship. Only selected categories are visible. When you revoke coach access or a programme relationship ends, active visibility stops. Historical records may remain stored for service and legal obligations — revocation is not an instant purge of every past note or message.
Privacy is the default. Access is intentional, purpose-bound to the relationship, and can be reviewed or revoked through product controls and support where required.
Who can see what
You choose what each relationship can see. Anything you do not share stays private.
Active
Shared by you
Active
Limited programme visibility
Private notes and messages are not shared.
Private
Only you can see this information unless you choose to share it.
Illustrative access states. Exact permissions depend on role, purpose, and consent. Read the Privacy Policy
Identity, contact details, and role settings so you can sign in, receive invitations, and use the correct workspace.
Roles, projects, documents, samples, outcomes, and related proof so Opportunity Fit reviews and plans start from current context.
Materials and target-role context you submit so Orinavis can compare requirements with available evidence for human review.
Shared actions, progress, bookings, messages, and session notes that support continuity between meetings.
Security, reliability, and product-operation signals (such as authenticated analytics events) needed to run and improve the service safely.
Card payments are processed by our payment provider, Stripe. Orinavis does not store full payment-card numbers in product databases.
Plain-language categories for product use. Full legal detail — including lawful bases and retention — lives in the Privacy Policy.
Request an access export from account settings or support. Evidence summaries and radar exports are available where the product provides those tools; broader copies are fulfilled as privacy requests.
Update profile and career evidence in your workspace. Rectification requests that need support follow the privacy-request flow.
Request erasure through account settings or support. Requests are processed as privacy workflows — not an automatic wipe of every backup or legally retained record.
Revoke a coach connection from settings when the relationship should end. Programme participation ending stops active programme visibility under that relationship.
Product tools and support workflows handle rights requests. Some records may be retained where legally required, for security, billing history, or contractual obligations. Instant complete deletion of every system copy is not claimed.
Requires an invitation and client consent. Coaches see only permitted categories (such as evidence or notes) under an active CoachClientAccess relationship. Opportunity Fit results are additionally opt-in per scan — sharing a scan is separate from invite category checkboxes.
When Specialist workflows expand, access is intended to stay scoped to a defined engagement and the context the Job Seeker consents to share for that need — not broad profile access or marketplace browsing.
Invitation-based and purpose-limited. Supporters are designed to see only what was explicitly shared for the help they were asked for — not a Coach or Specialist workspace.
In team and programme contexts, advisers work from assigned participant relationships with consent-aware visibility — not a free browse of every private file.
Focused on operational indicators such as consent status, assignments, milestones, and agreed delivery signals. Mature cohort analytics remain early-release and conversation-scoped.
Configuration, roles, and governance for an agreed organisation workspace. Admin visibility still respects participant consent and relationship scope.
Programme oversight does not automatically mean access to every private document, message, note, or Opportunity Fit detail. Visibility follows consent, assignment, and role.
Public traffic to Orinavis is served over HTTPS so data is encrypted while moving between your browser and our servers.
Authentication, session controls, CSRF protection on mutating routes, role checks, and consent-gated coach or programme visibility reduce unauthorised access.
Infrastructure and optional services are limited to configured providers. Processing detail and subprocessors belong in the Privacy Policy — not as marketing absolutes.
Security and privacy incidents are handled through internal response processes and support channels. Contact Orinavis if you believe there has been a misuse of access.
Operational safeguards we can stand behind today. Certifications, encryption-at-rest detail, hosting region, backup frequency, and penetration-test claims are not published here without verified evidence.
Legal notice covering collection, use, retention, rights, and processors.
Allowed and prohibited uses, including no automated hiring or ranking of people.
Our accessibility commitment and how to raise barriers.
Explicit access, reviewable advisory outputs, and human responsibility stay visible in the product — not bolted on as after-the-fact promises.