Skip to main content

Local-first processing

The landing page promises one thing very directly: your clients' data stays where it belongs — on your device. This page is the technical version of that promise.

What "local-first" actually means​

Zeno CY parses your documents in your browser, on your device. The extraction step that turns a PDF into structured fields happens locally — under 30 seconds on a normal laptop. Your documents do not leave the device unless you explicitly opt into a path that requires it.

How a single document flows​

  1. You select a document. The file is read into your browser, not uploaded to a server.
  2. Processing happens locally. WASM-based extraction runs on your device's CPU. No cloud round-trip in the default path.
  3. Only metadata syncs. The structured fields — date, amount, counterparty, VAT, document type — are saved to your workspace so the Registry persists across sessions.

The original file stays where it was. If you want to delete it from your device, that is your call.

What stays on your device​

Always local in the default path:

  • the original document file (PDF, image, scan),
  • the full text content of the document,
  • any sensitive details printed on the document.

What syncs to the workspace (with your action):

  • the extracted fields (dates, amounts, counterparty names),
  • document metadata (type, status, period),
  • VAT validation results (valid / not determined / unknown),
  • your reviews and registration decisions.

When something needs to leave your device​

A few specific moments require a network round-trip. They are always visible and always optional:

VAT validation​

When the parser extracts a VAT number, Zeno CY checks it against the official EU VIES service. What is sent:

  • the VAT number itself.

What is not sent:

  • the document, the text around the VAT, the counterparty details — none of it.

Exports​

Exports go where you tell them to go. Download to your computer keeps everything local. Sync to Google Sheets requires the Drive consent you already gave. Either way, the routing is explicit.

Things Zeno CY does not do​

  • Upload documents in the background.
  • Share your data without permission.
  • Keep copies of files you have deleted.
  • Run cloud processing on your documents in the default path.

Common questions​

Does this work offline?​

The local processing part does. VAT validation, registry sync, and exports need the internet to reach the relevant services. You can capture and parse documents offline and let them sync the next time you are online.

What if my device is slow?​

Local processing leans on your device's CPU. Older hardware takes longer. The output is the same — only the wait changes.

Can I trust local processing?​

Yes. The extractor that runs in your browser is the same WASM-compiled engine used elsewhere in the product. Same code, same quality, just running closer to your data.

What happens to my documents after the workflow?​

They stay wherever you put them. The extracted information lives in your workspace, the original lives on your device. You can delete one without affecting the other.