DPP Atlas trust page
How DPP Atlas separates framework rules, adopted law, working-plan signals, operator guidance, and vendor claims.
DPP Atlas is an independent operator publication, not an EU institution, law firm, certification body, or software vendor. Its editorial responsibility is to show what a source supports, what remains unsettled, and what practical preparation follows without turning that preparation into a legal conclusion. Pages are published under the DPP Atlas organisation; questions, disputed claims, and source corrections go to hello@dppatlas.eu.
The default order is final EU legal text on EUR-Lex; delegated and implementing acts; official European Commission communications, working plans, consultations, and implementation pages; harmonised standards references and recognised standards bodies; national authority or credible expert material; and vendor publications. A lower-tier source can explain practice but does not override higher-tier legal text. Search snippets and generated summaries are discovery aids, never the final authority for a regulatory claim.
Framework means the enabling architecture is in force while product detail remains dependent on later measures. Adopted means a final legal act supports the stated duty or date. Work plan means an official priority or indicative adoption signal, not a universal operator deadline. Horizontal means a measure may apply across several product groups. Market and operator-tool content is practical guidance. Inferred, vendor-claim, and needs-review labels identify conclusions that require extra caution.
A regulatory statement is checked against the operative article, relevant definitions, annexes, scope provisions, application dates, amendments, corrigenda, and linked implementing or delegated acts. DPP Atlas distinguishes entry into force from application, an adoption target from a business deadline, and a Registry or reporting step from substantive product compliance. Article and annex references are added near consequential claims wherever the page format allows.
Every serious date is classified before publication. An adopted application date can be presented as a hard planning anchor only for the products and operators within its scope. A working-plan year is described as indicative adoption timing. Consultation, draft, pilot, launch, and vendor roadmap dates retain those labels. Product thresholds, exclusions, operator roles, and transition periods are included when they materially change who must act.
When sources appear to conflict, final and more specific law takes priority over general communications; a later consolidated or amending text takes priority over an older version; and the product-specific rule takes priority over generic guidance for that product. The discrepancy is recorded rather than silently blended. If the conflict cannot be resolved, the claim is narrowed, labelled as uncertain, or withheld until a primary source settles it.
Readiness advice is derived from durable operating needs such as identifiers, source data, supplier evidence, access rights, change control, and exportability. It is deliberately separated from adopted duties. A recommended action can be sensible before a final delegated act exists, but DPP Atlas does not present it as mandatory, sufficient for compliance, or a substitute for advice from qualified legal and compliance professionals.
Vendor statements are attributed to the vendor and tested against visible public evidence. A passport demo, standards claim, Registry integration, or product feature is not treated as proof that a customer's product complies with applicable law. Terms such as approved, certified, compliant, and verified are used only when a source supports the exact actor, product, scope, scheme, and date. Vendors have a documented correction path and can submit supporting public material.
High-priority legal and deadline pages are checked at least monthly and when a known Commission milestone lands. Timeline and category records are updated when an official source changes their status, scope, or timing. Adopted near-term obligations receive closer monitoring. Vendor material, once published, is reviewed on a scheduled basis and when a visible claim changes. An old review date is not refreshed merely because layout or unrelated copy changed.
A source checked date records when that source was actually opened and reviewed. A page review date records a substantive editorial review of that page. Sitemap and structured-data dates are derived from page-level records where available rather than a blanket site deployment date. Minor typography, build, or navigation changes do not make regulatory content newly reviewed. This prevents freshness signals from overstating editorial work.
Correction requests should identify the URL, disputed text, and supporting source. DPP Atlas checks the claim against the source hierarchy, updates the page when warranted, and records material factual corrections on the corrections page. New legal developments are normal updates rather than corrections unless the previous page was inaccurate at the time it was published. Vendor disputes follow the same evidence standard as other claims.
Search, structured extraction, code, and AI-assisted tools may support discovery, comparison, translation, and consistency checks. They do not replace primary-source review for consequential legal claims. URLs, dates, article references, and generated outputs are checked against the underlying source before publication. Where evidence is incomplete, the content is labelled, narrowed, or left unpublished rather than completed with a plausible unsupported statement.