VN Revival / App Privacy & Security
App Privacy & Security
What our localization apps access, what they send, and how to verify a download.
Updated: 8 October 2026
Who makes the apps
VN Revival is an independent fan project maintained by Anton / Master1C8. This is the author of the localization tools, not the developer of the original games. Public source repositories are linked on each game page. Contact: [email protected].
Standard localization installers
Installers access the game folder you choose and write localization files there. Keep a backup of saves and original files, and follow that release’s instructions to restore or remove the mod. A completed standard localization can be used without a translation service during gameplay. Downloading the app and any separately required resources still requires a network connection.
Real-time translators and external services
When an online translator is enabled, game text is sent to the selected service. Depending on the app, requests may also include nearby source text, glossary terms, translation instructions and the target language. Google Translate and OpenAI-compatible endpoints are used by CoC2 and TiTS packages. A local provider translates locally, but downloading models or glossary updates can still contact external servers. Provider policies and retention rules apply; local translation and online translation have different privacy properties.
Keys, cache and local data
Apps may retain settings, selected game paths, translation caches and diagnostic logs on your device. Caches and logs can contain game text. Supported credential helpers store provider API keys in macOS Keychain or Windows Credential Manager; do not put keys into a custom prompt or send them in a bug report. Use the app’s key-removal and cache-clearing controls where available. Uninstalling an app may leave settings, cached translations, models or saved credentials behind.
Permissions and connections
Runtime translators can read the running game through a local helper or debugging connection and insert their translation interface. Loopback helpers are intended for this device; do not expose them to a network. Remote custom API endpoints in the CoC2 and TiTS packages require HTTPS, with HTTP allowed for local loopback providers. Other releases may have different capabilities: read the included instructions. Do not disable system security protections to resolve an installation warning.
Website, downloads and third parties
The website remembers your language preference and uses Cloudflare for delivery and aggregate analytics. Download counts are stored as daily totals by game, platform and language. The site’s privacy policy covers website processing. Opening GitHub, Steam, GOG, Discord, Telegram, YouTube or a translation provider contacts that third party. A translation provider receives requests from the app; VN Revival is not that provider.
Verifying releases
Each available platform file has its own SHA-256. Release evidence is captured from the archive served by the site and bound to its exact upload record. A source commit is linked only when build provenance records it; the current repository HEAD is not substituted for a legacy build. Missing build provenance remains unknown until supported by evidence. Version numbers, hashes and source commits do not imply Apple notarization, Windows Authenticode signing, an independent security review or reproducible builds.
Reporting a security issue
Report suspected security problems privately to [email protected]. Include the game, platform, release version, archive SHA-256 and reproduction steps. Remove keys, account details, personal paths, saves and private text from logs before sharing them. For an ordinary translation problem, use the feedback links on the game page.
Release verification
macOS: shasum -a 256 downloaded.zip
Windows PowerShell: Get-FileHash .\downloaded.zip -Algorithm SHA256
[email protected] · Master1C8 / GitHub · Google Privacy Policy
Download statistics distinguish browser signals, same-day repeats, known bot/tool signals, marked technical checks and unknown requests. A signed download receipt cookie expires at midnight UTC and is limited to that download path. It contains no visitor ID; IP addresses and raw browser headers are not saved in download analytics. These signals do not prove a unique person or a completed download.