How Gyggle turns four accounts into one drive.

A technical walkthrough, no hand-waving.

STEP 1

1. Link the accounts you already own

Click Link Account and authenticate with Google OAuth. Gyggle requests drive.file scope — meaning it can only see and manage files it created. It cannot read, list, or touch anything else in your Drive.

Link as many accounts as you have. Gyggle immediately reads each one's remaining quota and draws you a map.

What we ask for: drive.file (create + manage Gyggle's own files), userinfo.email (label accounts in your dashboard).

What we never ask for: full Drive access. Ever. If a tool asks for drive scope, close the tab.

Link your first account

STEP 2

2. Gyggle encrypts and splits

Point Gyggle at a file or folder. Here's what happens on your device, in order:

Each file is encrypted with AES-256-GCM using a key derived from your passphrase via Argon2id.
The ciphertext is split into shards — default size 256 MB, configurable from 64 MB to 1 GB.
Each shard gets a SHA-256 checksum and a sequence number.
A manifest is written: a small JSON index describing every shard, its checksum, and which account holds it.
Smart Balance picks a destination account for each shard based on current headroom.
Shards upload directly from your browser to Google Drive. They never pass through Gyggle's servers.

{
  "manifest_version": 1,
  "file_id": "gyg_8f3a91",
  "original_name": "wedding_archive_2019.mp4",
  "original_size": 41875931136,
  "shard_size": 268435456,
  "shards": [
    { "seq": 0, "account": "personal@gmail.com", "file_id": "1aBc...", "sha256": "9f2c..." },
    { "seq": 1, "account": "work@gmail.com",     "file_id": "2dEf...", "sha256": "77a1..." }
  ]
}

STEP 3

3. Your library puts it back together

Open your Library, click any file, hit Download. Gyggle fetches the shards in parallel from whichever accounts hold them, verifies each checksum, decrypts, and stitches the original file back byte-for-byte.

A 40 GB video feels like a normal download. Except it came from four different accounts at once.

See it in the app

STEP 4

4. What happens when an account dies

Every manifest is stored in every linked account — it's tiny. If one account becomes inaccessible, Gyggle:

Flags every shard it held as AT_RISK in red on /app/analytics
Shows you exactly which files are affected and how much is degraded
Offers one-click Replication to copy orphaned shards to healthy accounts
Rebuilds the manifest from any surviving copy automatically

You lose a home, not a file.

Redundancy note: Pro users can enable 2× replication — every shard stored in two accounts. Cuts your effective capacity in half and your anxiety to zero.

Ready?

Get Started Free Read the security model first