WhatsApp program evidence
Visual proof of PlayerDesk member authentication over WhatsApp.
This page is a public reviewer walkthrough for the PlayerDesk Member Authentication WhatsApp program. Sender display name: PlayerDesk. Sender key: playerdesk-whatsapp.
PlayerDesk is a DBA of Flying Banana Productions LLC.
Privacy Policy
https://www.playerdesk.net/privacyTerms of Service
https://www.playerdesk.net/termsProgram
Program scope and required disclosures
These statements are the canonical compliance copy used across the website, legal pages, and member consent surfaces.
By checking this box and providing your phone number, you agree that PlayerDesk (sender key playerdesk-whatsapp) may send you recurring automated WhatsApp messages at the number provided for PlayerDesk member authentication, including authentication one-time passwords (OTP) sent as WhatsApp authentication-template messages. This is the PlayerDesk Member Authentication WhatsApp program. Consent is not a condition of any purchase. You can opt out at any time in PlayerDesk account settings, or by using WhatsApp's built-in message controls. WhatsApp messages are not SMS — replying STOP or HELP has no effect. See our Privacy Policy (/privacy) and Terms of Service (/terms) for details. Program evidence: /compliance/whatsapp-member-auth.
Account signup verification codes
One-time passwords sent as WhatsApp authentication-template messages when a member starts QR self-registration.
Account sign-in codes
One-time passwords sent during WhatsApp login for eligible members with active WhatsApp auth consent.
Phone verification codes
One-time passwords sent to confirm that a member controls the phone number on file before WhatsApp enrollment.
Opt-In
Website flows where members consent to WhatsApp authentication
Consent is collected before the first WhatsApp authentication template is sent. SMS STOP/HELP keywords are not used.
- Step: The visitor opens the public registration landing page from the venue QR code.
- Step: They select WhatsApp (no channel is preselected) and enter their name and mobile number.
- Step: PlayerDesk shows the WhatsApp auth disclosure, with links to the Privacy Policy and Terms of Service, directly beside the send button.
- Step: The tap is the consent. Pre-account consent evidence is recorded before any OTP is sent.
- Step: PlayerDesk sends a WhatsApp authentication-template OTP. After the visitor enters the code, the account is created or linked.
- Step: The member verifies a mobile phone number in settings by WhatsApp, or, with a verified phone, chooses WhatsApp under "Send my sign-in codes by".
- Step: PlayerDesk shows the WhatsApp auth disclosure, with links to the Privacy Policy and Terms of Service, directly beside that button.
- Step: The tap is the consent. PlayerDesk records it before any code is sent, and sign-in codes then go by WhatsApp. One consent covers every PlayerDesk venue.
Live Copy
Exact sample messages
These are representative authentication-template bodies. Free-form WhatsApp bodies are never used for business-initiated OTP.
Your PlayerDesk WhatsApp registration code is: [code]. This code expires in 10 min.
Your PlayerDesk WhatsApp login code is: [code]. This code expires in 10 min.