Data Handling
Last updated 10 August 2026
The operational detail behind the privacy policy: where the data physically is, how it is protected, and what happens when something goes wrong. Written for the contractor who wants to know, and for anyone doing vendor due diligence.
Where it lives
One SQLite database on one virtual server in Europe, reached only over HTTPS. The database file is not exposed to the internet; only the application process reads it.
Backups
- A consistent snapshot is taken nightly using SQLite's own backup API — not a file copy, which can capture a database mid-write and produce something that will not open.
- Every snapshot is verified with an integrity check immediately after it is taken. A snapshot that fails the check is discarded and the run reports a failure.
- 14 days are kept on the server and each is also copied to object storage in a different country and a different provider — the server is in Vilnius, the backup copies are in Helsinki — so losing the server does not lose the backups.
Access
- Passwords are stored as bcrypt hashes. Nobody, including us, can read them.
- Sessions are cookie-based, marked
HttpOnlyandSecure, so the browser will not expose them to scripts or send them over plain HTTP. - Sign-in attempts are rate limited per account and per address.
- Every query the app makes is scoped to the account that owns the row, so no contractor can reach another contractor's jobs.
- Authorised staff hold an administrator role that can read account data, and use it for support and for administering the service. Aggregate figures we keep for ourselves — how many people came back the week after signing up — are counted across accounts, and are counts rather than anybody's schedule.
Share and subcontractor links
These are deliberately open: a homeowner should not need an account to see when their kitchen will be finished. Each link carries a long random token, is not listed or indexed, and can be revoked from the project at any time. A share link shows the schedule and progress — it deliberately withholds your internal figures, including schedule health grades and per-task slip.
Recovery
Honest version: the service runs on a single server. If it is lost, recovery means restoring the most recent nightly snapshot onto a new one. The realistic worst case is losing up to one day of logged progress. Schedules themselves are recomputed from your project settings, so they come back with the data.
If there is a breach
If data is exposed, we will tell affected account holders by email with what we know, what was involved, and what to do — without waiting until the picture is complete.
Deleting your data
Deleting a project removes it and everything logged against it immediately. Asking us to close your account removes all of it. Both persist in backups for up to 14 days, after which the backups holding them are deleted on rotation.
Contact
ContractorGantt is a service of Dimetris, UAB, which is the data controller. Registration details are on the privacy page.