The current pre-release site does not need an account just to read it. Normal hosting/security logs may still record connection data.
Your privacy
Use the minimum data needed. Keep setup and audio local by default.
PRIVACY AT A GLANCE
The short version first.
The full notice below remains the governing detail. This summary is here so you do not have to decode legal wording before you understand the basic shape.
Send only what is needed to solve the problem. Do not send passwords, stream keys or payment-card details.
Prepared payment and licence routes remain closed. When enabled, provider handling must match the final deployed configuration and notice.
Dedicated routes exist for data rights and data-protection complaints.
Invited beta testers: the specific processing, lawful bases and retention periods for the private beta are in the Private Beta Privacy Notice.
Plain English: RigWave should not turn your streaming setup into a data-harvesting exercise.
Who is responsible for your data
The data controller is Gary Woodward, sole trader, trading as RigWave Streaming Systems. Trading, business correspondence and service address: 6 Adlington Drive, Northwich, Cheshire, CW9 8BP, United Kingdom. Privacy, data-rights and data-protection complaint enquiries can be sent to info@rigwavesystems.co.uk. The owner has expressly authorised publication of this address for RigWave customer and legal-compliance purposes.
What stays local
Audio analysis, setup profiles, device/routing information, backups and optimisation history are local by default in V1.0. Cloud profile sync is not part of V1.0.
Registration and licence data
Minimum registration, licence and device/install information may be needed to run the trial, activate a paid licence, prevent obvious trial abuse, process resets and keep legal/payment records. RigWave does not currently use a conventional customer website login account for the trial/licence flow.
Diagnostics and support
Support reports are customer-triggered. You should be able to see what will be sent and cancel before upload. Normal diagnostics should avoid passwords, stream keys, access tokens, private messages and unnecessary sensitive data. Exact retention periods are not being presented as final in this preview because the retention schedule still requires professional approval. Support tickets and diagnostics should be kept only for as long as they are genuinely needed for support and any applicable legal, security, fraud, accounting or dispute purpose. The approved periods and any preservation exceptions must be published and bound to the release process before automated retention/deletion rules are enabled.
Website and browser-service data
The private-beta download gate reads a same-origin static release manifest and does not ask for your name, email address or payment details. Normal website hosting can still create technical connection logs such as IP address, time, requested path, browser/network headers and security events.
The prepared paid purchase and recovery journeys remain locked. When enabled in a later release lane, RigWave backend services use Supabase for licence/purchase workflow state and Stripe for payment checkout/confirmation. Payment-card entry is intended to occur on Stripe’s payment surface, not in a RigWave-hosted card-number form. Exact enabled services, purposes, retention and international-transfer information must match the deployed configuration before commerce opens.
While the website-side commerce lock is active, the Founder availability widget does not call the live backend. If that counter is enabled later, the browser will make a read-only request to a RigWave backend service and ordinary network metadata will accompany the request.
Recipients, processors and international transfers
Depending on the feature used, RigWave may use Stripe for payments, Supabase for backend/licensing services, Resend if retained for transactional email, Fasthosts for hosting/domain/email, and Meta/Facebook/WhatsApp only for optional features that pass their production release gates. RigWave maintains supplier/DPA/subprocessor and transfer evidence internally. Some providers may process data outside the UK; the final production record must identify the applicable lawful UK transfer safeguard rather than claiming that all data stays in the UK.
Lawful bases
RigWave maps a lawful basis to each purpose rather than using one blanket basis: contract/pre-contract steps for necessary purchase, licence and support administration; legal obligation where law genuinely requires records; legitimate interests for proportionate security, fraud prevention and legal-claim protection after necessity/balancing review; and consent where a genuine optional choice is required, including non-essential storage/marketing or channel-specific messaging where applicable.
No default usage tracking
Automatic product-usage tracking is not intended to be on by default. Any future analytics must have a defined purpose, lawful basis and any required storage/access consent or objection mechanism before it is enabled; "anonymous" must not be claimed unless the deployed data flow genuinely supports that description.
Audio supplied for support
Customer-uploaded support audio is case-specific and should be deleted as soon as reasonably possible after the support need ends. It should not be reused without separate explicit permission.
Live Sharing
Live Sharing uses a consent-first design. Before any Live Sharing WhatsApp alert is sent, a recipient must make an affirmative choice on the consent page. A minimal protected recipient identifier may be processed first only to create/manage the invitation and check suppression. A STOP/disable route must be clear, and a suppression record may keep only the minimum identifier and opt-out date/source needed to respect the choice.
Live Chat Hub and platform data
Live Chat Hub is not available to customers in this test site. If released, each connection must use the platform’s official authorised access and use only the account/chat information needed for the connection, source label, connection health and any moderation action you choose.
The final privacy notice must identify the exact permissions, retention, service providers and international-transfer position before those connections are enabled.
Private beta downloads and feedback
The private-beta download page is designed not to require an account, card, name or email address. The release manifest contains build identity, approval state and download-path information, not tester identity.
If you voluntarily email beta feedback or request support, RigWave may process your contact details, the content you send, candidate/build identity, diagnostics you deliberately attach and ordinary message metadata for support, defect investigation, security, fraud prevention or dispute handling as applicable. Do not include passwords, stream keys, access tokens, private conversations or unrelated personal data.
No automatic product-usage analytics is enabled by this website package. If telemetry or analytics is proposed later, it requires a separate documented purpose, data-flow review and any notice/choice required by the law in force.
Your rights
You may have rights to access, copy, correct, delete, restrict or object to processing. The intended process is to respond to valid data-rights requests without undue delay and within the applicable legal time limit, normally one calendar month. Lawful extensions, exemptions and retention duties may apply. See Data rights and Data protection complaints.
Automated decisions
RigWave should avoid solely automated decisions with legal or similarly significant effects unless a lawful basis, safeguards and human-review route exist.
Privacy contact
For privacy and data-protection enquiries, use info@rigwavesystems.co.uk. This address has passed a pre-launch inbound-and-reply round-trip test, and the returned message passed SPF, primary DKIM and DMARC authentication checks. Professional legal/privacy review remains a separate check before public launch.
Data protection complaints
If you think RigWave has handled your personal data incorrectly, use the dedicated Data Protection Complaints route. This is separate from making a data-rights request.
Final legal review
Before public release, the final Privacy Notice must clearly state why each type of personal data is used, the legal basis relied on, how long it is kept, who receives it and any required international-transfer information. Professional privacy/legal review remains open.
Privacy information should stay short, clear and easy to find, with extra detail available when it is useful.
Privacy by design
RigWave must minimise personal data from the design stage, restrict access to what each function genuinely needs, keep secrets out of ordinary logs/support bundles and document the purpose, lawful basis, retention and recipients for live processing. A new or materially changed high-risk processing activity must be assessed before it is enabled, including a DPIA where the law requires one. Production processor/subprocessor and international-transfer arrangements must be verified against the exact deployed services rather than inferred from test fixtures.
This is a safety-design statement, not a claim that every final data-protection document or DPIA has already been professionally approved.