Privacy Policy

This page is maintained by MediCore to explain how personal and clinical information is handled when a hospital ("customer") uses the MediCore platform. It is app-owned content provided for transparency; it is not an independent certification.

1. Roles

Each hospital ("tenant") is the data controller for the patient and staff data it enters into MediCore. MediCore acts as the data processor: we store and process that data on the hospital's behalf, per its instructions.

2. Data we collect

• Account data: name, email, phone, role, and tenant assignment.
• Clinical & operational data: patient records, appointments, consultations, prescriptions, lab and radiology orders, admissions, billing and pharmacy records — as entered by the hospital.
• Technical data: IP address, browser type, timestamps, and audit logs of writes performed inside the app.
• Support data: messages sent to us via email, chat, or contact forms.

3. How we use data

• Operate the platform and its modules for the hospital.
• Authenticate users, enforce role-based access, and secure the account.
• Provide customer support and respond to requests.
• Detect abuse, fraud or security incidents.
• Improve service quality using aggregated, non-identifying metrics.

We do not sell personal or clinical data. We do not use patient data to train third-party AI models.

4. Data isolation

Every record in MediCore carries a tenant_id and Row-Level Security policies at the database enforce that users can only read or write rows belonging to their own tenant. This isolation is implemented at the data layer, not just the application layer.

5. Storage & security

• Encryption in transit (TLS) between the browser, our servers and the database.
• Encryption at rest for the primary database and object storage.
• Least-privilege service accounts; production secrets stored in a managed secret store.
• Role-based access controls inside the application, backed by a separate user_roles table.
• An immutable audit trail of writes, capturing actor, timestamp, and before/after values.

6. Subprocessors

MediCore uses vetted infrastructure providers to run the service (hosting, database, email delivery, SMS delivery). A current list is available on request via the contact page. New subprocessors are only engaged where they meet equivalent security and confidentiality obligations.

7. Retention

Clinical and operational data is retained for as long as the hospital's account is active, plus any statutory retention period the hospital instructs us to observe. On account termination, the hospital may export its data; after a grace period it is deleted from live systems and rotated out of backups on our normal schedule.

8. Your rights

Patients whose data is stored in MediCore should contact their hospital first — the hospital is the controller of that data. Where MediCore holds account data directly (for hospital staff), individuals may request access, correction or deletion by writing to privacy@medicore.app.

9. Cookies & analytics

The public marketing pages use minimal, first-party session cookies to keep you signed in and to remember your preferences. We do not use third-party advertising trackers on authenticated hospital surfaces.

10. Incident response

If a security incident affects hospital data, we will notify affected tenants without undue delay and provide the facts we have, the impact, and the steps we have taken.

11. Changes to this policy

We may update this policy from time to time. Material changes will be announced inside the app and by email to tenant administrators.

12. Contact

Questions? Email privacy@medicore.app or use the contact form.