Guide
Account Security
Password changes, two-factor authentication, recovery codes, and workspace access.
SoundSync
Protect the developer account
-
Use a private account
Keep account credentials separate from product keys and partner integration tokens.
-
Enable two-factor authentication
Use the security setup in Settings and your authenticator to complete the challenge. A displayed setup secret alone does not mean 2FA is enabled.
-
Store recovery codes privately
Recovery codes are sensitive, single-use fallback credentials. Keep them outside public repositories, screenshots, and support posts.
-
Review team access
Use scoped roles and product assignments instead of sharing the owner account.
-
Handle account changes
Use the supported password/email-verification workflow and review sessions/access after a suspected compromise.
Login enforcement
An enabled two-factor account must complete the login challenge with its authenticator or a supported recovery code. Password knowledge alone is not the whole login flow.
Account closure and personal-data deletion are support-reviewed procedures. Do not assume a commented-out or internal delete route is an available self-service deletion feature.
