ALT VIDEO Privacy
Effective October 23, 2026.
ALT VIDEO is a personal media-library experience operated by WESTONB.DEV LLC. This notice covers ALT VIDEO and altvideo.net. Features and data practices vary by platform and build.
The planned Meta Quest edition
The standalone Quest edition has not been released. We are not collecting runtime data through a released Quest app. Meta processes activity on its store, including wishlists, under its own privacy policy. The desktop features described below are not a claim that those integrations or permissions are implemented on Quest. Before the Quest edition becomes available, we will update this notice to describe its actual data practices, including any device permissions, tracking information, account identifiers and deletion controls.
Your collection and connected services
The desktop app stores collection information on your device, including imported titles and artwork, ratings, notes, history, shelf arrangements, media-source identifiers and server settings. It uses this information to display your collection and open the media you choose. When you choose local media or music folders, the app reads the selected files and paths for playback. Personal radio files and paths stay on the device and are excluded from store exports.
When you connect a media server or online service, the app sends requests to that service to sign in, retrieve library information or artwork, and play media. The receiving service sees the request and network information, including your IP address. Your selected Plex, Jellyfin or Emby server and other providers have their own privacy practices. Public Letterboxd imports contact Letterboxd; catalogue and artwork requests may contact TMDB. These connections are not a promise that every integration is available in every build.
Credentials can remain in the current session or, where supported and you choose to remember them, be stored on your device. The Windows implementation protects remembered credentials using Windows account protection. A successful provider disconnect disables its routes and removes locally stored credentials. If credential cleanup fails, the app reports it and you can retry. Cached collection data remains. Disconnecting does not revoke access at the provider; you can manage or revoke access separately with that provider.
Where the Steam Cloud feature is available and you choose to upload, a portable collection bundle is sent to Steam. It can include titles, ratings, notes, curation and permitted artwork. Device-specific media paths and connection settings are excluded. Steam handles that cloud copy under its own policies. Deleting local files does not by itself delete a cloud copy.
Diagnostics and support
The desktop app keeps local diagnostic records to help investigate faults and performance. These include build and device details, performance measurements and selected error and playback-state events. The app’s diagnostic recorder keeps at most eight sessions, each capped at 1 MiB or 2,048 lines; it prunes older sessions at launch. It does not automatically send those diagnostic files to us. This recorder is separate from the operating system, game engine and distribution platform's own logs or services.
If you contact support or send a log, screenshot or other file, we receive the information you choose to send and use it to respond and investigate the problem. Review files before sharing: ordinary player logs and screenshots may include personal information, server addresses or other details. Do not post credentials or private deletion requests in a public bug report.
The website and community features
The website is hosted by Vercel. The Requests page and supporter submissions use Cloudflare. These providers process network information needed to deliver and protect their services. Their own policies describe their processing.
The Requests page stores a random browser identifier, submissions, comments, optional display names, votes and timestamps. It also records a salted hash of an IP address for abuse controls. Your browser stores the identifier in local storage. Clearing browser storage does not erase server-side submissions or votes. Requests and comments are intended for public display. If an anti-abuse challenge is enabled, Cloudflare receives the challenge token and IP address to check the request.
If you submit a supporter-name request, we store the supplied Twitch username, requested public name, resolved Twitch user identifier, moderation status and timestamps, together with an IP-address hash for abuse prevention. The Twitch identifiers are used to verify the subscription associated with the name claim. Approved names may appear on the website and in the game. Submit only a name you want made public. External payment or subscription providers handle transactions on their own services; this notice does not mean a payment feature is currently available.
Retention and deletion
Session credentials are kept for the current session. Your local collection and remembered credentials remain on your device until removed through available app controls or by deleting the app's stored data. Contact us for help identifying the correct files for your platform. Back up anything you want to keep. Uninstalling an app may leave its saved data behind.
We retain website submissions and supporter records while they serve the community feature, moderation or support purpose, unless removed following a deletion request or administrative action. These records do not currently have an automatic expiry. Support correspondence is retained while needed to resolve the issue and meet applicable obligations. Records held independently by a platform or provider are governed by that service; deleting data with us does not delete their copies.
For access, correction or deletion of information we hold, contact westonbdev@gmail.com. Identify the relevant submission or supporter name and the information you want removed. We may request enough information to verify that you control the record. Do not send passwords, payment details or government identity documents with the initial request. We will explain any data that must be retained and the applicable reason.
Updates
We will revise this notice when our practices change and display its effective date. Material changes will be described here before the changed practices take effect.