Security & data handling

When you drag a local agreement into the employer tools, the file is sent once, over HTTPS, directly to a short-lived serverless function. It is held in memory only for the duration of that single request.

The file is never written to disk, never saved to a database, and never included in application logs. Once the response is sent back to your browser, the server holds nothing.

You must tick a consent checkbox before any file leaves your browser.

If an AI provider key (OpenAI or Anthropic) is configured for the deployment, the extracted document text (not the raw file) is sent to that provider for a single extraction call, scoped to a strict prompt that only returns figures literally present in the text.

If no AI provider is configured, extraction falls back to a local, fully offline pattern-matcher — the document content never leaves the BizDays server in that mode.

We do not use uploaded content to train models, ours or a third party's.

File size is capped (5 MB) and only plain-text and text-based PDF files are accepted.

Every extracted figure is shown back to you with a confidence label before it is applied to any calculation — nothing is auto-applied silently.

You can discard a result at any time; nothing is retained after you close the tab.

The CBA dropdown ships with a small, clearly-labelled illustrative starter set, not a licensed real-time feed of union agreements.

Every entry that hasn't been checked against its primary source is marked unverified in the UI, with a note on what to confirm before relying on it for payroll.

Prefer zero third-party AI involvement? Simply don't set an AI provider key for your deployment — the heuristic extractor still works, entirely on infrastructure you control, with no outbound calls for document content.

Running an internal/enterprise deployment? Bring your own AI provider key and data-processing agreement so uploaded content is governed by your organisation's own contract with that provider, not a shared one.

Self-hosting is supported — the project is a standard Next.js app with no required external services beyond the optional AI key.

Planned: per-file malware/AV scanning before parsing, per-IP rate limiting on the analysis endpoint, and an audit trail of which figures were applied to a calculation (without ever storing the source document).

If BizDays later offers persistent storage (e.g. saving a company's applied agreement for next time), that data will be encrypted at rest, scoped per authenticated workspace, and deletable on request — this page will be updated before that ships.