Knowledge Base
Frequently Asked Questions
search
Verifield generates a SHA-256 hash for each photo and stores it alongside captured metadata (time, GPS coordinates, and device context). During verification, we recompute the hash and compare it with the stored record to detect changes.
verified_userProtocol: SHA-256 + Metadata
Verified captures include GPS coordinates and a timestamp. In the verification view, you can review details like Server UTC Time, coordinates, and map address. If GPS data is missing, the capture can't be verified.
Yes. You can keep capturing while offline, and Verifield will sync queued captures when you're back online. Some actions (like verification sharing and exports) may require a connection.
Verifield organizes work by workspaces, projects, and workOrders. Assign work, capture required photos, and review everything in one place with a clear audit trail.
Upload a photo to run an integrity check. Verifield computes the file hash and validates it against the original secure capture record. If it matches, you'll see verification details like time and location metadata; if not, it's flagged as a mismatch.
No, the photos which are not synced to server are not considered in report generation.
Yes, organization admins can delete photos taken by members. However, if a copy of the photo is still stored locally on a device, it may remain available for later verification. In such cases, the verification may detect the photo as tampered. The organization admin is shown a warning about this possibility before deleting the photo.
Still have questions?
Our technical specialists are ready to help you secure your digital evidence workflow.