Privacy Policy for Checksum Verifier

Developer: Aktyva konsaltynh technologies
Privacy contact: mateuszbednarski696@gmail.com

About this policy

This policy describes how Checksum Verifier handles information when you calculate checksums, compare values, and manage verification records. Hash calculations and saved records are handled on your device. The app does not require an account.

Information accessed and processed

When you select files through Android's document picker, the app reads their contents to calculate SHA-256, SHA-512, or MD5 checksums. It also accesses available file information, including the filename, size, type, and last-modified time. File references are used during processing; saved records do not retain permission to reopen original files.

When you enter text, the app processes its UTF-8 representation, including spaces and line breaks, to calculate a checksum. You may also enter hexadecimal digests for comparison, expected checksums, labels, filenames, and source notes.

The app does not save copies of original file contents or entered text in its verification records. File selections, text inputs, and batch processing state are held in memory during use.

Information saved on your device

The app stores your default hashing algorithm and local records in Android app-private preferences. Records can contain timestamps, labels, filenames, algorithms, computed and expected checksums, comparison outcomes, source notes, and file metadata.

Completed valid comparisons are added to local history automatically. Expected checksum entries and individual or batch reports are saved when you choose the corresponding save action. These records support searching, filtering, reusing expected values, reviewing results, and exporting reports.

Collection and network use

The inspected implementation does not send your files, entered text, checksums, or saved records to the developer. No advertising, analytics, tracking, or remote crash-reporting SDK was identified. The app uses Android, AndroidX, Jetpack Compose, and Kotlin libraries for its interface, file operations, local storage, and processing.

Although the Android manifest includes Internet permission, no network transmission is implemented in the inspected app workflow. There is consequently no app-operated transfer for which encryption in transit can be described.

Exports, clipboard, and platform services

When you choose to copy a checksum, the app places that value on the Android clipboard. Clipboard access and retention are governed by Android and your device settings.

When you export a report as text or CSV, the app writes the report to a destination you select through Android's document picker. Reports can include timestamps, names, algorithms, computed and expected checksums, outcomes, metadata, and notes. A destination provided by a cloud storage service may upload the exported file under that service's own practices. Likewise, selecting a file from a remote document provider may cause that provider to retrieve it. These services operate separately from the app.

Android backup is enabled in the app configuration. Depending on your device, account, and system settings, Android may back up and restore app data, including local preferences and records. Such backups are handled by the platform or backup provider rather than an app-operated server.

Security

The app processes checksums locally and uses Android app-private storage for saved records. No additional app-level encryption for those records is implemented. The code can write technical error details to device logs when operations fail; no remote log transmission was identified.

No storage or processing method guarantees complete security. Protect your device and consider the contents of labels, filenames, and notes before copying or exporting records. A matching checksum confirms agreement with an expected value; it does not establish authenticity. MD5 is provided for legacy compatibility and is unsuitable for security-sensitive authenticity decisions.

Retention and deletion

Local comparison history retains up to 200 records, with older entries replaced as new comparisons are added. Saved expected checksums and reports have no automatic expiration in the inspected implementation and remain until you delete them or clear the app's data. The default algorithm preference remains until changed or app data is cleared.

You can delete individual saved checksums, history records, and reports, including report groups. Settings also provides controls to clear history, saved checksums, and reports separately. Android's app settings can clear the app's local data.

Deleting an app record does not delete the original file, an exported report, a clipboard copy, or a backup managed by another service. Manage those copies through the relevant device controls, storage destination, or provider.

For deletion questions or requests, contact mateuszbednarski696@gmail.com. The app has no developer-operated repository of your local verification records, so the developer cannot remotely delete records stored on your device. If you contact the developer by email, the message and information you voluntarily include are handled through email services to address your request. A specific retention period for support correspondence has not been established in the supplied information.

Children's privacy

No specific target age group has been established in the supplied information. The inspected app does not request age information or implement accounts, advertising, analytics, or transmission of user records to the developer. Children and their guardians should avoid putting personal information into record labels, notes, exports, or support messages unnecessarily.

Changes to this policy

This policy may be updated to reflect changes in the app or its data handling. Review the privacy policy available with the app's listing for the current version.

Contact

For privacy questions or deletion requests concerning Checksum Verifier, contact Aktyva konsaltynh technologies at mateuszbednarski696@gmail.com.