Privacy Policy & Data Minimization Notice

Depending on whether you access MINE GUARD in Evaluation Demo Mode or with Authorized Colliery Credentials, data processing is strictly limited to:

• Evaluation Mode (Judges & Evaluators): No personal data is requested or stored. Selecting an evaluation role (Safety Officer, Mine Manager, Geotechnical Engineer, or Administrator) operates entirely within client-side memory (React state) without creating user records.
• Authorized Sign-In (Optional Supabase Backend): If authenticating with colliery infrastructure credentials, only the official work email and password are submitted directly over TLS 1.3 to the configured Supabase authentication service. No personal tracking profiles are maintained.
• Sensor Telemetry Ingestion: Telemetry received via the API (`/api/telemetry/ingest`) consists exclusively of physical transducer readings (extensometer displacement, biaxial tilt, rockmass strain, vibration velocity PPV, acoustic pulse counts, battery millivolts, and RSSI). Telemetry packets contain zero personal identifiers.
• Statutory Shift Sign-Offs: When an operator acknowledges an alert or signs off on a shift log, the designated role title (e.g., “Safety Officer”), action summary, and timestamp are committed to the demonstration audit trail to demonstrate compliance with Coal Mines Regulations (CMR) 2017 Reg 112.

MINE GUARD operates without non-essential, tracking, or marketing cookies. We do not use third-party analytics suites or advertising beacons.

Because only strictly functional storage is utilized, no invasive cookie consent banner is mandated or displayed.

The web application is hosted on Vercel and interacts optionally with Supabase (Managed PostgreSQL):

• Server Logs: Standard HTTP edge logs (client IP address, user agent, requested URL, response status code, and latency) are processed by Vercel exclusively for security monitoring, DDoS mitigation, and operational error tracing. These logs are maintained in compliance with Vercel's infrastructure retention policies.
• Self-Hosted Typography: All fonts (IBM Plex Sans, IBM Plex Mono) are self-hosted via `next/font/google` and bundled into static assets during build time. At runtime, the client browser never connects to Google Font servers or third-party CDNs.

• Client-Side Demo Isolation: In demo mode, simulation data is held purely in browser memory (Zustand state store) and resets upon tab closure or page refresh.
• Row-Level Security (RLS): When connected to a live database, all tables enforce PostgreSQL Row-Level Security policies. Anonymous public writes are rejected.
• API Key Protection: Ingestion routes (`/api/telemetry/ingest`) require a secret `x-api-key` header to prevent unauthorized telemetry submission. Service-role secrets are never bundled into client-side code.

Because this website functions as an engineering demonstration and collects no personal consumer profiles, consumer data deletion requests are generally not applicable.

However, if you have authenticated using colliery test credentials and wish to have your test account removed from the testing Supabase instance, or if you have questions regarding the project's data governance, please contact the project development team: