flikt.

End-to-end encrypted · v1 sealed envelopes

flikt.

Capture, share, sealed.

End-to-end encrypted screenshots that live in your own Drive.

Download — macOS · Windows View source

.pkg · .msi · MIT licensed

What stays private

The server holds ciphertext. The fragment holds the key.

Every screenshot is encrypted on your device with a fresh AES-256-GCM key the moment you drag a region. The ciphertext travels to your own Google Drive. The key never reaches the server — it lives in the URL fragment, the part browsers refuse to send upstream.

Flikt requests only the drive.file scope, so it can read files it creates and nothing else in your Drive. The refresh token stays server-side, AES-GCM wrapped at rest with a key the operator never sees in plaintext.

The threat model below is the abbreviated version. The full essay walks through five attacker classes — and what each one can and can't reconstruct.

Attacker has Refresh tokens Image contents
.users.json backup leak onlyNoNo
Both .users.json and .envYesNo — ciphertext only
Full URL incl. #k=...Yes

Read the full threat model →


How it works

Three steps. No CLI.

01 · Install

Download & double-click

Pick the installer for your OS. No CLI, no terminal, no config files. On macOS you'll grant screen-recording once on first run.

02 · Sign in

Connect Google Drive

Grant the drive.file scope. Flikt can only ever see files it created. Your refresh token is wrapped at rest; the encryption key never leaves your device.

03 · Capture

Press the hotkey, drag a region

⌘+Shift+X on macOS, Ctrl+Shift+X on Windows. The image is sealed with a fresh AES-256-GCM key, uploaded as ciphertext, and the key lives in the URL fragment on your clipboard.


Open source

Built in the open.

MIT licensed. Roadmap public. Issues welcome.

Flikt is MIT-licensed and developed in public. The desktop client, server, and this site all live in a single repository — there's no hidden build, no SaaS dashboard, no telemetry. Every release is signed and reproducible from the tag.

The current roadmap — distribution, end-user setup, signed auto-updates — is tracked openly in Linear. Issues and pull requests are welcome at github.com/FisiFla/flikt.