Security measures

https://ova.dev/en/security-measures · Updated 14 November 2026

For operators Security measures

Updated

Basis

This overview describes how Ovadev GmbH protects the data in TICKETOVA and JANUNA (Art. 8 FADP, Art. 1 to 3 DPO). It names only measures implemented in the platform. Ovadev GmbH holds no certification.

Location and network

Database, files and application run in a data centre in Switzerland. The servers have no ports open to the internet: requests reach them only through an encrypted tunnel of the network provider, the firewall rejects everything else. For maintenance administrators sign in with short-lived certificates.

Connections are encrypted (TLS). The database accepts only encrypted connections from its own application servers.

Separation of businesses

Each business's data is separated in the database by row level security, which applies to every role of the application. In addition the application checks the business and the person's permission on every request.

Encryption

The platform stores names, email addresses and phone numbers of customers and accounts, and the details of ticket holders, encrypted (AES-256-GCM). It stores sign-in codes, IP addresses in counters and device markers only as verifiers.

Company, person and account details from a business's sign-up are encrypted, as are the access keys of the merchant accounts at the payment service provider. The keys are not kept in the database.

Card details do not reach the platform: guests enter them on the payment service provider's payment page or at the payment terminal.

Sign-in and permissions

The platform has no passwords. Persons sign in with a one-time code by email or with a passkey. Sensitive actions require a fresh confirmation. A session is bound to the device and expires.

The operator grants permissions through roles. The console of Ovadev GmbH is accessible with a passkey only, and a second person approves a staff member's first passkey.

Support access to a business's account needs a reason, is limited in time and visible to the business.

Logs

The platform records changes and access by Ovadev GmbH in a log that can only be added to, not changed. It is sealed daily with a chain of checksums.

Operating logs contain no names, email addresses, codes or card details. Error reports are cleaned first and collected on a server of Ovadev GmbH's own.

Availability and backup

The database is backed up encrypted: in full weekly, the changes daily and the transaction logs continuously. Backups are kept for 30 days and restores are rehearsed. Files are copied hourly to versioned storage, older versions kept for 30 days. Before the yearly anonymisation an encrypted offline copy is made, which is destroyed after 12 months.

Requests are limited to fend off abuse. Forms check the browser with a service of the network provider.

Devices

The operator pairs tills, scanners and other devices in the dashboard. Each device receives a key that never leaves it, and short-lived credentials. Commands to devices are signed. The operator can lock a lost device. Remote support needs consent on site.

Development and operation

Changes to the code go through a pull request with automatic checks, among them a search for secrets in the code and for known vulnerabilities in dependencies. Releases are signed. The servers' credentials are kept encrypted and never in the code.

Deletion

The platform anonymises customers' personal data every year after the period the business sets. Details relevant for accounting remain for 10 years (Art. 958f CO, Art. 70 VAT Act). The individual periods are named in the data overview.