Source: Dubai Land Department open data via data.dubai, Dubai Open Data Licence (licence text). Independent analysis by WIZI Premium, not affiliated with or endorsed by the Dubai Land Department, any government entity, developer, management company or data provider.

Publication compliance: licence, company names and privacy

This page sets the rules that every public file of WIZI Premium Market Data must meet, explains what is masked and how, and lists the residual risks and the open licence question. It applies to everything under data/out/, site/data/, site/downloads/ (licence texts and these methodology documents only: since 5 November 2026 the site offers no table downloads) and the site pages (the "public outputs"). Code: scripts/common/compliance.py.

1. Rules

# Rule Where it is enforced
1 No company names of developers, master developers, management companies, escrow agents or brokers. Project, building, area and community names are allowed as place labels, but developer credits (<project> by <developer>) and legal-entity tails (... Real Estate Development LLC, FZE, PJSC, ش.ذ.م.م) are removed. A label that is nothing but a company name is left empty. clean_label / clean_labels / clean_label_ar in scripts/common/compliance.py, called from the modules where labels are written; mask_company_labels in supply_stock
2 No unit-level rows. The smallest published level is a building, plot, project, community or area. No column named unit_number / unit_no / unit_id. module design; checked by the scanner
3 Cells built from fewer than 5 records are suppressed (empty / null, shown as "<5" on the site). each module (MIN_N / MIN_PUB = 5)
4 Dubai Open Data Licence only. No extra or different terms, no CC/ODbL label on the data, no conditions on quoting the figures. The site offers no table downloads (owner decision of 5 November 2026; the website is a Work Product, licence clause 3.3.1); if tables are ever offered again, they must be free and never gated (no form, no registration, clause 3.1.1). Attribution: "Source: Dubai Land Department open data via data.dubai, Dubai Open Data Licence". DATA-LICENSE.md, site footer, meta object in every site/data/*.json
5 Only DLD open data is published. Internal quality-check material is kept outside the published folders, is never copied into site/ or data/out/, and none of its figures may appear in a public file. Tables with company names stay in data/restricted/. scanner (file names, internal reference numbers)
6 site/data/ stays under 8 MB in total, and every site/data/*.json carries a meta object (module, source, data-through date, notes). scanner

2. How company names are found

company_names(con) collects the distinct names in the staging tables

normalised to upper case with single spaces, keeping names longer than 6 characters (about 2,600 names). From each name it derives the name without legal form (<NAME> DEVELOPERS L.L.C -> <NAME> DEVELOPERS), the core name without legal form and company words (<NAME>), and the distinctive first word of the core (a "brand"; generic words such as Dubai, Al, Golden, Park, Residences are excluded). The same rules are used by supply_stock's mask_company_labels (exact or long contained names are blanked) and by the new label cleaning.

Brokers do not appear in any staging table used by the project, and no broker field is read by any module.

3. What is masked, and how

clean_label(label) keeps the place name and removes the company reference:

Case Example (placeholders) Published
Trailing developer credit, developer known in the DLD tables Starz Tower by <Developer> Starz Tower
Credit naming a company with company words Residences 11 By <Name> Real Estate Development Residences 11
Credit inside a longer label Golf Horizon By <Developer> - Golf Horizon by <Developer> Townhouses Golf Horizon - Golf Horizon Townhouses
Joint credit Art House Hills by <A> and <B> Art House Hills
Design credit <Tower> Interiors by <Brand> / <Villas> designed by <Brand> <Tower> / <Villas>
Trailing credit to a name not in the DLD tables (1-4 words, no digits, not a property word) Deansgate by <Initials> Deansgate
Credit naming part of a company in the DLD tables (2-4 words of the company name, at least one distinctive) <Project> By <Two Words> where the company is <X> & <TWO WORDS> DEVELOPERS L.L.C <Project>
Trailing credit by Al <Name> (Arabic article + 1-2 words, no digits; or the leading words of a company AL <NAME> INVESTMENT ...) <Project> by Al <Name> <Project>
DLD placeholder project for sales outside a registered project, naming the seller Sold Without Project for <Company> Sold Without Project
Legal form at the end of a place label Cedre Villa Master Community Fze Cedre Villa Master Community
Owners-association company used as a building name <Tower> Owner Association Management Services Dmcc <Tower>
The label is only a company name <Name> DEVELOPERS L.L.C, <اسم> للتطوير ش ذ م م empty
Credit after | naming a company or developer brand <Name> Places | <Developer> <Name> Places
Last segment after -, @ or |, or last word, equal to the brand of the project's own developer (project linked to the DLD Developers dataset through developer_id), when a distinctive word remains <NAME> <DEVELOPER BRAND> <NAME>
Arabic twin of a project name any not published

The Arabic project-name column is not published at all: Arabic credits cannot be parsed safely (باي is both "by" and "Bay", as in Business Bay; من can be glued to the previous word; a brand can lead the name). It is kept in the restricted copy. The site is in English and Russian and uses the English labels. Official place names are never cut by the trailing rules.

Labels that change for no compliance reason are left exactly as published by DLD (spacing and case are not touched). Residual labels that the generic rules cannot recognise are fixed by an explicit table (MANUAL_LABEL_FIXES, keyed by a hash of the label so that the source file does not contain the company name). The hashes of labels known to have leaked a credit (REGRESSION_LABEL_KEYS, including the Arabic names found in the October 2026 review) are checked by the scanner, and compliance.py --selftest re-runs the cleaner on them.

Where cleaning is applied (all at the point where labels are written; restricted copies keep the original labels):

Module Labels cleaned Effect in this build
price_index community_map: DLD area, master project, project name (rows whose labels become identical are summed before the <5 suppression) 386 rows cleaned
service_charges building name, project name and community in building_year_usage, category_lines, building_latest, same_name_budgets, community_* and site/data/service_charges.json 4,169 label cells cleaned
supply_stock projects (English project name, master project; the Arabic name is not published), stock_by_project, stock_by_building, site/data/supply_stock.json 391 project and 461 building rows cleaned (incl. 7 Sold Without Project for <seller> placeholders); 2 + 2 labels blanked as company names
sales_market, rents_market, yields, developers_internal no hits (area / master-project / community labels only; developers_internal publishes anonymous statistics only) none

4. Brand and place-name policy

Some official place names contain a developer's brand, or coincide with the name of a company (often the master developer, or a project company named after the place). These are place names in the DLD area lookup, the projects register and the transaction records, and we publish them as place names. They are not used to refer to the company, and nothing is attributed to the company.

Explicit list of brand-bearing community / master-project names kept as published (BRAND_PLACE_NAMES in scripts/common/compliance.py; matched on the whole label or its leading part, e.g. DAMAC Hills 2, Sobha Hartland II):

Only names that exist as a DLD area, master-project or master-community name (lookup of areas, master_project of transactions, units and projects, master_community_name_en of service charges) belong on this list, directly or without a trailing ordinal; the scanner self-test (--selftest) fails when an entry does not. A name that DLD uses only inside project names (for example a project series called "<Brand> Islands - <phase>" or "<Brand> <Name> 1 .. 60") is not a place name: community labels built from such clusters are neutral, named after the DLD area with "(project cluster)" (see price_index.md). On 9 October 2026 three project-series entries (two of the form "<Brand> <Name>", one "<Brand> Beachfront"), Sobha Hartland 2 / II and Dubai Investments Park were removed because they are not DLD place names; the three series entries had let a whole project series publish project-level sales under the brand (85 projects withheld since; the 86th, whose developer rarely puts its brand into project names, has been withheld by test (b) of the brand rule below since 9 November 2026). The scanner reports any community label that starts with a developer brand and is not a DLD place name.

Further rules of the policy:

5. Checks (scanner)

.venv/bin/python scripts/common/compliance.py reads every data file (CSV, Parquet, JSON) in data/out/**, site/data/**, site/downloads/** (licence texts and methodology documents), and every text file there and in site/ (Markdown, HTML, JavaScript, CSS), and prints a report; it writes nothing. Exit status 0 means no unresolved hits. Sentences in data files (file descriptions, notes) are only checked for full legal company names; text files are checked line by line for full legal company names, by <developer> credits naming a registered developer or company, and Arabic company words or legal forms. A check that cannot run (no internal reference files) is reported as SKIPPED, not OK. It checks:

  1. full legal company names (with their legal form) inside any text value;
  2. labels equal to a company name, or to a company name without legal form that still contains company words;
  3. by <company> credits and legal-entity forms / company tails (English and Arabic) that clean_label would change;
  4. columns named unit_number, unit_no, unit_id, property_unit_no;
  5. internal reference figures: numbers read at run time from the internal reference files (never copied into code or output). Large AED values are a hit anywhere; smaller distinctive numbers (counts, two-decimal rates) are a hit only in a record of the same period (read from the reference file names, not hard-coded), module and place; a public row that carries a reference row's label and at least 3 of its numbers is a hit;
  6. public files with the same content as an internal file, or named / placed like one;
  7. a meta object in every site/data/*.json, and the total size of site/data/ (limit 8 MB);
  8. labels known to have carried a developer credit (REGRESSION_LABEL_KEYS);
  9. community labels (community columns and keys) that start with a developer brand and are not a DLD area or master-project name;
  10. project rows (project_name_en, dld_project_name) whose name carries a developer brand, and rows keyed by the project_number of a project flagged withheld_brand_name in supply_stock/projects, that still hold a sales value (columns sales_*, n_sales*, per-sq-ft and price medians and quartiles, launch / latest prices, off-plan ratios and sale months; also the {columns, rows} tables of the site JSON).

The company dictionary must be complete: if a staging table it reads is missing, or fewer than 2,000 company names are found, the scanner and every module stop instead of silently checking against a shorter list.

Result for the build of 2026-11-09: no company names, developer credits or legal forms, no unit-number columns, no internal reference figures and no internal files across all public files (data, site data, download copies and site pages); site/data/ stays under 8 MB; every site/data/*.json carries meta (the plain list site/data/index.json is exempt). The only by credits left are the documented series exceptions of section 4. scripts/run_all.py now ends with scripts/build_site.py and this scan, and fails on unresolved hits. Run the scanner after scripts/run_all.py, after refreshing site/downloads/, and before every publication.

6. Known residual risks

7. Open question to confirm in writing with data.dubai

The Dubai Open Data Licence excludes Private Entity Data (a private entity's name, purpose and legal status) from the licence grant (clause 2.2.4) and prohibits disclosing it without consent (clause 2.3.2). Clause 3.2.2 further prohibits using the publisher's or the Dubai Government's name with a Work Product and attributing or associating a Work Product with the Dubai Government, any Dubai or Federal Government Entity, any Private Entity or any natural person.

Until data.dubai (the licensor) confirms otherwise in writing, this project:

Questions to put to data.dubai:

  1. Are developer, master-developer, escrow-agent and management-company names contained in the DLD open datasets "Private Entity Data" in the sense of clause 2.2.4, so that publishing them (e.g. sales by developer) needs the companies' separate permission?
  2. Are official place names that contain a company's brand (section 4), and project names identical to the name of a project company, acceptable as place labels?
  3. Does clause 3.2.2 allow (a) anonymous market-structure statistics (concentration of sales among the top developers, without names), and (b) publication of the Work Product under the publisher's own brand (WIZI Premium, by WIZI Properties) with the attribution line and the not-affiliated statement used on the site?
  4. May sales statistics be published per project when the registered project name contains the developer's brand (for example the last-12-months sales of a project whose name begins with the developer's brand)? Until the answer, such projects show sales only inside community totals (section 4). The same question for the sub-communities and phases of the official brand-bearing master communities on the place-name list of section 4 (DAMAC Hills, DAMAC Hills 2, DAMAC Lagoons, Sobha Hartland, Emaar South): their project-level sales are published at present because the leading name is an official DLD place name; is that acceptable, or should they also be limited to community totals?
  5. Registered project names that contain a natural person's name (for example "<First name> <Brand> Residence"): may they be shown as place labels, given that clause 3.2.2 also covers association with a natural person? Until the answer, they are kept as place labels with nothing attributed to the person (section 4).

Record the answer (date, sender, text) in this file when received.