Diagnostics & Privacy
Found a bug, got stuck during setup, or have an idea that would improve the Suite? Your feedback helps us understand what needs attention.
You don’t need to diagnose the problem yourself. Explain what you were trying to do and what happened—we’ll work from there.
Sending useful feedback
Open Feedback & Diagnostics from the Control Hub’s navigation.
Choose the category that best fits, then include:
- A short summary of the problem or suggestion.
- What you were trying to do.
- What you expected to happen.
- What actually happened.
- Steps to reproduce it, if you know them.
- Whether it happens every time or only occasionally.
For setup or navigation feedback, tell us where you first looked, what wording you expected and whether you needed help. If something was confusing, that’s useful feedback even when the feature technically worked.
An example of the feedback form. You don’t need to fill every field to describe something useful.
Preparing a diagnostic report
A diagnostic report adds technical context to your feedback, such as version information, connection states and the status of relevant features.
- Open Feedback & Diagnostics.
- Select Refresh diagnostics so the information reflects the current state.
- Select Preview report and read through it.
- Use Copy report or Export report… to prepare a copy.
- Share it through the support or feedback area of the private-beta Discord.
Tell us if you restarted the Hub or OBS after the problem occurred. Some information may have changed by the time you prepare the report.
Preparing, previewing or exporting a report does not send it to us. You choose whether to share it.
Feedback & Diagnostics includes a summary of the Suite’s version and connection information. This example uses demo data.
Screenshots and recordings
A screenshot or short recording can help explain a visual problem, confusing setting or unexpected behaviour.
Before sharing, check for private messages, email addresses, account information, stream keys and other details you don’t want included. Capture just the relevant window or area where possible.
Please avoid including copyrighted music or video when a silent recording or screenshot will explain the issue.
If the Hub won’t open
You can still report the problem through the beta Discord.
Include the version you were installing or using, your Windows and OBS versions if known, and the exact wording of any error message. Explain whether the problem happened during installation, startup or after a particular action.
You don’t need to collect technical files before asking for help.
What information is included in diagnostics?
Diagnostic reports provide technical information intended to help investigate a problem. This can include:
- Hub and plugin version information.
- Build and beta-expiry information.
- OBS connection and version information, where available.
- Music-provider and song-request states.
- Relevant feature settings and status information.
- The feedback you entered into the form.
Use Preview report to see the actual contents before sharing. Some information may be unavailable when OBS or another component is disconnected.
What information is excluded?
The diagnostic report is designed to exclude authentication tokens, OAuth codes, Spotify Client IDs, raw credentials, chat contents and local music details. Usernames in file paths are redacted.
However, information you type into the feedback fields—or include in a screenshot—may still contain personal details. Review the complete report and any attachments before sharing them.
Is feedback sent automatically?
No. The Feedback & Diagnostics page does not automatically submit your feedback or diagnostic report.
The information stays on your computer until you choose to share it. Copying a report places it on your clipboard; exporting creates a file you can review and attach yourself.
Connecting the Suite to services such as Twitch or Spotify is separate from submitting diagnostics. Those integrations communicate with their respective services to provide the features you enable.
What happens when I share a report?
Shared reports are used to investigate problems, understand your setup and improve the Suite. We may ask follow-up questions or suggest a check to help narrow down the cause.
A report posted in a Discord channel can be seen by people with access to that channel. If you think it contains sensitive information, ask for a suitable private support route before posting it.
Never send passwords, stream keys, authentication tokens or recovery codes.
Why do you ask for my streamer identity?
Your streamer identity may differ from the name on your store account or order.
The beta application collects information used to review your application and contact you. You can also optionally provide your preferred stream name, Discord username, Twitch channel and alternative email on the beta product page.
We use these details to match your order with your application and contact you about beta access and support. They may also be recorded on your customer profile so we can recognise you by your streamer identity.
How do I correct my details or ask a privacy question?
Contact us through the store’s Speak to Us page if your contact details need correcting or you have a question about information you’ve provided.
Please don’t post personal information in a public Discord channel when making a privacy request.
For information about the store’s handling of customer and order data, read the Imperial Infusions Privacy Policy.
Can I still access diagnostics after the beta expires?
Yes. The current beta expires on 31 October 2026.
Normal Suite functionality is disabled after expiry, but Feedback & Diagnostics remains available so you can still prepare information for support.