Cookies & storage technologies
Use only what the site genuinely needs, explain it clearly and do not hide tracking behind the furniture.
What this test site does now
The current test-site files do not include an analytics tag, advertising pixel or marketing tracker. The live hosted site must be checked again before this statement is used for public launch.
Purchase continuity
Prepared purchase and account-recovery journeys may use short-lived storage in the same browser tab so a return or retry can continue without accidentally creating a duplicate attempt. Those live journeys are currently locked.
If they are enabled later, RigWave must keep the stored information to what is genuinely needed, explain it in plain language and apply any notice or consent requirement that is in force.
Third-party calls
The current private-beta website package keeps the Founder availability widget disconnected while commerce is locked, so that counter does not make a live backend request. If the counter is deliberately enabled later, the browser will make a read-only request and ordinary connection information will accompany it; the request is not intended to send your name, email address or licence ID.
The exact hosted site, service logs, response headers and any other third-party calls must be checked again before launch.
Browser storage is part of the privacy check
Browser storage can still fall within privacy and storage/access rules even when it is not called a cookie. Before purchase or recovery is enabled, each use must have a clear purpose, use the minimum information needed and provide any notice or choice required by the rules in force.
Consent rule
If non-essential cookies, analytics, pixels, browser storage or similar storage/access technologies are added later, they must not run before the required valid consent unless a lawful exception applies. Users must be told what is used and what it does.
Desktop app
Local app settings, profiles and backups are not website cookies. They are local software data and are covered by the Privacy Notice and the final product design.
Launch check
The exact deployed website must be tested again for cookies, browser storage, scripts, tags, pixels and third-party calls before the public notice is finalised.