Security

1. Overview

ManageYourClinic handles sensitive clinic and patient data, so security is built into the architecture rather than added after the fact. This page summarizes the technical and organizational measures we use to protect the Service. It is a supplement to, and does not replace, our Terms of Service and Privacy Policy.

2. Infrastructure

The Service runs entirely on Google Cloud Platform / Firebase — Firebase Hosting, Firestore, Firebase Authentication, and Cloud Functions — inheriting Google's infrastructure security certifications (including ISO 27001 and SOC 2). We do not run our own physical servers.

3. Encryption

• All traffic between clients and the Service is encrypted in transit via TLS.
• Data at rest in Firestore and Cloud Storage is encrypted using Google-managed encryption by default.
• Secrets and service credentials (e.g., payment API keys) are stored in Firebase/Google Cloud secret management, never in client-side code.

4. Access Control & Multitenancy

• Every resource is scoped under a clinicId; queries cannot cross clinic boundaries from the client.
• Role-based access control (Clinic Admin, Clinic Manager, Consultant) governs what each user can view or edit.
• Firestore Security Rules are the authoritative enforcement layer — client-side role checks are a UX convenience only, and all access is re-validated server-side.
• Sensitive operations — plan enforcement, quota checks, AI requests, payment webhooks — run exclusively in Firebase Cloud Functions, never client-side.

5. Application Security

• All forms and callable functions validate input with schema validation (Zod) before processing.
• No Firebase service account credentials or private keys are ever exposed in client code.
• File downloads use signed, time-limited URLs rather than public Storage links.
• Dependencies are kept current and reviewed for known vulnerabilities.

6. AI Processing Security

All requests to Google's Gemini API are made server-side from Firebase Cloud Functions — never directly from the browser — so API keys are never exposed to end users. Only the minimum data needed for a given AI request is transmitted, and AI-generated output is stored under the same clinic-scoped access controls as any other record.

7. Payment Security

Payments are processed by Stripe and Razorpay, both PCI-DSS compliant payment processors. We never receive or store full card numbers, CVVs, or UPI credentials — checkout is handled directly by the processor, and we store only subscription and billing metadata.

8. Monitoring & Audit Logging

Clinic-level actions are recorded in an in-app activity log, and platform-level administrative actions are recorded in a superadmin audit log. These logs support traceability of who accessed or changed what, and when.

9. Backups & Continuity

Firestore data benefits from Google Cloud's built-in durability and replication. We rely on Google Cloud Platform's infrastructure resilience for the Service's underlying availability.

10. Incident Response & Breach Notification

If we confirm a security incident affecting your data, we will investigate, take reasonable steps to contain and remediate it, and notify affected Clinics without undue delay, consistent with our obligations under India's Digital Personal Data Protection Act, 2023 and other applicable law, including any required notification to a competent data protection authority.

11. Responsible Disclosure

If you believe you've found a security vulnerability in the Service, please report it to hello@manageyourclinic.com with enough detail to reproduce the issue. Please report privately and give us a reasonable time to investigate and remediate before any public disclosure. We will not pursue legal action against good-faith, non-destructive security research conducted under this policy.

12. Personnel & Access Discipline

Access to production systems and customer data is limited to what is necessary to operate and support the Service, and superadmin actions are logged. Clinic Admins are responsible for provisioning and promptly revoking their own staff's access as roles change.

13. Your Responsibilities

• Use strong, unique passwords and protect OTP/MFA codes for your account.
• Grant staff only the role/permissions they need, and deactivate accounts promptly when staff leave.
• Report suspected unauthorized access to your account immediately.
• Keep your own devices and browsers up to date and free of malware.

14. Contact

For security questions or to report a vulnerability, contact hello@manageyourclinic.com.