Privacy notice
Resonance Social processes only the information needed to connect accounts, gather a user's own post history and metrics, and synchronize that information with the application.
Information processed
- A random Resonance Social user and device-session identifier.
- Identifiers and display names for social accounts the user explicitly connects.
- Post metadata and available performance metrics supplied by those platforms.
- Encrypted access and refresh tokens needed to maintain a connection.
- Operational timestamps and errors needed to run and diagnose synchronization.
What is not collected
Resonance Social does not collect social account passwords. It does not sell personal information or use connected account data for advertising.
Storage and security
Backend information is stored using Cloudflare services. Application session tokens are stored as one-way hashes. Social-platform tokens are encrypted before database storage, and provider secrets are never included in public application or website files.
Third-party platforms
When a user connects a platform, that platform's terms and privacy policy also apply. Resonance Social requests only the permissions needed for post discovery and analytics.
Retention and deletion
Information is retained while the connection or Resonance Social backend account remains active. A user can disconnect accounts or permanently delete backend information. See the data deletion instructions.
Contact
During private testing, privacy questions should be sent directly to the person who provided the testing build. A dedicated support address and operating entity details will be published before wider release.