What breaks in a cloud-first invoicing app
If the customer list and document templates live on a server, losing signal usually means a spinner, a stale cache, or an app that refuses to create a new record because it cannot reserve an invoice number.
The failure lands exactly where it hurts: at the end of the job, in front of the customer, when you want the paperwork closed.
Where the connection genuinely is needed
Sending the finished PDF by email or messaging requires a connection at the moment you send it, which is unavoidable for any app.
App Store purchases, subscription management and restoring an entitlement run through Apple's servers and need a connection. Optional Pro iCloud sync also needs one to propagate, and resumes on its own once you are back in range.
Offline and private are the same design
An app that stores records locally works offline as a side effect, and keeps customer data off a vendor server as another side effect. Those are two views of the same architecture.
QuoteLocal has no QuoteLocal account, no advertising SDK and no behavioural analytics SDK. Backups are password-protected AES-256 files under your control.