Viofuse moves video files from your Photos, iCloud, Google Drive, or Google Photos straight to your own YouTube channel. This page explains exactly what the app touches along the way, and what it doesn't.
Viofuse is a native mobile app that helps you back up and publish video files to YouTube from wherever they already live on your device or in your cloud accounts. It is built and operated by an independent developer, not a company with a separate data-processing arm — the same person who writes the code operates the backend described below.
The short version: your video files travel directly from their source to YouTube's servers. Viofuse's own backend never stores or streams the video content itself — only the small amount of metadata (titles, timestamps, upload status) needed to show you a history of what you've uploaded.
| Category | What it includes | Why |
|---|---|---|
| Account identity | Email address, YouTube channel name — read once via Google's own APIs after you sign in | Show you which account is connected; personalize the app |
| Authentication tokens | Google OAuth access & refresh tokens, Supabase session tokens | Keep you signed in without re-entering credentials on every launch |
| Video file content | The video bytes themselves, read from the source you select | Streamed directly to YouTube as the upload — this is the app's core function |
| Upload metadata | Filename, file size, duration, chosen title/description/privacy, resulting YouTube video ID, processing status | Show your upload queue and history; resume interrupted uploads |
| Source connection state | Which sources (Photos, iCloud, Drive, Google Photos) you've connected, and your auto-sync preferences per source | Remember your settings across sessions and devices |
Viofuse does not include advertising or analytics SDKs, does not track you across other apps or websites, and does not sell or rent any data to anyone, under any circumstances.
When you sign in with Google, you're asked to grant specific, individually-listed permissions (Google calls these "scopes"). Viofuse only requests what each feature actually needs:
youtube.upload: Upload videos to your own YouTube channel. This is the app's core function — without it, Viofuse cannot operate.youtube: Read your channel name, set the privacy status on videos you upload, and create or add videos to playlists when you use auto-organization presets.photoslibrary.readonly: Optional, off by default. Powers an in-app album browser for selecting videos directly from your Google Photos library, as an alternative to Google's own picker.photospicker.mediaitems.readonly: Lets you select videos through Google's own secure picker interface. Viofuse only ever receives the specific items you choose in that picker — never open-ended library access.userinfo.email: Shows which Google account is currently signed in, inside the app's own Settings screen.Viofuse deliberately does not request Google Drive scope access. Drive files can be selected only through system-level file pickers that never hand Viofuse a standing grant to your Drive.
Authentication tokens and your account email are stored in iOS Keychain, the operating system's encrypted credential store — the same mechanism iOS itself uses for passwords. This data never leaves your device except as part of the API calls described below.
Video files are streamed in chunks directly from your device to YouTube's resumable upload endpoint over an encrypted connection. Viofuse's own servers are never in that path — the app is a client of YouTube's API, not an intermediary that receives your video first.
If you sign in with a full account (rather than using the app as a guest), upload metadata and source-connection preferences are synced to a Supabase-hosted database so your history is available if you reinstall the app or move to another device. Every row is scoped to your account with row-level security — no other user's account can query your data, including by Viofuse's own infrastructure short of direct database administration.
Viofuse shares data with exactly two categories of third party, both acting on your direct instruction, not Viofuse's:
In plain terms: Nobody sees your videos except YouTube, because YouTube is where you're publishing them. Viofuse doesn't have a copy to share even if it wanted to.
Local tokens and cached data are removed from your device immediately when you sign out. Backend-synced data (upload history, source preferences) is retained for as long as your account exists, so your history survives a reinstall.
To request permanent deletion of your backend account data, contact us using the details below — requests are processed within 30 days.
Viofuse is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us data, contact us and we'll remove it.
If this policy changes in a way that materially affects how your data is handled, the last reviewed state at the top of this page will update, and significant changes will be noted in the app's release notes.
Questions about this policy, or requests to access or delete your data, can be sent directly to: privacy@viofuse.com