# Data and Privacy Requests - Link: https://radiofluxx.com/data-privacy-requests/ - Published: 2026-10-08T04:50:31+00:00 - Author: Tim R **RadioFluxx** | Operated under the name **TLRDev.com** | Updated October 7, 2026 This is called True Transparency. ## 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 | | email | 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 | 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. ## Our privacy-first account design RadioFluxx’s supplied user-table export shows that typical user records are pseudonymous. An anonymous record has a generated display name, account identifiers, bundled avatar reference and playback preferences. In that export, email addresses are empty or null and deviceId is null throughout. The service is designed so that standard anonymous listening does not require a legal name or email address. ## Exactly what the account record stores The observed fields are: id, uid, email, displayName, photoUrl, isPro, isAnonymous, subscriptionExpirationDate, locale, marketingOptIn, deviceId, autoDownloadPodcasts, streamingQuality, carModeEnabled, createdAt and updatedAt. The id and uid are UUID- style persistent account identifiers, and timestamps record creation and update. Avatar references in this snapshot point to bundled application assets. RadioFluxx does not currently provide an avatar-upload interface. An account may use a generated display name, but that name is still associated with its unique record. ## Distinguishing device tracking from account identification The deviceId field was null in every supplied row. The table itself contains no physical location, telephone number, contacts or payment card information. Nevertheless, an account UUID can single out an application account. This export cannot prove that server logs, Supabase authentication logs, third-party stream hosts, advertising SDKs or other services never receive a device or network identifier. We will make no absolute ‘zero tracking’ claim without a wider technical audit. ## Anonymous and non-anonymous rows Some rows show isAnonymous=false while the email and displayName fields are empty or null. An empty email field is not enough to determine why that account was created or what other authentication metadata exists. A user seeking deletion should not be required to invent an email that was never collected. ## What you can request Depending on applicable law, a person may request access to, correction of or deletion of information associated with an account, and may have rights relating to certain disclosures, marketing or advertising uses. We will review requests based on the actual records and legal requirements rather than demand unnecessary personal details. ## How to contact us Use the [RadioFluxx contact page](https://radiofluxx.com/contact/) and write ‘Data request’ or ‘Delete RadioFluxx account’. Describe whether the request concerns anonymous account settings, saved library items, a premium entitlement or website support data. Do not send passwords, payment credentials or government identification with the initial request. ## How we confirm account control Anonymous users may have no email address on file. We should therefore rely on a secure in-app account deletion or request token, authenticated session proof or another proportionate confirmation method rather than demanding government ID. The actual verification and in-app request methods must be implemented and confirmed; this draft does not imply they already exist. ## What deletion means Once verified and where applicable, requests can include removing the account’s corresponding records and any related data the operator controls, subject to lawful retention exceptions, operational backups and feasible propagation. App uninstall or clearing local data alone may not delete a server-side account. We must confirm whether associated saved radio, podcast, audiobook, history and entitlement tables are linked to uid or id so no connected records are overlooked. ## Data outside our systems RadioFluxx cannot automatically delete logs held independently by radio broadcasters, podcast delivery servers, audiobook hosts, app-store operators or other independent third parties. If those systems receive data, their own privacy and request channels may apply. ## Marketing preferences The current table contains marketingOptIn and supplied rows display true. That is a stored setting, not evidence that users knowingly consented to messages. We must verify its default, actual opt-in UI and any marketing integrations before describing it as valid consent or using it for campaigns. ## Deadlines, appeal and complaints Applicable privacy laws may specify response deadlines, verification rules, exceptions and appeal rights. We will follow the obligations actually applicable to the verified legal operator and user’s location. Support should keep a limited internal record of the request and resolution for compliance while minimizing additional personal data. ## Google Play deletion requirements If RadioFluxx allows users to create an in-app account, including through anonymous authentication where covered, the app may need an in-app account deletion option and a working web request mechanism. Publication of this page alone does not satisfy those technical requirements. ## Requests involving analytics and push notifications Our user database identifiers are distinct from Google Analytics or Firebase app- instance identifiers and OneSignal notification subscriptions or push tokens. Where legally applicable, we will review access, deletion and objection requests involving information under our control and identify relevant provider-specific processes. A user’s empty email field is not proof that analytics or notification services hold no technical data. We will not promise deletion from all independent providers without confirming technical capabilities. ## Plain English: three different identifiers **Your RadioFluxx account UUID** connects app preferences to your account. **An analytics app-instance ID** can distinguish an app installation for measurement.** A OneSignal push token or subscription ID** helps deliver notifications. Those are different things. We should explain all three rather than pretend the database’s blank deviceId field means that no technical identifiers exist. ## Technical steps remaining Before publication, confirm all Supabase user and library tables, authentication identifiers, account deletion RPCs, backend cascade handling, backups, server logs, active SDKs, location permissions and legal operator details. Then update the public text to reflect confirmed facts.