Privacy Policy

1. Overview & Single Purpose

This Privacy Policy outlines how LamaniSync ("we", "our", or "the Extension"), operated by Lamanify Technologies ("Lamanify"), collects, handles, stores, and shares information when authorized healthcare clinic personnel install and operate the LamaniSync Chrome Extension and associated synchronization services.

LamaniSync serves a single, well-defined operational purpose: to provide a secure, authenticated, and verified synchronization bridge between certified cloud Clinic Management Systems (CMS) and the LamaniHub operational dashboard.

We operate under strict healthcare data protection standards, including the Malaysian Personal Data Protection Act (PDPA 2010 / 2024 Amendments) and international healthcare data privacy principles.

2. User Data Collection

LamaniSync enforces the principle of data minimization. We only collect the minimal technical and operational telemetry strictly required to maintain an active, secure synchronization tunnel:

• Workstation Technical Telemetry: Ephemeral workstation installation identifier (UUID v4), browser vendor version, extension build version, and local workstation hardware nickname assigned by the clinic administrator.
• Authentication State: 15-minute rotating pairing tokens, local non-exportable WebCrypto Ed25519 public verification keys, and cryptographic leader-lease tokens used to prevent split-brain execution across multiple front-desk terminals.
• Operational Sync Metadata: De-identified appointment timestamps, calendar slot duration, operatory/chair identifiers, and provider schedule availability status.

3. Data Handling & Processing Practices

LamaniSync handles data using a sandboxed, ephemeral execution model within Google Chrome:

• Sandboxed In-Memory Processing: Operational appointment sync requests are held in volatile RAM only for the duration of the cryptographic handshake (typically <200 milliseconds) and are immediately scrubbed upon completion.
• Two-Phase Readback Verification: Appointment write actions are committed via authenticated DOM interactions and verified via two-phase readback before mathematical confirmation receipts (SHA-256 state hashes) are returned.
• Ambient Session Execution: LamaniSync operates within the existing authenticated session of the clinic staff member. It never intercepts, copies, or reads staff passwords, session cookies, or master credentials.
• No Arbitrary Remote Code: In accordance with Chrome Manifest V3 security requirements, LamaniSync executes zero remote scripts, eval() statements, or dynamic remote imports. All adapter instructions are pre-compiled and digitally signed.

4. Data Storage & Security Safeguards

We employ defense-in-depth security safeguards to protect all technical data:

• Zero Local Hard Drive Retention: LamaniSync writes zero patient data to local workstation disks or external storage devices.
• Isolated Extension Storage: Minimal operational state (workstation pairing ID, active lease state, paired CMS origin) is stored in isolated chrome.storage.local, accessible strictly to the LamaniSync extension context.
• Hardware-Backed Cryptography: Device authentication uses W3C WebCrypto Ed25519 non-exportable asymmetric keypairs stored in browser-enforced secure key stores.
• Transport Layer Security: All external communication to the LamaniHub API uses outbound-only TLS 1.3 encryption over port 443 with strict certificate pinning. No inbound listening ports are opened.

5. Data Sharing, Disclosure & Third Parties

We do not sell, rent, monetize, or trade clinic data under any circumstances. Data disclosure is governed by the following strict boundaries:

• Zero Third-Party Advertising & Data Brokering: We never share data with advertising networks, commercial data brokers, data aggregators, or credit assessment bureaus.
• Zero Third-Party Tracking SDKs: The extension contains zero tracking analytics (no Google Analytics, Facebook Pixel, Mixpanel, or third-party behavioral trackers).
• Authorized Clinic Infrastructure Only: Telemetry and verified synchronization event receipts are transmitted solely to the clinic's dedicated, authenticated LamaniHub organization instance (https://app.lamanihub.com).
• Legal & Regulatory Disclosures: We will only disclose operational logs if required by enforceable court order, valid legal subpoena, or applicable Malaysian statutory law, with prompt prior notification to the affected clinic where legally permissible.

6. Data Retention & Account Unpairing

Clinics maintain complete data sovereignty over their pairing records:

• Immediate Local Purge: Clicking "Unpair Workstation" in the LamaniSync popup immediately deletes all local extension storage, purges WebCrypto keys from memory, and unregisters all dynamic content scripts.
• Server-Side Revocation: Revoking a terminal from the LamaniHub admin console instantly invalidates the workstation lease, permanently blocking all subsequent sync requests.
• Telemetry Retention Window: Routine operational handshake logs and connection timestamps are automatically rotated and purged after 30 days.

7. Compliance & Regulatory Alignment

LamaniSync is designed to maintain compliance across global and regional healthcare frameworks:

• Malaysian PDPA 2010: Aligns with the 7 Personal Data Protection Principles, ensuring data minimization, purpose limitation, security, and clinic retention control.
• HIPAA Security Rule: Aligns with Technical Safeguards (§ 164.312) regarding transmission security, unique user identification, audit controls, and data integrity.
• Google Chrome Web Store User Data Policy: Strictly complies with Single Purpose, Limited Use, and User Data Disclosures.

8. Contact & Compliance Inquiries

For questions, privacy assessments, audit verification, or PDPA data protection inquiries, contact our dedicated compliance office: