Contact for data requests: support@1clickaway.xyz ยท +971 55 602 7771
Requests are identity-verified and handled under applicable law and the relevant hospital agreement.
| Category | Data fields | Purpose | Deployment requirement |
|---|---|---|---|
| Marketing website visitors | Name, email, hospital name, message (contact form); anonymised usage data via Google Analytics (page views, session duration, browser type) | Respond to demo requests; understand which content is useful | Purpose and lawful basis documented before collection |
| Hospital staff accounts | Full name, role, department, mobile number (optional); FCM device token for push notifications; login timestamps | Account authentication, request dispatch, push notifications | Hospital instructions and signed service agreement |
| Operational requests | Room number, language required, department, request status, timestamps at each stage | Dispatch, tracking, audit reporting for the hospital | Hospital instructions and approved workflow |
Data minimisation: The platform is designed for operational coordination rather than clinical records. Patient identifiers, diagnoses, and treatment notes are not required fields. The deployment data inventory and staff training must prevent unnecessary clinical content from being entered into free-text fields.
| Data type | Retention period |
|---|---|
| Contact form submissions | Defined in the marketing data-retention schedule |
| Staff account data | Defined in the hospital agreement and deprovisioning procedure |
| Operational request records | Defined by the hospital's approved retention schedule |
| Website analytics, where enabled | Configured and documented before collection |
| Audit logs | Defined by security, legal, and operational requirements |
| Sub-processor | Location | Purpose |
|---|---|---|
| Google LLC (Firebase) | Deployment-specific | Authentication, operational datastore, and audit records |
| Google LLC (FCM) | Deployment-specific | Push notifications to approved staff devices |
| Google LLC (Analytics) | Configuration-specific | Marketing website analytics, where enabled |
| Supabase Inc. | Deployment-specific | Server-side notification relay |
| Vercel Inc. | Deployment-specific | Hosting and delivery of public application files |
| Formspree Inc. | Configuration-specific | Marketing contact forms, where enabled |
Data residency: No residency location is promised by this public notice. Hosting regions and transfer paths must be verified and committed in writing before a hospital deployment is approved.
- Analytics cookies are used on the marketing site only โ never inside the operational hospital app.
- No advertising or retargeting cookies are used.
- You can opt out of Google Analytics at any time via your browser settings or the Google Analytics Opt-out Browser Add-on.
- Access โ request a copy of the personal data we hold about you.
- Correction โ request correction of inaccurate or incomplete data.
- Deletion โ request deletion where the right applies, subject to legal and contractual retention duties.
- Restriction โ request that we limit how we use your data in certain circumstances.
- Portability โ request your operational data in a structured, machine-readable format.
- Objection โ object to processing based on legitimate interest.
- Supported production traffic is intended to use HTTPS/TLS in transit.
- Operational access is designed to be restricted by authenticated identity, hospital scope, and role.
- Vendor assurance evidence is reviewed as part of deployment due diligence.
- Production staff access is intended to be provisioned and deprovisioned by authorised administrators.