Last updated 26 August 2026
Privacy notice
This notice covers this website and the WeCare × MEDgo UK dental information-day registration process. It is written to make the brands’ different roles and the handling of health-related enquiry data clear.
1. Who uses your information
WeCare Dental Turkey manages this website, general enquiries, referral coordination and Antalya travel logistics.
For an accepted UK event request, the verified registration controller and authorised recipient are identified in the disclosure below. Authorised event users can access the shared lead record for booking coordination and follow-up.
The form includes one separate, optional and unticked consent for weekly event emails. It does not request SMS, WhatsApp or phone marketing permission.
2. Information we collect
The event form collects your name, UK mobile number, optional email, chosen city, preferred time, preferred contact method, confirmation that you can attend and that you are 18 or over.
The form does not collect treatment interests, diagnoses, symptoms, X-rays, medical histories or other clinical records.
We also record privacy and consent versions, registration source, UTM campaign fields, referrer, timestamps and security information needed to prevent abuse and duplicate submissions.
The public event form does not request X-rays, full medical history, identity documents or payment-card information. If a named treatment provider later needs clinical records, it must provide an appropriate secure clinical route and its own privacy information.
3. Why we use it
Contact and booking details are used to process your requested information-day registration or interest request, confirm or change a slot, answer your enquiry and keep an audit record of your required consent choices.
Request receipts and appointment-specific reminders at 72 hours and 24 hours are service messages for the event you asked to attend. Weekly upcoming-event emails are sent only when you tick the separate optional box.
4. Who receives it
Authorised WeCare and MEDgo users can access the shared registration panel according to their role. Hosting, security and communications suppliers may process limited data under written instructions.
A clinic or clinician receives your information only when needed for the referral, after the relevant role and privacy information have been explained. We do not sell event leads.
Event booking details are shared only with the authorised event team and contracted processors needed to operate the requested service.
5. Retention and security
The intended maximum for an event lead that does not become a patient record is 12 months after the relevant event, unless a shorter period is requested or a legal claim requires limited evidence to be retained. A named administrator must operate a documented review-and-deletion process.
Lead access requires an authorised role and a verified authenticator code. Status changes are recorded in an audit table; this release does not claim to audit every read. Public forms use validation, shared rate limiting and anti-abuse controls. Clinical files are not stored in the event lead panel.
6. Your choices and rights
You can ask for access, correction, deletion, restriction, objection, portability or withdrawal of consent where the relevant right applies. You may also complain to the UK Information Commissioner’s Office.
You may unsubscribe from weekly event emails at any time using the link in each weekly email. This does not cancel a requested or confirmed appointment or its necessary service messages.
Send a privacy request to [email protected]. We may need to verify your identity without collecting more information than necessary.
7. Cookies and measurement
Essential security and signed-in session storage may run without marketing consent. This release does not load non-essential advertising or analytics storage on the UK event registration pages and therefore does not present a cookie-preference widget there. If non-essential measurement is added later, it must remain off until a working consent control is implemented and you choose it.
We do not create advertising audiences from clinical information or other health data.
Request-service readiness disclosure
The request form remains visible for validation and readiness checks, but this environment must not accept or report a request as received until the verified controller, recipient and secure storage details are connected. If those details are not ready, the API returns an error and the request is not stored. The attributed WhatsApp route remains available for a minimal non-clinical enquiry.