Privacy Policy

1. Introduction & Legal Architecture

MedLog Pro provides a professional logging environment and portfolio consolidation system engineered to help operational trainees, institutional residents, and technical supervisors manage curriculum metrics and complete skill verification workflows.

Under prevailing global data protection frameworks, the legal relationship regarding data handling is explicitly segregated. MedLog Pro acts strictly as a Data Processor, providing empty data structures, localized storage containers, and processing logic. The individual registered platform user, alongside their governing vocational facility or appraisal organization, acts as the absolute Data Controller. The Data Controller retains total ownership and legal responsibility over the content blocks they collect, input, and manage.

If you disagree with the access management, platform isolation, or complete anonymization practices established within this policy, you must execute the necessary steps to flush local browser/device cookies or caches and permanently discontinue your use of our services.

2. Strict Anonymization Architecture (Zero Third-Party Identity Policy)

MedLog Pro mandates a strict, unyielding Anonymized Data Ingestion Model. The application software architecture is explicitly configured to prevent the entry, transmission, caching, or long-term cloud hosting of any trackable personal customer identities or third-party sensitive variables.

Absolute Restrictive Blocks: Users are legally and structurally prohibited from entering individual names, private government registration indices, account tracking matrices, telephone numbers, direct physical location profiles, or uploading unredacted media assets that show trackable third-party personal details.

The application only permits, processes, and tracks the following data categories when voluntarily recorded by an authenticated user:

2.1 Anonymized Activity Metrics (User-Generated Workspace Data)

• Auto-Incrementing Case Unique Identifiers: To maintain formal institutional audit records without introducing identity vectors, the software calculates an abstract string locally on your device based on work type and calendar loops (e.g., SURG-000042-2026). This sequence tracking relies on simple local integer variables and real-time database index collision queries, remaining completely separated from real-world record systems.
• De-Identified Classification Demographics: Non-personal workspace categorization variables limited to general age ranges, abstract demographic classifications, and general grading tags.
• Operational Execution Data: Timelines of technical tasks, operational durations, general category findings, specific workflow difficulty levels, and assigned user implementation profiles (e.g., Primary Lead, Secondary Assistant, Observer).
• Task Complications Indexing: Technical performance variables mapped strictly to objective international tracking frameworks, including the five-tier operational grading register (Grades I through V).
• Media Workspace Uploads: Visual records strictly limited to physical training logbook sheets, textbook syllabus matrices, or thoroughly redacted validation sheets.

2.2 Workspace Platform Identity Information

• Access Authentication Credentials: Electronic email communication strings utilized exclusively to form unique user profile entries via enterprise OAuth 2.0 validation tokens (Google Sign-In) or secure backend hashed password nodes.
• Operational Hierarchy Roles: Selected platform personas (e.g., Student, Resident, Specialist, Supervisor) which programmatically alter the visible database viewing scopes.
• Workflow Status Parameters: Local activity timestamps, text template saving preferences, and state monitoring tags mapping the communication cycle between a trainee and an inspector.

2.3 Local Device Assets

• Basic environmental system variables (Operating System API versions, physical device models, and localized technical crash logs if enabled by system choices) to maintain database connection stability.

3. Data Utilization & Traffic Monitoring

All recorded variables are handled solely to establish, format, and generate your career portfolios, including:

• Aggregating task volume trends to calculate overall performance targets against predefined benchmarks.
• Routing submitted logs to designated workspace supervisors to enable evaluation and digital sign-offs.
• Tallying Professional Credit Hours based entirely on verified, finalized portfolio submissions.

System Load Restrictions: Consistent with enterprise open-source tracking tools, our networks deploy automatic system checks. If an account acts outside normal operating thresholds or exhibits abnormally high database interaction volume, the platform will flag the profile for structural validation. Project managers may be contacted to confirm usage boundaries, but your underlying portfolio datasets remain completely closed and un-accessed during this technical maintenance process.

No logged workspace details are ever cross-referenced, sold, rented, or repurposed for corporate behavioral profiling, consumer market trends, or third-party targeted commercial advertising.

4. Lawful Basis for Processing & Controller Obligations

Data is handled strictly under the execution of User Consent and our legitimate interest in delivering a resilient, localized workspace container. Because users operate as the absolute Data Controllers of their portfolios, the user assumes all personal legal liability for ensuring that their inputs are entirely de-identified. All entries must completely align with the data privacy guidelines, organizational covenants, and regional oversight rules of their respective local training institutions before committing data to cloud-sync networks.

5. Application Hardening & Infrastructure Safeguards

MedLog Pro implements rigorous multi-layered technical controls to defend data integrity across your workspace:

• Google Cloud Addendum Alignment: Off-device storage, portfolio replication, and secure asset backups run on an enterprise-grade cloud provider (Firebase Firestore/Storage) explicitly bound by the signed Google Cloud Data Processing Addendum (CDPA).
• Hardware Biometric Verification: Users can choose to secure app entry points by activating native biometric locks (Fingerprint or Face ID) via the androidx.biometric system, preventing local database visibility even if the mobile device is left unlocked.
• Local Application Enclosure: Un-synced log drafts, operational templates, and local records are sandboxed in private internal storage folders via Context.MODE_PRIVATE configurations, blocking cross-app visibility or unauthorized external reads.
• Code Obfuscation: Production builds use R8 and ProGuard compilation rules to systematically minify and obfuscate database structures, shielding endpoints from reverse-engineering.
• Secure Intracommunication: File passing between modules uses restricted content providers (androidx.core.content.FileProvider) using isolated content:// URIs rather than insecure root file links.

6. Automated Data Retention & Comprehensive Erasure

Records are preserved only during the active lifestyle of your user profile. MedLog Pro implements comprehensive self-service data destruction routines to respect user sovereignty over their information:

• Localized Item Deletion: Users can manually drop individual log entries within the main database layouts. This fires an immediate command that purges the record from both the device SQLite database (Room instance) and the cloud-synced mirror node.
• Absolute Account Purge: Activating the "Delete Account & All Data" routine in the Profile dashboard triggers an automated, irreversible script that instantly wipes:
  1. All local SQLite database files and layout caches.
  2. All distributed remote documents across all cloud collections.
  3. All binary media assets, tracking pictures, and file attachments.
  4. The core authentication profile and system login nodes.
• Institutional Audit Preservation: To balance user rights with organizational record continuity, if a trainee deletes their profile but has already submitted an activity log to a supervisor's review queue for institutional validation, the raw performance metrics remain visible to that supervisor to prevent breaking department training tallies. However, the log is permanently stripped of all personal user account attributes and user email details, remaining completely anonymous.
• Manual Request Fulfillment: If the application has already been removed from your mobile unit, a manual deletion sequence can be initialized via our public legal directories or by contacting jamaalbutt@gmail.com. Verified manual requests are cleared from all active infrastructure channels within 7 business days. All purges are final and cannot be recovered.

7. Changes to This Policy

This Privacy Policy may be modified periodically to ensure continuity with evolving mobile operating systems. The active tracking version will always be declared via the "Last Updated" date at the head of this document. Alterations take immediate effect upon deployment to the platform link.

8. Contact Information

For legal inquiries, verification requests, or custom data porting reports, contact:
Jamaal Butt
Email: jamaalbutt@gmail.com