FyzioDesk

Data Processing Agreement

Effective from 26 October 2026.

This agreement forms part of the terms of service and governs how FyzioDesk processes the personal data of a practice's clients under Art. 28 of Regulation (EU) 2016/679 (GDPR). It is based on the European Commission's standard contractual clauses (Implementing Decision 2021/915). The Slovak version is binding.

1. Parties

Controller — the practice (clinic, outpatient practice, independent therapist) that has ordered the FyzioDesk service. The practice's details are listed in the app under Settings.

Processor — Fellow Bytes s.r.o., Na Hôrke 54/40, 949 11 Nitra, Slovakia, Company ID 55274307, registered in the Commercial Register of the District Court Nitra, section Sro, file 59691/N. Data protection contact: info@fyziodesk.sk.

The agreement is concluded when the practice admin accepts it in the app or signs a written copy, and lasts for as long as the practice uses FyzioDesk. We will send a signed copy on request.

2. Subject matter and purpose

The Processor processes personal data only to provide the practice with the FyzioDesk service under the terms of service: calendar and booking, client records and medical documentation, exercise plans, client communication, invoices, the client portal and the features the practice turns on. Annex 1 describes the scope of processing.

3. Controller's obligations

  • It is responsible for the lawfulness of processing, including the legal basis, informing clients under Art. 13 GDPR and keeping medical documentation as required by law.
  • It enters into the service only the data it needs for its purpose.
  • It decides who in its team gets access and with which rights, and it turns optional features and integrations on.

4. Processor's obligations

The Processor:

  1. processes personal data only on documented instructions from the Controller. The instructions are this agreement, the terms of service and the settings the practice makes in the app. If it believes an instruction infringes the law, it says so without undue delay;
  2. does not use the data for its own purposes, sell it, use it for advertising or use it to train artificial intelligence models;
  3. binds the persons with access to the data to confidentiality that continues after their work for the Processor ends;
  4. takes the security measures under Art. 32 GDPR described in Annex 2;
  5. does not access client data without instructions. During support, the service operator sees client data only in anonymised form;
  6. helps the Controller handle clients' requests to exercise their rights (access, rectification, portability, restriction, erasure), mainly through app features: editing data, export and anonymisation;
  7. helps the Controller with security, breach notification and data protection impact assessments (Art. 32 to 36 GDPR), to the extent of the information available to it;
  8. provides the Controller with the information needed to demonstrate compliance with Art. 28 GDPR and allows audits under section 9.

5. Sub-processors

  • The Controller gives general authorisation for engaging sub-processors. The current list is in Annex 3.
  • We notify the practice admin by email at least 30 days in advance of any intended addition or replacement of a sub-processor. The practice may object within that period; if we cannot agree, it may terminate the agreement without penalty.
  • Every sub-processor is bound by a contract with the same data protection obligations as this agreement. We remain liable to the Controller for its performance.

6. Transfers outside the European Union

We store client data in the EU (Frankfurt, Germany). Data leaves the EU only for features the practice explicitly turns on, and only on the basis of an adequacy decision (EU–US Data Privacy Framework) or the European Commission's standard contractual clauses. Annex 3 lists those features.

7. Personal data breaches

  • We inform the practice admin of a breach affecting the practice's client data **without undue delay and no later than 48 hours** after becoming aware of it.
  • We describe what happened, which data and roughly how many clients are affected, the likely consequences and the measures taken or proposed. Whatever we do not know yet, we add as soon as we find out.
  • The Controller notifies the authority and the clients; we prepare the supporting information.

8. Termination, return and deletion

  • The practice can export its data at any time (Settings → Data transfer). Note that the practice must keep medical documentation for the period required by law even after the service ends — download it before leaving.
  • After the agreement ends, we hand the data over on request and delete it within 90 days, including backups once their retention period expires. We send the practice admin a notice before deletion.
  • Data we must keep by law ourselves (e.g. accounting records for the subscription) is kept only for the required period.

9. Audits

The Controller may verify compliance with this agreement, primarily by questionnaire or by requesting documentation of the security measures. On-site inspections are agreed with reasonable notice, at most once a year, and in a way that does not put other practices' data at risk; the requesting party bears the costs unless the inspection reveals a material breach.

10. Final provisions

  • If this agreement and the terms of service differ on data protection, this agreement prevails.
  • We notify the practice admin of changes by email at least 30 days before they take effect. A change required by law or by a decision of the authority may take effect sooner.
  • The agreement is governed by the law of the Slovak Republic.

Annex 1 — Description of processing

ItemDescription
Data subjectsthe practice's clients and their legal guardians; members of the practice team; contact persons such as the referring physician
Ordinary personal dataname, contact details, date of birth, national ID number, address, health insurer, appointments, invoices and payments, messages and communication, consents and signatures, exercise plans and adherence
Special categorieshealth data: diagnoses, contraindications, medical history, therapy notes, examinations, pain map, questionnaires, photos and attachments
Processing operationsstorage, viewing, editing, search, export, sending reminders and messages, backup, anonymisation and deletion
Durationfor the term of the agreement, then as in section 8
LocationEU (Frankfurt, Germany); exceptions in Annex 3

Annex 2 — Security measures

  • Practice separation — each practice's data is separated directly in the database (row-level security); the app connects to the database with an account that cannot bypass this separation.
  • Role-based access — admin, physiotherapist, reception, trainer and client have different permissions; by default a physiotherapist sees only clients with appointments at the clinics they are assigned to.
  • Sign-in — passwords stored as hashes (argon2id), two-factor sign-in for every user, short-lived access tokens, alerts on sign-in from a new device, rate limiting.
  • Encrypted transport — all communication over HTTPS. Integration credentials are encrypted in the database (AES-256-GCM).
  • Documentation is never overwritten — correcting a therapy note creates a new version; the original stays.
  • Audit log — sign-ins, exports, anonymisation, AI use and other important actions are recorded.
  • Operator access — during support, client data is shown anonymised and export and anonymisation are unavailable.
  • Backups — the database and files are backed up every night; each backup is verified and kept for 14 days.
  • AI — off by default; names, contact details, national ID numbers and other identifiers are removed from the text before sending; photos and attachments are never sent.
  • Updates — dependencies and server software are updated continuously; a backup is taken before every release.

Annex 3 — Sub-processors

WhoFor whatWhereWhen
OVH GmbH (OVHcloud)server, database, files, backupsFrankfurt, Germanyalways
WebSupport s.r.o.sending emails to clients (reminders, confirmations, consent requests)Slovakiaalways, unless the practice uses its own mail server
Anthropic, PBCAI features (summaries, note suggestions, report explanations)USA (EU–US framework or standard contractual clauses)only if the practice turns AI on

Integrations the practice turns on itself. With these, data goes to a service the practice has chosen and has its own contract with; they are not our sub-processors:

  • the practice's own mail server (SMTP),
  • Google Calendar sync — depending on the setting, either busy time only or also the client's name and the service,
  • the practice's payment gateways (Stripe, GoPay, Besteron),
  • AI assistants connected through an API key or connector (e.g. Claude) — they receive only the data the practice grants them access to; therapy notes, photos, attachments and consents are always excluded.