Dubaist · Academy
Access is not a data licence
A publicly visible page does not automatically permit extraction, storage or commercial redistribution.Separate visibility from permission
A webpage can be open in a browser and still carry restrictions on extraction, storage, reproduction or commercial use. Visibility answers whether a person can access the page at that moment. It does not answer what a publisher may do with the content afterward. Dubaist therefore does not use the word public as a substitute for licensed. A reader may follow an official link and manually inspect an issuer identity or disclosure while automated collection remains disabled. Search-engine indexing, a successful HTTP response and the absence of a login are technical observations, not grants of rights. Robots instructions also describe crawler routing; they do not create copyright, database or redistribution permission. Before using any source, identify the owner, the material, the intended operation and the audience. Linking to an official page, quoting a short attributed passage, extracting structured fields repeatedly, storing a historical archive, transforming data into a product and selling access are different acts. Each can have a different answer. If the governing terms, licence or written response does not establish the needed right, the status is unresolved and the proposed operation stays off.
Define the complete intended use
A rights review must describe the actual workflow rather than ask whether data use is allowed in general. Record whether access is manual or automated, how frequently requests occur, which exact endpoint is involved, what fields are collected, how long they are retained, whether the original file is stored, which transformations are performed, how attribution appears, who receives the output and whether the use is commercial. An approval for a human to read disclosures does not prove permission for a scheduled collector. Permission to use an API does not necessarily authorize permanent storage or redistribution. A licence for internal analysis may exclude a public website, and a public display right may exclude resale or downstream feeds. Dubaist records these dimensions separately so one favourable answer cannot silently activate everything. The source registry also distinguishes content rights from endpoint stability and technical security. Even with written permission, an adapter should not run until its origin, authentication method, response contract, rate limits and failure behaviour are certified. Conversely, a technically stable endpoint remains inactive when rights are unresolved. The narrowest proven use controls publication.
Use a withheld source decision
Every source receives a decision supported by evidence. Rights approved means the precise operation is covered by a licence or an attributable written permission whose scope and date are recorded. Rights unresolved means the material may be visible, but the necessary authorization has not been established. Rights blocked means a governing term or owner instruction conflicts with the intended use. These states are not interchangeable. Silence, a general marketing reply or an invitation to view a website is not approval. A permission for one exchange, issuer, endpoint or document class cannot be copied to another. The decision should include the exact terms URL or correspondence reference, review date, reviewer and scope. When terms change, the source returns to revalidation before new automated work continues. Dubaist’s current exchange certification keeps automated collection disabled for ADX, DFM and Nasdaq Dubai because the required rights and stable approved endpoints have not all been established. That does not prevent carefully attributed links to eligible official pages or original explanatory writing based on manually verified identity context. It prevents an unlicensed ingestion path from being presented as operational.
Transform evidence without copying the source
A useful public page does not need to reproduce someone else’s database, report or visual design. Start with the smallest eligible fact required by the assigned URL, preserve its source and verification date, and write an original explanation of what the fact establishes and what it does not. Do not copy full articles, tables, charts, photographs, logos or large passages merely because they are easy to download. When a document mixes public facts with private correspondence, personal data or paid material, extract nothing beyond the independently eligible portion. Financial values require their own publication gate, provenance and rights; an identity link does not authorize a price feed. Dubaist keeps source documents, facts, calculations and editorial narrative as separate entities so provenance survives transformation. Attribution does not cure a prohibited use, and paraphrasing does not turn a protected database extraction into a new right. If a page can be useful with an identity, methodology and primary-source link, publish that bounded layer while showing missing or unavailable for the rest. This approach creates value through organization, explanation and traceability rather than through wholesale copying.
Give readers and issuers a correction path
Rights-aware publishing should remain verifiable after release. Display the source owner, direct eligible link, verification date and the boundary of the claim. Keep an internal record of the applicable decision without exposing private correspondence or credentials. If a source is removed, corrected or superseded, update the public state and retain an audit trail rather than leaving an unsupported statement live. Issuers should be able to point Dubaist to an official replacement, clarify attribution or ask for review of a disputed use. The ADCB identity-only example on this guide shows the distinction: Dubaist can identify Abu Dhabi Commercial Bank as ADX ticker ADCB and link readers to official exchange resources without reproducing a protected dataset or implying automated access. Any later disclosure, document or data feed would receive its own rights and evidence decision. Readers can therefore see why a page may contain a verified company identity while a financial table, live market field or automated update remains unavailable. A clear boundary is a product feature: it tells users what is supported, tells issuers how to improve the record and prevents technical access from being mistaken for permission.
Identity-only issuer example
ADCB as a bounded identity link
Dubaist identifies Abu Dhabi Commercial Bank as ADX ticker ADCB. A primary-source identity link supports that bounded statement; it does not establish permission for automated extraction, storage or redistribution of other material.
Abu Dhabi Commercial Bank · ADX · ADCB