MediBridge
Privacy & data

Know what you share—and what stays out.

A plain-language notice covering the information this site collects, why it is used, where sharing can occur, and the choices available to you.

Last updated
Notice status
Operational draft · Legal review pending

Before you share information

Three boundaries to know now.

Optional analytics
They stay off until you accept. Core website and coordination paths still work if you decline.
Data minimisation
The assessment does not request record uploads or full payment-card details.
Analytics boundary
Form answers, names, contact details, and medical details are not analytics events.

Privacy notice

How MediBridge handles website information.

This draft applies to the website, assessment, checkout, booking, and messaging journeys. Launch contacts, retention periods, providers, transfer safeguards, and legal bases remain pending verification or counsel review where stated.
01

Who is responsible

MediBridge Limited is responsible for information submitted through this website. The company registration number and launch contact details are still pending client verification and legal review.

02

Information we collect

Depending on the feature you use, we may collect:

  • Assessment. Name, email, optional phone number, country, procedure of interest, optional self-reported summary, budget band, and preferred travel window.
  • Checkout and booking. Package choice, email, provider references, payment status, and the name, email, and time supplied to the scheduler.
  • Messaging. Channel identifier, messages, and the optional intake details you provide through WhatsApp or Telegram.
  • Direct contact. Messages and files you voluntarily send to the coordination team.
  • Optional analytics. Consent state and code-only interaction events after you accept optional analytics cookies. Form values are not sent in analytics events.

The website assessment does not request medical-record uploads, a formal diagnosis, or full payment-card details. Card details are entered on the payment provider's hosted checkout and are not stored by MediBridge.

03

Why we use it

We use information to answer enquiries, prepare and deliver requested administrative coordination, arrange appointments and travel logistics, process payments, prevent abuse, keep service records, and improve the website where consent permits. We do not use website submissions to diagnose, prescribe, or make treatment decisions.

04

Service providers and transfers

Information may be handled by providers supporting hosting, email, payments, scheduling, analytics, and the hospitals or logistics providers involved in a request. Cross-border coordination can require information to move between countries. The launch version must identify the contracted providers, transfer safeguards, and applicable legal bases after counsel review.

05

Retention and security

Records currently remain until an authorized administrator or database operator removes them. Launch-specific retention periods, deletion schedules, and handling procedures are pending legal approval. We use access controls and transport encryption, but no online system can be guaranteed completely secure.

06

Your choices and contact

You can decline optional analytics cookies. Subject to the law that applies to you, you may also have rights to request access, correction, deletion, restriction, portability, or to object. Contact hello@medibridge.example. The verified launch contact and response procedure remain pending client confirmation.