Skip to content
TrustIQ

Lumen QX7 55" TV

Television · Lumen Electronics · LQX7-55

Device model
LQX7-55
Publisher
Lumen Electronics
Platform
Lumen TV OS
Versions
Firmware 9.2.114 · Lumen TV OS 9.2
Scan date and region
Sep 8, 2026 · US-West (user capture)
Consent state
Unknown — capture did not record settings
Scan method
Supported diagnostic capture — router DNS log
Coverage
Insufficient · methodology 0.9

Observed connections (3 endpoints, 3 companies)

Each row is a transmission observed in the tested session, the operator identified for that endpoint, and the information seen in requests. This table is the accessible equivalent of the data-sharing map.

Endpoints contacted by Lumen QX7 55" TV, their operators, scenarios, and information observed
Observed endpointIdentified operatorRoleScenariosInformation observed
acr.crestline.example

Contents not readable

Crestline Measurement

Declared

Analytics and measurement
  • Scenario not recorded
Unknown
ads.adreach.example

Contents not readable

Adreach Exchange

Declared

Advertising services
  • Scenario not recorded
Unknown
cdn.nimbuscdn.example

Contents not readable

Nimbus Edge

Declared

Content delivery and infrastructure
  • Scenario not recorded
Unknown

Documented relationships

Ownership and business relationships come from public records. They do not show that data from this product moved between these companies.

  • Adreach Exchange → Meridian Media Group

    DeclaredDocumented ownership

    Source: Meridian Media Group annual report 2025, list of subsidiaries · Mar 2, 2026

  • Crestline Measurement → Meridian Media Group

    DeclaredDocumented ownership

    Source: Meridian Media Group press release, Feb 2026 · Feb 9, 2026

  • Adreach Exchange → Tallymark Analytics

    DeclaredDocumented business relationship

    Source: Tallymark integrations page lists Adreach · May 14, 2026

Unknown Further sharing unknown

TrustIQ observes what leaves the product. What recipients do afterward, including onward sharing, is outside what this scan can see.

Open questions

  • Nimbus Edge

    • Content delivery contact establishes where files were fetched from, not why. Purpose is attributed to the publisher, not to Nimbus Edge.