What SiteBinder stores
SiteBinder stores the information needed to run one connected field-and-office job file. That includes workspace identity, project records, job photos, support records, report and customer file content, invoice support, app activity, subscription access, AI request content, and inbound business messages.
Owner accounts, workspace profile details, seat and invite records, and sign-in context are stored so the right people can reach the right job files.
Project basics, job photos, internal notes, photos safe to share, support records, report text, invoice support, and customer file content are stored so one job can stay in one memory system.
Support requests, demo requests, pilot requests, and owner follow-up notes are stored so the business can respond clearly and keep the early customer pipeline organized.
The app sends usage events with an app-generated install ID, app version, time, and action details to SiteBinder so we can understand where setup or purchase steps fail. Apple handles App Store billing; RevenueCat helps check subscription access linked to your SiteBinder account.
When an AI feature runs online, relevant saved job details or the selected image are sent from the SiteBinder server to OpenAI to produce the requested answer or draft. Offline and unavailable AI uses a local helper instead.