RigPlane
Legal

Privacy Policy

Last updated: November 20, 2026

This Privacy Policy explains how RigPlane collects and uses information when you visit rigplane.com, join the open beta, sign in to your RigPlane account, download software, buy RigPlane Pro, or contact support.

1. Information We Collect

We collect information you provide directly, such as your email address when you join the open beta or contact support. If you buy RigPlane Pro, Paddle provides us with order and license-related information needed to deliver the product and support the purchase.

When you use the website, we may receive basic technical information such as pages visited, browser type, approximate region, and referrer through consent-based analytics and hosting logs. When you download releases, our CDN or hosting providers may log request metadata needed for security and delivery.

If you send diagnostics or support files, they may include app version, operating system, radio model, configuration metadata, logs, support identifiers, and any contact information you choose to include.

2. Signing in with Google

You can sign in to your RigPlane account, including from RigPlane Pro, with your Google account. We ask Google only to confirm who you are. From Google we receive your email address, whether Google has verified it, and a Google account identifier. Google's sign-in screen may also offer your name and profile picture; we do not store them.

We use this information only to sign you in, to connect your RigPlane account to your beta access, licenses and activated computers, and to contact you about your account and support requests. We do not use it for advertising, we do not sell it, and we do not share it with analytics services. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We keep this information while your RigPlane account exists. To delete your account and the Google sign-in information linked to it, email [email protected] from the address you sign in with. We will delete it within 30 days, except purchase and license records we must keep for tax and accounting. You can also remove RigPlane's access at any time at myaccount.google.com/permissions.

3. How We Use Information

  • To operate rigplane.com and provide downloads
  • To send beta or product updates you requested
  • To process purchases, license access, refunds, and support requests
  • To diagnose product issues and improve RigPlane
  • To protect the website, downloads, and licensing infrastructure from abuse

4. Cookies and Analytics

We show our own analytics preferences panel to remember your choice (stored in your browser's local storage on this device) and manage consent for non-essential analytics. Necessary cookies, such as security or delivery cookies, may run because they are required to operate the website.

If you allow analytics cookies, we may use Google Tag Manager, Google Analytics, PostHog, and Microsoft Clarity to understand page visits, traffic sources, session behavior, and interactions with website links such as download, beta, account, pricing, checkout, support, and documentation links. We do not intentionally send raw email addresses, account identifiers, license keys, activation codes, hardware identifiers, support IDs, payment card details, or support files to these analytics services.

If you decline analytics cookies, we still count the visit with PostHog without cookies, browser storage or your IP address, so we can see overall traffic; this count is not linked to you. If you allow analytics, we also keep a random visit identifier in your browser's local storage for 30 days to connect a visit with a download or sign-in on our own sites. It is deleted when you withdraw consent.

You can change your cookie choice from the Cookie preferences link in the footer.

5. Crash reports in RigPlane Pro

Beta builds of RigPlane Pro send crash and error reports to Sentry, the service we use to track errors. A report is sent when the app crashes, a part of it stops unexpectedly, or an error occurs in the app window. This is on by default during the beta, and the app tells you about it the first time you run a beta build. A report contains the app and Core versions, your operating system and its version, processor type, radio model (without the serial number), connection type (USB, LAN or remote), technical details of the error, and a random install ID that you can reset in the app. We do not deliberately include your callsign, email address, IP or station addresses, frequencies, modes, QSOs, audio, license keys, settings or log files as fields of these reports. The technical details of an error are free text, though, and an error message can contain such information incidentally, for example a setting value or a mode name. Before sending, the app removes text that looks like callsigns, email addresses, IP addresses, host names, frequencies, passwords or tokens, and user names in file paths from the error details; if it can't do this, the report isn't sent. This removal is automatic, covers only the kinds of text listed above, and cannot guarantee that nothing identifying remains in the error details. Sentry keeps reports for 90 days and then deletes them automatically. Your IP address is not stored with them. You can turn reports off in Settings > Diagnostics; sending stops right away and reports still waiting to be sent are discarded (a report already on its way may still arrive). RigPlane Core, the open-source part, has no crash reporting of its own; RigPlane Pro reports only that Core stopped, with its exit code.

6. Services We Use

We use third-party services to run the product and website, including DigitalOcean for hosting, Cloudflare for security and delivery, Google for account sign-in, Resend for account and transactional email, Zoho Desk for support tickets, Google Tag Manager, Google Analytics, PostHog, and Microsoft Clarity for consent-based website analytics, Buttondown for email subscriptions, GitHub for public source code and issue workflows, Paddle for paid checkout, taxes, invoices, and payment support, and Sentry for crash and error reports from RigPlane Pro beta builds. These providers process information under their own policies and agreements.

7. Payments

Payment card details are handled by Paddle and its payment processors. We do not receive or store full payment card numbers. We may receive purchase status, customer email, product, license, tax, and refund metadata from Paddle so we can deliver RigPlane Pro and provide support.

8. Sharing

We do not sell personal information. We share information only with service providers that help operate RigPlane, when needed to complete a purchase or support request, when required by law, or when necessary to protect our rights, users, infrastructure, or the public.

9. Retention

We keep information only as long as reasonably needed for the purposes above, including product delivery, accounting, tax, security, support history, and legal obligations. You can unsubscribe from beta emails at any time using the unsubscribe link in the email.

10. Your Choices

You may contact us to request access, correction, deletion, or export of information we control, subject to legal and operational limits. For payment records controlled by Paddle, Paddle may need to handle the request directly.

11. Security

We use reasonable technical and organizational measures to protect information. No internet service can be guaranteed completely secure, so please avoid sending secrets, passwords, private keys, or radio credentials in support emails unless specifically requested through a safe channel.

12. Children

RigPlane is not directed to children, and we do not knowingly collect personal information from children.

13. Contact

Privacy and support questions can be sent to [email protected].