Security and deployment

Where Zeyto Contracting runs, how your data is kept, and what it records. Written from what the product does, not from a certification: we have no third-party security certificate to show you.

Ask us about your setup

Deployment

Local first

Installs on a Windows PC or server in your office, with its own private PostgreSQL database, as Windows services.
Users on the office network connect to it from the desktop app or a browser. Daily work does not need the internet.
Internet is used to activate the licence, to fetch updates and for the phone relay.
A separate client installer is for extra Windows PCs on the same network.

Hosted

Hosted option: coming

A hosted deployment is planned. It is not offered as a service yet and has no price, region or service level.
If you need your data off-premises today, ask us: we will tell you honestly what we can do now.

Phones

How phones connect

The office server dials out to a cloud relay; no inbound port needs to be opened on your router.
The relay is a mailbox between your server and your phones. A Zeyto Contracting licence only connects to Zeyto Contracting connections.
Every phone is approved by the office before it works, with a trust level (basic, standard or full), roles and projects.
The office can block a phone, mark it lost, lock it, force a sign-out or wipe it remotely.
Records are kept in an encrypted queue on the phone and sent when it is online; photos upload in resumable chunks.

Backups

Backup and restore

Backup and restore tools are built in. Backups are encrypted files (AES-GCM with a key derived by Argon2id).
A Zeyto Contracting backup has its own file header. Restore refuses a backup that belongs to another Zeyto product, and says whose it is.
Uninstalling or updating keeps your data. A silent uninstall deletes nothing unless given an explicit purge phrase.
Keep a copy of backups off the server. A backup on the same disk is not a backup.

Audit

A trail you can show an auditor

Every change to project tables, masters, users, roles, approval rules and document headers is recorded with before and after values, the user and the reason.
The trail is hash-chained, so a gap or an edit shows up.
Four-eyes rules are enforced in the database for budget changes and retention release: the creator cannot approve.
Period locks, per-project cost locks and filed VAT period locks stop late changes to closed figures.

Access

Who can do what

Roles and permissions decide screens and actions; modules you did not license answer with a clear message.
Approvals can be set by project, department, node and amount, with delegation and time limits.
Client approval links carry a long random token; only its hash is stored. A link expires, can be revoked, and can require a six-digit code.
If a licence lapses the system goes read-only rather than losing data; an administrator can still sign in to fix it.

Not done yet: an independent penetration test, and a clean-machine installation test of the Windows installers. Both are planned before release. For the Zeyto platform in general see the Zeyto security page.