Your production media stays yours.
VeriFile has no advertising, analytics, tracking, or cloud media storage. Production media remains on the sources and destinations you choose.
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. 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 or Google. VeriFile stores the provider, provider user ID, display name, email when supplied, and authentication date in the device Keychain. It does not store the provider password.
Google Sign-In stores its session credentials in Keychain and communicates with Google for authentication. The current build has no VeriFile-hosted account backend and does not upload the local account record to the developer. Signing out removes VeriFile’s local account record and ends the Google SDK session when applicable.
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.
Source media is never included. VeriFile does not upload or send the report automatically. The user can inspect the ZIP before choosing whether to submit 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. Submitted reports are retained while the problem is investigated and can be deleted after support work is complete.
Contact
Privacy and support questions can be sent to seanmgoode@me.com.