Data & deletion guide
Know what stays, what leaves, and what deletion removes.
VIRAL⁴ analyzes selected creator media on the Windows device. This operational guide explains the local-data boundary in practical terms; the Privacy Policy remains the controlling privacy notice.
Files you choose.
VIRAL⁴ reads only media you deliberately select for a workflow. It may read the file name, file path, container and codec details, duration, dimensions, audio characteristics, timing information, and other measurable properties required for analysis.
The original source stays in the location you selected and is not modified by the application.
App-managed local data.
To provide previews, repeatable analysis, history, and exports, the application can create local working copies, proxies, snapshots, technical metadata, evidence, revisions, and project records inside the current Windows user's app-data environment.
Use Settings → Open data folder to open the location used by the installed application. The exact physical path can vary with Microsoft Store and Windows packaging behavior.
What is not uploaded.
VIRAL⁴ does not transmit selected creator media, project records, analysis results, or local file paths to Justice Peace or to a generative-AI service. No VIRAL⁴ account is required for local analysis.
Microsoft separately processes Store acquisition, licensing, installation, updates, and optional Windows diagnostics under Microsoft's own terms.
Delete all local history.
- Finish or cancel active analysis and export operations.
- Open application Settings.
- Use Delete all local history and confirm the action.
- Open the data folder if you want to verify remaining app-managed files.
Before and after uninstall.
Use Delete all local history before uninstalling if you want the application to remove its managed project records. Windows may retain some local application data depending on package and cleanup behavior. After uninstall, review the former app-data location and remove remaining VIRAL⁴ data manually if appropriate.
Exports, backups, and original source files must be reviewed separately because uninstalling does not remove files you saved outside the application's managed storage.
Protecting local files.
VIRAL⁴ does not add file-level encryption to local project files. At-rest protection depends on Windows account permissions and any enabled Windows Device Encryption or BitLocker configuration. Use a protected Windows account, lock the PC when unattended, and keep Windows updated.
Publisher-held information.
Because local analysis data is not transmitted to Justice Peace, the publisher cannot retrieve or delete those local files for you. For information submitted through the website contact form or support email, follow the request process in the Privacy Policy.