Quartiero®
HomeProductPricingAboutHelpContact
HomeProductPricingAboutHelpContact

Technical and organisational measures (TOMs)

This page describes the technical and organisational measures (TOMs) of the platform that runs the portals, the booking of advertising and the screens. It forms part of the platform's two data processing agreements (DPA): the DPA for customers who show their own content on their screens, and the DPA for advertisers. In both, it sets out section 6 in detail. The agreement that applies on this website is available under DPA.

The legal basis is Art. 9 of the Swiss revFADP and Art. 3 of the Data Protection Ordinance (DPO), and where the GDPR applies, also Art. 28 and Art. 32 GDPR.

In the DPA for customers with their own content, the processor is Quartiero GmbH. In the DPA for advertisers, it is the operator of the booked screens who issues that agreement. K-I-Soft IT&Holding GmbH develops and runs the technical platform as a subprocessor (section 7 of the DPA). The measures on this page apply to the whole platform and therefore equally to every operator.

Quartiero GmbH may adapt individual measures to the state of the art as long as the level of protection does not decrease. The version published on this page applies. The information describes the production environment; the test environment runs in an AWS account of its own.

1. Storage location and infrastructure

The database, content, media and invoices are stored with Amazon Web Services (AWS) in the Zurich region. The platform uses managed AWS services for this, among them AWS Lambda for the application, Amazon DynamoDB for the database, Amazon S3 for files and Amazon Cognito for sign-in.

Where data only passes through or is briefly processed outside Switzerland, for example at the access point of the delivery network, for the real-time connection in Frankfurt and for video conversion, section 7 of the DPA describes it.

2. Confidentiality

2.1 Physical access to the data centres

The platform runs no server rooms of its own. Physical access to the data centres is governed by AWS; the platform inherits this measure from AWS. The AWS data centres are certified under ISO 27001 and SOC 2, among others.

2.2 Access to the systems

  • Sign-in to the portals: through Amazon Cognito in Zurich, with two-factor sign-in required. Besides the password, an authenticator app serves as the second factor. Signing in with a passkey requires confirmation by PIN or biometrics, and that counts as the second factor. SMS is not used.
  • Passwords: at least 12 characters with upper and lower case letters and digits.
  • Sessions: an access token is valid for 60 minutes. The session cookie cannot be read by scripts in the browser and is only sent over encrypted connections. Refresh tokens can be revoked.
  • Access to the AWS accounts: only through the AWS access portal (AWS IAM Identity Center), with personal accounts at Microsoft Entra ID. Entra ID requires two-factor sign-in, which is remembered on known devices for at most 7 days. Changes to the production environment are triggered only by one designated person.
  • Access of the screens: see section 7.

2.3 Access to data and separation per organisation

  • Roles: Within an organisation there are owners and administrators. Deleting the organisation and handing over ownership are reserved to the owners.
  • Tenant separation: The backend checks every request against the membership in the organisation concerned. Hiding something in the user interface never counts as protection on its own.
  • Delegation: A commissioned service provider only gets access to the screen placements the organisation assigns to it.
  • Platform administration: The platform's administrators form a group of their own in Amazon Cognito; the backend checks their functions separately.
  • Screens: A screen only receives the content intended for its screen placement.
  • Real-time notices to the portals: They carry no content, only the notice that something needs reloading. The data is then loaded through the authorised request. On this channel the browser can only listen.
  • Screenshots: They can only be retrieved with a signed cookie that is valid for 10 minutes and limited to the path of the screenshots.
  • Storage: The file stores are blocked against public access account-wide and are delivered only through the AWS delivery network (Amazon CloudFront). Upload addresses are valid for 15 minutes.
  • Payment data: Card and TWINT data is captured and stored by wallee AG alone. The platform only stores a reference to it.

2.4 Encryption

  • Stored data: The database, media, invoices and the application logs are encrypted with a key of the platform's own in the AWS Key Management Service (KMS) in Zurich. The key is rotated automatically. It cannot be deleted by accident together with the infrastructure, and a manual deletion has a waiting period of 7 days.
  • Data in transit: Websites, portals and interfaces can only be reached over HTTPS with at least TLS 1.2, and the browser is instructed to connect only in encrypted form (HSTS). The file stores only accept encrypted connections. The screens likewise connect only in encrypted form (section 7.2).

3. Integrity

