Live Sharing privacy
No WhatsApp alert before the recipient chooses. A STOP blocks new Live Sharing sends to that recipient on that channel immediately. Changing how RigWave privately recognises the recipient behind the scenes must not reset or weaken that STOP. If any earlier send is still being checked, RigWave must show STOP REQUEST RECEIVED / CHECKING until the stop can be confirmed.
Explicit opt-in
A minimal, protected recipient reference may be processed first only to create or manage the consent invitation and check whether that person has already asked not to receive Live Sharing alerts. That is not consent and does not send a WhatsApp alert. An affirmative recipient choice is required before future Live Sharing alerts or content may be sent. Turning on another RigWave feature must not silently turn on Live Sharing. Live Sharing consent is only for Live Sharing alerts; it is not consent to marketing, newsletters or promotions. After STOP, alerts stay off until the recipient makes a fresh affirmative opt-in choice; reloads, sender actions and unrelated settings must not silently turn them back on.
Enter the recipient number safely
Use the full international phone number beginning with + and the country code, for example +447700900123. Spaces, brackets and hyphens may be accepted for readability and reduced to that same international number before use. Letters, extra plus signs, dotted or slashed forms, or a number whose country meaning is unclear must be rejected rather than guessed. If RigWave cannot safely understand the number, it must stop without creating consent or send eligibility.
Clear stop route
A clear STOP or disable control must be available. Once STOP is received, RigWave must not start another Live Sharing send to that recipient on that channel. If any earlier send for the same recipient and channel is still unresolved, show STOP REQUEST RECEIVED / CHECKING rather than MESSAGES STOPPED. If RigWave is updating how it privately recognises that recipient, or cannot safely match the recipient yet, keep the customer state at STOP REQUEST RECEIVED / CHECKING, keep new sends blocked, and do not ask the customer to try again. Final MESSAGES STOPPED wording is allowed only after no send for that recipient and channel remains unresolved and the stop has been committed. Do not claim whether an earlier message was delivered. Opting out of Live Sharing does not cancel the core RigWave licence or unrelated features.
Minimum stop record
After a STOP request, keep only the minimum protected recipient and channel reference, request date/source and bounded checking/finality evidence needed to respect and prove the request. A behind-the-scenes identity change must keep the same stop state. Final stopped wording may be shown only after no send for that recipient and channel remains unresolved and the stop has been committed. Message content should not be kept unless genuinely necessary.
Customer responsibility
You remain responsible for lawful messages, recipient permissions, platform rules, content rights and destination choices.
Harassment and harmful content
Do not use Live Sharing for bullying, harassment, stalking, threats, discrimination, doxxing, impersonation, deception, spam, fraud, unlawful surveillance or exploitation. For help with threatening or harmful online content, see Police.uk online harassment guidance ↗ and Report Harmful Content ↗.