Technical and Organisational Measures (TOMs)
pursuant to Art. 32 GDPR · Annex 2 to the Data Processing Agreement
Version of 18 November 2026
1 Scope and Organisation
This document describes the measures by which F.N. Software Studios ensures the security of processing in the OnSite-Soft software. It applies to the production environment of each data region (EU, US), backups, support and development.
F.N. Software Studios is an owner-managed business. The owner, Fabian Neumann (kontakt@onsite-soft.de), is responsible for information security and data protection. No data protection officer is currently appointed because, in the company’s assessment, the requirements of Section 38 German Federal Data Protection Act and Art. 37 GDPR are not met. Any employees or freelancers are bound to confidentiality and data protection and trained before starting work.
2 Confidentiality (Art. 32 (1)(b) GDPR)
2.1 Physical access control
- Production systems run exclusively in data centres of the sub-processor IONOS SE in Germany (EU region). Access only for authorised data centre staff with multi-level access control, video surveillance and 24/7 security; the data centres’ information security management system is certified to ISO/IEC 27001 (operator’s evidence).
- F.N. Software Studios does not operate its own servers in office premises. Work devices are encrypted, locked by passcode/biometrics and not left unattended.
2.2 System access control
- Server access exclusively via SSH with keys (no password login), only for the administrator; the firewall (ufw) is active and allows inbound only SSH, HTTP (redirect to HTTPS) and HTTPS; everything else is blocked. Root login is disabled.
- Database, API and worker run in separate containers without publicly reachable ports; the database is in an internal network without internet access. Only the reverse proxy (Caddy) is publicly reachable.
- Users log in with a password (stored only as a scrypt hash with individual salt) and a second factor (TOTP), which is always mandatory for administrators and can be required by Customer for all users, or via single sign-on (OIDC/SAML) through Customer’s identity provider.
- Web portal sessions use httpOnly, Secure cookies; login steps expire after one day, ended sessions are deleted after 30 days.
- Kiosk iPads authenticate with their own device credentials (stored in the iOS keychain) that can be revoked individually.
- Integrations use OAuth2 client credentials with limited permissions; rate limits protect against brute-force attacks (default 600 requests/minute per client, public endpoints 120/minute per IP).
2.3 Data access control (permissions)
- Role-based permission model with rights per tenant, site group or site; default deny and least privilege. Nobody can grant rights they do not hold themselves.
- Reception staff do not see employee attendance data by default.
- Administrative access by F.N. Software Studios to Customer data only as required for operation, support at Customer’s request or incident resolution.
2.4 Separation control (tenant isolation)
- Each customer is a separate tenant. Separation is enforced threefold: checks in application code (tenant always from the authentication, never from input), composite foreign keys (tenant, ID) and PostgreSQL row-level security. The application uses a database role without ownership rights that is subject to row-level security.
- Separate instances per data region (EU/US) with their own database, backup and email delivery; a tenant is immutably assigned to one region.
- Production, test and development environments are separated; no production data is used in test and development.
2.5 Pseudonymisation and encryption
- Transport encryption: exclusively HTTPS with TLS 1.2 or higher, automatically renewed certificates; email delivery via TLS/STARTTLS.
- Secrets (e.g. webhook secrets, connector credentials) are stored encrypted with AES-256-GCM.
- Backups are encrypted client-side before transfer (restic, AES-256); the key is not held by the storage provider.
- QR codes contain no clear data but signed tokens (Ed25519) with visit ID and expiry.
- Data on kiosk iPads (emergency package) is stored in the app container with iOS data protection (device file encryption).
- Statistical exports can be created without contact data.
3 Integrity (Art. 32 (1)(b) GDPR)
3.1 Transfer control
- Transfers exclusively encrypted (see 2.5). Webhooks are signed with HMAC-SHA256; delivery only to public addresses, redirects are not followed (protection against SSRF/DNS rebinding).
- CSV exports are logged with filters, role and row count and protected against formula injection.
3.2 Input control
- Tamper-evident safety log (audit log): each row with sequence number and hash chaining; updates and deletions are blocked by database triggers, even for the table owner.
- Attendance corrections are stored as separate events with mandatory reason; original events are retained.
- Briefing acknowledgements, signatures and incident histories are stored immutably (exception: erasure under data protection law).
- API usage logs are retained for 90 days, webhook delivery logs for 30 days.
4 Availability and Resilience (Art. 32 (1)(b) and (c) GDPR)
- Daily encrypted backup of the database (including uploaded files) and configuration to separate object storage in the same region; retention of 14 daily, 8 weekly and 12 monthly snapshots.
- Documented and tested restore procedure; target RPO 24 hours, target RTO 8 hours.
- Monitoring of availability of app, API and website (uptime monitoring, check every minute) with alerting.
- Containers with memory limits and automatic restart; maintenance in fixed maintenance windows.
- Data centre with redundant power supply (UPS, emergency power), air conditioning and fire protection (operator’s measures).
- The iPad app’s emergency mode works offline with the last synchronised state and reconciles entries later without conflicts.
- Devices without heartbeat are reported offline after 5 minutes.
5 Regular Review (Art. 32 (1)(d) GDPR)
- Automated tests (integration tests against a real database) for every change; changes via pull requests with review before merging.
- Dependencies are regularly updated and checked for known vulnerabilities.
- Operating system and container images are regularly updated; security updates for critical vulnerabilities at short notice.
- Restore tests at least semi-annually and review of these TOMs at least annually.
- Process for security incidents and personal data breaches (see incident response plan), notification to customers within 24 hours.
6 Processor Control
- Sub-processors are selected based on their security measures and contractually bound under Art. 28 GDPR (see sub-processor list).
- Processing only on Customer’s instructions (configuration, DPA). Support access only on request or for incident resolution.
7 Data Protection by Design (Art. 25 GDPR)
- Privacy-friendly defaults: mandatory visitor fields are minimal by default, photo and signature only if enabled by Customer.
- Automatic deletion after configurable periods (defaults: visit data 90 days, attendance 180 days, visitor photos 30 days).
- Functions for access, export and erasure per person; versioning and hash evidence of the privacy notice displayed.
- Person flags (e.g. blocked badges) reject at the kiosk without displaying the reason.