3.1 Input and change control

  • Events: Every organisation keeps a list of its events with the time and the person who triggered them, for example changes to members, delegations, access for AI assistants, export and import, billing and deletion.
  • Acceptances: The acceptance of terms and DPA is recorded with version, time and person.
  • Screen history: Interventions on a screen, for example opening remote maintenance, are recorded with the time in the device's history.
  • Concurrent changes: Every record carries a version number. A change based on an outdated state is refused and overwrites nothing.
  • Invoices: An issued invoice can no longer be changed; it is corrected only by cancellation or credit note. The application has no right to delete invoice files, and their store keeps every version.
  • Uploaded files: Only file types from a fixed list are accepted. They are delivered with headers that prevent scripts from running.
  • Logs: Requests to the platform's interfaces are logged, as are administrative actions in the AWS accounts (AWS CloudTrail, with a check against later alteration). The retention periods are in section 6.

3.2 Transfer control

  • Transfer: All data is transmitted in encrypted form (section 2.4).
  • Export of an organisation: It can only be started by the organisation's owners and administrators, by the operator responsible for it and by the platform's administrators. The download address is valid for 2 minutes.
  • Screens: A screen only receives its own content and only listens to its own control commands (section 7.2).
  • Firmware packages: They are only delivered with an access key that is valid for 30 minutes and bound to the single file.
  • Subprocessors: Which service providers receive data and where it is stored is set out in section 7 of the DPA.

4. Availability and resilience

  • Delivery: Websites, portals and media run through Amazon CloudFront.
  • Protection against attacks and overload: A web application firewall (AWS WAF) stands in front of the websites and portals, with the AWS managed rules against known attack patterns and addresses with a bad reputation. Per IP address, at most 10,000 requests to the interface are possible in 5 minutes. The interface itself also limits the load, especially strictly for public requests and for pairing screens. The backend refuses requests that bypass the delivery network.
  • Protection against guessing: PIN and pairing codes are blocked after 10 failed attempts within 15 minutes.
  • Monitoring: Alarms report errors, overload and unusual access patterns by e-mail, for example an accumulation of refused requests. Amazon GuardDuty monitors the AWS accounts in all regions in use and reports findings of medium severity and above by e-mail.
  • Screen updates: New software goes to a small group of devices first and only afterwards to the rest. Firmware is installed only at night and only when nobody is standing in front of the screen.

5. Recoverability

  • Database: For the tables with accounts, organisations, content, playlists, devices and invoices, a continuous backup runs. It allows a restore to any point in time within the last 15 days. Excluded are short-lived tables such as pairing codes and counts, and the logs, among them the history of the devices and the events of the organisations.
  • Invoices: The store of the invoice files keeps every version.
  • Key: The key that encrypts the data is retained even when parts of the infrastructure are rebuilt.
  • Software: Every release of the platform is kept in a store. The production environment receives the same release that ran unchanged in the test environment before, and an earlier release can be rolled out again.

6. Data minimisation and retention periods

The platform stores only what operation requires. The screens' counts are anonymous (section 7.7). These retention periods apply to technical data:

DataRetention
Anonymous raw counts of the screens90 days, after that only as anonymous daily values
Error logs of the screens30 days
History of a screen (technical events and interventions)180 days
Live images of the remote view30 days
Access logs of the delivery network180 days
Access logs of the interfaces180 days
Application logs90 days
Error logs of the sign-in check at the access point30 days
Firewall log (only refused or conspicuous requests)30 days
Log of administrative actions in AWS365 days
Files for export and import1 day
Pairing codes1 hour
  • Access for AI assistants: Only a non-reversible check value is stored. An access expires after one year at most and is deleted when the person leaves the organisation.
  • Deleted account: Name and e-mail address are removed, also from the record of e-mails sent.
  • End of contract: Data is deleted or returned under section 10 of the DPA.
  • Deleted organisation: If there is anything to bill or to prove, it keeps running until the end of the month and can still be restored for 30 days after that. Then the platform deletes its content, media, playlists, screen placements, memberships, history and the counts of its content for good. If an invoice is still open or a device has not been returned by then, the deletion waits until that is settled. An organisation with neither is deleted completely at once.
  • Kept for ten years: invoices with payments and accounting entries, orders, the acceptances of the terms and the DPA, and the organisation details these records refer to (Art. 958f CO).

7. The screens in the field

The platform controls screens with a built-in Android computer (ARM), advertising screens on a PC (x64) with a dedicated Android firmware, and screens that run in a browser.

