Privacy policy

Last updated: September 13, 2026.

Who is responsible

RetroFeel is developed and operated by Chris Gliddon, doing business as Tiger/Wolf Games, in British Columbia, Canada. For privacy questions, access or correction requests, or help deleting information, reach Chris, our Privacy Officer, through the contact form.

This notice covers retrofeel.org and describes RetroFeel’s current recording and optional YouTube publishing features. It does not cover separate Variant Hunter game accounts and online services. RetroFeel was built to help develop Variant Hunter and remains in active development; the YouTube publisher is currently a studio-operated workflow, not a public hosted upload service.

Visiting this website

This is an informational site hosted by Cloudflare, with a server-side contact form. We do not add advertising, visitor analytics scripts, tracking pixels, embedded video players, or application cookies to these pages. Fonts are hosted here rather than requested from a third-party font service. Merely visiting does not connect your Google account or upload recordings.

Cloudflare processes network and request information, such as IP addresses, requested URLs, and browser information, to deliver and protect the site. The contact service uses IP-based rate limits and operational logs to limit abuse and diagnose failures. We do not deliberately log message bodies or submitted email addresses. Cloudflare may apply its own security mechanisms. Its handling and retention are described in the Cloudflare Privacy Policy. The hosting and email networks can process information outside Canada.

When you submit the contact form, Cloudflare processes your name (if provided), reply email address, topic, and message, and sends them to our support mailbox using Cloudflare Email Service. We use that correspondence to answer your request and investigate related issues. The website does not maintain a separate message database. Correspondence remains in our email system according to the retention practices below. The form does not accept attachments or subscribe you to marketing. Please do not send passwords, authorization tokens, sensitive recordings, or unnecessary personal information.

Local recording and transcription

Depending on your platform and enabled features, RetroFeel processes gameplay video, screenshots, game/system audio, microphone audio, timestamped transcripts, controller or other supported input events, device and game identifiers, input layouts, file paths, and recording diagnostics. Local library and export features also use preferences, game-library information, save data, and manifests.

Recordings can contain names, chat, voices, and notifications visible or audible during a session. Use the applicable RetroFeel or Steam controls to start and stop capture. Avoid entering sensitive information while recording, tell other participants what will be captured, and obtain appropriate permission.

Recording files are stored on the computer or Steam Deck running RetroFeel. The configured local transcription workflow processes audio on-device. Model, core, and artwork downloads contact external distributors; those requests disclose ordinary network information and may identify the requested game or file. Sharing an exported recording with us or an external review/AI tool is a separate action, subject to the recipient’s practices.

Connecting YouTube

RetroFeel uses YouTube API Services only for the optional authorized publishing workflow. Google handles sign-in and consent. RetroFeel receives authorization tokens, not your Google password.

The publisher reads channel identity, recent uploads, processing status, and caption information to verify the destination, avoid duplicates, and track completion. It sends eligible MP4 videos, available SRT subtitles, and metadata including game name, recording time, session identifier, title, description, category, and selected visibility. Raw input logs, ROMs, and save files are not included in that upload workflow.

Each publisher has a separate channel-bound token. Tokens, resumable-transfer state, video and caption identifiers, and receipts are stored locally to support the operation. The Google scope can permit broader YouTube management than this feature uses; the current uploader does not delete YouTube videos, post comments, or change ratings.

Publishing privacy is explicitly configured; the example uses Private. Eligible historical recordings can be included according to the configured cutoff. Private videos still leave your device and are processed by Google. YouTube’s Terms of Service and Google’s Privacy Policy apply. Google may process information outside Canada.

RetroFeel’s handling of information received from Google APIs is subject to the Google API Services User Data Policy, including Limited Use. This publishing workflow uses that data for channel verification, uploads, captions, and recovery—not advertising, data brokerage, or general-purpose AI-model training.

Retention and controls

You control recordings and exports stored on your own devices. In the current managed Deck setup, only derived MP4 archives are scheduled for deletion seven days after successful YouTube processing, matching visibility, and resolved caption handling. Incomplete uploads keep their MP4. Original sources, input data, manifests, transcripts, subtitles, and receipts are not deleted by this rule.

The current software does not automatically expire all retained YouTube API receipts or clean them up after authorization is revoked. These require separate handling; the MP4 retention setting is not an account-deletion feature. Contact us for assistance with the managed setup. We do not represent this early implementation as a complete automated data-deletion service.

Disable publishing to stop future automated uploads. You can separately revoke authorization through Google’s connected-app permissions. Revocation does not remove existing local files or videos already uploaded to YouTube. Manage uploaded videos and captions in YouTube Studio, or contact us if we operate the destination channel.

For support correspondence and material we receive, contact us to request access, correction, or deletion. We may need proportionate identity verification. We assess retention according to the purpose of your request and applicable legal obligations; we do not promise that a local deletion removes independently held copies or provider backups.

Safeguards and your rights

The current Deck setup uses owner-restricted files for OAuth secrets and HTTPS for Google communication. File permissions are not encryption at rest. Access to your devices, backups, and shared recordings also needs protection; no system guarantees absolute security.

We seek meaningful consent where required and handle information for the relevant recording, publishing, support, and security purposes. You may decline microphone or YouTube access and use features that do not need it. Withdrawing consent can prevent the affected feature from operating and does not undo completed disclosures.

You may contact us about information in our custody or control, including access, corrections, use, disclosure, or a privacy concern. Rights and exceptions depend on applicable law. You may also contact the Office of the Information and Privacy Commissioner for British Columbia; other regulators may apply to particular activities.

We will update this page as practices change and seek further consent where required. Publishing this notice does not assert that Google has audited or verified RetroFeel.