Terms of Service

By creating a property on Meurneoba OS or signing in to an existing one, you agree to these terms. If you are accepting on behalf of an organisation (your village, estate, farm, or hotel), you confirm that you are authorised to bind that organisation.

Meurneoba OS is the operating intelligence layer for resorts, estates, farms, infrastructure, teams, sensors, alerts, work orders, and AI reasoning. It is built to run manually on day one and to gain capability as sensors and integrations are added.

The product boundary is intentional. Meurneoba OS is not:

• a PMS, booking engine, or channel manager
• a POS, restaurant POS, or retail POS
• a payments processor, card processor, or invoice system
• an accounting, tax, or payroll system
• a bank-reconciliation tool

We integrate with these systems where it helps operations, but we do not replace them. The accounting record of money continues to live inside your PMS, POS, payment processor, or accounting software.

You are responsible for safeguarding your account credentials and for the actions of users you add to your village. Roles (founder, operator, scoped managers, technician, worker, resident) define what each user can see and do; you remain responsible for the role assignments you make.

Login sessions can be revoked at any time. Suspended accounts cannot access the OS even with otherwise-valid tokens.

You agree not to:

• upload credentials, secrets, or API keys into the OS outside the encrypted integration forms;
• impersonate another user or village;
• attempt to access another tenant's data;
• use the OS to violate applicable law or third-party rights;
• reverse-engineer the platform to build a competing product.

The OS includes AI-generated briefings, predictions, classifications, and suggested actions. These are operational aids, not legal, financial, medical, or safety guarantees. Detailed terms for AI use, including how outputs are cited and how mock/system-test outputs are labelled, are in the AI & Data Use document.

When sensors, PMS webhooks, POS webhooks, weather APIs, or similar external sources are connected, the OS receives data on the contracts those sources define. We surface that data with provenance — manual, sensor, API, or simulated — so operators can tell the difference. Outages, mis-configurations, or contract changes at the source can affect the OS's view; the OS continues to operate manually in those cases.

AI outputs, predictions, and suggested actions are best-effort. They must not be relied on for safety-critical, regulated, or legally binding decisions without human review. The founder/operator on each village remains responsible for the operational and safety choices their team makes.

We aim for reliable uptime but do not guarantee uninterrupted service. Scheduled maintenance, vendor outages (Supabase, AI provider, weather API), and emergencies can briefly affect availability. Critical alerting and the manual data paths are prioritised during such events.

To the maximum extent permitted by law, Meurneoba's aggregate liability for any claim is limited to the fees you have paid for the OS in the twelve months preceding the claim. We are not liable for loss of profits, loss of data caused by external systems we do not control, or indirect or consequential damages.

Either party may terminate the service at any time. On termination, you may request export of your operational data through the Data Requests flow. We may suspend access for non-payment, acceptable-use violations, or security incidents.

We may update these terms. Material changes will be announced to the founder/operator email on file. Continued use after such announcement constitutes acceptance.

Questions about these terms can be raised through the support page or at zuka@meurneoba.com.