7.1 Identity

  • A key of its own per device: An Android screen creates its private key itself in Android's protected key store (Android Keystore). The key never leaves the device.
  • Certificate: AWS IoT Core issues an X.509 certificate for the key. When a device is deregistered or decommissioned, the certificate is deactivated and deleted.
  • Sign-in to the backend: The device identifies itself with a signature made with this key and receives an access token in return, which is valid for one hour and signed with a platform key in AWS KMS.
  • Browser screens: They are connected through a PIN or a pairing code that is valid for 15 minutes. The backend keeps the device credential for it only as a check value.

7.2 Connection

  • The devices connect to the platform only over encrypted connections, over HTTPS and, for the real-time connection, over MQTT with TLS.
  • On the real-time connection a device may only subscribe to its own topics. It may not send anything there; status reports go through the encrypted interface.

7.3 Locked-down operation (kiosk)

  • On the Android screens the player app is set up as device owner and runs in lock task mode. Status bar and lock screen are switched off, and the app cannot be uninstalled.
  • Also blocked are safe mode, additional users, external storage media and the choice of other default apps. The Google Play Store is hidden. The app does not allow backups through Android.
  • The advertising screens on a PC accept no incoming connections except through the remote maintenance tunnel (section 7.5) and Android's debug access (ADB), which is protected by a key and switched off at every start.

7.4 Software and firmware

  • Player app: It is signed (APK signature scheme v3). Android installs an update only if it is signed with the same key. The signing key is kept in AWS Secrets Manager of the production account, and signing happens only on one designated workstation.
  • Checksum: Before installing, the device checks the checksum (SHA-256) of every update and every firmware package and aborts on a mismatch.
  • New devices: Every screen receives the current firmware before it is put into service.
  • Distribution: Updates go through rollout rings; a blocked release cannot be assigned to any ring.

7.5 Remote maintenance

  • The debug access (ADB) and the remote maintenance tunnel are opened only by the platform's administrators. The backend checks the permission, and every opening and closing is recorded in the device's history.
  • The tunnel is a WireGuard connection with a new key for every session, which is kept only in the device's memory. A restart or switching off closes it.
  • The tunnel's hub only lets the debug access through from the administrators' accesses to the devices. Through it, devices reach neither each other nor the internet.
  • An open debug access has no time limit; it closes when an administrator closes it or the device restarts.

7.6 Data on the device

  • The device keeps the content, media and playlist of its screen placement in a cache, together with its identifier and its key.
  • Nobody signs in at the screen, so the device stores no accounts of persons.
  • Wi-Fi passwords appear in no log.
  • When decommissioned, the device deletes its certificate, key and enrolment. A factory reset erases the whole storage.

7.7 Sensors and screenshots

  • No camera: The player app requests no permission for camera or microphone.
  • Presence: A radar sensor only detects whether someone is standing in front of the screen. It delivers no images. The device switches off the sensor's Bluetooth access during operation.
  • Counts: For each event the platform only receives its kind, presence or touch, with the time and the content that was running. No link to a person arises.
  • Location: A device measures its position by GPS only if the operator switches this on for that device and the device has a receiver.
  • Screenshots: They only show what the screen is displaying at that moment. They can be requested by the platform's administrators and by authorised persons of the organisation the screen belongs to (section 2.3).

8. Review and improvement

  • Security review: On 13 October 2026, the code and configuration of the whole platform were reviewed for vulnerabilities. Most of the measures derived from it are in place, among them the check of file types on upload, the protection of screenshots by signed cookies, the firewall with load limits, the access logs, monitoring by AWS CloudTrail and Amazon GuardDuty, and the alarms.
  • Register of measures: Every security measure is listed in a register with its risk, decision, implementation, evidence of the check and remaining residual risk.
  • Dependencies: New versions of the libraries in use are proposed automatically every week and are reviewed and adopted by hand; security fixes at any time.
  • Tests: Every change to the portals, the player and the infrastructure goes through automated tests.
  • Release: A release runs in the test environment first and then reaches the production environment unchanged.

9. Control of processing and notifications

  • Subprocessors: Which service providers are used, for what and where the data is stored is set out in section 7 of the DPA.
  • Instructions and confidentiality: They follow section 5 of the DPA.
  • Data security breach: The notification to the customer within 72 hours is set out in section 9 of the DPA.

As of 20 November 2026

Quartiero

Digital building info for Swiss apartment buildings.

Swiss Made Software

Navigation

HomeProductPricingAboutKnowledgeHelpContact

Legal

Legal noticePrivacyTermsDPATOMs
Solutions forRental propertiesCondominiumsHousing cooperativesSmall portfolios
© 2026 Quartiero. All rights reserved.Quartiero® is a registered trademark of Quartiero GmbH.Technology partnerK-I-Softv0.1.617