Skip to main content
Tibacare

Data Protection & Privacy

Your information should be protected wherever care happens.

A plain-language guide to responsibility, access, hosting and privacy across Tibacare. It explains the practical boundaries. Our Privacy Policy explains how this website uses personal information.

How the boundaries work

Clear responsibility before information is accessed.

These principles explain the operating model in practical terms. They do not replace the rights, lawful-basis and retention detail in the full Privacy Policy.

UK protection as our baseline

A consistent baseline, with local requirements respected.

UK data-protection standards are Tibacare's baseline. A person's location is not a reason to provide less protection for their personal information.

Requirements connected with the relevant country, person, organisation and service must also be considered. UK standards do not replace applicable local law.

Who is responsible for information

Responsibility depends on why information is being used.

Tibacare is operated by Data Agile Ltd. Data Agile is generally a controller for its own platform purposes, such as accounts, service coordination, security, billing, network administration, clinician verification and Tibacare governance.

Where Data Agile hosts clinical information for a healthcare organisation or an independently practising clinician, it generally acts as a processor for that clinical content and follows the responsible controller's documented instructions.

Direct Tibacare services
Data Agile generally decides why necessary account, coordination, payment, security and governance information is used.
Hospital or healthcare organisation
The organisation generally controls its patient and case records; Data Agile provides the hosted technology and implements authorised access.
Independent clinical judgement
A clinician remains responsible for professional clinical content and record purposes they determine independently.

Clinical information stays under clinical responsibility

Technology does not transfer clinical accountability.

A healthcare organisation using Clinical Workspace remains responsible for the purposes of its patient and case records. Data Agile hosts and technically manages that information within the agreed service boundary.

Authorised Data Agile personnel may process or access clinical records only where necessary to provide, protect or support the agreed service. That technical responsibility does not give every Tibacare team member access or make Data Agile the clinical decision-maker.

An independent clinician remains responsible for their professional judgement, the clinical content they create and the professional obligations that apply to them.

Access follows responsibility

There is no network-wide view of clinical information.

Being part of Tibacare does not give a clinician access to every patient's information. Clinical Workspace information does not automatically become visible to the Tibacare Specialist Network.

When a specialist is authorised into a case, they receive only the relevant information through the approved clinical or collaboration workflow. The responsible clinical controller decides who should have access and for what clinical purpose; Data Agile enforces that decision technically.

UK-hosted by default

Core production infrastructure follows a UK-hosted model.

The approved production architecture places core databases, files, backups, logs, authentication and supporting service infrastructure in UK hosting regions, including Azure UK regions where applicable.

UK hosting describes where the core service is hosted. It does not mean authorised people can never access information from another country.

This public website is hosted separately, in Microsoft's West Europe region. Our Privacy Policy explains how the website handles personal information.

International expertise, controlled access

Cross-border access requires an approved route.

International access may occur only where it is necessary for the approved service and the applicable privacy, security, clinical-governance and data-transfer path has been reviewed.

A new country or cross-border clinical-data flow does not go live simply because the technology can support it. Local data-residency or transfer requirements must be addressed before launch.

No automatic secondary use

Technical possession is not permission for secondary use.

Clinical information is not sold or used for advertising. Hosting or transmitting it does not authorise unrelated analytics, AI or model training, unrelated product research, or another independent commercial purpose.

Any materially new purpose requires its own role, lawful-basis, sensitive-data, transparency, security, retention, clinical-governance and country review before use.

Privacy by design

Material change must pass privacy and access gates.

Tibacare applies role-based access, technical audit controls and defined country and transfer gates. Significant new clinical-data features and material processing changes require a privacy impact screening, followed by a full assessment where the screening shows one is required or appropriate.

These controls are designed to make responsibility and permitted use explicit before access is enabled, rather than relying on broad access after launch.

Your rights and questions

One front door for privacy rights and questions.

You do not need to decide whether Data Agile, a healthcare organisation or a clinician is responsible before asking for help. Tibacare's organisational contact route will signpost privacy requests so they can be identified and directed to the appropriate responsible party.

Depending on the circumstances, privacy rights can include asking for access, correction, deletion or restriction, objecting to certain uses, or asking for information to be transferred. These rights are subject to the law and the context in which the information is held.