iVaultWho this covers
This policy covers the iVault desktop app, published by iVaultkh (ichamrong) under the MIT License, on every platform and in every store where it is offered. It also covers this website: static pages hosted on GitHub Pages, with no cookies, forms, analytics or third-party requests. Even its fonts are served from this site.
What we collect
Nothing. We do not run a service that receives data from the app. iVault contains no telemetry, crash reporting, advertising or tracking code, and it does not create a user account with us.
What stays on your computer
- Your library and jobs: file paths, series and episode details, upload progress and the links iVault produced, in a local database in the app's data folder.
- Encoded video: temporary HLS files while a job runs.
- Catalog exports: when you export a series to wuxia-web, iVault writes JSON files into the folder you chose on your computer. Nothing is uploaded; you commit and publish them yourself.
- App lock password: only if you turn the optional lock on (Settings → General → Privacy). iVault keeps a salted hash of it in the app's local storage, never the password itself, and deletes it when you turn the lock off.
- Credentials: storage access keys, bot tokens, OAuth refresh tokens and API keys, stored in your operating system's secure credential store (Windows Credential Manager, macOS Keychain or the Linux Secret Service).
Where your data goes
iVault only makes the network requests needed for features you turn on. Data travels from your computer straight to the service, under that service's privacy policy and an account that belongs to you.
Your computer
- Library and job history
- Encoded video, while a job runs
- Credentials, in the OS keychain
Services you connect
- Your storage provider
- Google or Microsoft sign-in
- TMDB and Gemini, with your own keys
Every service, when it is contacted and what it receives:
| Service | When | What is sent |
|---|---|---|
| Your storage providerCloudflare R2, Amazon S3, MinIO, WebDAV, GitHub (and jsDelivr for public GitHub links), Google Drive, OneDrive or Telegram | When you connect it and when you upload | Your encoded video segments, playlists and file lists, with the credentials you entered for that provider. |
| Google or Microsoft sign-in | When you connect Google Drive or OneDrive | A standard OAuth sign-in in your browser. The reply comes back to the app on your own computer (127.0.0.1); iVault keeps only the resulting token, in the keychain. |
| The Movie Database (TMDB) | When you search for a series, with your own TMDB key | Your search text. Posters and details come back. |
| Google Gemini | When you ask for a Khmer title and description, with your own Gemini key | The English title, description and year of that series. The generated text is a suggestion you review before saving. |
| FFmpeg download sitesevermeet.cx on macOS, johnvansickle.com on Linux | Only if you ask iVault to download FFmpeg. On Windows you download it yourself | An ordinary file download request. |
Your content
You are responsible for the videos you upload and for having the right to store and share them. Links iVault creates are as public as the storage you point them at: a public bucket or public repository makes the video reachable by anyone with the link.
Your choices
- Remove a service: on iVault's Storage screen, choose Disconnect… from the provider's menu, and its credentials are deleted from your keychain with it.
- Remove everything: uninstall the app and delete its data folder.
- Requests to us: because we hold no data about you, there is nothing for us to export, correct or delete. For data held by a service you connected, use that service's own tools.
Security
Credentials are kept in the OS credential store and are removed from error messages and logs before they are shown. Connections to services use HTTPS where the service offers it.
Children
iVault is a tool for publishing video and is not directed at children under 13. It collects no personal information from anyone.
Changes to this policy
If the app starts handling data differently, this page is updated before that version ships, and the change is listed here.
- Added: the optional app lock in iVault 1.2.1 keeps a salted hash of your password on your computer.
- Corrected: exporting a series to wuxia-web writes files on your computer and sends nothing, so “Your website” is no longer listed as a service. Gemini also receives the year.
- First published, for iVault 1.0.
Contact
Privacy questions
Open an issue and add “privacy” to its title. Leave out access keys, tokens and passwords.