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
developers.developer_name_enprojects.developer_name,projects.master_developer_name,projects.escrow_agent_name(Arabic)service_charges.management_company_name_en
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):
- DAMAC Hills, DAMAC Hills 2, DAMAC Lagoons
- Sobha Hartland (its phases "Sobha Hartland 2 / II" match through this leading part)
- Emaar South (a master community of the service-charge dataset)
- Jumeirah Golf Estates, Dubai Hills Estate, Dubai Investment Park (the DLD areas Dubai Investment Park First and Second)
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:
- A project or building name that begins with a brand (
<Brand> Hillcrest,<Brand> Towers) is the registered project name and is kept; only the credit afterbyand legal forms are removed. - About 150 published place labels are identical to the name of a company without its legal form (for example community names such as Business Bay, Al Furjan, Dubai South, or project names whose project company carries the same name). They are kept as place labels; the scanner lists them as information, not as hits.
- A numbered credit that is part of a series name (
Rise by <Sub-brand> 1 ... 4,Verdes by <Sub-brand> 1, 2) is kept, because dropping it would merge distinct projects; these credits name a community sub-brand (a master community), not a company in the DLD tables. They are the onlybycredits left in the public files, and they are documented exceptions, not scanner hits. - Brand words alone (
<Brand>) are not on the list:... by <Brand>is always removed. - Sales of projects named after a developer brand are published only at community level (owner decision of
7 October 2026, until data.dubai answers question 4 of section 7). Project names that begin with or contain a brand
stay as place labels, but summing project-level sales by that brand would rebuild the developer ranking that this
project keeps restricted. A project is brand-named when its registered or published name contains (a) the brand of
a developer that puts its brand into at least 3 of its own project names (
naming_brandsinscripts/common/compliance.py; about 70 brands), or (b) the brand of its own developer (the developer linked to the project in the DLD projects register) when that brand belongs to a developer group with at least 3 projects in the register (registered developers whose names share the brand word;own_brand_words, about 155 brands). Test (b), added on 9 November 2026 after an independent re-check, catches a large developer's project that carries the brand although the developer rarely names projects after itself (<Name> <Brand> Beachfront,<Brand> Hills,<Brand> Sky Tower), and a registered name that credits its own developer (<Project> by <Brand>, published as<Project>). A brand word that is also a word of an official DLD place name is not counted by test (b): projects in Expo City or Jebel Ali Village are named after the place, not after a company; the leading words of the brand place names listed above stay brands. In the data of 9 November 2026 this exempts 16 projects from test (b): 14 named after Expo City or Jebel Ali Village, and 2 elsewhere whose own developer's brand word (a word of another DLD place name) appears only in the registered name, which is not published (the DLD placeholderSold Without Project for <Company>and a<Project> by <Brand> <Name>credit). Both brand sets are derived at run time from the DLD projects and developers registers and are not listed here;compliance.py --selftestchecks that three projects named after their own large developer (kept in the code as label hashes) are withheld and that projects in Expo City and Jebel Ali Village are not. In both tests an official brand place name at the start of the label is not counted (DAMAC Hills 2 - <cluster>is a sub-community of DAMAC Hills 2). For such projects the sales columns ofsupply_stock/projects(sales_all_time,sales_12m,sales_12m_offplan,sales_12m_value_aed,median_aed_sqft_12m,n_sales_psf_12m; flagwithheld_brand_name), every sales-derived column and row ofproject_detailandn_sales_usedofprice_index/community_mapare empty. With the data of 9 November 2026 this concerns 823 projects (785 before test (b) was added; the 38 added projects had 1,742 sales in the last 12 months), with about 44% of the last 12 months' project-level sales; their sales are still counted in every community, master-project and area total. The rule leans towards withholding: a few projects whose name merely shares a word with such a brand lose their sales columns too. Smaller developers: the own name of a developer group with fewer than 3 register projects is not a brand for test (b). Such a company is mostly a project company named after its project: the project name came first and is the place label (see the bullet above on place labels identical to a company name), and one or two project rows do not rebuild a developer ranking. This keeps the threshold of 3 that test (a) and the scanner use. In the data of 9 November 2026 about 160 projects (about 3,900 sales in the last 12 months, 2.5% of project-level sales) keep their project-level sales although a word of their own developer's name is in the registered or published name; in about 70 of them the developer's whole name (without legal form and company words) is part of the project name, and in about 50 the word appears only in thebycredit of the registered name, which is not published. A threshold of 2 projects would withhold 51 more projects, counting every own-name word 157 more. Explicit limit of the rule: because a leading official brand place name is skipped, the sub-communities and phases of DAMAC Hills, DAMAC Hills 2, DAMAC Lagoons, Sobha Hartland and Emaar South (DAMAC Lagoons - <cluster>,Sobha Hartland <phase>) keep their project-level sales, insupply_stock/projectsand, with quarterly history and bedroom tables, inproject_detail. Summing those rows by the brand word rebuilds part of the developer's volume inside its own master communities (about 135 projects and 5,600 residential sales in the last 12 months in the build of 9 November 2026). This is accepted for official place names only, until data.dubai answers question 4 of section 7, where the list is named; a stray Arabic diacritic in front of a Latin project name no longer exempts the name from the check (and is removed from the published label). - Personal names inside project names (for example a residence named after a person and a developer brand) are registered project names. They are kept as place labels, with nothing attributed to the person; the case is part of question 5 of section 7. Their sales follow the brand rule above.
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:
- full legal company names (with their legal form) inside any text value;
- labels equal to a company name, or to a company name without legal form that still contains company words;
by <company>credits and legal-entity forms / company tails (English and Arabic) thatclean_labelwould change;- columns named
unit_number,unit_no,unit_id,property_unit_no; - 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;
- public files with the same content as an internal file, or named / placed like one;
- a
metaobject in everysite/data/*.json, and the total size ofsite/data/(limit 8 MB); - labels known to have carried a developer credit (
REGRESSION_LABEL_KEYS); - community labels (
communitycolumns and keys) that start with a developer brand and are not a DLD area or master-project name; - project rows (
project_name_en,dld_project_name) whose name carries a developer brand, and rows keyed by theproject_numberof a project flaggedwithheld_brand_nameinsupply_stock/projects, that still hold a sales value (columnssales_*,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
- Derivable suppressed cells (accepted, owner decision of 7 October 2026). Suppression is applied cell by cell. A suppressed cell (<5) can sometimes be recovered by subtraction: a total minus its published parts (All = Title Deed + Oqood; All residential = Apartment + Villa/Townhouse in an area or master project; a type or area total minus the other bedroom cells; Ready + Off-plan in an untrimmed price-index window; a building's units from the area total), adjacent rolling windows, or a city figure minus the published areas. In the build of 7 October 2026, differencing recovers about 5,700 area-month and 9,000 master-project-month sales cells, several hundred of them single sales with their price. No secondary (complementary) suppression is applied, by decision: the source itself, the DLD transactions file on data.dubai, already publishes every sale with its date, area, project and price, so a recovered cell discloses nothing that the licensor does not publish, and the open data carries no buyer, seller or owner. The suppression of cells under 5 is therefore a presentation rule against reading noise as a statistic, not a confidentiality guarantee. The rule is reviewed if a non-public source is ever added.
- Building-level tables.
stock_by_buildingand the service-charge tables are per building. Counts of 1-4 units are suppressed, but a building with few units, combined with outside knowledge, narrows down owners' identities. No transaction, rent or owner data is linked to a unit or building row. - Counts that are not record counts are published as they are: planned units from the projects register, the
number of projects in a pipeline, completion or outside-register cell (
supply_stock; every project is a row of the project table), the number of budget lines, the number of active developers in a month (developers_internal, can be 1-4 in early months). They do not describe people, but the anonymous concentration statistics could be linked to a large developer by someone who knows the market. - Name matching is not complete. Company names are matched against the DLD tables. A credit to a name that is not
in those tables is removed only when it is the trailing
by <1-4 words>of a label. A company reference that is not introduced bybyand is not in the tables (an abbreviation, a misspelling, a brand after-that is not the project's own developer) can remain. - The generic trailing-credit rule can remove a non-company word after
by(a hotel or designer brand, a person's name). This shortens a few official project names; the project id and number are unchanged. - The internal-reference check is heuristic. It catches copied figures and copied rows, not a figure re-derived and rounded differently. Coincidental equality of small numbers is possible and is resolved by manual review.
- Arabic project names are not published (see section 3).
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:
- publishes no company names (they stay in
data/restricted/), - publishes brand-bearing place names only as place names (section 4), and anonymous market-structure statistics only,
- states on every page that it is an independent analysis not affiliated with or endorsed by the Dubai Land Department, any government entity, or any developer, management company or data provider.
Questions to put to data.dubai:
- 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?
- 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?
- 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?
- 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?
- 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.