Privacy Policy

This Privacy Policy explains how David Dias Digital handles information for Radarboard, including the public website, beta signup, documentation links, desktop downloads, and the Radarboard app experience.

Radarboard is designed as a local-first product. The app can run with a local SQLite database by default. Optional integrations, optional sync providers, hosted features, beta programs, and website services may involve third-party services as described below.

We collect only the information needed to operate the website, manage beta access, deliver the app, respond to requests, and improve the product.

• Contact information, such as the email address you submit when joining the beta list or contacting us.
• Website and product interest information, such as pages visited, referring pages, approximate location, device type, browser, and session activity collected through privacy-conscious analytics.
• Download and release information, such as the GitHub release page or installer asset you choose to open.
• Support information you choose to send, such as messages, screenshots, logs, diagnostics, or other context you provide when asking for help.
• App configuration and integration information that you enter into Radarboard, such as service connection settings, API keys, OAuth credentials, webhook URLs, or local preferences.

Radarboard is built to keep day-to-day board data on your device when you use the default local desktop setup. The desktop app uses local SQLite by default and can store preferences, layouts, widget configuration, and integration credentials locally.

If you choose optional cloud sync, hosted features, remote databases, third-party integrations, or MCP-connected workflows, information may be sent to the services you configure. Those services process information under their own terms and privacy policies.

Radarboard may encrypt stored credentials before writing them to supported credential stores, but you remain responsible for choosing which services to connect and for protecting your device, accounts, tokens, and database configuration.

We use information for the purposes described at collection and for normal operation of Radarboard.

• Provide the website, app downloads, beta signup, documentation, support, and product communications.
• Send beta access updates, welcome emails, release information, and service messages.
• Understand website usage, improve page content, and evaluate demand for integrations and features.
• Operate, secure, debug, and improve Radarboard, including investigating errors, abuse, or reliability issues.
• Comply with legal obligations and enforce our Terms.

Radarboard uses third-party services where they are needed for the website, beta program, downloads, analytics, communications, and user-configured integrations.

• OpenPanel may process website analytics events when analytics is enabled on the marketing site.
• Resend processes beta signup contacts and welcome emails submitted through the waitlist form.
• GitHub hosts Radarboard source code, releases, release notes, and downloadable desktop assets.
• Integration providers process the data you authorize Radarboard to access, such as GitHub, Sentry, OpenPanel, RevenueCat, Resend, Google Search Console, App Store Connect, and similar services.
• Infrastructure, hosting, email, security, and support providers may process limited information needed to deliver their services.

The marketing site may use cookies, local storage, pixels, or similar technologies for analytics, security, session continuity, and basic site operation. We do not use these technologies to sell personal information.

Browser and device controls may let you block or delete cookies and limit analytics collection. Some site features may not work correctly if required browser storage is disabled.

We do not sell personal information. We share information only when needed to operate Radarboard, use service providers, honor your instructions, protect rights and security, complete a business transaction, or comply with law.

When you connect a third-party service inside Radarboard, information may move between your device, Radarboard, and that service based on the permissions and credentials you provide.

We keep information only as long as reasonably needed for the purpose collected, including beta communications, support, security, legal compliance, and product operations.

Local app data remains on your device or in the storage provider you configure until you delete it, uninstall the app, reset the database, revoke credentials, or remove the connected service data. Third-party providers may retain information under their own policies.

We use reasonable administrative, technical, and organizational safeguards appropriate for the nature of the information we handle. No online or local system can be guaranteed to be perfectly secure.

You are responsible for protecting your device, accounts, secrets, API keys, OAuth credentials, database URLs, and any services you connect to Radarboard.

Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain processing of your personal information. You may also have the right to withdraw consent or complain to a data protection authority.

To make a request, contact hello@radarboard.app. We may need to verify your request before acting on it. Some requests may be limited by legal, security, fraud-prevention, or operational requirements.

Radarboard is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information to us, contact us so we can take appropriate action.

David Dias Digital is based in Canada, and our providers or users may be located in other countries. Information may be processed in Canada, the United States, the European Economic Area, and other locations where we or our providers operate.

Where required, we rely on appropriate legal mechanisms for cross-border processing and transfers.

We may update this Privacy Policy as Radarboard changes. When we make material changes, we will update the date above and, when appropriate, provide additional notice through the website, app, email, or release notes.