Legal
Sub-processors
Last updated 6 October 2026.
These are the companies whose services Medhank uses to run the platform and that may process personal data while doing so. Each receives only what its job needs and is bound to protect it.
Current list
| Service | What it does for us | Data it receives | Location |
|---|---|---|---|
| Contabo GmbH | The servers that run Medhank and its databases. | All data held in Medhank. | Europe (European Union) |
| Cloudflare, Inc. (R2 object storage) | Stores files: identity photos, captures taken at a warning, question images and organization logos. | Those files. Stored privately, opened only through short-lived links. | Asia-Pacific |
| Cloudflare, Inc. (R2 object storage, backups and logs) | Keeps off-site copies of Medhank’s databases in a private bucket, to restore after a failure, and a year of our web server’s and API’s logs. | All data held in Medhank’s databases, and the logs: IP addresses, browsers, and the pages asked for and when. | Asia-Pacific |
| Cloudflare, Inc. (Realtime TURN relay) | Relays the live proctor view between the candidate’s and the proctor’s browsers, including on networks that block a direct connection. | The live view’s audio and video, encrypted end to end so the relay cannot read them, and the two browsers’ IP addresses. Nothing is recorded or kept. | Cloudflare’s global network, at the location nearest each participant |
| Cloudflare, Inc. (Realtime SFU media server) | Where several staff may watch a candidate at once, forwards the live proctor view to each of them, so the candidate sends it once. | The live view’s audio and video, which it must decrypt to forward — encrypted in transit on both sides, but not end to end — and the browsers’ IP addresses. Nothing is recorded or kept. | Cloudflare’s global network, at the location nearest each participant |
| Functional Software, Inc. (Sentry) | Collects reports of errors in Medhank’s servers and in the staff consoles, so we can fix them. | What failed and where in our code, the page asked for (without its query) and the browser. Not answers, passwords, cookies, IP addresses or what was sent. | European Union (Germany) |
| Slack Technologies, LLC | Tells our engineers, in their team chat, when the API reports an error. | The error line from the API’s log, with email addresses, IP addresses and query strings removed. | United States |
| mailtr (mailtr.co) | Sends transactional email: invitations, sign-in links, password resets, reminders. | Recipient name and email address, and the contents of the message. | India |
| Google LLC | Only if you choose “Sign in with Google”. | The email address and name Google confirms to us. | United States and other Google locations |
How each is bound
Each sub-processor is bound to protections no weaker than our data processing agreement. Cloudflare, for its storage, its relay and its media server, processes personal data for us under the Cloudflare Data Processing Addendum, which forms part of our agreement with Cloudflare and includes its commitments on security, confidentiality and international transfers.
What is not on this list, and why
- Camera and microphone analysis, face counting and ID-card reading run on the candidate’s own device. No image or recording is sent to any third party to be analysed.
- The live proctor view goes through Cloudflare’s media server or relay, listed above, or a relay Medhank runs itself. The relays pass on media they cannot read; the media server decrypts it only to forward it to the staff watching. None of them records it.
- Medhank uses no analytics, advertising or tracking services.
Changes
We announce a new sub-processor on this page at least 30 days before it handles organizations’ data. To be told by email, or to ask about any of these, write to [email protected].