Hotel data means guest names, contact details, preferences, and stay history. Here is how our applications handle it, so your IT and finance teams can assess us properly instead of guessing.
OPERA Cloud authentication runs from the application server using your environment’s own client credentials. The browser never holds a token or calls Oracle directly, so nothing sensitive is exposed to the client session.
Imports run only against OPERA environments you configure and authorise. There is no back door, no shared tenancy of your property data, and no write path outside the environments you have set up.
Workbook Studio never writes to OPERA at all. In Configurator, validation runs check-only, and a live import is an explicit action against a named environment.
Migration works on the extracts your project requires, for the cutover it is scoped for. Preparation work in Workbook Studio uses configuration data, not guest records.
Every imported row is logged with its outcome and the identifier OPERA returned. If someone asks what was written and when, there is a record rather than a recollection.
The applications are ordinary Node.js and MySQL services. Where your policy requires it, they can run inside your own environment rather than ours. Confirm hosting arrangements during scoping.
This page describes how the applications are built and operated. It is not a certification claim, and it does not replace your own due diligence or a data processing agreement. We are glad to complete your security questionnaire.
Tell us your data handling requirements and any chain or ownership policy that applies.
Confirm hosting, environments, credentials, retention, and who holds what.
Work through authorised environments with logged, reviewable activity.
Agree what is retained after cutover and what is removed.
Opening a property, moving to OPERA Cloud, or improving your existing setup? Tell us what you are working with and we will tell you honestly whether we can help.
Email ark@scstech.me · WhatsApp +968 9390 0840