Beta support

What support can help with

• Google sign-in, a cancelled callback, or a provider-account mismatch.
• Editing climbing profile, goals, locations, equipment, capabilities, or preferences.
• Why Beta returned no workout or asked about unplanned work.
• Offline workouts, restored timers, pending sync, session conflict, or takeover.
• Notification settings and denied permissions.
• Progress states with insufficient comparable evidence.
• Export status, deletion status, or a protected sign-out warning.

Safe information to include

You may include the app version, device platform and OS, language, approximate time of the problem, the visible safe error code, and a correlation ID shown by the app.

Never send a password, bearer or refresh token, provider credential, database row, raw athlete snapshot, pain note, account-export document, or an unredacted screenshot.

Safety boundary

Support can explain Beta controls and can advise stopping an app-directed workout. It may not override a pain gate, diagnose an injury, prescribe rehabilitation, or promise that a workout prevents injury. Seek an appropriately qualified health professional for medical concerns and local emergency services for an emergency.

Urgent product incidents

Cross-account access, data loss or duplication, a bypassed safety gate, deletion without reauthentication, local data cleared before server confirmation, or exposed private data must be escalated immediately through the monitored support channel.

Access, correction and privacy requests

Edit profile information in settings. For other corrections, access, export, objection or restriction, use the privacy contact on the privacy page. Initially send only the type of request; do not include health information, export files or identity documents. Support will arrange proportionate identity verification if needed. An acknowledgement does not mean the request has been fulfilled.