Security
This page lists only what is true in the code and on the server today. Anything still in progress is marked as such.
Last checked against the code: 15 November 2026.
How we protect your data
Server and encryption
- Our own server in Hetzner’s EU data centre.
- The database and uploaded files sit on a LUKS-encrypted data volume.
- Every connection uses HTTPS; HSTS for one year, including subdomains.
- Security headers: nosniff, framing blocked, strict Referrer-Policy. In the app, a per-request nonce CSP and a narrow Permissions-Policy.
Separating companies
- Every table holding company data is under Postgres row-level security (RLS, FORCE).
- The app runs with a database role that cannot bypass row-level security.
- On every database update a machine check confirms that no company table is left unprotected; if one is, the deployment stops.
Sign-in
- Two-step sign-in with an authenticator app (TOTP). Mandatory by default for the company administrator, and always for the platform console.
- TOTP secrets are encrypted (AES-256-GCM); single-use recovery codes are stored only as hashes.
- Sign-in limits: 20 failed attempts per IP and 15 per account within 15 minutes; in front of the server, 60 requests per minute per IP on the sign-in paths.
- The session cookie is HttpOnly, Secure and SameSite=Lax, and lasts at most 13 hours.
Sign-up and public demo
- Self-service sign-up with email confirmation: the confirmation link lasts 48 hours and is stored only as a hash.
- Sign-up is limited to 5 attempts per IP address in 15 minutes; disposable email addresses and automated form-filling are filtered out.
- The public demo is a separate demo company: a session lasts at most 2 hours, and one-click sign-in is limited to 10 per IP address per hour.
- Blocked in the demo: password, two-step sign-in, account deletion, invitations, permissions, publishing the public page and creating client links. Uploads up to 8 MB, in a limited number per IP address.
- The demo content is reset to its starting state every night.
The client link
- Read-only: nothing can be changed from the progress page.
- A random 96-bit identifier; it can be revoked at any time and expires a set time after the job is closed.
- Only entries marked as client-visible appear; search engines do not index it and the browser does not store it.
- Requests per IP address are rate-limited.
- A finalised report is numbered and its entries are locked, so the version shown at handover stays the same.
Logs
- The app contains no third-party analytics or advertising code, and this website sets no cookies.
- In the server access log and the audit log, IP addresses are truncated (IPv4: /24, IPv6: /48) and tokens are removed from links.
- The audit log is append-only: existing rows cannot be changed or deleted.
- The failed sign-in log keeps the full IP address for 90 days to detect abuse.
- Going live
Backup
- A database backup on the server every six hours, with a copy sent to Cloudflare R2 storage.
- Retention: database backups for 30 days, weekly backups for 89 days.
Website statistics backup
- The website statistics (Umami) database is backed up daily, encrypted, to Cloudflare R2 in the EU jurisdiction; we keep 7 daily, 4 weekly and 6 monthly backups, with an integrity check every Sunday. Restoring has been tested.
Leaving and deletion
- When a company leaves, all of its data can be downloaded as a ZIP; the download link is valid for 7 days and at most 5 downloads.
- Company data is deleted only after a verified export, and a machine check confirms afterwards that nothing remains.
- You can delete your own account yourself in the account settings.
Development
- A dependency check on every change: code with a high or critical vulnerability does not ship.
- A software bill of materials (SBOM) and a secret-scanning check on every build; dependencies are updated weekly.
- On the server: key-only SSH, root login disabled, automatic security updates.
Where we are today
Honestly: what is done, what is going live now, and what is not there yet.
Done
- Company separation with row-level security
- Two-step sign-in
- Encrypted data volume
- HTTPS and security headers
- Full export when leaving
Going live
- The copy of the six-hourly backup to Cloudflare R2
Not yet
- External penetration test
- ISO 27001 or SOC 2 certification
- Bug bounty programme
- A CSP header on the website (the app has one)
Who processes your data
The data processing terms name these sub-processors. We do not pass the content of your jobs to third parties.
| Hetzner | Server and storage | EU |
|---|---|---|
| Cloudflare | Backup (R2) and DNS | — |
| Resend | Email delivery | — |
Found a vulnerability?
Write to security@joboptim.com. The contact is also listed in security.txt.
What we commit to
- We confirm that we received your report.
- We investigate it and let you know about the fix.
What we ask
- Do not access other companies’ data and do not change anything.
- Do not overload the service.
- Give us time to fix it before you publish.
Legal documents
In force since 15 November 2026; currently in Hungarian only.
Frequently asked questions
Where is my data?
On our own server in Hetzner’s EU data centre, on an encrypted data volume. A copy of the backup goes to Cloudflare R2 storage.
Can another company see my jobs?
No. All company data is under row-level security, and a machine check confirms this on every database update.
What does my client see?
Only the entries you mark as visible to them, on a read-only link. You can revoke the link at any time.
What happens to my data if I leave?
You can download all of it as a ZIP, and we delete it only after a verified export.
Has there been an external security review?
Not yet: there is no external penetration test or certification so far. We will say so here when there is.