ClearFlow is an internal patient workflow management application used exclusively by staff at our dental clinic. It is not a public-facing application and is not accessible to patients.
This Privacy Policy applies to all personal data processed through the ClearFlow application, including data about patients and data about clinic staff who use the system.
For the purposes of GDPR, the dental clinic operating this system is the Data Controller. Google LLC (Firebase) is a Data Processor acting on our behalf.
We collect the minimum data necessary to operate the clinic workflow. All data collected has a clear, documented purpose.
| Data Item | Purpose | Lawful Basis |
|---|---|---|
| Patient name | Identifying the patient in the workflow queue | Legitimate interest (clinic operations) |
| Appointment time | Scheduling and queue management | Legitimate interest (clinic operations) |
| Treating dentist / radiographer | Assigning patients to the correct clinical staff | Legitimate interest (clinic operations) |
| Scanner / room assignment | Directing patients to the correct equipment | Legitimate interest (clinic operations) |
| Payment category | Billing and administrative processing | Contractual necessity |
| Clinical notes | Communicating relevant patient information between staff | Legitimate interest (patient safety) |
| Attached documents (T&C forms) | Recording signed consent forms and administrative paperwork | Legal obligation / Consent |
| Workflow status history | Audit trail of patient movements through the clinic | Legitimate interest (clinical governance) |
| Data Item | Purpose | Lawful Basis |
|---|---|---|
| Full name | Identifying staff in the system and audit logs | Contractual necessity (employment) |
| Email address | Authentication credential for login | Contractual necessity (employment) |
| Role | Controlling access permissions within the app | Contractual necessity (employment) |
| Actions taken (audit log) | Clinical governance, accountability and error investigation | Legitimate interest (clinical governance) |
| Chat messages | Internal team communication about patient workflow | Legitimate interest (clinic operations) |
As a dental clinic, we are legally required to retain patient records for a minimum of 6 years from the date of the last treatment, in accordance with the Dental Council of Ireland guidelines, the Health Service Executive (HSE) records management policy, and the Statute of Limitations. For patients who were minors at the time of treatment, records must be kept until the patient's 25th birthday (or 26th if the patient was 17 at the time of treatment).
ClearFlow is the daily operational workflow tool for the clinic. The detailed long-term patient records (clinical notes, X-rays, treatment histories) are maintained in the clinic's primary patient management system, not in ClearFlow. The data held in ClearFlow is limited to the scheduling and workflow information described in Section 2.
| Data Type | Retention Period | Legal / Regulatory Basis |
|---|---|---|
| Daily patient workflow records (name, time, scanner, payment, status history) |
6 years from date of last treatment | Dental Council of Ireland — Dental Records Guidance; HSE Records Management Policy; Statute of Limitations Act 1957 (Ireland) |
| Attached patient documents (T&C forms, signed consent forms) |
6 years minimum from date of signing. Consent forms relating to treatment: retain for the lifetime of the patient record. | Legal obligation — contractual and regulatory compliance |
| Records for minor patients | Until the patient's 25th birthday (or 26th if aged 17 at treatment date) | Statute of Limitations Act 1957 — extended limitation period for minors |
| Activity / audit log | 200 most recent entries (rolling); exported logs retained for 6 years | Clinical governance, accountability and regulatory inspection requirements |
| Chat messages | 500 most recent messages (rolling) | Operational communication — no long-term retention requirement |
| Staff account data | Duration of employment + 6 years | Employment law obligations; potential regulatory investigation requirements |
Access to ClearFlow data is controlled through a strict role-based permission system. Each staff member only sees and can act upon data relevant to their role.
| Role | Access Level |
|---|---|
| Receptionist | Can add and check in patients, view full queue, notify radiographer, mark missed, delete patients |
| Radiographer | Can view queue, call patients downstairs, mark missed. Cannot add or delete patients. |
| Downstairs | Can confirm patient arrival and complete second check-in. Can upload daily roster. Cannot add or delete patients. |
| Admin | Full access including staff account management, data export, and clearing records |
All data is transmitted over HTTPS (TLS encryption) provided by Netlify. All data is stored in Google Firebase (europe-west1 region — within the EU).
No patient data is shared with any third parties outside the clinic other than Google Firebase as our data processor (see Section 5).
We use the following third-party services to operate ClearFlow. All are GDPR-compliant and operate within or provide appropriate safeguards for EU data.
| Processor | Service | Data Location | GDPR Safeguard |
|---|---|---|---|
| Google Firebase (Google LLC) |
Real-time database, user authentication, file storage | europe-west1 (Belgium) 🇧🇪 | Google Cloud Data Processing Addendum (DPA) — must be signed in Google Cloud Console |
| Netlify Inc. | Web application hosting | CDN (global) / US origin | Netlify DPA available — sign at netlify.com/trust/gdpr |
| Google Fonts | Typography (DM Sans font) | CDN | No personal data transmitted. Font files only. |
Under GDPR, individuals whose data we hold have the following rights. These apply to both patients whose records appear in ClearFlow and staff members with accounts on the system.
To exercise any of these rights, contact the clinic's data controller using the details in Section 10. We will respond within 30 days. If you are not satisfied with our response, you have the right to lodge a complaint with your national data protection authority.
We have implemented the following technical and organisational measures to protect personal data:
In the event of a personal data breach, we will follow the procedure below in accordance with Article 33 of GDPR.
ClearFlow uses browser localStorage (not cookies) to store the following information on your device:
| Item | What it stores | Can be cleared |
|---|---|---|
| Theme preference | Your dark/light mode choice | Yes — resets on clearing browser data |
| Daily roster | The uploaded patient schedule for the current day | Yes — replaced each morning on upload |
| ID sequence | A counter for generating patient record IDs | Yes — resets to 1 on clearing browser data |
Firebase Authentication stores a secure session token in your browser's IndexedDB to keep you logged in. This is managed entirely by Google Firebase and is cleared when you sign out.
No advertising cookies, tracking scripts, or analytics are used in this application. ClearFlow does not use Google Analytics or any third-party tracking.
To exercise your data rights, report a concern, or make a data subject access request, please contact the clinic's Data Controller:
When making a data subject access request, please include your full name and enough information for us to identify your records. We may need to verify your identity before processing the request.