### UAE Privacy & Digital-Security Dossier — Updated Case reference: UAE-PRIVACY-2026-01 · Version 1.2 · 18 October 2026 The dossier has been updated with your incident intake covering 2025–2026, multiple UAE emirates, multiple devices, stalled or partially loading websites, and available screenshots or security alerts. ### Current evidence assessment Reported Websites stalled or loaded only partially; the concern involved multiple devices and locations. Screenshots or security alerts are reported to be available. Unverified DNS hijacking, deliberate targeting, unauthorized device access, hotel-room surveillance and reservation-data exposure. Pending Review of the actual screenshots, alert contents, technical logs, dates and device records. ### 1\. Updated incident record | Field | Recorded information | | ---------------------------------------- | ----------------------------------------------------------------------------- | | Period | 2025–2026 | | Geographic scope | Multiple UAE emirates; exact incident-to-location mapping not yet established | | Devices | Multiple devices; models and operating systems not yet specified | | Primary symptom | Websites stalled or partly loaded | | Evidence reportedly available | Network or DNS symptoms; screenshots or security alerts | | DNS manipulation | Suspected, not confirmed | | Unauthorized access | Not established | | Responsible party | Unknown | | Financial loss or reservation compromise | Not established in the supplied intake | ### 2\. Technical assessment The reported symptoms warrant investigation, but several explanations remain possible. Hypothesis A — DNS interference DNS responses may have been incorrect, manipulated or inconsistent. Confirmation requires relevant DNS records, reproducible results or credible forensic findings. Hypothesis B — Network or hotel Wi-Fi problems Connection instability, captive portals, filtering, packet loss or misconfigured DNS can cause websites to stall or load incompletely without a malicious attack. Hypothesis C — Device configuration or security issue VPNs, proxies, browser settings, installed profiles or compromised accounts may be relevant. The current information does not distinguish between these possibilities. Because you report symptoms involving multiple devices, the investigation should determine whether the devices were connected to the same network when the problems occurred. That comparison could help distinguish a network-level issue from a device-specific one. ### 3\. Evidence preservation and next actions * Preserve the screenshots and alerts. Keep original files and capture the date, time, device and network associated with each incident where known. * Create a device-by-device timeline. Record which device experienced which symptom and whether it happened on hotel Wi-Fi, mobile data or another connection. * Examine the DNS evidence. Record the DNS resolver, queried domain, returned address and any unexpected redirect, if those details are available. * Check for independent compromise indicators. Review unfamiliar account sessions, security alerts, configuration changes and unauthorized transactions. * Avoid destroying potential evidence. If a device may require forensic examination, avoid resetting it or deleting relevant records before obtaining specialist advice. ### 4\. What remains necessary to complete the dossier The most valuable next step is to examine the actual evidence rather than expand the allegations without support. Please upload the screenshots or security alerts you mentioned. I can review each item, extract relevant technical details, distinguish what it demonstrates from what it merely suggests, and add it to an evidence register with an incident reference. Until that review is complete, the dossier supports documenting a reported digital-security concern; it does not yet establish DNS hijacking, deliberate targeting, or a connection between the hotel stays and any unauthorized activity.