Privacy Policy

Last Updated: November 30, 2025

Overview

ClippyFront respects your privacy and is committed to transparency about data collection. All data is stored locally in your database instance and never shared with third parties. We do not use external analytics services or telemetry.

What Data We Collect

1. Account Information

When you create an account, we store:

  • Username and email – For authentication and account recovery
  • Password hash – Securely encrypted, never stored in plain text
  • Profile information – Display name, avatar, bio (optional)
  • Integration tokens – Twitch/Discord OAuth tokens (encrypted)
2. Content Analytics (Your Clips Only)

To power the Analytics Dashboard, we track engagement metrics for your Twitch clips:

  • Clip metadata – Creator name, game name, view count, creation date
  • Discord engagement – Share count and reactions on clips shared in Discord
  • Aggregated insights – Top creators, top games, viral clips, engagement trends

This data is YOUR content data (scoped to your user account) and used exclusively for analytics features visible in your dashboard.

3. Activity Logs (Audit Trail)

For collaboration features and audit purposes, we log:

  • Team actions – Member added/removed, role changes, team creation/updates
  • Project events – Project created, shared with teams, compilation started/completed
  • Timestamps and user IDs – Who did what and when

Activity logs help you track team collaboration history and troubleshoot project issues.

4. Render Usage (Quota Enforcement)

To enforce tier-based limits, we track:

  • Compiled video duration – Seconds of rendered output per project
  • Monthly totals – Aggregated usage to enforce Free/Pro/Team tier quotas

This prevents abuse and ensures fair resource allocation across users.

5. Application Logs (Debugging)

For troubleshooting and performance monitoring, we log:

  • Request metadata – API endpoint, HTTP method, IP address
  • User context – User ID and username (if authenticated)
  • Error traces – Stack traces for failed operations
  • Background task status – Celery task IDs and worker names

Logs are rotated and stored in instance/logs/ for operational debugging only.

What We DO NOT Collect

  • No third-party analytics – We don't use Google Analytics, Amplitude, Mixpanel, Segment, or similar services
  • No external telemetry – All data stays in your PostgreSQL database
  • No data selling or sharing – We never sell, rent, or share your personal information with third parties
  • No tracking pixels – No invisible trackers or third-party cookies beyond session management
  • No PII harvesting – We only collect what's necessary for core functionality

Data Security

  • Encryption – Passwords are hashed with bcrypt; OAuth tokens are encrypted at rest
  • User isolation – All queries are scoped by user_id to prevent cross-user data leaks
  • Database pooling – Connection limits prevent resource exhaustion and DoS attacks
  • HTTPS – All traffic is encrypted in transit (when deployed with SSL/TLS)

Data Retention

  • Account data – Retained until account deletion
  • Activity logs – Retained indefinitely for audit trail (team collaboration history)
  • Application logs – Rotated after 30 days or 50MB per file
  • Analytics data – Retained as long as associated clips exist

Your Rights

You have the right to:

  • Access your data – View all data associated with your account via API endpoints or admin panel (if admin)
  • Delete your data – Delete your account and all associated projects, media, and analytics
  • Export your data – Download compiled videos and media files at any time
  • Revoke integrations – Disconnect Twitch/Discord OAuth at any time from account settings

Self-Hosted Deployments

If you're running ClippyFront on your own infrastructure:

  • You control all data storage and retention policies
  • You are responsible for database backups and security
  • You can audit the codebase to verify data collection practices
  • You can disable analytics features if desired (set ENABLE_ANALYTICS=false in environment)

Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected in the "Last Updated" date at the top of this page. Significant changes will be announced via in-app notifications.

Contact

If you have questions about this privacy policy or data practices, please contact us through: