Privacy Policy
RadioFluxx | Operated under the name TLRDev.com | Updated October 7, 2026
Example of an anonymous account
Fictional example. These are illustrative values based on the account fields we reviewed, not a real user’s record.
| Stored field | Example | Purpose |
|---|---|---|
| uid | Random account UUID | Identifies the account without a real name |
| Empty | No email provided | |
| displayName | anon123456 | Generated nickname |
| photoUrl | assets/avatars/rock_avatar.png | Built-in app avatar. No photo upload feature |
| deviceId | null | No device ID in this record |
| locale | en | Language preference |
| streamingQuality | standard | Playback quality preference |
| isPro | false | Premium status |
| marketingOptIn | true | Database flag. Not proof of active consent |
This example does not show all database fields. The actual schema also contains an internal row ID, subscription expiration, other settings, and creation/update timestamps. A stored account UUID is a pseudonymous identifier. A null deviceId field does not tell us what external audio hosts, hosting infrastructure or SDKs may process.
Privacy by design
RadioFluxx is designed to let people enjoy radio, podcasts and audiobooks without requiring them to provide a legal name or email address for the ordinary anonymous listening experience. The current user-table export reviewed for this notice shows empty or null email fields and null deviceId fields in the supplied records. This is evidence about that table, not proof that IP addresses, application identifiers or advertising-related information are never processed elsewhere.
What an anonymous account actually contains
The current account schema includes two UUID-style identifiers (id and uid), an optional email field, an automatically generated display name, a bundled avatar asset reference (photoUrl), not an uploaded photo; RadioFluxx does not currently offer avatar uploads, anonymous-account status (isAnonymous), a premium subscription flag (isPro), a subscription expiration field, locale, a marketing preference field (marketingOptIn), a deviceId field, automatic podcast download preference, stream quality, car-mode preference, and creation and update timestamps. These are application account records and settings. Neither the UUIDs nor pseudonyms directly display a user’s legal identity, but they can distinguish a particular account from other accounts and may therefore qualify as personal data under some privacy laws.
What we observed in the supplied snapshot
The supplied user-table snapshot contains anonymous rows with generated names such as anon followed by digits, plus several rows in which isAnonymous is false but the email and displayName fields are also empty. Every deviceId value in that snapshot is null. The snapshot does not establish that device IDs can never be collected, or that every possible future account will lack an email address.
Why account identifiers are needed
The system uses identifiers to associate application settings, saved lists or entitlements with the correct app record where those capabilities are implemented. Users generally do not need to enter personal contact information for the default anonymous experience. UUIDs and pseudonyms are identifiers rather than proof of a person’s real-world identity.
Preferences and account settings
The user record currently supports language or locale, avatar selection, whether podcast downloads are enabled, streaming quality, car mode, subscription status and a marketing opt-in value. The export shows marketingOptIn=true even in anonymous records. This field alone does not prove that permission for marketing emails was affirmatively collected, that marketing is being sent, or that valid consent exists. Marketing behavior and default values must be separately checked.
Data the table does not show
This export does not include an IP-address column, GPS location, contacts, telephone number, date of birth, payment card number, or non-null deviceId. However, it does not include all database tables, authentication provider logs, stream-provider requests, network infrastructure, crash diagnostics, advertising services or website cookie storage. We will not claim that none of those systems processes information without confirming them.
Other service data and third-party connections
Using websites, cloud services or internet audio can expose an IP address and basic connection information to hosting infrastructure and independent stream providers. If advertising, diagnostics, analytics, push services or embedded media integrations are enabled, those providers may also process certain data independently. A complete vendor and network-traffic inventory must be confirmed before a final public disclosure is issued.
How information is used
Relevant account information may be used to recognize pseudonymous sessions, save preferences and library selections, provide appropriate app behavior, verify entitlements, protect service integrity, handle user requests and maintain functionality. We do not assert that the account table alone establishes listening-history retention, ad targeting or analytics practices.
Sharing and selling
We do not infer from the account export that identifying information is sold, shared for cross-context behavioral advertising, or transmitted to particular vendors. Such claims must be made based on a review of actual application and website integrations, not just the account table. Where privacy law provides advertising opt-outs or requires consent, those controls must reflect real processing practices.
Storage, retention and security
Account creation and update timestamps are stored in the supplied records. Exact account retention periods, backup deletion schedules and security safeguards must be documented from the actual infrastructure. Deleting the application does not necessarily remove a server-side pseudonymous account or backups. We cannot promise immediate deletion from every system unless implemented and verified.
Access, correction and deletion requests
To inquire about a RadioFluxx account or seek access, correction or deletion where available under law, use the Data and Privacy Requests page and Contact form. Because default accounts may have no email address, support may need an in-app authenticated deletion flow or a privacy-preserving proof that the requester controls the account UUID. Do not publish a raw user export or disclose another person’s identifier.
Account deletion and Google Play
If the application allows creation of anonymous authenticated accounts, Google Play account-deletion requirements may apply even though emails are blank. Confirm whether the app has an in-app deletion pathway, accessible web deletion request, and backend deletion or anonymization handling. A written policy is not a substitute for those controls.
Children, region and legal rights
RadioFluxx is intended as a general-audience audio app. Applicable rights for access, correction, deletion and marketing choices vary by jurisdiction and circumstances. Children’s privacy and audience rules need to be validated against the Play Console target-audience settings and implemented data flows.
Google Analytics and Firebase
We plan to use Google Analytics and Firebase services to understand app use, improve reliability, and support selected app functionality. Google Analytics for Firebase may process app-instance identifiers, session information, operating system and device model, approximate geography, app launches, screen and event interactions and, depending on configuration, Android advertising identifiers. Exactly which Firebase products are installed and the status of data collection and advertising integrations must be verified before release. Read Google’s Firebase data collection information and Firebase Play Data disclosures.
OneSignal push notifications
RadioFluxx plans to use OneSignal for push notifications. If enabled, the OneSignal mobile SDK may process push subscription and device identifiers or tokens, IP address, device model, operating system, language, time zone, network information and message engagement needed to deliver and manage notifications. Precise location is not assumed to be collected; OneSignal says collection depends on app permission and configuration. Notification preferences and revocation through device settings should be supported. See OneSignal’s Privacy Policy.
Direct explanation: what ‘no device tracking’ means
The supplied RadioFluxx user-account table shows deviceId as null. That means this particular database field is not populated in the sample. It does not mean Google Analytics, Firebase, OneSignal, infrastructure logs or external media providers have no technical identifiers. We distinguish what the RadioFluxx user profile stores from what each third-party service processes. We will not claim zero device tracking while those SDKs operate.
Integration inventory
Services identified for the product include Supabase, Google Analytics, Firebase and OneSignal, plus independently hosted audio sources. Product names and functions here identify planned or known integrations, not confirmation that each currently processes data in production. The complete inventory, configuration, collection periods, vendor contracts and consent controls must be checked before final publication.
Google Analytics and Firebase
RadioFluxx plans to use Google Analytics and Firebase. Depending on the exact SDKs and configuration, Google Analytics for Firebase may collect app-instance identifiers, operating-system and device information, approximate region, app launches, sessions, interactions and Android advertising identifiers. Firebase includes multiple distinct services, and their data practices vary. We will disclose verified configurations and user choices rather than assume that our account database describes every SDK. See Firebase’s data collection documentation.
OneSignal notifications
RadioFluxx plans to use OneSignal for push notifications. Its mobile SDK may process notification subscription IDs and push tokens, IP address, operating system, device type, language, time zone, network information, and notification interactions. OneSignal states that precise location collection depends on application permission and configuration; we do not assert that it is enabled. Notification permissions and applicable consent choices must be honored. See OneSignal’s Privacy Policy.
What we mean by anonymous
In simple terms: RadioFluxx can create a pseudonymous account without asking for a real name or email. Our sampled user table shows deviceId as null, but Firebase Analytics, OneSignal, hosting providers and audio services can use separate identifiers or receive connection information. Anonymous to RadioFluxx is not the same as invisible to every service involved in delivering the app.
Updates and operator contact
We may update this notice when the underlying product changes. The operator is listed as TLRDev.com for now, but the actual responsible legal person or entity must be identified in the final publication. For questions use RadioFluxx Contact.
Required verification before publishing
Check the actual Supabase Auth setup, all related library/history tables, RLS and deletion logic, server and CDN logs, Google AdMob SDK and consent settings, analytics/crash SDKs, website cookies, data exports, device/location permissions, retention, marketingOptIn defaults and whether the anonymous account creation flow falls under Google Play’s account-deletion requirement. These details have not been proven by the supplied user-table export.