Sensitive data approach
Archaeological records, precise resource locations, project boundaries, and field notes belong in authorized project systems. This public site explains the Ology workflow without publishing that material.
Product descriptions, a generic workflow diagram, and the Ology app artwork. The illustrations are conceptual. No project names, site records, precise archaeological locations, field returns, master databases, or trained models are included in the site files.
The trainer request form asks for contact details and a general interest category. Do not submit project names, site numbers, site records, coordinates, maps, photographs, or other restricted information through the public website.
Inside the product workflow
Recon, the iPhone app, and Intelligence exchange project files and library snapshots. The project team controls what is imported, reviewed, and shared.
Project and master data are prepared and reviewed in the desktop and phone tools. Offline field packages support work away from cell service.
Generated bid estimates, draft DPRs, document matches, and uncertain locations need qualified review before they become deliverables or part of a master.
Crew packages, field returns, reference libraries, and GIS exports are separate outputs. Review contents and access rights before transferring any package.
This page describes the current product approach. Formal privacy terms for any broader public distribution should be published separately.
Public communication
Ology examples on this site use generic language and conceptual visuals. Keep actual resource details in the authorized record system and follow applicable agency and client requirements when sharing them.