PRIVACY & DATA · UPDATED OCTOBER 20, 2026

Your screen stays yours.

ClipForge records and edits files locally. Recordings, screenshots, audio, filenames, file paths and diagnostic logs are not automatically uploaded to this site.

Optional usage statistics

Usage sharing is off by default. If you enable it in the desktop app, ClipForge can send launches, app-open time, recording duration, feature use, quality choices and success/failure counts with a random installation ID and app version. App-open time includes idle time. These statistics help the developer understand what works and what needs improvement.

Feedback you choose to send

Feedback includes the category, your message, optional email address and app version. Avoid private recording details or passwords. Queued submissions may remain in your local profile until they can be delivered. A successful local queue message does not mean the developer has received it yet.

Infrastructure and storage

This project is designed for Vercel hosting and Supabase database storage. The receiving infrastructure sees network information such as your IP address. The application stores a daily keyed digest for rate limiting rather than a raw IP. Hosting providers may retain their own operational logs.

Retention and controls

The database cleanup function is designed to remove raw usage events after 90 days, feedback after 180 days, and expired rate-limit buckets after one day. The operator must schedule that function as described in the deployment guide. Backup retention depends on the configured database provider.

You can turn usage sharing off in More → Privacy & usage statistics. This deletes queued usage events; it cannot recall requests already sent or data already received. Feedback submission is independent of usage sharing.

Contact and deletion requests

For privacy questions or deletion requests, contact the developer through hichamhr.com. Include a feedback submission ID or the installation ID from your local outbox metadata when available. Do not send your recordings or local database file.

Operator setup: confirm the live hosting region, retention schedule and contact route before enabling public collection. This page describes the intended deployment and does not claim that a collector is already live.