# Advertising, Cookies and Tracking

- Link: https://radiofluxx.com/advertising-cookies/
- Published: 2026-10-08T05:16:00+00:00
- Author: Tim R

**RadioFluxx** is a digital audio discovery and playback service operated under 
the name **TLRDev.com**. This document covers radiofluxx.com, its Android app and
associated functionality unless expressly stated otherwise. Last revised October
7, 2026.

## Advertising relationships

RadioFluxx may be supported by display, audio or other advertisements, direct sponsorships
or optional paid features. Where legally required, sponsored content will be identified
so users can distinguish it from independent editorial selections. The current production
inventory of ad partners must be verified before naming them as active.

## Potential ad-related information

Depending on the installed SDK and user choices, ad providers may process advertising
identifiers, IP-derived approximate location, device type, app interactions, impression
events and fraud signals. Certain jurisdictions require consent before certain tracking
or personalized advertising; user choices must be honored by the actual software.

## Website cookies and similar technologies

The website may use strictly necessary session or administration cookies and, if
enabled, optional measurement, embedded content or promotional cookies. A production
cookie scan is needed to describe each cookie’s provider, name, lifespan, purpose
and category accurately.

## Consent, rejection and withdrawal

Where applicable law requires opt-in consent, nonessential technologies should not
run before valid consent. Where opt-out rights apply, choices should be accessible
and respected. Consent withdrawal should be as easy as giving it where legally required.
Global Privacy Control or similar preference signals should be evaluated under applicable
rules.

## App and device controls

Android offers settings relating to ad identifiers and app permissions. These do
not replace a mandatory in-app consent mechanism or guarantee that every independent
provider will stop all permitted processing. Advertising preferences and privacy
choices should be documented after implementation testing.

## Children and sensitive data

Advertising configuration should reflect Play Console audience settings, age-related
requirements, restrictions on sensitive data and applicable children’s privacy laws.
Do not assume that an entertainment app is exempt from these rules.

## Analytics, notifications and advertising are different purposes

Google Analytics and Firebase may provide audience and product performance measurement.
OneSignal may enable push delivery and notification engagement measurement. An advertising
network such as Google AdMob, if enabled, has separate advertising and consent considerations.
These should not be conflated merely because Google operates more than one service.

## Technical identifiers and choices

Google Analytics for Firebase may generate an app-instance ID and may collect the
Android advertising ID by default unless properly configured otherwise. OneSignal
uses identifiers or tokens to route notifications. A null deviceId in RadioFluxx’s
user table does not negate those other identifiers. Optional collection, consent,
opt-outs and notification controls must be implemented in the actual software where
applicable, not only described in policy language.

## Transparency and vendor checks

An operational disclosure should identify ad network partners, privacy links, consent
management configuration, data handling, regional applicability and relevant SDK
versions. It should agree with the Google Play Data Safety form and the actual [Privacy Policy](https://radiofluxx.com/privacy-policy/).