Privacy Policy

Meurneoba OS is an operational intelligence layer for resorts, estates, farms, and similar properties. The platform is operated by Meurneoba Village LLC ("Meurneoba", "we", "our"). For privacy questions, use the support page or write to zuka@meurneoba.com.

When you operate a property on Meurneoba OS, we may process:

• Account data: name, email, role, login session metadata.
• Property configuration: sites, units, devices, modules enabled.
• Operational records: alerts, work orders, site logs, schedules, tasks, harvest entries, sensor readings, irrigation/energy schedules, asset maintenance logs.
• Workforce data: roles, scoped access, team assignments, task verification.
• Hospitality and revenue intelligence derived from your PMS/POS via webhook receivers (operational summaries — not bookings, payments, or card data).
• Telegram chat-binding status (chat IDs are stored to deliver alerts; we never expose them through the API surface).
• AI-generated outputs: briefings, predictions, agent logs, alert classifications.

We do not process payment instruments, bank account numbers, passport/ID images, full PMS card data, tax records, or accounting ledgers. Those remain inside your PMS, POS, payment processor, or accounting software.

Data arrives at Meurneoba OS through four distinguishable channels:

• Manual — entered by your team in the OS.
• Sensor — pushed from connected devices.
• API / webhook — received from a connected PMS, POS, weather provider, or similar.
• Simulated — mock data for system tests or demo tenants, kept clearly labelled.

The OS works manually on day one. It gains more capability with sensors and integrations, but no integration is required for core operation.

We process operational data to:

• Run the OS — display dashboards, raise alerts, schedule work orders, route tasks.
• Provide AI assistance — generate briefings, predictions, and suggested actions (see the AI & Data Use page).
• Maintain audit and reliability logs.
• Support requests you raise (account, integration, bug, security).

Meurneoba OS is designed with tenant isolation: each property's data belongs to its village, and access is gated by JWT-derived villageId on every backend route. Within a village, role-based access (founder, operator, scoped manager, technician, worker, resident) controls which modules and records a user can see.

Cross-tenant data access is rejected by the backend (returns 404 for unknown-tenant IDs). This is enforced in code and verified by tests.

Mutations recorded by the OS are written to an audit log. Sensitive contextual fields (briefing context, agent triggers, secrets) are not surfaced through the read APIs that drive the UI.

We retain operational records for as long as the property's subscription is active, plus a reasonable period for backups and audit. You can request export or deletion at any time — see the Data Requests page.

Meurneoba OS runs on a database hosted by Supabase. AI processing uses large-language-model providers chosen at the time of generation; the provider in use is visible inside the AI Center. We use OpenWeatherMap for weather and the National Bank of Georgia for FX rates. When you enable a PMS or POS integration, your data flows through their webhook contracts; their privacy terms apply to data still held inside their systems.

Meurneoba OS is designed with tenant isolation, role-based access, an audit log, and a data-export/deletion request flow. We do not currently claim SOC 2, ISO 27001, HIPAA, or GDPR certification. If a certification is required for your deployment, contact us before launch.

You can request a copy or deletion of your operational data through the Data Requests page. Requests are handled by the founder/operator on file for your village.

We may update this policy as the OS evolves. Material changes will be announced to the founder/operator email on file for each village.