Privacy policy

Your production media stays yours.

VeriFile has no advertising, analytics, tracking, or developer-hosted media library. Production media remains on the sources and destinations you choose, including any cloud destination you configure.

Effective September 24, 2026VeriFile 0.9.0Mac · iPhone · iPad

Mac app data

The Mac app stores projects, transfer history, recovery records, clip notes, reusable setups, and preferences in the current user’s Application Support folder. It reads media only from sources the operator selects or inserts and writes it only to selected destinations.

Production media

VeriFile does not upload production media to the developer or a VeriFile cloud service. If you configure a third-party cloud destination, VeriFile sends the selected copy to that service. It does not erase source media. Generated reports may contain filenames, paths, media metadata, project details, and information entered by the operator; those reports are written to locations the operator chooses.

iPhone and iPad monitor

The optional companion communicates directly with the Mac on the local network. It receives project, source, destination, progress, speed, verification, recovery, version, and status information. Status text can contain local filenames or paths.

The four-digit code is exchanged for a random session token stored in the device Keychain. The companion keeps up to 20 recent completion or failure events locally and can show notifications and a Live Activity.

The current local connection uses HTTP without an internet relay or transport encryption. Use it only on a trusted private network. Stopping Mac sharing invalidates the session token.

Optional account login

Users may sign in with Apple. VeriFile stores the Apple account identifier, display name, email when supplied, and authentication date in local app preferences. It does not store the account password, Apple access token, or refresh token.

The direct-download Mac app uses the VeriFile HTTPS service to complete Apple’s web sign-in exchange. Project records and production media are not sent during sign-in. Signing out removes VeriFile’s local account record.

You can delete your VeriFile account in the app. This removes the hosted account profile and its active sessions. It does not delete local projects, copied media, App Store purchase records held by Apple, or support reports submitted separately. Contact us if you need help deleting a support report.

App Store purchases

VeriFile Pro purchases and restorations are processed by Apple through StoreKit. VeriFile receives the entitlement state needed to unlock features; payment details remain with Apple.

Bug reports

The Mac app creates a bug-report ZIP only when requested by the user. It may contain a problem description, selected attachments, recent events, drive characteristics, app and system versions, and recent VeriFile crash reports. Project, computer, volume, and path names are redacted by default.

VeriFile does not automatically include source media. If you choose to attach an image or video to a support report, that file is included in the ZIP. The ZIP is saved locally first and is uploaded to the private VeriFile support queue only when you choose Submit Report. You can inspect the ZIP before submitting it.

When a user submits a report, the ZIP and the supplied report details are stored in the private VeriFile support service and are available only through the owner dashboard. The service stores a one-way hash of the network address for abuse prevention and limits submissions to five per 24 hours. The service deletes report ZIPs and ticket details after 90 days when a new report is submitted or the owner opens the support dashboard. If the service is inactive, deletion may occur later. Email copies sent to support are handled separately and can be requested for deletion at the contact address below.

Contact

Privacy and support questions can be sent to info@verifileapp.com.