1.Status, scope and definitions
1.1This is a review draft, not an approved or effective policy. It describes verified website functions and a proposed framework for professional engagements. Statements about future or unverified practices are conditional. The confirmation items in section 23 must be resolved before adoption; this document does not certify compliance with every law mentioned.
1.2Personal data means information relating to an identified or identifiable individual. Processing includes collecting, recording, organising, accessing, using, disclosing, transferring, retaining and deleting such information. A controller determines processing purposes and means; a processor acts on a controller’s behalf. Sensitive or special-category data has the meaning given by the applicable law, which may differ between jurisdictions.
2.Organisation and privacy contact
2.1MENA ADVISORS is a UAE-established international professional advisory business operating at Dubai CommerCity, Umm Ramool, Building B1, Office 108, Dubai, United Arab Emirates. Where it determines purposes and means, it acts as controller. [CONFIRM BEFORE ADOPTION: full registered legal entity name and the identity of any other controller involved in an engagement.] No registration number, designated data protection officer or overseas representative is asserted here.
2.2Privacy enquiries and rights requests may be addressed to info@mena-advisors.com, by telephone on +971 4 410 1151, or by post to the address above. Website: www.mena-advisors.com. A dedicated mailbox, privacy@mena-advisors.com, is recommended but is not confirmed as operational; use the general email until its creation and monitoring are confirmed.
3.Applicable legal regimes
3.1UAE Federal Decree-Law No. 45 of 2021 on Personal Data Protection is the principal federal framework potentially applicable to this UAE business. Its territorial and material scope, exclusions and any operative implementing measures must be assessed for each activity. Sector-specific rules, including health, banking, cybersecurity and electronic communications requirements, may apply separately. Dubai data-governance rules do not automatically subject every private business to every Dubai data law.
3.2DIFC Data Protection Law No. 5 of 2020, as amended, and ADGM Data Protection Regulations 2021 apply only where their respective scope is met; a Dubai address alone does not establish their application. EU GDPR may apply through an EU establishment or relevant offering of goods or services to, or monitoring of, individuals in the EU. UK GDPR and the Data Protection Act 2018, as amended including relevant commenced provisions of the Data (Use and Access) Act 2025, require a separate assessment. Website availability alone does not establish EU or UK targeting.
3.3Other potentially relevant regimes include Saudi Arabia’s PDPL and implementing and transfer regulations; Bahrain Law No. 30 of 2018; Qatar Law No. 13 of 2016; Oman Royal Decree 6/2022 and its Executive Regulations; and Kuwait’s applicable CITRA data-privacy and sector-specific rules. Their application depends on establishment, residents or individuals concerned, processing locations and statutory scope. Other national laws and European implementing legislation may also apply. [CONFIRM: engagement-by-engagement applicability, registrations, representatives and permits; no universal compliance representation is made.]
4.Individuals covered and sources
4.1This framework covers website visitors, prospective, current and former clients, company representatives, directors, shareholders and beneficial owners, employees and applicants, suppliers, business partners, investors, counterparties, professional advisers, service providers and people whose data clients provide. It also covers users of AI chat features. Personal data may come directly from individuals, authorised representatives, clients, public registers, lawful public sources and other professional or lawful third-party sources.
4.2Clients supplying another person’s data should have authority to do so, supply only relevant information and provide required notices or permissions under applicable law. Where indirect-collection notice obligations apply, the relevant controller must meet them, subject to lawful exceptions such as protected professional confidentiality. Providing data does not by itself establish an engagement or legal professional privilege.
5.Categories of personal data
5.1Depending on the service, identification and contact data may include names, addresses, email, telephone, professional details, nationality, residence and necessary passport or identification records. Corporate data may include directorships, shareholdings, beneficial ownership, structures, registration and licensing records, business correspondence, contracts, investments, transactions and counterparty information. Financial and tax data may include banking details, accounts, financial statements, tax identifiers, VAT records, transaction records and legally required source-of-funds or source-of-wealth evidence.
5.2Employment and HR records may include CVs, qualifications, work history, payroll, employee identifiers, visas, immigration documents and work permits. Legal and regulatory materials may include contracts, corporate records, litigation and arbitration materials, filings, compliance and due-diligence records, investigations, claims and disputes where lawfully handled. Public website forms are not designed to receive this full range of engagement documents.
5.3Website-related information includes submitted contact and project details, correspondence, chatbot prompts and replies, selected advisor and language, and any information a user includes in a message. Hosting, authentication or security services may process IP addresses, access records and technical logs; their precise retention requires confirmation. This must be distinguished from Lovable’s visitor analytics, which does not retain IP addresses or identify visitors. Browser storage is described in section 9.
5.4Certain engagements may involve health, biometric, criminal-offence or other sensitive information, but routine collection of such data is not confirmed. Processing must have a valid general lawful condition and every additional condition, authorisation or permit required by the relevant law. Under EU GDPR, Article 9 requires a separate special-category condition; criminal-offence data is governed by Article 10. An Article 6 basis alone is insufficient for Article 9 data.
5.5Do not submit unnecessary sensitive data, confidential client documents, passwords, banking credentials or legally privileged information through public AI chats or general enquiry fields. Confidential engagement material should use a channel agreed with the responsible professional. Contractual confidentiality obligations and any legally applicable privilege are distinct from data-protection obligations and cannot be assumed from a chatbot interaction.
6.Processing purposes and lawful conditions
6.1Enquiries, consultations and client administration: to respond, assess requirements, arrange meetings and manage relationships. Under EU GDPR, contractual necessity applies only where the individual is a contracting party or requests pre-contractual steps; corporate contacts may instead require balanced legitimate interests or consent. Advisory delivery, incorporation, licensing, restructuring, tax, accounting, HR, payroll, immigration, PRO work and contract administration may rely on contractual necessity, relevant legal obligations or appropriately assessed legitimate interests, depending on the actual activity and individual.
6.2Due diligence, statutory filings and regulatory compliance require assessment of applicable legal duties; fraud prevention, information security and necessary business administration may rely on balanced legitimate interests under EU GDPR where permitted. Disputes, arbitration, litigation support and protection of claims may require contractual, legal-obligation or legitimate-interest grounds, with Article 9(2)(f) considered only where its conditions for special-category data are met. Recruitment, suppliers and partners require contract, legal-obligation or legitimate-interest analysis as appropriate.
6.3Website operation, troubleshooting and optional AI assistance may involve legitimate interests or consent under EU GDPR, subject to necessity, balancing and applicable device-storage rules. Marketing requires the appropriate consent or other lawful ground together with local electronic-marketing requirements. Consent is not a universal basis. Vital interests apply only in genuine qualifying situations; public-task processing is not asserted for ordinary consultancy activities. UK bases and exceptions must be checked against its amended law, not assumed identical to EU GDPR.
6.4Under UAE PDPL, consent and the specific exceptions in Article 4 must be assessed on their own terms, including necessary contractual steps, employment-related obligations, legal claims and duties imposed by other laws where the statutory conditions are met. A GDPR-style legitimate-interest basis must not be imported into UAE federal law. Saudi and other GCC regimes require their own consent, necessity, lawful-interest or statutory-exception analysis; restrictions on sensitive data and marketing differ. [CONFIRM: documented purpose-by-purpose bases before adopting this framework.]
7.Controller and processor responsibilities
7.1MENA ADVISORS may be controller for its website enquiries, business relationships, recruitment and suppliers, and processor for particular client-directed accounting, HR, payroll or administration tasks. Some professional advisory processing may remain independent-controller processing even when commissioned by a client. Roles follow the substance of each operation, not contractual labels alone; joint determination may require a joint-controller arrangement.
7.2Where acting as processor, the applicable agreement should address documented lawful instructions, confidentiality, security, sub-processor authorisation and equivalent obligations, assistance with rights requests and breaches, audit information and return or deletion on termination subject to lawful retention. Requests relating to client-controlled data may be referred to that client. Separate engagement, confidentiality and data-processing agreements supplement this notice; their existence and terms require confirmation and cannot remove mandatory individual rights.
8.Artificial Intelligence, Automated Technologies and AI-Powered Services
8.1The public website provides AI advisor personas and a concierge chatbot, not live human conversations. Prompts, conversation context, selected advisor and language are sent through Lovable AI Gateway to a Google Gemini model to generate replies. The current chat request includes up to the latest 24 messages. The website stores up to 60 messages per selected language in your browser. A consultation request also attaches an excerpt of up to 12 recent messages, limited to 8,000 characters, to the stored request. Clearing browser history does not erase an already submitted consultation record or copies held by providers.
8.2These tools provide general information, routing and assistance. Replies are not formal legal opinions, tax or accounting advice, or professional recommendations, and do not replace individual professional assessment. Human review of every public chatbot response is not implemented or promised. Professional advice requires a separate human-led engagement. The inspected website does not implement solely automated decisions producing legal or similarly significant effects; where such processing is introduced, applicable safeguards, human intervention and challenge rights must be assessed, including EU GDPR Article 22 where applicable.
8.3Third-party AI processing may involve overseas access, provider logging and generated information. [CONFIRM BEFORE ADOPTION: contractual provider identities and roles, processing countries, retention, sub-processors and whether prompts or outputs may be used for model training or service improvement.] No claim is made that chats are anonymous, legally privileged, end-to-end encrypted or automatically deleted. Optional internal AI research, analysis or document organisation must be separately assessed for minimisation, purpose limitation, confidentiality, security and oversight. EU AI Act obligations depend on scope, role, use case and applicable commencement dates, not merely use of AI by a UAE company.
9.Cookies, browser storage and preferences
9.1The inspected public pages do not implement an advertising pixel, Google Analytics tag, embedded social-media feed or cookie-consent banner. Google Fonts stylesheets are loaded from Google; your browser sends connection information, including IP address and browser request information, to Google when fetching them. Images and brochure files load from content-delivery services; publication documents are retrieved through temporary signed URLs. These services may receive network requests and associated technical information; their contractual roles, logs and hosting locations require confirmation.
9.2Functional local storage remembers your language under mena-language and chat history separately for English, Arabic and German. These entries have no automatic expiry in the current code and remain until removed, replaced or cleared by your browser. Team sign-in uses persisted authentication storage managed by Lovable Cloud; it is needed to maintain an authenticated team session. Authentication-provider logs and session lifetime require confirmation. Local storage is a similar technology to cookies for device-access rules, even though it is not an HTTP cookie.
9.3Necessary technologies support requested sign-in and essential functions; functional technologies retain preferences or requested chat continuity. Analytics and performance technologies measure use or reliability; advertising technologies support targeting; third-party cookies originate from another provider. These categories do not mean every category is currently deployed. Applicable law determines whether prior consent, an exemption or an opt-out is required. Before introducing optional cookies or tracking, the firm must assess those requirements and implement a genuine preference mechanism where required. The controls below clear only local language and chat records; they are not analytics consent settings and do not stop cookie-free visitor counting. Browser settings can manage cookies and site data; blocking necessary storage may impair sign-in.
Browser storage settings
This is not an analytics opt-out.
10.Lovable visitor analytics
10.1Lovable’s visitor analytics and click tracking are enabled for the published site. With no consent banner connected to Google Consent Mode, page visits and clicks are recorded for every visitor. It records visited pages, referral sources, country, browser, operating system, device type, time on site, page-load speed and errors. The app also reports exceptions; no separate custom business-event sending was found in the inspected code. The editor preview is not counted.
10.2This analytics uses no cookies, stores nothing on the visitor’s device, does not keep IP addresses and does not identify visitors. Page visits, time on page, page speed and errors are recorded for every visitor without cookies and without identifying anyone. Detailed analytics data is kept for 90 days and daily summaries for a year. Lovable collects this data for us. Lovable’s privacy policy explains how it handles it. This analytics disclosure does not mean that contact forms, chat storage, authentication or other website services collect no personal data.
11.Disclosure and recipients
11.1Where necessary and lawful for an engagement, recipients may include clients and authorised representatives, licensing and registration bodies, tax authorities, regulators, courts, tribunals and dispute-resolution bodies, banks, insurers, external legal advisers, accountants, auditors, professional consultants and HR, payroll or recruitment providers. IT, cloud, content-delivery, authentication and AI providers may support website or business processing. Affiliated entities or network partners are not automatically entitled to all client data; any sharing must have a specific lawful purpose and appropriate authority.
11.2A recipient may be a processor subject to instructions, an independent controller with its own statutory duties, or an authorised third party. Appropriate agreements, confidentiality restrictions, minimised disclosure and transfer safeguards must be assessed for the recipient’s role. Disclosure may be required by law or valid official process, or permitted to establish or defend claims; confidentiality and privilege restrictions remain relevant. [CONFIRM: complete supplier register and contractual safeguards.]
12.International and cross-border transfers
12.1International engagements may involve overseas hosting, cloud and AI services, remote access from another country, external advisers, authorities, client-authorised recipients and approved sub-processors. A transfer includes qualifying access from abroad, not only moving a file. International business activity or a client instruction is not itself a transfer authorisation. [CONFIRM: actual hosting and processing countries, recipient identities, onward transfers and mechanisms already in place; no particular contractual safeguard is represented as executed.]
12.2EU GDPR Chapter V requires an applicable adequacy decision, appropriate Article 46 safeguards such as the European Commission’s Standard Contractual Clauses (Decision 2021/914, with suitable modules), or a narrowly applicable Article 49 derogation. Where required, transfer assessment and supplementary measures must address destination-law risks, access and onward transfers. Derogations are not a routine substitute for safeguards. UK transfers require the separate UK adequacy or safeguard framework, including the IDTA or UK Addendum where appropriate and the applicable transfer-risk/data-protection test. EU clauses alone are not necessarily sufficient for UK transfers.
12.3UAE PDPL Articles 22 and 23 distinguish transfers to jurisdictions providing an adequate level of protection and permitted transfers where that level is absent, subject to their specific conditions and operative measures. Saudi PDPL Article 29 and its transfer regulations require their own purpose, minimisation, protection and risk requirements; relevant safeguards may include SDAIA Standard Contractual Clauses, Binding Common Rules or other authorised safeguards where their conditions are met. Their use must not be assumed from an EU agreement.
12.4DIFC and ADGM use their respective adequacy and approved-safeguard regimes. Bahrain’s rules may require an approved destination, authorisation or a qualifying statutory route. Oman’s transfer conditions and any sensitive-data permits, Qatar’s statutory restrictions and Kuwait’s relevant sectoral requirements must be assessed independently. One transfer mechanism does not satisfy every jurisdiction. Copies or meaningful descriptions of relevant safeguards may be requested from the privacy contact, subject to confidentiality and lawful redaction, once the arrangements are confirmed.
13.Retention, deletion and disposal
13.1Engagement data should be retained only as necessary for the purpose, taking account of tax and accounting obligations, corporate records, professional duties, limitation periods, disputes, regulatory requirements and justified security or audit needs. Different records require different schedules. [CONFIRM: approved retention periods for enquiries, client files, HR, payroll, identification records, backups and provider logs; no fixed deletion period is promised for these records.] Legal holds may suspend routine disposal.
13.2At the end of an applicable retention period, data should be securely deleted, returned where appropriate, or irreversibly anonymised. Pseudonymisation is not anonymisation where re-identification remains possible. Backup disposal and residual copies require a documented process. Local chat and language entries currently have no automatic expiry; analytics periods are specifically stated in section 10. A deletion request may not remove records required by law or necessary for legal claims.
14.Information security
14.1The inspected website uses HTTPS access, validated enquiry inputs, team authentication and role-gated publishing; longevity enquiry records are restricted to authorised administrative access through configured permissions. These observations do not establish the security of every client workflow or supplier. Appropriate technical and organisational measures must be selected for the data and risk, including proportionate access controls, confidentiality, secure handling, incident readiness and vendor review. Encryption at rest, backup configuration, certifications, penetration tests and staff procedures are not independently verified and are not claimed. No electronic transmission or storage is entirely risk-free.
15.Personal data breaches
15.1A suspected breach should be reported promptly to the privacy contact. The proposed response framework is to identify and contain the incident, preserve relevant evidence, investigate scope and consequences, assess risks to individuals and coordinate remedial action. Controllers must notify the competent authority and affected individuals where the governing law requires it; processors must inform and assist the relevant controller as required by law and contract. Deadlines differ by jurisdiction and circumstance; there is no universal notification deadline. [CONFIRM: operational incident procedure, escalation responsibilities and contacts.]
16.Individual rights and requests
16.1Depending on applicable law, you may have rights to information, access, correction, erasure, restriction, objection, portability, withdrawal of consent and safeguards against qualifying automated decisions. EU GDPR rights are subject to Articles 12–22 and applicable exceptions; direct-marketing objections have specific protection. UAE PDPL provides its own information, portability, correction/erasure, restriction or cessation and automated-processing rights under their statutory conditions, not an identical copy of EU rights. Saudi and other GCC rights and sensitive-data protections must be assessed under their own laws.
16.2Contact info@mena-advisors.com with enough information to locate the relevant processing and describe your request. Proportionate identity or representative-authority verification may be needed; do not send a passport unless requested through an appropriate channel. Requests are subject to applicable deadlines, lawful extensions, confidentiality, third-party rights, statutory retention and other exceptions. Where allowed, reasons for refusal or limitation and available complaint routes should be explained. Consent withdrawal does not invalidate earlier lawful processing or prevent processing on another valid ground. Requests concerning data held solely for a client may need that controller’s decision.
17.Direct marketing and communications
17.1Necessary engagement updates and responses to a requested enquiry are distinct from marketing. Newsletters, promotional emails, event invitations and other direct marketing, if introduced or used, require assessment of applicable consent, lawful-basis and electronic-communications rules, including national exceptions and opt-out requirements. The inspected site does not implement a newsletter subscription workflow. You may ask the privacy contact to stop marketing; any marketing messages should provide a suitable unsubscribe route where required. Essential service and legal notices may continue on their appropriate lawful basis.
18.Children’s information
18.1The website presents professional services to business users and adults; it is not designed as a service for children. This does not exclude lawful handling of a child’s information in a specific family, employment-benefit or other client matter. Such processing requires the relevant jurisdiction’s safeguards and any necessary guardian authority or permission. No universal age threshold is stated. If unnecessary child data is submitted through the website, contact the firm so that appropriate restriction or deletion can be assessed. [CONFIRM: any child-data engagement practices.]
19.Third-party websites and services
19.1Links lead to Calendly for meeting scheduling, WhatsApp for direct chat, Google Maps for directions, Instagram, LinkedIn and partner websites including MENA LEGAL, BREXENDORFF & ASSOCIATES and LEGAL MAJLIS. These are outbound links, not embedded feeds or booking frames in the inspected pages. When you follow a link, the third party may process device, account and interaction information under its own privacy terms. MENA ADVISORS does not control independent third-party processing. Information you send to the firm through those services may also become business correspondence handled for your request.
20.Complaints and competent authorities
20.1Please raise concerns with the privacy contact; this does not limit any right to complain directly to a competent authority or seek a judicial remedy. Depending on scope, the authority may be the UAE Data Office, DIFC Commissioner of Data Protection, ADGM Office of Data Protection, an EU national supervisory authority, the UK Information Commissioner, SDAIA in Saudi Arabia, Bahrain’s competent personal-data protection authority, Qatar’s National Cyber Security Agency, Oman’s MTCIT or Kuwait’s CITRA for matters within its competence. No single authority is asserted to govern all processing. Confirm the relevant jurisdiction and current complaint route before filing.
21.Policy changes and dates
21.1Draft last updated: 16 November 2026. Effective date: [PENDING LEGAL AND FACTUAL APPROVAL]. On adoption, the effective and last-updated dates must be set and subsequent material changes communicated where legally required. Continuing to browse does not automatically constitute consent to new processing purposes or every policy update. Where consent is required, it must be obtained separately and be withdrawable under applicable law.
22.Mandatory law and engagement terms
22.1The firm’s UAE establishment does not displace mandatory foreign privacy law where its scope is satisfied. This notice is not an exclusive UAE jurisdiction agreement, a waiver of statutory rights, or a substitute for engagement-specific terms. Any contractual governing-law or forum provision remains subject to mandatory data-protection rules and remedies. The English, Arabic and German versions are review drafts; their legal equivalence must be reviewed before adoption rather than assuming one language removes rights granted by law.
23.Outstanding confirmations before publication
23.1Confirm the registered controller identity; applicable laws and sectoral exclusions; any required DPO, representative, registration or permit; actual employee, client and sensitive-data workflows; the supplier and sub-processor list; signed processing and transfer agreements; hosting and AI processing countries; provider training, logging and retention terms; record and backup schedules; operational security and incident procedures; marketing practices; device-storage consent requirements; and ownership and monitoring of any privacy mailbox. None of these missing matters is established by this draft.
23.2Official sources were checked during drafting on 16 November 2026, but a complete current-law verification could not be concluded. UAE implementing measures, consolidated DIFC/ADGM amendments, UK commencement details, current adequacy lists and all relevant national transfer requirements still require qualified review. An ADGM consultation draft is not treated as enacted law. The policy must remain a draft until those legal and factual checks are completed; no publication or compliance approval is given.