Do you process personal data to count impressions?

No. Makan uses Proof-of-Play (PoP) and contextual data to produce modeled impressions, following IAB/MRC guidance. No personal data is required or processed for standard measurement.

Are RTA approvals included?

No. Network operators must secure the necessary permits from the RTA and other municipal authorities. The Makan platform enforces the technical guardrails (like brightness and format) to help you comply with those permits.

What about federal roads outside Dubai?

The updated Dubai RTA manual is being considered as a reference for federal roads. We monitor these developments and will update our policy presets as official guidance evolves.

Which jurisdictions are out of PDPL scope?

The UAE PDPL is a federal law and does not apply to free zones like DIFC and ADGM, which have their own data protection regimes. You should consult legal counsel for operations that span multiple jurisdictions.

Can Makan export log-level data for audits?

Yes. Proof-of-Play logs, programmatic deal logs, and modeled impression data are all exportable in standard formats (CSV/JSON and PDF) to support audits and reconciliation.

Compliance & Measurement

Policy-safe operations. IAB-aligned measurement. PDPL-ready privacy.

Makan bakes RTA guardrails into delivery, models impressions to IAB/MRC methods, and applies UAE PDPL privacy principles by design—so you can plan, buy, deliver, and prove outcomes with confidence.

Request Key Documents View Security Practices

Built-in trust from planning to billing.

Policy-Aware by Design

RTA placement, format, and brightness guardrails are enforced pre-publish and at runtime.

Standardized Measurement

Proof-of-Play is converted to modeled impressions following IAB/MRC guidance, exportable for BI.

Privacy First

UAE PDPL principles (lawfulness, minimization, security, regional storage) are embedded in all data flows.

Dubai RTA (OOH Advertising Manual)

Operate safely. Earn public trust.

Location & format eligibility: Screens must respect approved zones, placement, and format classes. Makan surfaces eligibility at planning time and blocks unsafe schedules at delivery.

Brightness & distraction controls: Runtime guardrails for brightness, contrast, and animation cadence, with stricter constraints near roadways and driver sightlines.

Innovation within rules: Support for modern formats (e.g., 3D builds, lasers, drones) where permitted—always subordinated to safety and permit terms.

Toward national alignment: The updated Dubai manual is under review as a reference for federal roads (Ministry of Energy & Infrastructure). We monitor these changes and reflect them in presets.

Note: Makan enforces guardrails but does not replace local permitting. Operators remain responsible for approvals with RTA/municipal authorities.

UAE PDPL (Federal Decree-Law No. 45 of 2021)

Privacy by design—without using personal data.

Our stance: DOOH measurement with Makan does not require PII. We rely on PoP and context; if a use case introduces personal data, PDPL controls apply.

Key PDPL principles we implement:

Lawfulness & transparency: Clear purposes and records of processing; no hidden data collection in standard DOOH ops.
Data minimization & retention: Only the logs needed for PoP/ops; configurable retention windows; regional storage by default.
Security & accountability: Encryption, access controls, audit trails; DPA/SCC-style terms on request.

Scope & timelines: PDPL is a federal law (excludes DIFC/ADGM, which have their own regimes). Enforcement milestones were phased through 2023–2024; we keep controls current.

Disclaimer: This page is informational and not legal advice. Confirm obligations with counsel, especially for DIFC/ADGM entities.

Measurement (IAB/MRC-aligned)

From PoP to modeled impressions you can defend.

Method at a glance:

Proof-of-Play (PoP): Tamper-evident logs per play (screen, creative, timestamp).
Context & eligibility: Venue class, format, day-part, availability and conflict flags.
Modeling: Convert PoP to modeled impressions using industry guidance (IAB’s DOOH Measurement Guide; MRC OOH Standards—Phase 1).
Reporting: CSV/JSON exports + human-readable PDFs; plan vs actuals; pacing/occupancy; uncertainty notes.
Reconciliation: Tie deals (PMP/Guaranteed/RTB) to PoP and modeled impressions for invoice packs.

Why “modeled”: IAB/MRC recognize that DOOH typically uses modeled, context-based approaches rather than census-level audience counts; Makan follows that standard.

Platform Security

Security & continuity you can audit.

Data in transit/at rest: Encrypted; signed PoP and manifests; scoped API tokens; SSO (SAML/OIDC).

Access & audit: RBAC, activity trails, export permissions; least-privilege defaults.

Resilience: Offline buffers, clock sync, automatic catch-up; HA/DR options on Enterprise.

Transparency: Public status page & incident history; post-mortems for Enterprise customers.

Request Key Documents

Select the documents you're interested in, provide your email, and we'll send them to you.

FAQs

No. Makan uses PoP + context to produce modeled impressions per IAB/MRC guidance.

No—operators must secure permits; Makan enforces technical guardrails to help you comply.

The updated Dubai manual is being considered as a reference for federal roads; we’ll maintain presets as guidance evolves.

DIFC/ADGM have separate regimes; consult counsel for dual-regime operations.

Yes—PoP, deal logs, and modeled impressions are exportable (CSV/JSON + PDFs) for reconciliation.

Ready to operate policy-safe networks and report with confidence?

Request Key Documents View Security Practices