Privacy policy
Mabaniq is a real-estate development platform by Jadwa for Studies & Development. The platform processes each developer's customer data on the developer's behalf (the developer is the controller, the platform the processor), and collects from visitors of these public pages only what is needed to answer a live-demo request.
1. Privacy notice for developers' customers
Version 1.0 · Effective since 2026-10-09
Controller and processor: المطوّر (المتحكم) عبر منصة مبانيك (المعالج)
Purposes
- تنفيذ عقد الحجز والبيع وتحصيل الأقساط
- التحقق من الهوية ومكافحة غسل الأموال
- خدمة ما بعد البيع والضمان واتحاد الملاك
- الالتزامات النظامية (الضريبة، حساب الضمان، نقل الملكية)
Data processed
- الاسم والهاتف والبريد
- وثيقة الهوية ورقمها وتاريخ انتهائها (مشفَّرة)
- تاريخ الميلاد والجنسية
- سجل السداد والعقود والمراسلات
Retention: مدة العقد ثم المدة التي يفرضها القانون للسجلات المالية والعقارية؛ وما عداها يُحذف أو يُخفى هويته عند الطلب
Your rights
- الاطلاع ونسخة من البيانات
- التصحيح
- الحذف أو إخفاء الهوية لما لا يلزم حفظه نظامًا
- سحب الموافقة لما لا يقوم على العقد أو القانون
Applicable law: قانون حماية البيانات الشخصية الصادر بالمرسوم السلطاني 6/2022 ولائحته التنفيذية
Contact: مسؤول حماية البيانات لدى المطوّر — يُستكمل عند التشغيل الفعلي
2. The “Request a live demo” form on this site
- What we collect: name, company, e-mail, phone, number of projects and an optional message.
- Why: only to contact you about the live demo you asked for. Never used for bulk marketing, never shared with third parties.
- Where: stored in the platform database and a copy is e-mailed to the Jadwa sales team.
- How long: 365 days from the request, then deleted automatically by the retention policy. You may ask for earlier deletion by replying to the contact e-mail you receive.
- No account is created from this form, and the full IP address is not stored (only a short hash, for abuse prevention).
3. Cookies and tracking
- The public pages (home, Arabic version, this policy) set no cookies and use no third-party analytics or advertising tools.
- After sign-in only strictly necessary session cookies are used (HttpOnly, for security); they end on sign-out or inactivity.
- No fonts, scripts or images are loaded from any external host; everything is served by the platform itself.
4. Security
- Identity data is encrypted in the database, and every developer is isolated at the database row level.
- Every change is written to a hash-chained audit log that cannot be edited or deleted.
- HTTPS only, with documented security headers (a CSP without inline scripts or external hosts).