Information we collect
We collect account registration details, profile information, course enrollment records, lesson progress, payment transaction references, invoice review status, certificate records, and administrator activity logs needed to operate the LMS.
How we use information
We use this information to authenticate learners and administrators, provide course access, review payment requests, issue certificates, protect accounts from misuse, maintain audit history, and improve platform reliability.
Supabase and hosting providers
MechatronicsLAB uses Supabase for authentication, database storage, and row-level security enforcement. Hosting, logging, and uptime providers may process limited technical data such as request paths, status codes, errors, latency, and browser diagnostics.
Payments and invoices
Payment review is based on transaction identifiers, payment references, buyer contact information provided by the learner, course price, invoice status, and administrator review notes. The platform does not require screenshot upload for the current payment flow.
Analytics
The production app uses first-party page-view analytics only when explicitly enabled by configuration. It does not set analytics cookies and it respects browser Do Not Track. Analytics events are used for operational product insight, not advertising resale.
Monitoring and uptime
Browser error reports, server errors, CSP reports, health checks, uptime checks, and log drains may be used to detect failures. These reports are designed to redact secrets and avoid collecting passwords, authorization headers, cookies, or service keys.
Data sharing
We do not sell learner data. Data may be shared with infrastructure providers only as needed to run authentication, database, hosting, monitoring, payment review, support, or security operations.
Retention
Account, payment, enrollment, progress, certificate, and audit records may be retained while the account is active and for a reasonable period afterward for operational, fraud-prevention, support, and legal recordkeeping needs.
Your choices
You may request correction, access review, or account support through the official support channel. Some records, such as payment review and administrator audit logs, may be retained where required for security, dispute, or legal reasons.
Security
Access to learner-owned data is protected with authenticated APIs and Supabase row-level security. Administrator APIs require an admin profile and server-side service-role operations are kept out of client bundles.