Privacy Policy

Risuko is local-first: by default it works entirely on your machine and sends us nothing. The app contains no analytics, tracking, or crash reporting.

Three optional features — an account, cloud sync, and file sharing — use our backend at api.risuko.app. Downloading itself connects to the sources you choose. Everything below explains what data each of these involves.

Creating an account is optional. You can sign in with your email (we send a one-time code) or with GitHub (which shares your GitHub ID, username, and email address via the read:user user:email scope).

We store your email address, or your GitHub ID and username, plus short-lived login codes and session tokens (sessions last about 30 days). We never receive or store a password. Your IP address is read transiently from request headers for rate-limiting and is not saved to a database.

The files you download, your task history, and your settings are stored locally. Saved credentials (site logins, cloud-upload keys) are kept in your operating system's secure keychain — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux.

The Clipboard Watcher, when enabled, reads your clipboard only on your device to spot download links; contents are never sent anywhere and it can be turned off in Settings. If no system keychain is available, secrets fall back to a local config file — see Cloud Sync for why that matters.

When you download, Risuko connects directly to the URLs, trackers, and peers you provide — over HTTP(S), FTP/SFTP, BitTorrent, ED2K, HLS, and others. Those third-party hosts see your IP address and requests; we are not involved.

BitTorrent and other peer-to-peer protocols are public by design: your IP address and the content identifiers (info hashes) are shared with trackers, the DHT, local-network peers, and other downloaders, and Risuko uploads (seeds) to them. Media downloads may launch an external yt-dlp you have installed.

Cloud sync is off unless you sign in and enable it, and it is selectable per category. The categories you choose are uploaded to our backend (api.risuko.app, on Cloudflare D1) and associated with your account. We store only those settings and their timestamps.

Be aware that some categories can contain sensitive values — proxy settings and cookie headers, FTP/SFTP passwords, SSH private keys, and RPC secrets. When such a secret is held in your OS keychain it stays out of sync; if it is stored inline (for example, on a system without a keychain) and you enable that category, it is transmitted to and stored on our server as part of the settings blob. Enable only the categories you're comfortable syncing. You can disable sync or delete your synced data at any time.

Risuko's file sharing is peer-to-peer (built on iroh): the file moves directly between devices and is never uploaded to us. To connect two devices, our server briefly stores a rendezvous record — a pairing code, a connection ticket, and basic file metadata (names and sizes). These records expire after about an hour and are single-use.

The connection ticket includes the sender's network address, so whoever holds the code (and our rendezvous record) can see it. When a direct connection can't be made, the encrypted transfer falls back through public relay servers operated by n0 (the iroh project); relays carry only encrypted bytes and cannot read your files.

To download from sites that require a login or bot check, you can import cookies that Risuko reads directly from your installed browser's local cookie database (Chrome, Firefox, Edge, Brave, Safari, and others). Decrypting them may prompt your OS keychain or ask for elevation. Imported cookies are stored locally and used only for your downloads — they are not sent to our servers (though the generic cookie field is one of the syncable categories described above).

If enabled, Risuko checks for updates from risuko.vercel.app, sending your app version, operating system, and architecture. The optional BitTorrent tracker list refreshes from public CDNs (GitHub / jsDelivr). Our marketing website uses privacy-friendly, aggregate analytics; the app does not. None of this is linked to any account.

The app contains no analytics, usage tracking, or crash reporting. Even with an account, we never collect the contents or names of the files you download, the text on your clipboard, the contents of files you share (transfers are peer-to-peer), the sites you browse, or any advertising profile. Risuko shows no ads.

Our account, sync, and sharing backend runs on Cloudflare (Workers, the D1 database, and email delivery for login codes). GitHub provides optional OAuth sign-in and hosts release downloads. Update checks use Vercel (which also serves the website and its analytics), peer-to-peer relays use n0, and the tracker list comes from public CDNs. Downloads, cloud-upload destinations you configure, and media sites all involve the third parties you point Risuko at. Each operates under its own privacy practices.

One-time login codes and file-sharing rendezvous records are short-lived and purged automatically. Login sessions expire on their own. Your account record and any synced settings are kept until you delete them or close your account.

Cloud sync, file sharing, browser-cookie import, update checks, tracker sync, and DNS-over-HTTPS are all optional and can be turned off in Settings. Storing credentials in your OS keychain keeps them off cloud sync entirely. You can clear Risuko's local data by removing its configuration directory or uninstalling, and remove your synced data or account by signing out or contacting us to delete your server-side records.

We may update this policy as Risuko evolves; changes are reflected by the “last updated” date above. Questions or data-removal requests can be raised on the project's GitHub repository.