Stored in the app
Business profiles, customers, jobs, pricing, estimate snapshots, signatures, permissions, photos, templates, receipt settings, and local backup copies.
JobFrame currently stores its working database and media locally on the Android device. The user decides when to export, share, import, restore, or erase those records.
Business profiles, customers, jobs, pricing, estimate snapshots, signatures, permissions, photos, templates, receipt settings, and local backup copies.
PDFs, messages, photos, and backup ZIPs leave JobFrame when the user chooses an Android sharing or document destination.
The current release does not require a JobFrame cloud login or synchronize records to a JobFrame server.
Cloud delivery and accounting connections will require separate disclosure and authorization before they are introduced.
A JobFrame backup may include highly sensitive business and customer records:
Backup ZIPs are not currently password encrypted. Store them as private business records. Use a protected device, encrypted drive, trusted cloud account, or other location appropriate for customer information.
A backup kept only inside JobFrame may be lost if the app is uninstalled or all app data is cleared. Save an external copy before resetting the app, changing devices, or joining a test that may require destructive steps.
JobFrame validates imported backups and creates a recovery backup before replacing current records. Database replacement is transactional so a failed restore does not intentionally leave half-imported records.
The Data Management screen can remove locally stored jobs, customers, business profiles, templates, photos, signatures, uploaded logos, and in-app backup copies. External copies saved elsewhere are not deleted by that action.
Use fictional test data whenever possible. A full backup may expose signatures, addresses, prices, photos, and internal notes.