Understand Oprivia in minutes

Oprivia is a coined name derived from “operations” and “via”, the Latin word for way or route. It refers to a structured operating path after the booking.

Oprivia is a web-based B2B software platform for professional accommodation operations. It supports registration, required information, requests, cleaning, partner coordination, records, escalations and evaluation in one shared structure.

After the reservation, guest details, clarifications, cleaning, handovers and partner services often spread across separate channels. Oprivia brings that work into a traceable operating context.

Oprivia is designed for professional hosts, business apartments, serviced apartments, property managers, portfolio operators and operational partners with recurring coordination needs.

Oprivia is not designed for occasional private rentals without ongoing operational complexity. It is also not a booking portal and does not take over all operator responsibilities.

Oprivia is currently being developed and validated through controlled pilot use. The public website explains the offer; operational access is provided step by step to authorised users.

Oprivia is being built in Switzerland and follows a quality standard based on precision, reliability and controlled development. The Swiss origin describes an operating standard, not a legal or performance guarantee.

The central areas are registration, required information, requests, cleaning, partner coordination, roles, records and evaluation. Which areas are introduced first depends on the specific operating model.

No. Oprivia can be introduced step by step. During the pilot, the areas with the highest practical value for the specific operation are prioritised.

Cross-functional elements include roles, access rights, processing status, time windows, checklists, records, escalations and overviews.

Potential extensions include inventory functions, additional reporting, integrations and further review or risk functions. Features that are not yet available are marked as planned, optional or under review.

No, not by default. Oprivia can operate as a separate platform with its own login. A connection to existing systems is only required if data should be imported, exchanged or synchronised automatically. Such interfaces are subject to technical review and explicit agreement.

Oprivia uses roles such as guest, host or operator, operational user, administration and governance. Tasks, information and permissions depend on the assigned role.

A role only sees the information required for its intended task area. Access can also be limited by organisation, property, stay or work case.

A case can be assigned to a responsible role, a processing status and, where required, a time window. Handovers and changes remain traceable.

Escalations can be triggered for overdue items, missing records, blocked cases or defined exceptions. The case is then routed to the designated control or decision role.

No. Oprivia can structure information, apply rules and highlight review needs. Critical approvals, exceptions and decisions remain with the responsible people.

Critical actions are added as new events in a continuous history. Earlier entries are not silently overwritten; corrections remain possible but are documented as additional entries.

Oprivia is not a public review portal. The focus is on internal records, feedback, deviations and work results, not stars or rankings.

Quality is assessed through defined review points such as checklists, photo records, feedback, rework, approvals and documented outcomes.

Depending on the area and agreed setup, checklists, images, documents, notes, confirmations, timestamps or decisions can be assigned to the relevant case.

Critical audit events should not be silently overwritten. Corrections and new findings are added as additional entries. The exact scope depends on platform version and agreement.

The pilot assesses whether Oprivia can be applied meaningfully to a specific operating case. The focus is on onboarding, operational assessment, roles, checklists, partner tasks, photo records and evaluation.

Suitable pilot clients are professional operators or partners with a concrete challenge, recurring workflows, named contact persons and willingness to participate in a structured evaluation.

The pilot can cover registration, required information, requests, cleaning, partner coordination, records, escalations and evaluation. The actual scope is defined separately.

At the beginning, the property, operating model, involved roles, partners, relevant workflows, observation points and excluded services are defined. This creates a clearly limited pilot scope.

The pilot client provides contact persons, property information, existing process documents, partner contacts and feedback. Access, data migration or integrations are agreed separately where required.

A pilot can be continued, adjusted, paused or closed. It creates a decision basis, but no automatic rollout, acceptance or contractual obligation.

No. The specific price depends on the operating model, property structure, required support, selected areas and agreed service frame.

The fee generally consists of a monthly base fee and a revenue-based component. Depending on the agreed setup, implementation, training, integrations, additional support or third-party services may be added.

Key factors include the number of units, locations, operating model, roles, support needs, selected areas, implementation effort and ongoing assistance.

The revenue-based component is part of the commercial model. Its percentage, calculation basis and billing period are defined in the individual proposal.

The base fee covers platform access, structure and agreed support. The revenue-based component reflects Oprivia’s deeper involvement in scaling, operational relief and improved controllability.

Pilot conditions are set out in a separate proposal. The decisive factors are pilot scope, modules, support effort, technical requirements and agreed participation.

A public guest pricing package is not planned. Commercial conditions are generally agreed with the operator or contractual partner.

Additional costs can arise from identity services, integrations, special configuration, additional support, external partners, cleaning, laundry, consumables, repairs or payment processing. Such items are listed separately.

Yes. A successful referral may qualify for a 10% discount on the monthly base fee. Several successful referrals may be combined up to a full reduction of the monthly base fee. The specific conditions are defined in the referral terms or individual proposal.

Depending on the areas used, Oprivia may process stay, contact, identity, task, role, record, communication and evaluation data. Details are defined in the applicable data protection information and agreements.

Visibility depends on role, organisation, property, responsibility and specific case. Sensitive information should only be available to expressly authorised roles.

Personal data is processed for defined operational and contractual purposes. Purposes, categories, recipients and access rights depend on the setup, agreement and data protection information.

Retention and deletion depend on data type, purpose, agreement and legal requirements. Different data categories may be subject to different retention periods.

External providers may be used for hosting, identity verification, communication, analytics or integrations. Their use and any relevant data transfers are disclosed in the applicable documents.

No. Oprivia does not broker accommodation, publish listings or manage reservations and pricing. The platform starts after the booking.

No. Oprivia is not an Airbnb manager, booking portal or channel manager. The platform supports workflows around preparation, stay, cleaning, partner coordination and closure.

A property manager may take operational responsibility for properties and services. Oprivia supports structure, coordination and documentation, but does not automatically perform operator tasks itself.

PMS and check-in systems often focus on reservation, calendar, communication or arrival. Oprivia connects several work steps after the booking through roles, records, escalations and evaluation.

No. Oprivia is not a payment service provider and does not process payments as its own provider. Financial transactions are handled through designated external systems.

No. Oprivia supports operational organisation and documentation, but does not replace professional or legal review. Responsibility for applicable obligations remains with the operator or contractual partner.

No. Oprivia can structure workflows, make information visible and support documentation. A specific commercial result or automatic legal conformity is not guaranteed.

First, the operating model, property, current challenge and desired level of support are assessed. This makes it possible to determine whether an initial discussion, a pilot review or another clarification step is appropriate.

No. An initial discussion is used first for orientation. A pilot, pricing agreement or later platform use requires a separate decision and corresponding agreement.