This notice explains how information is handled when you use RearSilver Stream Suite or RearSilver Avatar Suite, including their Demo editions, licensing, updates and support. It supplements our website privacy policy (https://imperialinfusions.com/policies/privacy-policy), which covers shopping and website activity. For the software activities described here, this notice provides the more specific explanation.

Who is responsible

IMPERIAL INFUSIONS LIMITED, company number 12560066, is responsible for personal information it processes through RearSilver licensing and support services. RearSilver is our product brand.

Address: 1 Chilham Court, North Shields, Tyne & Wear, NE29 8HB, England.

Email: contact@imperialinfusions.com. Website: https://imperialinfusions.com.

What stays on your computer

Settings, presets, artwork and other saved work are stored locally. Processing something in the application does not, by itself, upload it to us. Broadcasting output, connecting an integration, requesting updates or sharing a diagnostic report can involve separate data flows described below.

The paid editions are designed to store a signed licence entitlement and a protected customer licence key on your computer. The entitlement identifies the licence, product, edition and activation issue time. The saved key authorises future update downloads. Windows user-level protection is intended to protect the record; it does not make the information inaccessible to every program or privileged person on your computer.

Local use of a successfully activated paid edition does not require periodic online licence checks. Removing the local licence removes that app's saved licensing and update credentials but preserves settings and saved work. It does not erase server records, store orders, backups or copies you have exported.

Activation and licence administration

When you activate a paid edition, the app sends the entered licence key and product identifier to our licensing service over HTTPS. The activation request does not include an order number, customer account or hardware/device identifier. The service verifies the key and returns signed proof of its edition.

Our licence database stores a fingerprint of the key, its final eight characters, a licence identifier, batch identifier, product, edition, intended distribution destination, creation time and active/revoked status. Revocation and restoration records include their times and an administrative reason or reference. The database does not store the complete readable key. The complete key is nevertheless processed during generation, activation and authorisation and may be held in the store's delivery system or support correspondence.

The licensing service does not automatically synchronise purchaser names, orders or assignments from Shopify or itch.io. If you contact us about a purchase, we may use the assigned key and order information to find the relevant licence. Licence fingerprints and identifiers should therefore not be treated as anonymous information.

Initial paid activation needs the key. Without it, the paid app cannot activate. Demo editions do not require a paid key or use paid activation.

Updates and connection information

Checking for updates requests release information from our update service. Builds with update checking enabled can check automatically after startup; you can also check manually. Downloading an installer is a separate user action and requests the selected product/build/version file. Installer downloads and resume information are saved locally. Current Demo builds have update checking disabled.

Paid installer downloads are designed to send your licence key as an authorisation credential and check it with the licensing service; the installer file is delivered through Cloudflare infrastructure. This does not create an ongoing online check for local software use. Private Beta downloads use separate build-access credentials.

As with other internet requests, the hosting infrastructure processes connection information such as your IP address, request time, route and response status, and any request headers supplied by the client. Sending no device identifier in the activation body does not mean that the connection is anonymous.

Stream Suite integrations

When you enable Twitch integration, Stream Suite connects to Twitch for authorisation, account information and chat. It processes login/display names, user identifiers, role indicators and chat messages for the requested commands and song-request features, and can send chat messages as configured. Account credentials and request information are held locally where needed. This is separate from the RearSilver licence service; chat is not submitted to that service.

When you enable Spotify, Stream Suite uses Spotify authorisation and playback APIs. Spotify receives the authorisation/playback requests, search text or selected track identifiers. Stream Suite receives account and playback information such as display name, track/artist/album details, queue state and artwork. The app stores its configuration and a protected refresh credential locally; working access credentials are used to make requests.

YouTube searches and playlist requests pass through our RearSilver YouTube resolver, hosted on Cloudflare, which requests metadata from Google's YouTube Data API. Search text, video/playlist identifiers or URLs and filtering options are processed by this service and Google. The resolver also uses a country code supplied by Cloudflare to select region-appropriate results. Search terms and playlist URLs are included in requests to the resolver and can form part of the connection information processed by the hosting infrastructure. Playback then connects to YouTube/Google through the embedded player. Remote artwork can be downloaded from the relevant provider hosts.

Local music files, library paths and metadata, preferences and some request information are stored locally. Local playback, Suite/OBS communication, overlay delivery and replay presentation use local application or OBS resources. They are not uploads to the RearSilver licence service. Output you broadcast or media you access through an online provider is handled by the streaming/provider software you choose.

Avatar Suite processing and integrations

Avatar Suite reads the selected microphone locally to calculate the level that drives animation. It does not record, upload or retain the raw microphone audio. The selected microphone device identifier is saved in local settings; it is not sent as a hardware identifier to the licence service.

Imported artwork is copied to local application storage. Presets, drafts, image references and preferences are saved locally, and exported presets can include artwork. You choose where to save or share those exports.

Avatar rendering and Spout texture sharing occur locally. Its automation connection accepts commands from applications on the same computer and can return information such as preset/layer/effect names to those local clients. Avatar does not itself connect to Twitch, Spotify or YouTube; your separate automation or streaming tool may connect to those services under its own settings and privacy terms. Capturing or broadcasting Avatar output through that tool makes the output available wherever you choose to send it.

Diagnostics and support

Diagnostic reports and packages are prepared locally. The app does not automatically submit them to us. You choose whether to save, copy or share them and which support channel to use.

Reports can contain product/build versions, user-entered feedback, settings and connection status, system information and relevant activity summaries. Stream Suite can export a ZIP containing its report, selected local logs and Windows crash records/dumps. A crash dump can contain fragments of process memory, including personal information or credentials, even where text reports and logs redact sensitive fields. Review what you share, and omit a dump if you do not want to disclose its contents.

Avatar's current export is a text report rather than a crash-dump package. It excludes image contents, local image paths, microphone device names and credentials, but can include your active preset name, last automation action and entered feedback. Raw Avatar runtime logs are separate: they can contain full local artwork paths. Do not assume a raw log is redacted just because a generated report excludes those fields.

When you contact us, we receive the information you supply, such as your email or platform username, issue description, order information and attachments. If you use a third-party support platform, that provider also processes the information under its own terms and privacy notice. Sharing a diagnostic package is optional and does not by itself subscribe you to marketing.

The apps do not include a first-party advertising, usage-analytics or automatic diagnostic-upload service. Third-party embedded runtimes, online providers and Windows may process their own technical information under their respective terms and privacy notices.

Why we use information

We use information for the following purposes:

- Providing purchased activation, authorised updates and related support: performance of our contract with you, where the processing is necessary for that contract.
- Protecting licensing and delivery services, investigating misuse and maintaining relevant security/audit records: our legitimate interests in operating reliable services and preventing fraud, subject to assessing your rights and the necessity of the processing.
- Meeting applicable accounting, legal and regulatory requirements: compliance with the relevant legal obligation.

Providers and disclosures

Cloudflare provides our licensing, database and update-hosting infrastructure. Authorised personnel and service providers may access relevant information where necessary to operate these services or answer a support request. Purchases and key delivery through Shopify, Pendora or itch.io involve those services separately from app activation. Optional integrations communicate with their respective providers as explained in the product sections.

We may disclose information where required by law or where necessary and lawful to protect our services or establish, exercise or defend legal claims. Some providers process information on our behalf; others operate independent services under their own privacy notices.

How long information is kept

Local settings and saved work remain under your control until removed; exports, backups and Windows crash records may have separate lifetimes. A local licence remains until removed or replaced. Uninstalling an app may preserve its local data.

Our licence database currently has no scheduled automatic expiry for licence, status or revocation/restoration audit records. These records support recognition of perpetual licences, reinstalls, licence administration and investigation of disputed or misused keys. Removing a licence from your computer does not delete these server records. You can contact us about access, correction or erasure; applicable legal requirements and the continued need to recognise your licence may affect what can be deleted. Support correspondence and infrastructure logs are separate from the licence database and may have different retention periods. Contact us for information about the records relevant to your request.

Your rights and choices

Depending on the applicable law and basis for processing, you may have rights to access or correct your information, request erasure or restriction, object to processing and receive portable information. These rights are subject to applicable conditions; for example, some records may need to be retained for a legal obligation or legal claim.

Contact contact@imperialinfusions.com to make a request or raise a concern. We may need proportionate information to confirm that the request concerns your information. Do not post a licence key publicly to identify yourself.

You may complain to the UK Information Commissioner's Office at https://ico.org.uk/make-a-complaint/ or another supervisory authority available to you under applicable law.

Changes

We will update this notice when the relevant processing changes and provide further information or notice where required.