Privacy Policy

The developer of the SVXConnect apps is RF.Guru (rf.guru), a trademark of Dielectricum. For privacy questions, contact info@rf.guru. For general support, use our contact page.

Identity. Your call sign and email address are typed by you. They identify the operator on the reflector and form the subject of the X.509 client certificate you request. Email is used only for certificate-related correspondence initiated by the reflector operator — not by us.

Audio. Microphone audio is captured only while Push-to-Talk is active. It is encoded with the Opus codec and transmitted in real time to the reflector you configured. Audio is never recorded, stored or retained — on the device or by the developer.

Location. When enabled, the app uses the platform location service (Google Play services on Android, Core Location on Apple platforms) to obtain your approximate or precise coordinates. If that is unavailable or denied, the app may make a one-shot request to ipwho.is to derive an approximate, city-level location from your public IP. You can disable automatic location entirely and enter a city / latitude / longitude manually. Location is sent to your configured reflector so other operators can see where you transmit from; it is not collected by the developer.

Cryptographic material. A private key, certificate signing request (CSR) and the certificate issued by your reflector are generated and stored locally in the app's private storage. They never leave the device except as part of the CSR / certificate exchange with your reflector.

Settings. Reflector host, port, talkgroup lists, audio device choice and other preferences are stored locally on your device.

The app does not collect device identifiers, advertising IDs, contacts, photos, files, SMS or call logs, and contains no third-party analytics, advertising or tracking SDKs.

Your configured reflector. Receives your call sign, certificate-related material, real-time audio during transmission, your location (if enabled), and standard protocol metadata (selected and monitored talkgroups, software version). The reflector is chosen and operated by you or a third party you selected; its data handling is governed by that operator, not by us.

ipwho.is. Used only as a location fallback. The request consists of your outbound IP address as seen by the service. See ipwho.is for their policy.

Reflector portal. The app fetches public reference data (talkgroup metadata, call-sign hints) via GET requests for static resources. These include no personally identifying information beyond your IP address, as with any web request.

Platform location services. On-device location resolution uses your operating system's location provider; that provider's privacy policy applies (e.g. Google on Android, Apple on iPhone, iPad and macOS).

RF.Guru does not operate a backend that receives your personal data. Data leaves your device only to the destinations listed above.

• Microphone — to capture audio while Push-to-Talk is active.
• Background / foreground audio — to keep the reflector connection and receive-audio playback running when the app is in the background (a foreground service with a visible notification on Android; background audio modes on Apple platforms).
• Location (when in use) — to show other operators where you transmit from. Foreground use only; the app never requests background-location access.
• Notifications — to display the background-service notification (Android).
• Network — to connect to your reflector.

All app data lives on your device: settings and PKI material in the app's private storage; no audio recordings are kept.

To delete everything, uninstall the app, or clear its data via your platform's app settings. You can also reset the certificate material from inside the app (Settings → Certificates → Reset PKI).

The app is intended for licensed amateur radio operators. It is not directed to children under 13 and does not knowingly collect data from children.

Because you choose which reflector to connect to, the destination of your audio and metadata may be in a different country from where you are. Choose reflectors whose operators you trust.

Communication with reflector portals uses HTTPS. Reflector authentication uses an X.509 client certificate issued to your call sign, with the private key generated and held only on your device. The reflector protocol operates over UDP; some setup messages may transit in cleartext as defined by the SvxLink protocol.

If material changes are made, the "Last updated" date above will be revised and the new version published at this URL.

Privacy: info@rf.guru
Support: shop.rf.guru/pages/contact