The whole flow, from connect to recover.

You sign into Trigunatita with the Google account that owns your primary channel. Google's consent screen asks for a narrow set of permissions — exactly what a backup product needs and nothing more. You'll see the request list before you approve it; nothing is hidden.

You repeat the flow with a second Google account — typically one you already have for another purpose, or a fresh account you create specifically for the backup. The two accounts never share a password with Trigunatita, because Trigunatita never asks for your password. You can revoke either connection at any time from your Google account settings, and the revocation is instant.

Treat the backup Google account like a safe-deposit box: strong password, distinct recovery phone number, real 2FA method, and not shared with collaborators. Backup is only useful if the backup account itself doesn't get compromised.

You open Trigunatita and see an upload screen that mirrors YouTube Studio's layout on purpose — Details, Video elements, Checks, Visibility. There is nothing new to learn. You fill in the title, description, tags, thumbnail, category, playlists, and visibility schedule you would have filled in on Studio anyway.

Your browser uploads the video file directly to private, encrypted storage. The upload is resumable, so a dropped connection on a 4 GB file picks up where it left off rather than restarting. You can close the tab once the upload finishes — the rest happens in the background.

Metadata (title, tags, thumbnail, playlist choices) is captured once and applied to both destinations. There is no step where you fill in the backup channel's fields separately, because that's exactly the kind of friction that causes creators to skip the backup.

The video publishes to your primary channel with exactly the visibility you set — public, unlisted, or scheduled for later. At the same time, a private copy goes to the backup channel on your second Google account. Title, description, tags, thumbnail, playlists, and category are identical on both. From YouTube's side, these are two legitimate uploads by the account owner, which is exactly what they are.

Backup uploads are always private, by design. This protects you from YouTube's duplicate-content and spam systems (which operate on publicly visible content, not private archives) and keeps your backup channel low-profile. You can still watch, download, or re-share your private backups from inside YouTube Studio whenever you want — they're yours.

If something transient goes wrong — YouTube returns a temporary error, your network has a blip, the API throttles — Trigunatita retries automatically. You see the mirror status in your library as it happens: queued, in progress, succeeded. If a retry ultimately fails, you get a one-click manual retry button with the exact reason logged so you know what to fix.

Every mirrored upload leaves a copy of your original video file in our long-term archive, encrypted and held outside YouTube's infrastructure. This is the layer that matters on the worst day — the day both your primary and your backup channel are lost. The mirror channel alone is strong; the mirror channel plus the off-YouTube archive is genuinely disaster-proof.

Archive retention is tier-dependent. Creator tier keeps files for 90 days; Pro for a year; Studio indefinitely. Restores from archive are fast enough for real disaster-recovery use — worst case, 12 hours, usually minutes. You can rehearse a restore any time without penalty, and we recommend you do, once a quarter, so the day you actually need one isn't the day you first try.

If you cancel, your archive stays readable for 30 days so you can export. After that, everything is deleted and you receive an email confirming the erasure. We do not hold archives of ex-customers as leverage for reactivation.

If your primary channel is terminated, the backup channel on your second Google account still has every video, private, with all metadata intact. Open Trigunatita, filter to the affected channel, and republish any video to a destination you authenticate. Titles, descriptions, tags, and thumbnails re-attach automatically. A creator with a mirror is publishing a bridge video to their audience within hours — not rebuilding from zero over months.

If both YouTube channels are terminated — the rare double-termination scenario that happens to less than 1% of affected creators but does happen — the off-YouTube archive has every original source file. Authenticate a fresh Google account, connect its new YouTube channel, and trigger a bulk restore. You're seeding a new channel from master files you already own.

Restore SLAs are real, not marketing. If your tier includes a restore SLA and we miss it on a real incident, the next invoice is credited 100%. It's in the terms of service, not buried in a support doc. We also run a quarterly internal restore drill with synthetic data so the path stays warm.