Privacy
The app keeps to itself.
OpenJSQ has no advertising and no account. There is no separate usage or crash reporting. We count the existing update checks by app version to understand release adoption, and you can turn those checks off.
What it does and doesn’t do.
- No separate usage reporting
- The app sends no separate usage or crash reports. It sends no callsign or messages with its update check.
- One check for a newer version (you can turn it off)
- When OpenJSQ starts with update checks enabled, it asks www.openjsq.com, at most once a day, whether a newer version exists. That request reveals your IP address and the OpenJSQ version, as any web request does. It sends no callsign, message or other data. If there is a newer version, OpenJSQ tells you and links to the download page in your own browser; it downloads and installs nothing. Turn it off in Settings › About & storage › Updates. When it is off, OpenJSQ makes no such connection.
- Aggregate update-check counts
- We count existing update-check requests to understand release adoption. Our statistics database stores only daily totals by app version, without IP addresses, callsigns, messages or installation identifiers. These totals show checks from participating profiles, not unique users or all installations. Turning off update checks also stops the requests used for these statistics. Download-count analytics remain disabled.
- Nothing else over the internet unless you choose it
- Apart from that check, OpenJSQ talks over your radio, your TNC and any network connection you set up yourself. The one other thing it opens for you: Help › Report a problem opens the problem report form in your own web browser, and you choose what to type and send.
- Diagnostics bundles
- A diagnostics bundle is made only when you ask for one. It holds recordings and logs of your station’s radio activity and settings. It stays on your computer until you decide to send it, and to whom. Look through it and remove anything personal first.
- Radio is public
- Amateur radio traffic is public by nature. Anyone with a receiver can hear and record what you send, including your callsign, your messages and your files. Do not send anything private over the air.
- Your data stays on your computer
- Settings, profiles, history, mail and files are kept in a data folder on your computer. Settings → Files & configuration shows where.
The application’s privacy terms are also in section 7 of the licence agreement.
The website and messages you send.
- Who is responsible
- Jerome Goddard II (W4IJG) operates this website. For privacy questions or requests, email contact@openjsq.com.
- Website hosting
- Cloudflare serves this website and the update-check file. It processes ordinary request information, including your IP address, request time and requested resource, to deliver the service and protect its security. Cloudflare’s privacy policy explains its processing of website visitors’ information.
- Website traffic reports
- We use Cloudflare’s aggregate website traffic reports to understand visits, popular pages and traffic trends. We do not use these reports to identify individual operators or track their activity across websites. Aggregate update-check counts are described above; download-count analytics remain disabled.
- Private dashboard sign-in
- The owner-only statistics dashboard uses an essential session cookie to keep its owner signed in for up to eight hours. This cookie is not used for analytics and is cleared when the owner signs out.
- Contact and problem reports
- The forms send your email and message, and any other fields you choose to supply, through FormSubmit to contact@openjsq.com. A name is optional on the contact form; callsign and email are optional on the problem-report form. We use what you send to respond, investigate problems and improve the documentation or software. FormSubmit handles its verification and confirmation pages. The forms do not upload diagnostic files.
- Material you send separately
- If you email a diagnostic bundle, screenshot or recording, it may include callsigns, messages and settings belonging to you or other operators. Review and redact it first. Send only what is needed to explain the problem.
- Fonts and statistics
- The fonts are served from this website, without a request to Google Fonts. Version statistics use only the existing update-check requests; download-count analytics remain disabled. We do not add analytics cookies, tracking pixels or installation identifiers. Hosting and form-verification processing still applies as described above.
- Why we use this information
- We rely on our legitimate interests in running and securing the website, understanding aggregate website traffic and release adoption, responding to requests and investigating software problems, subject to applicable data-protection law and your rights. We do not use support messages to build advertising profiles.
- Keeping information
- Correspondence and diagnostic material are kept only as long as needed to respond, investigate the issue and maintain a necessary support record, or meet a legal requirement. We remove or redact information no longer needed for those purposes. We review aggregate version totals after bench testing and keep them only as long as needed to understand release adoption. Hosting and form-service records are handled under the providers’ applicable terms and settings; we do not claim that those providers keep no logs.
- Other services
- The forum, GitHub and form-verification pages have their own privacy notices. Following an external link takes you to that service. Service providers may process information outside your country; consult their notices for their processing and transfer arrangements.
Your choices and privacy requests.
Turn off automatic update checks in Settings › About & storage › Updates. Creating or sending diagnostics is your choice.
Where applicable data-protection law gives you these rights, you can ask for access, correction, deletion or restriction of your personal information, object to its use, or request portability. Email contact@openjsq.com with enough detail to identify your request. We may need to verify your identity. GDPR requests are normally answered within one month; any permitted extension will be explained. You can also complain to your relevant data-protection supervisory authority.