Trust & Legal Center

1.1 Data We Collect and Process

We collect and process only the minimal operational data required to deliver reliable stock management and compliance auditing:

• Institutional & User Credentials: Full name, professional role (e.g., Lead Pharmacist, Dispensing Nurse, Clinic Director), institutional work email, clinic node identifier, and cryptographically hashed authentication tokens.
• Pharmaceutical Inventory Data: National Drug Codes (NDC), international nonproprietary names (INN), batch/lot numbers, manufacturer serials, manufacturing dates, expiry timestamps, safety stock thresholds, and physical shelf/storage bin locations.
• Dispensing & Movement Audit Logs: Timestamped records of inventory intake, inter-departmental transfers, wastage/spillage write-offs, physical count variance adjustments, and anonymized prescription voucher IDs.
• Device & Telemetry Data: Client device identifiers, offline terminal sync state, browser environment, IP address, and localized storage health metrics (IndexedDB storage utilization).

1.2 Partitioning of Direct Patient Health Information

MedSwift is engineered to track medications and supply movements. We enforce strict data partitioning: patient-identifiable clinical records, diagnoses, and personal contact information are not ingested or stored within the MedSwift inventory sync ledger. Dispensing actions reference internal institutional prescription numbers or voucher IDs to satisfy audit trail requirements without centralizing protected health information (PHI).

1.3 Local-First Offline Storage & Cloud Synchronization

MedSwift operates on a hybrid local-first architecture. When operating in remote or disconnected environments:

• Data is written locally to client-side IndexedDB databases (via Dexie.js) on the authorized terminal.
• Local cache is encrypted at rest within the sandboxed browser environment of the verified workstation.
• Once internet connectivity is re-established, the synchronization engine automatically flushes mutation queues over TLS 1.3 to our central PostgreSQL database (Supabase), verifying record integrity with cryptographic checksums.

1.4 Zero Commercial Data Exploitation

MedSwift does not sell, rent, monetize, or broker pharmaceutical supply data, pricing information, or facility inventories to third-party commercial brokers, advertisers, or unauthorized external entities. Aggregated, fully anonymized supply trends may only be utilized for regional supply chain resilience reporting with explicit institutional consent.

1.5 Data Retention, Archival & Deletion

Inventory audit trails and lot-traceability logs are maintained in accordance with statutory pharmaceutical recordkeeping mandates (typically 5 to 7 years depending on national pharmacy regulations for prescription and controlled substance auditing). Upon institutional contract expiration or lawful deletion request, operational data is expunged from live databases in accordance with DoD 5220.22-M sanitization standards.

2.1 Institutional Authorization & Account Provisioning

MedSwift is a closed-access clinical utility. Node access is granted exclusively to licensed healthcare facilities, accredited pharmacies, medical non-profits, and verified health ministries. Individual staff accounts must be provisioned by an authorized institutional administrator. Sharing account credentials across multiple individuals is strictly prohibited.

2.2 AI Decision Support Disclaimer

The institution retains full responsibility for verifying medication authenticity, physical packaging integrity, dosage accuracy, and batch expiry prior to patient administration.

2.3 Acceptable Use & System Integrity

Users agree not to:

• Attempt to falsify or tamper with automated electronic audit logs or stock adjustment records.
• Introduce malicious scripts, reverse-engineer proprietary AI forecasting models, or manipulate WebSocket sync events.
• Use the platform for unverified, illicit, or counter-indicated pharmaceutical distribution.
• Bypass Role-Based Access Control (RBAC) tiers or access inventory modules outside assigned clinical permissions.

2.4 Service Availability & Offline Resiliency

MedSwift is architected to ensure continuous local operation even during complete Internet outages. While MedSwift maintains high availability for central cloud synchronization infrastructure (99.9% uptime target), we are not liable for local hardware defects, operating system browser cache purges initiated by unauthorized personnel, or extended ISP outages.

2.5 Intellectual Property & Exportable Reports

The MedSwift software, user interface design, AI scoring engines, and brand assets are the exclusive intellectual property of MedSwift. All pharmaceutical inventory manifests, audit trail PDFs, valuation sheets, and CSV exports generated by the Customer remain the sole proprietary data of the Customer.

4.1 Offline Terminal Security & Sync Isolation

Because MedSwift operates in offline environments on clinical workstations and mobile tablets, we enforce specialized terminal protections:

• Encrypted Local Caching: Offline IndexedDB records are stored in browser-sandboxed partitions inaccessible to other web origins.
• Auto-Inactivity Session Timeout: Workstations automatically lock after a configurable period of inactivity to prevent unauthorized physical tampering in busy clinic wards.
• Conflict-Free Mutation Reconciliation: Sync engine leverages deterministic timestamp resolution to prevent inventory race conditions during multi-terminal synchronization.
• Remote Revocation: Administrators can remotely revoke compromised terminal tokens, instantly wiping cached offline keys upon reconnect.

4.2 Vulnerability Reporting & Incident Response

We maintain an active security monitoring and patch management lifecycle. In the event of a confirmed security incident impacting facility records, MedSwift adheres to a strict 72-hour notification protocol to affected institutional administrators in accordance with international healthcare notification regulations. Security researchers can submit vulnerability disclosures to security@medswift.network.