JustOne Health Care Solution
Privacy Policy
This Privacy Policy describes information handled through the JustOne Health Care Solutions website and Hospital Management System (HMS), how it is used, and the choices available to individuals and hospitals. The public website and the authenticated hospital platform handle different types of information.
Last updated:
1. Scope: public website and HMS platform
The public marketing website may receive information that you submit through its demo, contact, or support-request forms. It also uses essential session and security mechanisms when applicable.
Information entered inside the authenticated HMS, including patient and staff records, is processed in the context of a hospital account and is distinct from public marketing enquiries. Access to that information is controlled through application accounts and roles.
2. Information We Collect
The information handled depends on how you interact with the website or platform and which modules your hospital uses.
- Public website: name, email address, mobile number, hospital or clinic name, and the message or support details you choose to submit.
- Accounts and registration: account credentials and identifiers, contact details, hospital name and address, staff details, role assignments, and verification information such as email or mobile one-time codes.
- Hospital operations: patient identity and contact details, date of birth, clinical history, allergies, complaints, vital records, visits, appointments, admissions, prescriptions, reports, and other information entered by an authorized user.
- Technical and security information: the application processes authentication, session, and security data. Depending on hosting configuration, infrastructure providers may record request, device, browser, or network metadata in service logs.
- Subscription information: the platform stores subscription status and start/end dates. We have not identified an integrated online payment processor in the application; payment card or bank details should not be submitted through the HMS.
3. How We Use Information
Information is used as needed to operate the website and the modules enabled for a hospital, including to:
- create and administer hospital and staff accounts, authenticate users, verify registration, and enforce role-based access;
- support patient registration, records, appointments, visits, admissions, bed management, prescriptions, reports, and related hospital workflows;
- send account, verification, appointment, support, and service communications by email or, when configured, SMS;
- respond to demo, contact, and support requests and administer subscriptions;
- maintain service security, diagnose errors, prevent misuse, and meet legal obligations.
4. Patient Health Information
Patient and medical information is sensitive. It is processed within a hospital workspace to support the healthcare and administrative workflows selected by that hospital. The hospital and its authorized healthcare professionals determine why patient information is entered and which users may access it.
Hospitals are responsible for having the necessary authority, notices, permissions, and legal basis to collect and use patient information, and for configuring access appropriately. Users must only access information they are authorized to handle. The legal roles of the hospital and service provider depend on the applicable law and the parties' agreements.
5. Information Sharing and Disclosure
Information may be made available to authorized users within the relevant hospital account according to their roles and the platform's workflows. It may also be handled by service providers that support hosting, infrastructure, email delivery, or optional SMS delivery, as applicable to the deployment.
We may disclose information where required by law, valid legal process, or to protect the rights, safety, and security of users and the service. Any access or disclosure should be limited to what is necessary for the applicable purpose.
6. Data Security
The application uses account authentication, role-based access, and web security protections. Appropriate safeguards are intended to reduce the risk of unauthorized access, alteration, disclosure, or loss. No system or transmission method can be guaranteed completely secure, and no security certification or particular infrastructure control is represented by this policy.
Hospitals and users should use strong, unique credentials, protect devices and verification codes, promptly remove access when staff no longer need it, and report suspected account or data incidents through the contact details below.
7. Data Retention and Deletion
Information is retained for as long as reasonably needed to provide the service, administer accounts and support, meet contractual and legal obligations, resolve disputes, and protect the platform. Hospitals must determine and meet applicable medical-record retention requirements.
A hospital account holder may contact us to request assistance with access, correction, export, or deletion. Requests may require verification and coordination with the hospital. Deletion may be restricted by medical-record retention duties, other legal obligations, unresolved operational needs, or backup cycles. Specific retention periods and deletion procedures should be set out in the applicable service agreement.
8. Cookies and Similar Technologies
The Django application uses session and CSRF security cookies where needed for sign-in and protected form submissions. These cookies support core site and platform functionality.
The current application code reviewed for this policy does not show analytics or advertising trackers. The site loads fonts from Google Fonts and the Lucide icon library from unpkg; those providers may receive technical information such as your IP address and browser details when your browser requests those resources. Deployment or future changes may add other technologies, which should be reflected here.
9. User Rights and Choices
Depending on applicable law, individuals may have rights to request access to, correction of, or deletion of personal information, or to object to or restrict certain processing. Public-website enquiries may be directed to the privacy contact below.
For information held in a hospital workspace, contact the hospital that operates the account first. The hospital may need to verify your identity and determine whether a request can be fulfilled in light of clinical, legal, and record-retention obligations. We will assist the hospital as required by the applicable service arrangement and law.
10. Hospital and Healthcare Provider Responsibilities
Hospitals and healthcare providers are responsible for ensuring they have authority and a lawful basis to provide information to the HMS, giving any required notices, obtaining required permissions, maintaining accurate records, managing user access, and responding to patient requests as required by law. They must not enter information they are not authorized to process.
11. Third-Party Services
Depending on configuration, the service uses email delivery configured by the operator and may use Twilio to send SMS verification messages when Twilio credentials are enabled. The public pages load Google Fonts and the Lucide JavaScript library from their respective providers. These providers process information under their own terms and privacy notices.
The health-question feature reviewed for this policy uses a local knowledge base in the application. No external AI provider integration was identified in that feature. Hosting, database, backup, and other infrastructure vendors depend on the deployment and should be listed in the applicable hospital agreement.
12. Children and Patient Data Involving Minors
The public marketing website is not directed to children. The HMS may contain patient information about minors when entered by a hospital for legitimate care and operational purposes. Hospitals and healthcare professionals must follow applicable laws for minors, including rules on authority, consent, confidentiality, and access by a parent or guardian. The platform does not independently determine whether a particular user may access a minor's record.
13. International Data Transfers
The hosting region and all infrastructure locations have not been confirmed in the information available for this policy. Before production use, the service operator should identify the hosting and service-provider locations, determine whether information leaves the relevant country, and put any safeguards required by applicable law in place. Where international transfers occur, details and applicable safeguards should be added to the hospital service agreement and this policy.
14. Policy Updates
This policy may be updated when the service, legal requirements, or information practices change. The revised version and its update date will be posted on this page. Material changes will be communicated to account holders through an appropriate channel where required by law or the service agreement.
15. Contact Information
For privacy questions or requests relating to the public website, contact justonetechsolution@gmail.com. For patient information in an HMS workspace, contact the relevant hospital administrator first.
- Organization
- JustOne Health Care Solution
- Location
- Mumbai