Who this policy covers, and who it doesn't
QuiroFlow ("we", "us") is the software clinics use to run their practice. For a clinic's own patient data (appointments, clinical notes, billing, messages) the clinic is the data controller and QuiroFlow is its data processor under Art. 28 GDPR, acting only on the clinic's instructions. This policy describes what QuiroFlow itself does as a company: the account and staff data we hold directly, and our role as a processor. It does not replace the privacy notice each clinic gives its own patients; each clinic is responsible for that.
1. Who we are
Columnaquiro S.L., NIF B16365504, Calle Vivons 29, Bajo Izquierdo, 46006 Valencia, Spain. Contact: hola@quiroflow.com.
2. What data we process, and why
- Clinic staff accounts (name, email, role): to provide the service and manage access, under our contract with the clinic (GDPR Art. 6(1)(b)).
- Patient data entered by clinics (appointments, clinical notes, billing, messages, uploaded files): processed strictly on each clinic's instructions, as its processor. We do not decide why this data is collected or how it is used.
- Device and usage data (app opens, push-notification tokens): to operate and improve the mobile app.
- Location, in the patient app (precise and approximate location, including in the background): only if the patient uses place-based habit reminders (Cuidarme › Mis hábitos). The patient saves a place, such as home, and the app checks whether they are there, even when the app is closed or not in use, so that a habit reminds them only at that place. The app asks before using location, and the patient can decline and keep reminders by time. Saved places and location readings are kept and processed only on the phone: they are not sent to QuiroFlow, to the clinic or to anyone else, are not used for advertising, and are erased when the patient deletes the place or uninstalls the app. Legal basis: the patient's consent (GDPR Art. 6(1)(a)), which they can withdraw at any time in the phone's settings.
- Security and audit logs (staff sign-ins with IP address and device; who opened or changed which record, and when): to protect the clinic's data and let the clinic answer who accessed a patient's record (GDPR Art. 32; legitimate interest, Art. 6(1)(f)). Visible only to the clinic's owners.
- Error reports (the page and code location where the app failed, the browser, and the clinic and staff account IDs): to find and fix faults. Request bodies, search terms, cookies and IP addresses are removed before sending; no patient data is included.
- Support communications: to answer clinics that contact us.
3. Where data is hosted
The database and all files are hosted in the EU (Ireland), and the application servers run in the same region. Static parts of the web app (code, images) are delivered through Netlify's global network. How the data is protected is described in Security & data protection.
4. Subprocessors
We use the following subprocessors. Each has its own data processing terms; where data leaves the EU/EEA, the safeguard is shown.
- Supabase (Database, file storage and sign-in) — EU (Ireland), on Amazon Web Services; Data stays in the EU · Standard Contractual Clauses (EU 2021/914).
- Netlify (Application servers and delivery of the web app) — EU (Ireland) for the servers; global network for static files; EU-U.S. Data Privacy Framework.
- Resend (Email: reminders, invoices, documents) — United States; EU-U.S. Data Privacy Framework.
- Meta Platforms (WhatsApp) (WhatsApp messages and Facebook lead ads) — United States; EU-U.S. Data Privacy Framework.Only if the clinic connects WhatsApp or Facebook.
- Stripe (Card payments and subscriptions) — EU (Ireland) and United States; EU-U.S. Data Privacy Framework.
- Anthropic (AI receptionist and AI reply drafts) — United States; Standard Contractual Clauses (EU 2021/914).Only if the clinic turns these features on. Anthropic may not train models on this data, and deletes it within 30 days.
- Mistral AI (Transcribing WhatsApp voice notes for the AI receptionist) — EU (European Economic Area); Standard Contractual Clauses (EU 2021/914).Only voice notes, and only if the clinic turns the AI receptionist on.
- Google (Firebase, Google Wallet) (App push notifications; bono passes in Google Wallet) — United States; EU-U.S. Data Privacy Framework.
- Apple (Delivering notifications to iPhones and Apple Wallet) — United States; Apple Developer Program terms.Wallet updates are an empty signal; the pass itself is fetched from QuiroFlow.
- Sentry (Error reports) — EU (Germany); EU-U.S. Data Privacy Framework.No patient data: request bodies, searches, cookies and IP addresses are removed first.
5. How long we keep data
Staff account data is kept while the clinic's account is active. When the contract ends, we delete or return the clinic's data as the clinic instructs, except what the law requires to be kept (such as VeriFactu billing records). Patient data retention is set by each clinic in Settings › Privacy, in line with health-records law (Spain's Ley 41/2002 sets a minimum of 5 years for clinical records, longer in some regions); nothing is deleted without an owner deciding to.
6. Your rights
If you are a clinic staff member, write to hola@quiroflow.com to access, correct or delete your account data. If you are a patient, please contact your clinic: it is the controller of your health data and handles your request, and we assist it as its processor.
7. Security
Data is encrypted in transit (HTTPS) and at rest (AES-256). Each clinic's data is isolated by row-level security in the database, two-factor login can be made compulsory per clinic, and every change and every opening of a patient's record is kept in an audit log that cannot be edited or deleted. The full description is in Security & data protection.
9. Changes to this policy
We update the date at the top of this page when this policy changes and, for material changes, notify clinics directly.