Access boundary
No access is requested to patient record systems or medical archives.
Medical-tourism agency service
Data Security and Patient Privacy
As an agency we do not access patient data. Our work runs at anonymous flow and process level. Where access to institutional systems is required, the scope is limited in writing, access is time-bound and it is removed when the work ends.
The greatest risk for an agency working with healthcare institutions is unknowingly touching special-category data. We prefer to remove that risk structurally.
What we access and what we do not
We access: the site administration panel, analytics accounts, advertising accounts, content files and anonymous process data. We do not access: patient record systems, medical image archives, patient correspondence history or any record containing identity information.
Even in work such as a CRM build we do not request access to fields containing personal data; configuration runs on test records.
Security practices we apply
- Written, time-bound access scope, removed when the work ends
- Individual, permission-limited accounts rather than shared logins
- Two-step verification in use
- Files containing patient data never brought into the agency environment
- Working files held in access-controlled environments
- Files and access closed at the end of the engagement
The arrangement we recommend on the institution side
A similar discipline is needed internally: which team member accesses which data, where images arriving through messaging channels are saved, and what the retention periods are must all be defined.
Without that arrangement, every precaution on the agency side remains partial. That is why we recommend the data-flow map early in the engagement.
Boundary of responsibility
The agency does not assume the institution's data controller obligations. The privacy notice, consent structure and retention policy are the responsibility of the institution and its legal advisor.
Our role is to make the data-collecting points in communication channels visible and to implement the technical work within the framework the institution defines.
Time-bound rights
Access scope is written, time-limited and removed when the work ends.
Institutional responsibility
Data controller obligations stay with the institution; the agency does not assume them.
Working sequence
How we move, step by step
- 01Access plan
Which system, with which permission and for how long, written down.
- 02Secure setup
Access opened with individual accounts and two-step verification.
- 03Data map
Data-collecting points on the institution side made visible.
- 04Technical implementation
Consent flows implemented within the framework the institution defines.
- 05Closure
Access removed and files handed over at the end of the work.
Frequently asked questions
What institutions ask most about this
Do you see patient data during a CRM build?
No. Configuration runs on test records. Where real records must be touched, the institution does it with its own team.
Does the agency act as a data processor?
The processor role varies with the scope of the work. Your data protection lead should make that assessment and, where needed, a written framework should be established.
Is analytics setup risky for data protection?
Data-protection risk depends on configuration. Consent, retention period and cross-border transfer conditions are manageable when set correctly, and are configured with your approval.
Where are our files stored?
In access-controlled institutional environments and only for the duration of the project. Files are handed over when the engagement ends.
How is your team authorised?
Individual accounts, task-based permissions and two-step verification. No shared accounts are used.
What happens in the event of a data breach?
We report any incident we detect on our side to the institution without delay. Meeting notification obligations is a process the institution runs as data controller.
Next step
Let us define the access scope upfront
Share the systems we will work with and we will define the access plan together.