$ cat PRIVACY.md

Privacy and Google Drive data use

Last updated November 14, 2026

Skirk is software you run with an exit you control. It uses your Google Drive account as a mailbox for encrypted transport objects. This page explains what the software handles and what the exit operator can see.

Google account permission

Skirk requests https://www.googleapis.com/auth/drive.file. This scope lets the app create and manage files it creates or that you explicitly share with it. Skirk uses it to create a visible app-owned mailbox folder, list mailbox objects, upload encrypted objects, download them, and delete objects after use or cleanup. It does not request full-Drive access or scan unrelated Drive files.

What is stored

Message payloads in the mailbox are encrypted before upload. File names and Drive metadata can still reveal operational details such as session, direction, client and run identifiers, sequence numbers, object sizes, and timestamps. An object can remain in Drive after a crash or interrupted cleanup until the operator runs cleanup or removes the mailbox.

The generated client profile contains a Google OAuth refresh token and a tunnel secret. Skirk saves these in local configuration or platform storage on devices where you import the profile. Treat the profile as a password. Do not post it, include it in bug reports, or share it outside the people you intend to authorize.

What the exit can see

The exit decrypts Skirk frames and opens the requested destination connection. Its operator can see destination addresses and timing; for non-TLS application protocols it may also see plaintext traffic. Destination services see the exit network address. Skirk is a transport, so application traffic privacy still depends on the application protocol, including HTTPS where appropriate.

Who receives data

Google processes the mailbox objects and OAuth grant as part of Google Drive. The exit operator controls the exit machine and its outbound connections. In Skirk's normal self-hosted path, there is no Skirk-operated relay or account server between your client and your exit. This informational website is hosted by Cloudflare, which processes ordinary website requests; it does not receive your Skirk profile or Drive mailbox contents.

Retention and removal

The client and exit remove consumed mailbox objects, and the exit periodically cleans up stale objects. You can remove your local profile, delete the Skirk-created mailbox from Drive, and revoke the app's Google Account access. The repository documents cleanup and revoke commands ↗. Revoking access stops future token refreshes but does not delete objects already in Drive.

Changes and contact

This disclosure will be updated when Skirk changes how it uses Google data. For questions, contact shahablavasani@outlook.com or open an issue in the Skirk repository ↗.