Last updated: October 18, 2026

Vulkan Checker is provided by Alex Zaharia. The app offers two checks: Vulkan API requirements and the requirements of a documented VulkanMod Android snapshot. This policy explains the information processed during those checks. Contact: [email protected].


1. Information processed

Device and graphics information

When you select a check, the app reads Android Vulkan declarations and queries the system Vulkan implementation. The response can include manufacturer and model, Android version and API level, loader and graphics API versions, GPU name and type, vendor/device type codes, raw driver version and driver information, extensions, feature bits, queues, limits and memory heap/type capacities. Graphics type codes are not unique identifiers for your phone.

Measurement context

The app records the time, probe version, query stage, status and diagnostic message in the active result. It does not read unique device identifiers, serial numbers, IMEI, accounts, IP addresses or installed-app inventories. It does not inspect games, accounts, gameplay or launcher files.


2. Purpose of processing

The queried information is used to display reported graphics capabilities and compare them with the chosen requirements. The VulkanMod check uses a cited, fixed source snapshot. Unknown surface and runtime conditions remain unverified. No rendering benchmark or game performance measurement is performed. The app does not install drivers, change graphics settings or increase FPS.


3. Storage and retention

Current checks

Current results are held in application memory while the check screen is open. They are not added to a saved history. Returning from the result releases that screen's measurement; a new selection performs a new check. Operating-system process cleanup may also discard the in-memory result.

Temporary probe responses

The internal probe uses a temporary file in private app cache to transfer its response between app processes. The file is removed after reading. A file left by an interrupted run is removed on a later application start; Android may also clear cache. The response is not uploaded.

Earlier app data

This simplified edition does not read or write the saved report/profile storage used by the earlier implementation. If such data exists from an earlier installation, it can remain in private app storage until you clear the app's storage in Android settings or uninstall it. No previous saved data is silently imported or shared. Android backup is disabled in the app configuration.