Privacy Policy
Anaesthesia Companion — How your data is handled
Application: Anaesthesia Companion
Developer: Danial Hussain
Contact: hussain.danial@gmail.com
Last updated: May 2026 (v2.1.0)
1. Overview
Anaesthesia Companion is an independent clinical reference app for clinicians and trainees. This privacy policy explains what information this application collects, how it is used, and your rights in relation to it.
2. What Data We Collect
Data We Do NOT Collect
- No patient names, dates of birth, hospital numbers, or any other patient identifiers
- No personal details of the user (name, email, staff ID)
- No location data
- No usage analytics, page views, or behavioural tracking
- No cookies for tracking or advertising purposes
- No data is sent to any third-party analytics or advertising platform
Data Stored Locally on Your Device Only
The following minimal information is stored in your browser's session storage (cleared automatically when you close the browser or tab):
- Professional use acknowledgment: A flag recording that you confirmed the professional use notice during the current session. This is stored on your device only and is never transmitted.
Progressive Web App (PWA) Cache
If you install this app as a PWA (Add to Home Screen), your browser caches application files (HTML, CSS, JavaScript, images) locally to enable offline access. No personal or patient data is included in this cache — only static application files.
3. Calculator Inputs
All clinical calculator inputs (patient weight, age, laboratory values, clinical scores) are processed entirely within your browser. They are:
- Never transmitted to any server or external service
- Never stored beyond the current browser session
- Never logged by the application or its hosting infrastructure
4. AI Features
Some features in this application use an AI language model (OpenAI GPT-4) to generate educational content. When you use these features:
- The text you type into an AI tool input field is sent to the OpenAI API to generate a response.
- You must not include any patient-identifiable information in AI tool inputs.
- OpenAI processes requests in accordance with their own Privacy Policy and Data Processing Agreement. OpenAI does not use API inputs to train their models (as per OpenAI API terms).
- No AI inputs or outputs are stored by this application.
For more information, see OpenAI's Privacy Policy.
5. Legal Basis for Processing (GDPR)
As no personal data is collected or processed by this application in normal use, GDPR obligations are satisfied by design. In the limited context of AI tool use where a user voluntarily submits text:
- Lawful basis: Article 6(1)(f) GDPR — legitimate interests of the developer in providing a clinically useful reference tool to healthcare professionals.
- Data Controller: Danial Hussain (individual developer)
- Data Processor (AI features): OpenAI, LLC, USA — subject to Standard Contractual Clauses for international data transfers.
6. Your Rights
Under GDPR you have the right to access, rectify, erase, restrict, and port any personal data held about you, and to object to processing. Because this application stores no personal data, these rights are satisfied by design.
To raise a concern or exercise any right, contact hussain.danial@gmail.com. You also have the right to lodge a complaint with your national data protection supervisory authority (e.g. the Data Protection Commission in Ireland).
7. Data Security
- The application is served over HTTPS — all data in transit is encrypted using TLS 1.2 or higher.
- No database of user or patient information exists within this application.
- The application is hosted on a secure cloud platform.
- Any suspected security concern should be reported to hussain.danial@gmail.com.
8. Children's Privacy
This application is intended exclusively for qualified healthcare professionals and supervised trainees aged 18 and over. It is not directed at, and does not knowingly collect data from, individuals under the age of 18.
9. Changes to This Policy
This privacy policy may be updated when new features are added or when requirements change. The version number and date at the top of this page will reflect the most recent revision. Continued use of the application following a policy update constitutes acceptance of the revised policy.