Privacy policy
This is a drafting template, not legal advice. A UAE-qualified lawyer must review it against the Federal Decree-Law on Personal Data Protection and MOHAP health-data rules before launch. Placeholders in square brackets need real answers from the clinic.
Who we are
FertiClinic Fertilization Centre, Sahara Healthcare City, Al Nahda, Sharjah, UAE. For any privacy question, contact fertisharjah@ferticlinic.ae.
What we collect
Through the appointment request form we collect your name, mobile number, the service you selected, your preferred branch, doctor, date and time. We also record the date of your request, your IP address and browser information, and any campaign parameters in the link you arrived through.
Why we collect it
Solely to contact you and arrange your appointment, and to keep an internal record of that contact. Submitting the form does not create a medical record; clinical records are created only if you attend the clinic.
Who can see it
Only authorised clinic staff whose role grants appointment access. Every view and change is logged against a named individual account. We do not sell your data and do not share it with advertisers.
Marketing and advertising tools
We use website analytics and advertising measurement tools. These record anonymous page activity, not the contents of your appointment request. Personal details you type into the form are never sent to advertising platforms.
How long we keep it
Appointment requests are retained for [retention period — clinic to confirm], after which they are deleted or anonymised. Requests that become patient records fall under the clinic medical records retention policy.
Your rights
You may ask what we hold about you, ask us to correct it, or ask us to delete it where no medical or legal obligation requires us to keep it. Email fertisharjah@ferticlinic.ae and we will respond within [timeframe].
Security
Data is transmitted over an encrypted connection, stored in an access-controlled database, and reachable only through individual staff accounts with role-based permissions. Passwords are stored as one-way hashes.
Last updated: 29 Oct 2026