Privacy Policy
Last updated: June 30, 2026
This Privacy Policy explains how VLiva handles information for two separate areas:
- the public website at https://vliva.tamkungz.me
- the VLiva desktop software
VLiva is designed as a local-first Linux VTubing application. The goal is to avoid collecting personal information unless a feature truly needs it.
Quick Summary
- The website does not require an account.
- The software does not require an account for core local features.
- The software is designed to keep models, camera input, tracking data, settings, and logs on your device unless you choose to share or transmit them.
- Camera tracking is used for real-time avatar control and is not uploaded by default.
- VLiva does not sell user data.
- VLiva does not include advertising networks or cross-app tracking SDKs.
Website Privacy
When you visit https://vliva.tamkungz.me, routine technical information may be processed by hosting and security infrastructure.
This may include:
- IP address or approximate network information.
- Browser and device information.
- Request time, page path, and referrer.
- Basic security and performance logs.
This information is used for website delivery, security, abuse prevention, debugging, reliability, and performance improvement.
The website may link to third-party services such as GitHub, Reddit, X/Twitter, Live2D, BOOTH, or documentation resources. Those services have their own privacy practices.
Software Privacy
VLiva does not require account registration for core local software features.
The application is designed so model loading, Live2D rendering, tracking, avatar control, animation logic, plugin execution, and streaming workflows run locally on your system whenever possible.
Camera Access and Face Tracking
Some features need camera access to perform face tracking.
- Camera permission is handled by your operating system.
- If permission is denied, camera-based tracking features will not work.
- You can revoke permission through your system settings.
- Camera input and face-tracking data are used for real-time functionality.
- Camera input and face-tracking data are not uploaded by default.
- Tracking preview images are used locally inside the app UI.
- Tracking parameters may be exposed locally to plugin, UDP, or OBS workflows when you enable or use those features.
Models, Assets, and Local Files
You manage your own Live2D models, textures, expressions, motions, settings, plugins, backgrounds, images, recordings, and project files.
VLiva does not provide a default cloud upload pipeline for user models, recordings, private media, or project files as part of normal local use.
Your models and assets remain on your device unless you choose to move, upload, stream, share, or transmit them through another tool or service.
The software may create or update local configuration files such as model settings, app settings, cache files, logs, or plugin-related files. These files are stored on your device.
OBS, UDP, Plugins, and Streaming Output
If you use VLiva with OBS or other streaming tools, visual output may be captured, recorded, or broadcast depending on your streaming setup.
You are responsible for checking your scene setup before streaming or recording.
VLiva may support local UDP output, shared-memory capture for OBS, and plugins or extensions. These features can transmit or expose live tracking values, frame data, model metadata, or other runtime information to local tools or endpoints that you configure.
Only enable integrations that you understand and only install plugins from sources you trust.
Optional Network Features
Some optional features may use network connections.
Examples may include:
- Update checks.
- Documentation links.
- Optional integrations.
- User-configured endpoints.
- Steamworks features in Steam builds.
- Future plugin or extension features.
When optional network functionality is used, only the data needed for that feature should be transmitted.
Logs and Diagnostics
Diagnostic logs may be created locally for troubleshooting.
Logs may include technical details such as error messages, device information, graphics/backend status, plugin status, or app behavior.
Logs stay on your device unless you choose to share them with the developer or another support channel.
Steam and Store Platforms
If VLiva is distributed through Steam or another store, that platform may process purchase, account, device, achievement, refund, crash, or usage information according to its own policies.
VLiva does not control those platform-level systems.
Support Contact
If you contact the developer by email or another support channel, the information you send may be used to respond to your inquiry, investigate bugs, improve documentation, or resolve technical issues.
Do not send private models, personal documents, access tokens, passwords, or sensitive files unless they are necessary and you understand the risk.
Data Retention and Removal
Because VLiva is primarily local-first, most app data retention is controlled by you.
You can remove local data by deleting app files, project folders, configuration files, cache files, logs, or by uninstalling the application, depending on your platform and installation method.
Website logs, email records, or hosting/security logs may be retained for a limited time depending on the provider and operational needs.
If VLiva does not possess your local app data, the developer cannot delete that local data for you.
Third-Party Services and Components
VLiva may use third-party software components, SDKs, libraries, hosting providers, or development tools.
Third-party services and components may have their own privacy practices, licenses, and terms.
Examples include Live2D Cubism SDK, Qt, OpenCV, MediaPipe, GLEW, stb_image, OBS/libobs integration, Steamworks SDK, website hosting, and linked third-party websites.
Live2D Notice
VLiva uses Live2D Cubism SDK.
Live2D Cubism SDK is developed by Live2D Inc. and copyrights are held by Live2D Inc.
For usage conditions related to Live2D Cubism SDK, please also read the VLiva Terms of Use and the applicable Live2D license information.
Children’s Privacy
VLiva is not designed to knowingly collect personal information from children.
If you believe a child has provided personal information through a project contact channel, please contact the developer so the issue can be reviewed.
Security
Reasonable care is taken to keep the website and project infrastructure secure.
However, no system is perfectly secure. You are responsible for keeping your own device, streaming setup, plugins, models, and accounts safe.
Incident Response
If a confirmed incident causes unintended exposure of user information, a notice will be provided through appropriate project channels when reasonably possible.
Policy Updates
This Privacy Policy may be updated from time to time. The “Last updated” date indicates the latest revision.
Contact
For privacy, legal, licensing, or project inquiries:
Impressum / Business Information
Project: VLiva
Website: https://vliva.tamkungz.me
Maintained by: Independent developer / TamKungZ_
Business form: Sole operator / independent developer
Contact: vliva@tamkungz.me
Tax/VAT number: Not publicly listed