Stored in the app
Business profiles, structured customer records, tags, notes, follow-ups, activity, consent choices, jobs, pricing, estimates, photos, signatures, receipts, templates, outreach drafts, and local backups.
Local-first records
Data stays useful because it stays portable
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.
Leaves only by user action
PDFs, message drafts, photos, exports, and backup ZIPs leave JobFrame only when the user chooses an Android sharing or document destination.
No JobFrame account required
The current release does not require a JobFrame cloud login or synchronize working records to a JobFrame server.
Future services stay separate
Remote estimate approval, hosted delivery, and accounting connections will require separate disclosure and authorization before introduction.
What a backup can contain
A JobFrame backup may include highly sensitive business and customer records:
- Business profiles and customer display names, structured names, contact details, tags, notes, follow-up dates, activity, and consent records
- Jobs, pricing lines, estimate and receipt revisions, templates, outreach drafts, and reusable outreach templates
- Internal and customer-facing descriptions, payment details, and generated document settings
- Photos, signatures, and uploaded logos when media is enabled
- Generated receipt PDFs when that option is enabled
- Versioned JSON and CSV files, including portable customer data intended for backup and future integrations
Backup responsibilities
Backup ZIPs are not currently password encrypted. Store them as private business records. Use a protected device, encrypted drive, trusted cloud account, or another 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.
Restore protection
JobFrame validates imported backups and creates an Automatic Recovery Backup before replacing current records. Database replacement is transactional so a failed restore does not intentionally leave half-imported records. Older compatible backups restore missing newer fields with safe defaults rather than guessing customer data.
Exports and message drafts
CSV and JSON exports are created for portability. Outreach and receipt delivery content remains a draft until the user chooses a compatible Android app and reviews the destination. JobFrame does not automatically transmit customer outreach from its local database.
Clear all data
The Data Management screen can remove locally stored jobs, customers, business profiles, templates, drafts, photos, signatures, uploaded logos, and in-app backup copies. External copies saved elsewhere are not deleted by that action.
Before sharing a backup for support
Use fictional test data whenever possible. A full backup may expose names, signatures, addresses, prices, photos, consent choices, outreach content, and internal notes.