Audialyze
Beta

Privacy Policy

Effective Date: June 25, 2025

Audialyze values your privacy. This Privacy Policy explains how we collect, use, and protect your personal data when you use our service.

1. What We Collect

  • Email address (via authentication provider)
  • Audio files (temporarily stored in server memory for up to 1 hour)
  • User feedback (rating and optional comment)

📊 Google Analytics

We use Google Analytics to collect anonymous information about how visitors use our website. This includes details such as pages visited, time spent on the site, and interactions with elements like buttons and links. The data helps us understand user behavior and improve the experience.

Google Analytics does not collect personally identifiable information (PII) unless you explicitly provide it. You can choose to accept or decline cookies related to analytics when you first visit the site.

2. How We Use Data

  • To deliver audio analysis and mastering results in real time
  • To improve the service through anonymous usage metrics
  • To collect voluntary feedback for platform development

We do not sell, rent, or share your personal data with third parties, except as required by law.

3. Data Handling & Storage

  • Audio files are temporarily stored in server memory for up to 1 hour, then automatically discarded
  • Audio files are never written to disk or stored permanently
  • Feedback data (rating, comments, and email) is stored locally to help improve the platform

4. Third-Party Services

We use trusted providers for authentication and hosting:

  • Supabase (user authentication, email)
  • Vercel (frontend)
  • Fly.io (backend)
  • Google Analytics (website analytics, with user consent)

All providers comply with GDPR and other relevant EU data protection standards.

5. Your Rights

You may request to access, correct, or delete your personal data at any time. Please contact: team@audialyze.com

6. Legal Status

Audialyze is currently operated by an individual developer based in the EU. The service complies with GDPR and will be updated once a formal company is registered (planned in Estonia).