Skip to main content

Practical guide

Local-first invoice privacy

Invoices contain names, addresses, prices, bank details, tax labels, and sometimes sensitive notes about a client relationship. A local-first invoice tool should reduce the number of places that information travels. Formnivo's core editor is built around that idea: create, edit, save locally, print, and export in the browser without requiring an account or document upload.

Local-first is a privacy model, not magic. It protects against unnecessary server-side document processing, but it does not replace backups, device security, or careful sharing.

What stays local

Formnivo uses browser-native storage for local drafts. IndexedDB is designed for significant amounts of structured client-side data, while localStorage is better suited to smaller key-value preferences. That difference is why document drafts belong in structured local storage rather than being sent to a document database by default.

What local-first does not mean

MisunderstandingBetter expectation
"My documents are backed up automatically."No. Browser storage is local. Export PDFs and backup files for records you need.
"Nothing can ever leave my device."Your own exports, emails, screenshots, sync tools, or shared folders can move files.
"Local-first replaces security."Use device encryption, browser updates, screen locks, and careful file sharing.
"Analytics can include document details."No. Product analytics should use only safe metadata and never document contents.

Safe workflow for private invoice work

  1. Open the generator and complete the document in a browser you control.
  2. Export a PDF for the customer and a backup copy for your own records.
  3. Store exported documents in your chosen record system, not only in the browser.
  4. Clear drafts from shared devices after export.
  5. Do not paste secrets, passwords, private keys, or payment-card data into invoice notes.

How to clear local document data

If you used a shared or borrowed computer, clear drafts from the Formnivo workspace and then clear this site's stored data in your browser settings. Browser menus differ, but the privacy idea is the same: remove site data for formnivo.com after exporting anything you need to keep.

Offline boundary

Core editor work is designed to continue locally after required assets have loaded. A first visit, a hard refresh, fonts, browser updates, or a cleared cache can still require network access to fetch site assets again. Export important records instead of treating the browser as the only archive.

How Formnivo separates privacy from marketing claims

The public promise should be narrow and testable: document content is processed locally in the browser and not uploaded to a Formnivo document backend for core editing. The promise should not claim that a browser can protect against every risk after a user exports, emails, syncs, or screenshots a document.

The privacy policy covers the formal policy language. This guide is the plain-English explanation for users and resource pages that want to understand the practical privacy tradeoff.

References used for this explainer

Frequently asked questions

Does local-first mean my invoice is backed up automatically?

No. Browser-local editing keeps document data on this device, but it is not a cloud backup. Export PDFs and JSON backups when the record matters.

Can Formnivo read the invoice details I type?

The editor is designed so document contents are processed in your browser and not sent to a Formnivo document backend. Formnivo analytics excludes names, addresses, item descriptions, totals, and document numbers.

What can still expose my document?

Your own sharing, exported files, screenshots, browser sync, device malware, shared computers, and cloud folders can expose documents. Local-first reduces server exposure; it does not replace device security.

Try the private workflow

Open the free invoice generator or browse allbusiness document generators. For checklist-style document hygiene, read the invoice recordkeeping checklist.