Security at Reverb
Reverb is designed so creators can connect accounts and publish without sharing social-media passwords with us.
OAuth connections
Authorization happens on the social platform’s own consent screen. Upload-Post securely manages the resulting publishing connection. Reverb stores account identifiers and connection status, not your social-media password or raw platform OAuth token.
Application security
Reverb uses encrypted HTTPS connections, short-lived access tokens, rotating refresh sessions, password hashing and signed provider webhooks. Access to production credentials is restricted to server-side environments.
Infrastructure
The application is hosted using established infrastructure providers. Production services, databases and media storage are access-controlled, and provider credentials are not included in browser code.
Report a concern
If you believe you found a security issue, please email us with the affected page, a clear description and safe reproduction steps. Do not access another person’s data while investigating.
Questions?
Email hello@reverb.com.ng.
Last updated 10 September 2026