SUMMARY: NexQSO does not sell your personal data and does not use product analytics. The app stores radio settings locally, uses RevenueCat for subscription status, Google Mobile Ads for optional rewarded-interstitial ads that can extend a free connection session, and Web3Forms to deliver abuse and support reports. It also performs an IP-based location approximation to auto-select a nearby DMR server and resolves incoming caller IDs via the public RadioID database.
1. Introduction
This Privacy Policy describes how NexQSO ("we", "our", or "us") handles information when you use our mobile application and related web services hosted at https://nexqso.samuel.com.tr. We are committed to protecting your privacy and maintaining complete transparency regarding device permissions and data persistence.
2. Information & Third-Party Services
NexQSO minimizes the information it sends and does not operate a user-profile database. The following third-party SDKs may process limited technical or usage information under their own privacy policies:
- Google Mobile Ads: After a free connection session reaches its five-minute limit, the app offers a fully optional rewarded-interstitial ad that grants another five minutes. Google may process device identifiers, IP address, diagnostics, ad impressions, and ad interactions to serve, measure, and prevent fraud for ads. On iOS, NexQSO asks for App Tracking Transparency permission before starting the ad SDK. If you allow tracking, ads may be personalized and measured using your device identifier; if you deny it, ads are non-personalized. You can change this permission in iOS Settings. NexQSO does not use DMR voice content for advertising and does not sell personal data.
- RevenueCat: Subscription purchases and entitlement status are processed by RevenueCat and the relevant app-store provider. NexQSO receives subscription status so it can enable Pro features.
- IP-Based Server Selection (ipapi.co): When NexQSO needs to pick the closest DMR server, it may query the third-party service ipapi.co with your public IP address to approximate your region. The approximation is cached locally for up to six hours and is not shared with any other service.
- RadioID Lookups (radioid.net): When an incoming DMR call arrives from a caller whose identity is not already cached, NexQSO sends the caller's DMR ID to the public radioid.net API to resolve the associated amateur radio callsign for display.
- Abuse and Support Reports (Web3Forms): When you submit an in-app abuse report or the public report form, Web3Forms processes the reported DMR ID, callsign or display name, reason, optional details, optional contact email, app version, and timestamp, and emails the report to the developer. Reports are used only to review and act on the report, and are reviewed within 24 hours. Audio and message text are not uploaded. Do not include passwords or sensitive personal information.
- No Account Creation: We do not maintain user account databases, cloud user profiles, or centralized tracking servers.
- Opt-In GPS Position Reporting (Pro): If you enable "Position Reporting" in Settings, NexQSO may access your device's precise location while the app is open and connected, and transmit a formatted position report (NMEA RMC sentence) to the connected BrandMeister master. Reporting is off by default, is strictly opt-in, and never runs in the background. BrandMeister may forward valid reports to APRS-IS according to its own account/server policy. Position data is sent only to the connected DMR master and is not collected by NexQSO.
3. Local Data Storage & Persistence
To operate as a Digital Mobile Radio (DMR) client, the application stores user configuration parameters strictly locally on your device inside the application container sandbox:
- Amateur Radio Identifiers: Your CallSign and DMR Radio ID.
- Network Settings: Server hostname/IP, UDP port numbers, and hotspot access passwords.
- Favorites & Preferences: Saved Talkgroup lists, theme preferences, audio device and volume settings.
- Operational Caches: The last selected server, a cached server preset list, and the coarse IP-location approximation used for server selection.
- DMR Text Messages (Pro): Received and sent BrandMeister SMS threads, including message text, peer DMR IDs, timestamps, and read state, are stored locally on your device. Message text is never transmitted to logging.
These credentials and settings remain stored locally on your device. Uninstalling the application or selecting "Clear Storage" in system settings immediately removes all saved data.
4. Microphone Permission & Audio Data Rationale
NexQSO requests permission to access your device’s Microphone (`NSMicrophoneUsageDescription` on iOS and `RECORD_AUDIO` on Android).
Microphone Rationale: Microphone access is required solely to capture live speech audio while you press and hold the Push-To-Talk (PTT) button. Captured PCM audio is immediately encoded into DMR digital voice packets and transmitted directly over your active network socket to your connected DMR master server.
- Audio capture occurs only during active user-initiated PTT sessions.
- Microphone audio is never recorded in the background.
- Audio is never saved to disk, stored on external servers, or analyzed for voice recognition or targeted advertising.
5. Background Audio, Notifications & Pro Features
Pro subscribers may enable the following optional features; each is off by default or requires an explicit user action:
- Background / lock-screen receive: When "Background Audio" is enabled, NexQSO continues receiving and playing DMR audio while the app is backgrounded or the phone is locked. This keeps an active audio session running in the background; it does not record microphone audio. Push-to-talk remains disabled in the background, and audio stops if iOS suspends or terminates the app.
- Local notifications: With your permission, NexQSO may show local notifications for incoming private calls and new text messages while the app is not in the foreground. These notifications are generated on your device and are not routed through any NexQSO service. Notifications stop if the app is terminated; delivery after force-quit is not supported.
- BrandMeister SMS (Pro): Text messages are exchanged over your authenticated BrandMeister connection and stored locally on your device as described in Section 3.
6. DMR Network Communications & Public Transmissions
Amateur Radio operates as a public radio service governed by international regulations:
- When you transmit using NexQSO, your raw digital voice payload, CallSign, and DMR ID are transmitted across the user-configured DMR master server network (e.g. BrandMeister, TGIF, FreeDMR).
- In accordance with amateur radio regulations (e.g., FCC Part 97), communications over amateur radio networks are unencrypted and public. Other radio operators connected to the same talkgroup or reflector will hear your audio and see your CallSign.
7. App Store Privacy Disclosures
Apple App Store Privacy Nutrition Label
- Data Collected: Limited diagnostics and advertising data may be collected by the third-party SDKs described above.
- Data Linked to You: The applicable SDK and store disclosures determine whether technical data is linked to you.
- Data Used to Track You: If you allow App Tracking Transparency, Google Mobile Ads may use your device identifier to personalize ads and measure their performance. If you deny permission, ads are non-personalized. You can change this choice in iOS Settings.
Google Play Data Safety Declaration
- Data Collection: Google Mobile Ads, RevenueCat, and app-store services may collect limited technical, advertising, and purchase-related data.
- Data Sharing: Data is shared with these service providers only to deliver ads and process subscriptions.
- Security Practices: Data in transit is sent directly via socket to user-designated DMR servers.
8. Children's Privacy
Our Service is intended for licensed Amateur Radio operators and does not knowingly collect any personal information from children under the age of 13 (or 16 in certain jurisdictions). If you believe a child has provided us with personal data, please contact us for immediate resolution.
9. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. Any changes will be posted on this page (https://nexqso.samuel.com.tr/privacy.html) with an updated effective date.
10. Contact Us
If you have any questions or privacy concerns regarding NexQSO, please reach out via our support channel:
Website: https://nexqso.samuel.com.tr
Privacy Support: https://nexqso.samuel.com.tr/support.html
GitHub Repository: github.com/kaanyaren/NexQSO