Last updated: Jan 02, 2026

SonarBuzz Privacy Policy

This policy explains how the SonarBuzz trend intelligence platform collects, uses, and safeguards customer data across the SaaS service.

1. Data we process

Account data—name, email address, workspace metadata, and billing contact details supplied during signup or via support.

Event telemetry—metrics, KPIs, and contextual payloads you stream into SonarBuzz. Customers remain controllers of this data; we act as processors.

Product analytics—usage diagnostics (feature clicks, page timing) collected to improve reliability; these are aggregated and never sold.

2. How we use your information

  • • Deliver core functionality like anomaly detection, alerting, dashboards, and customer support.
  • • Secure the platform (fraud monitoring, audit logging, abuse prevention) and meet legal obligations.
  • • Send service announcements, onboarding tips, and billing notices. You may opt out of non-essential messages.
  • • Generate anonymized insights that help us optimize infrastructure capacity and pricing tiers.

3. Data retention & security

Customer event data is retained for the lifetime of the workspace plus 30 days unless a shorter retention window is configured. Backups are encrypted at rest using AES-256 and stored in EU + US regions.

Access to production systems is restricted through SSO + MFA, audited quarterly, and logged centrally. We maintain SOC 2-aligned controls and run continuous vulnerability scanning.

4. Subprocessors & data transfers

We rely on vetted infrastructure partners (cloud hosting, email delivery, customer support). Each subprocesser signs DPAs that mirror GDPR/CCPA obligations. Cross-border transfers use Standard Contractual Clauses.

5. Your rights

Depending on your jurisdiction you can request access, correction, deletion, or export of personal data. Reach us at privacy@sonarbuzz.com. We will respond within 30 days.

6. Contact

Questions about this policy or our security posture can be sent to security@sonarbuzz.com. Urgent incidents should be reported through the in-app support channel.