# Flowmoor Privacy Policy

Effective date: 2026-04-27

Flowmoor is a desktop application for downloading and organizing media from services such as YouTube and Twitch, and for synchronizing RecordTimeLabel records when the user signs in.

This document describes the data Flowmoor handles in the published desktop app. It is not a promise that any third-party platform permits every download use case; users are responsible for following the terms and laws that apply to the media they access.

## Data Stored Locally

Flowmoor may store the following data on the user's device:

- App settings, download preferences, output folders, UI layout, hotkeys, and feature toggles.
- Download history, task status, video titles, URLs, filenames, timestamps, subtitles, chat render settings, and local processing metadata.
- User-provided Twitch OAuth tokens, YouTube cookie file paths or cookie content, OpenAI settings, and other optional credentials entered by the user.
- Local logs and diagnostic state needed to troubleshoot downloads and app errors.

These local files remain on the user's device unless the user explicitly enables a feature that sends data to a third-party service.

## Google Sign-In And Firebase

Google Sign-In is used for RecordTimeLabel account identity and synchronization. Flowmoor requests Google OpenID Connect profile data through the `openid`, `email`, and `profile` scopes.

When the user signs in, Flowmoor may use Firebase services to store or process:

- Google account identity fields needed for login, such as user ID, email, display name, and profile image URL.
- RecordTimeLabel records selected for synchronization, such as video URLs, titles, timestamps, notes, tags, and related workflow metadata.
- Remote configuration, version gating, and update-related status.

Flowmoor does not use Google Sign-In to read Gmail, Google Drive, Google Calendar, contacts, or other Google product data.

Flowmoor's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

## Third-Party Services

Depending on the feature used, Flowmoor may connect to:

- YouTube, Twitch, their CDNs, or related public APIs to resolve media information and download media selected by the user.
- GitHub Releases to check for application updates.
- Firebase for authentication, RecordTimeLabel synchronization, and remote configuration.
- Hugging Face or model providers when the user installs ASR models.
- OpenAI or compatible endpoints only when the user enables those features and provides the relevant authorization or API settings.
- yt-dlp, FFmpeg, Deno, TwitchDownloaderCLI, and other bundled tools used locally by the app.

User-provided YouTube cookies and Twitch tokens are used for the relevant platform requests and are not intentionally sent to Flowmoor's Firebase project.

## Logs And Diagnostics

Flowmoor avoids logging OAuth authorization URLs, redirect URLs, access tokens, and ID tokens. Local logs may still include non-secret diagnostic details such as errors, task IDs, filenames, URLs provided by the user, platform names, and version information.

Users should review logs before sharing them publicly.

## Data Sharing

Flowmoor does not sell personal data. Flowmoor shares data only when needed to operate a user-requested feature, such as sending authenticated sync data to Firebase, contacting the selected media platform, checking GitHub Releases for updates, or calling a configured AI/API provider.

## User Control

Users can:

- Use Flowmoor without Google Sign-In for local-only workflows.
- Sign out of Google/Firebase synchronization.
- Remove local settings, credentials, logs, and download history from the app data folder.
- Delete or edit RecordTimeLabel records from the app or connected clients.
- Avoid entering optional API keys, cookies, or OAuth tokens.

Uninstalling the app may not remove files the user downloaded to custom output folders.

## Security

Flowmoor stores optional credentials locally and uses them only for the feature the user enabled. No desktop app can make locally stored credentials impossible to extract from a compromised device, so users should protect their operating system account and avoid sharing app data folders.

## Contact

Flowmoor is developed by Flowmoor Studio, an independent software studio in Taiwan founded by Jason Chiu.

For privacy or security concerns, email sunnoon00@flowmoor.com or use the project's GitHub security contact:

https://github.com/EsabiyaXCF/flowmoor/security