RigWave support
Find help, availability information and release notes.
How to contact RigWave
Choose the contact below that matches your question.
Support email
For product, licence and technical support, use support@rigwavesystems.co.uk. The support mailbox has passed a basic send-and-reply test. Automatic licence emails still need testing before launch.
General enquiries
For general, sales and business enquiries, use info@rigwavesystems.co.uk.
Data protection complaints
If your concern is specifically about how RigWave handled personal data, use the dedicated Data Protection Complaints route.
Facebook Messenger
Facebook Messenger may be added as another support route after launch.
Lost a paid activation code?
Do not buy again. Use Activation Recovery to read about the planned recovery process. Recovery is not open yet. When enabled, it will email a short-lived link to the original purchase address and replace an unused code with a fresh one.
Private beta feedback
Beta feedback is not open yet. When testing opens, invited testers will be able to record their Windows setup and report which functions worked, partly worked, failed or were not tested.
Use the Private Beta Notice for tester expectations and the Vulnerability Disclosure route for suspected security weaknesses.
Known Issues
RigWave is not public yet. See current access status and features still being tested on Known Issues.
Release notes
Public release notes will identify the released build. You can read current website and development updates on Release Notes.
Response times
Founder support is prioritised, but neither Founder nor standard support carries a fixed response-time promise.
Language and launch area
V1.0 website and support are planned in English for the UK launch.
Windows security warning? Do not switch protection off.
If Windows Security, SmartScreen or another trusted security product flags a RigWave download, stop and keep the warning visible. Check that you used the official download route, compare the published file identity, and contact support with the exact warning. RigWave support should never make “disable your antivirus” the standard fix.
Reporting a security issue
If you think you found a vulnerability rather than a normal support problem, use the Vulnerability Disclosure route so you know what information to include and how to avoid exposing secrets or other people’s data.
Find the real fault. Keep the safe path visible.
Explore scanning, audio routing and troubleshooting. Finding a problem is the first step; any supported fix still needs to be checked.