Reproduce ordinary issues publicly. Report sensitive issues privately.
Choosing the right route reduces back-and-forth and keeps LAN addresses, clipboard contents, credentials, and payment details out of public issues.
CHOOSE A SUPPORT PATH
Compatibility, installation, bugs, and feature requests
A public issue should include OS and architecture, CrossFlow version, control direction, input hardware, reproduction steps, expected result, and actual result. Remove personal content and LAN addresses.
Security, privacy, or abuse-enabling matters
Input loss of control, permission bypass, identity spoofing, sensitive-data exposure, or a privacy-rights request must be private. Put “Security” or “Privacy request” in the title.
Purchase, receipt, tax, and refund
Paddle handles transaction support after live sales. Have the purchase email and Paddle order details ready; never post payment data in a CrossFlow public issue.
Release status and known limitations
Before download, confirm systems, signing status, permissions, version, SHA-256, current limitations, and emergency-pause guidance.
BEFORE LIVE SALES
A dedicated support mailbox remains a sale gate.
No personal email address is published today. Dedicated support/privacy mailboxes and their operating process must be configured before Paddle live checkout opens, then the relevant routes on this page will be updated. Until then, private GitHub reporting is the confidential channel for sensitive matters.