Contact
Use the channel below for product support, privacy rights, business inquiries, partnerships, security disclosures and formal correspondence.
SUBJECT-LINE ROUTES
Account access, onboarding, Check-ins, Dashboard, Plan, performance issues, errors or unexpected behaviour.
Access, correction, deletion, restriction, portability, objection, consent withdrawal or questions about data handling.
Partnerships, campaigns, research, media, licensing, investment, supplier or strategic inquiries.
Suspected security weakness, unauthorised access, data exposure or integrity issue.
Formal notices, rights assertions, disputes or other correspondence requiring an auditable record.
Emergency boundary
This inbox is not monitored as an emergency service. For urgent health, safety or security risk, contact the appropriate emergency service, qualified professional or platform provider directly.
Include enough information to act
- —Your name and the account email, where relevant.
- —Device model, operating system and app version for technical issues.
- —Date, time and time zone of the event.
- —Steps taken, expected result and actual result.
- —Relevant screenshots with unnecessary personal information removed.
- —The outcome or resolution requested.
Privacy Requests
State the right you wish to exercise and the relevant account or data. RBD may request proportionate identity verification before releasing, changing or deleting personal information. Do not send identity documents unless a secure method is requested.
Security Reports
Describe the affected feature, reproduction steps, likely impact and any evidence. Do not access another user's data, disrupt the service, retain personal data or publish details before RBD has had a reasonable opportunity to assess the report.
Do Not Send
Passwords, authentication codes, access tokens, full payment-card details, unnecessary medical records, or confidential third-party information. Redact material that is not required to understand the request.
Correspondence Standard
Messages are assessed according to subject, legitimacy and urgency. Abusive, unlawful, fraudulent, automated or irrelevant correspondence may not receive a response. Formal records should use a clear subject line and retain the original message thread.
Closing standard. RBD is designed to make the next decision explicit, proportionate and open to correction.