← QuiroFlow

Security & data protection

Last updated: 29 October 2026

QuiroFlow holds clinical records, so we treat security as part of the product rather than an add-on. This page describes what the system does today, so your clinic can rely on it and quote it in its own records of processing.

Where your data is

  • The database and every file (clinical notes, documents, photos, invoices) are stored in the European Union, in Ireland, on Amazon Web Services infrastructure run by Supabase.
  • The application servers that read and write that data run in the same region, Ireland.
  • Supabase holds SOC 2 Type 2 and ISO 27001 certifications for the platform our database runs on.
  • Some features the clinic chooses to use (email, WhatsApp, the AI receptionist) send the message itself through providers outside the EU. They are all listed below, with the legal safeguard each one uses.

Encryption

  • In transit: every connection, from the browser, the mobile app and between our servers, uses HTTPS (TLS).
  • At rest: the database, the files and the backups are encrypted with AES-256.
  • Clinical documents, posture photos, invoices and WhatsApp attachments are kept in private storage. They open only through temporary links that expire within minutes to an hour.
  • Digital certificates uploaded for VeriFactu are encrypted again by QuiroFlow (AES-256-GCM), with a key kept apart from the database.
  • A document sent to a patient by email can be protected with a password (AES-256 PDF).

Who can see what

  • Each clinic is isolated in the database itself (row-level security). The rules live in the database, not only on screen, so one clinic's staff cannot reach another clinic's data even by calling the API directly.
  • Inside a clinic, roles and permissions decide what each team member sees and does: for example, a role can work the diary without seeing amounts owed.
  • Clinic settings such as fees or message templates can only be changed by someone with that page's permission, and the database checks it on every change.
  • Patients using the app or the portal see only their own appointments, documents and bonos.

Signing in

  • Two-factor login with an authenticator app is available to every team member, and a clinic's owner can make it compulsory for the whole team.
  • It is enforced by the database: when two-factor applies, a password alone, even a stolen one, reads nothing.
  • Passwords are never stored, only a one-way hash of them (bcrypt).

Activity log

  • Every change to patient records, clinical notes, billing, team permissions and settings is recorded with the values before and after, and who made it.
  • So is every opening of a patient's record or files, every export, every sign-in and every change of password or two-factor.
  • The log cannot be edited or deleted. The clinic's owners read it in Settings › Activity log, which lets the clinic answer exactly who accessed a patient's record.

Backups and availability

  • The database is backed up automatically every day, and the last 7 days of backups are kept.
  • Files are kept in Amazon Web Services object storage, which stores each one redundantly across several data centres in the region.
  • Errors are reported to us automatically as they happen, without any patient data in them.

Retention and patients' rights

  • The clinic decides how long clinical records are kept (at least 5 years, as Ley 41/2002 requires) in Settings › Privacy. Nothing is deleted by itself: a record past its period is anonymised only when an owner decides to.
  • Invoices sent to VeriFactu are kept even if the patient is deleted, because tax law requires it.
  • The clinic can export its patients at any time, and answer access, rectification and erasure requests from the patient's record.

QuiroFlow's own access

  • The clinic is the data controller and QuiroFlow is its data processor (Art. 28 GDPR): we process patients' data only to provide the service, on the clinic's instructions, and never for our own purposes.
  • Our internal control panel shows billing and counts (how many patients or appointments), never a patient's record.
  • Technical access to the database is limited to the people who run the service, and is used to keep it working or to solve a problem the clinic has asked us about.

Providers that process data (subprocessors)

Each one works under a data processing agreement. Where data leaves the EU, the transfer is covered by the safeguard shown.

  • SupabaseEU (Ireland), on Amazon Web Services

    Database, file storage and sign-in

    Data stays in the EU · Standard Contractual Clauses (EU 2021/914)

  • NetlifyEU (Ireland) for the servers; global network for static files

    Application servers and delivery of the web app

    EU-U.S. Data Privacy Framework

  • ResendUnited States

    Email: reminders, invoices, documents

    EU-U.S. Data Privacy Framework

  • Meta Platforms (WhatsApp)United States

    WhatsApp messages and Facebook lead ads

    EU-U.S. Data Privacy Framework · Only if the clinic connects WhatsApp or Facebook

  • StripeEU (Ireland) and United States

    Card payments and subscriptions

    EU-U.S. Data Privacy Framework

  • AnthropicUnited States

    AI receptionist and AI reply drafts

    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 AIEU (European Economic Area)

    Transcribing WhatsApp voice notes for the AI receptionist

    Standard Contractual Clauses (EU 2021/914) · Only voice notes, and only if the clinic turns the AI receptionist on

  • Google (Firebase, Google Wallet)United States

    App push notifications; bono passes in Google Wallet

    EU-U.S. Data Privacy Framework

  • AppleUnited States

    Delivering notifications to iPhones and Apple Wallet

    Apple Developer Program terms · Wallet updates are an empty signal; the pass itself is fetched from QuiroFlow

  • SentryEU (Germany)

    Error reports

    EU-U.S. Data Privacy Framework · No patient data: request bodies, searches, cookies and IP addresses are removed first

VeriFactu

Every invoice produces a chained, tamper-evident billing record that the database refuses to modify or delete. What QuiroFlow declares as the producer of the system is published in its responsible declaration.

Questions and reporting a vulnerability

Write to us at hola@quiroflow.com, for questions about this page, for the data processing agreement, or if you believe you have found a security problem. We answer security reports first.

Columnaquiro S.L. · B16365504 · Calle Vivons 29, Bajo Izquierdo, 46006 Valencia

Privacy policyTerms of service