Privacy Policy
Overview
This privacy policy explains what information WebVideoServer collects, how it is used and stored, and how uploaded files and related data are retained and deleted. It also describes identity features, administrative controls, and the automatic cleanup process that deletes files and database records after a configurable retention period.
Account and Identity
WebVideoServer uses ASP.NET Identity to manage user accounts. When you register or sign in we store basic account information (such as username, email, and account identifiers) in the application database. This information is used to authenticate you, associate uploaded files with your account, and to deliver notifications.
Uploaded Files and Processing
When you upload media files they are stored under the application's web root in a per-user, per-package folder (wwwroot/Files/{userId}/{packageId}). The files are processed by server-side tools (for example, ffmpeg) to create transcoded formats and poster images. Processing logs and job metadata are stored in the database and (where applicable) in Hangfire tables for background job tracking.
Retention and Automatic Cleanup
To limit storage use, WebVideoServer runs a scheduled cleanup process that deletes packages and their files after a configurable number of days from the date they were created. The default retention period is 5 days. Cleanup removes:
- All files in the package folder (original, processed, and archive ZIP files).
- Database records that reference the package (PackageJobs, UserPackages, Package entries).
Administrators can view and change the retention period from the Admin → Package Cleanup page. The cleanup job is executed by Hangfire and may be scheduled as a recurring background job. When cleanup runs, the database is updated to reflect removal and the CleanupSetting.LastRun timestamp is recorded.
Deletion and Notification
Deletion is permanent and irreversible. When a package is deleted (automatically or manually by a user or admin), the application attempts to delete on-disk files and then removes database records. If file deletion fails (for example, due to file locks or permissions), the application logs the error and still attempts to clean up database records. Users are responsible for retaining any data they wish to keep; download your package ZIP before the retention period expires.
Administrative Controls
Administrators have access to an admin panel that includes controls to configure the cleanup retention period and to start or stop the recurring cleanup job. The admin UI does not expose raw file system operations beyond the configured cleanup functionality.
Security and Access
Access to uploaded files is restricted by account ownership. The application verifies the logged-in user before serving downloads. File operations are performed by the application process; ensure the host grants appropriate file system permissions to the application identity. The application does not publish uploaded files publicly unless a user downloads them.
Third-Party Tools
Server-side media processing uses third-party binaries (for example, ffmpeg). These tools run on the server to transcode and generate thumbnails. The tools themselves do not receive user data outside the host environment.
Data Retention Exceptions
In some cases, the application may retain minimal metadata (for example, audit or logging records) for operational reasons even after files are deleted. Those retained records do not include the file contents and are kept only to support troubleshooting and auditing.
User Rights and Contact
Registered users may request deletion of their account and associated packages. Administrators may be able to assist with data removal. For questions about this privacy policy or to request data deletion, contact the administrator or support email configured for the deployment.
Changes to this Policy
This policy may be updated from time to time. The effective date and summary of changes will be provided in the application release notes or admin communications.