Local-first records

Data stays useful because it stays portable

JobFrame stores its working database and media locally on the Android device. The user decides when to export, share, import, restore, or erase those records.

Stored in the app

Business profiles, customers, appointments, reminders, jobs, pricing, estimates, Audio Notes, photos, signatures, receipts, templates, outreach drafts, and local backups.

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 require separate disclosure and authorization before introduction.

What a backup can contain

Customer and business records, contact information, notes, tags, follow-up, consent choices, appointments, scheduling rules, jobs, estimates, receipts, Audio Notes, templates, and outreach drafts.

Audio recordings, photos, signatures, uploaded logos, generated PDFs when enabled, and versioned JSON or CSV data.

Backup responsibilities

Backup ZIPs are not currently password encrypted. Store them as private business records in a protected destination.

A backup kept only inside JobFrame may be lost if the app is uninstalled or app data is cleared. Save an external copy before destructive changes.

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 data.

Exports and message drafts

CSV and JSON exports exist for portability. Outreach and receipt delivery content remains a draft until the user chooses another Android app and reviews the destination.

Record correction and deletion

Jobs and appointments can be corrected without rewriting issued snapshots. Permanent customer deletion is limited to truly empty accidental records; meaningful linked data blocks deletion.

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.