RadioGlobal

Privacy

RadioGlobal is the public brand of a worldwide radio and podcast service operated by an individual from the Dominican Republic.

Public contact: radioglobal.contacto@gmail.com.

RadioGlobal uses account, library, and technical data to provide playback and saved listening activity. Audio and feeds may come from third-party sources.

You can use the contact form without an account for privacy questions or requests about your data. Choose “My account and data”. Do not include your password or identity documents in the initial message. The form receives and stores your message; it does not send an automatic email reply. Contact form.

Local library and account

Favorites, history, followed podcasts, episode progress, and volume preferences can be stored in your browser. If you sign in, your account library is stored on the service and synchronized with your session. Registration uses an email address and a protected password; the browser uses a session cookie.

Contact messages

The contact form stores your name or alias, email, reason, message, receipt date, and read status to handle your enquiry. Only administrators can access messages. Messages expire 90 days after receipt in the active database. Expired messages cannot be consulted and are purged when the API starts and hourly while it operates. Administrators can delete them earlier; reading does not extend their expiry. Antispam counters use a hash incorporating the IP address and time window and remain valid for up to 15 minutes. Unused form tokens expire after one hour. Physical deletion happens in the cleanup cycle.

A hash used for abuse prevention is a pseudonymous identifier, not a guarantee of anonymity.

Deletion and backup copies

The contact-message retention period applies to the active database. Deleting a message or account data from that database does not immediately rewrite existing encrypted backup copies; those copies have a separate rotation. Signing out or letting a session expire does not delete your account or synchronized library.

Operational data

RadioGlobal usage-analytics transmission remains disabled for the initial release and AdSense is not integrated. Later activation requires the information and permissions applicable at that time. External stations or episodes may carry their own advertising. Technical operation processes connection information; logs can include routes, request identifiers, HTTP status and latency. Keeping analytics disabled does not remove local library, preferences, search history or temporary navigation storage.

The rg_session cookie lasts up to 30 days and uses HttpOnly, SameSite=Lax and Secure in production. The rg_locale language preference may last up to one year. Accounts have no self-service deletion or automatic inactivity deletion. You can request operator-assisted deletion. Session expiry does not prove immediate removal of every expired session row.

The account-backup job retains the latest 14 encrypted copies, rotating after successful backups: this does not guarantee deletion within 14 days. Manual release backups have separate lifecycles. Technical logs rotate by file size and count; no uniform maximum age in days is claimed for logs or all backups.

Images and third-party audio

RadioGlobal uses Contabo hosting. Preparing, restoring or playing external audio, including metadata preloading, can connect your browser to a broadcaster, publisher or CDN and follow redirects. Hosting location or international-transfer safeguards are not inferred from an IP address.

Some logos and podcast covers load directly from Cloudinary or other image providers. Viewing them connects your browser to those providers, even before you play audio. Playing a third-party stream or episode also connects to its provider and may follow redirects to another host. These providers receive connection information such as your IP address and browser headers and apply their own policies.

Access, correction, and deletion requests

You may request access, correction, deletion or opposition where applicable under Dominican Law 172-13 and any additional mandatory rights applicable to you. If a processing activity is subject to the GDPR, its relevant rights and deadlines also apply. Requests require human review and proportionate verification. No automatic, instantaneous deletion or deletion from independent providers is promised.

Use the channel on our contact page to request access to your account data, correct inaccurate data, delete your account data, or report an account-related incident. State which request you are making and include the email associated with the account. Describe any correction or incident briefly. Do not send your password or sensitive documents in the first message. We may need to confirm that the account belongs to you before acting on account data. Go to contact.

You can remove data stored only in this browser through its site-storage controls. This does not submit an account deletion request.