Draft

Technical and organisational measures

DraftNot approved. This text is a draft for legal review by the owner and is not yet part of any contract. Items in [square brackets] are still open.

Technical and organisational measures (Art. 32 GDPR)

Version: draft 0.1 of 11 November 2026. Annex 1 to the Data Processing Agreement of ImageNotion UG (haftungsbeschränkt) ("Awacino").

0. The basic design: little data, and no connection content

  • The content of connections (screens, files, commands, network traffic) runs end-to-end encrypted directly between the Customer's devices. The keys are created on the devices and never leave them. Awacino's servers only introduce the devices to each other.
  • Devices in the Customer's network open no inbound ports; they only connect outwards.
  • Exception: the web terminal in the browser is relayed by Awacino, encrypted in transit and not stored.
  • Device identifiers are stored only as a salted hash.

1. Confidentiality (Art. 32 (1) (b) GDPR)

1.1 Physical access control

  • Awacino runs no data centre of its own. Servers and databases run with providers whose data centres are certified (for example ISO 27001, SOC 2), see Annex 2 of the DPA.
  • Offices: [Owner: describe office access - locked rooms, no servers on site, devices encrypted].

1.2 System access control

  • Users sign in with Apple, Google, Microsoft, e-mail link or password; company accounts with the company's own login provider through OpenID Connect or SAML 2.0 (company version, Premium).
  • Admins, main admins and auditors of company accounts must use a second factor; critical changes ask for it again (company version).
  • Staff access to the production systems (database, cloud consoles) is limited to named persons and protected by a second factor. [Owner: confirm for PlanetScale, Cloudflare, bunny.net, Strato, Apple, Google, Stripe.]
  • Secrets (API keys, sign-in provider secrets) are kept in the providers' secret stores and never in source code or logs.

1.3 Data access control

  • Every database table is protected by row-level security: a user sees only their own rows, a company member only the company's rows that their role allows. Changes go through checked server functions that verify the role and write the audit log.
  • Five roles with least privilege: main admin, admin, user, read user, auditor (company version).
  • Every connection passes a live check of membership, role, device list and second check when it starts; removing or deactivating a user ends their sessions at once.
  • Company devices trust one company key. Each member who connects to company devices receives a copy of it, encrypted with that member's personal key, which only that member's app can open; auditors receive no copy. The key pair is generated and stored by Awacino's account service, protected by the company account's key password where one is set.

1.4 Separation

  • Data of different customers is separated logically by row-level security on the customer and company identifier.
  • Development and test systems are separate from production; production data is not used for testing. [Owner: confirm.]

1.5 Pseudonymisation and encryption

  • All connections to Awacino's services use TLS. Connections between devices are end-to-end encrypted.
  • The database provider encrypts stored data and backups (AES-256).
  • Usage statistics are pseudonymous: no IP address, no device identifier, a keyed hash of the account identifier.

2. Integrity (Art. 32 (1) (b) GDPR)

2.1 Transfer control

  • Transfers only over encrypted channels (TLS, end-to-end encryption between devices). No transfer on physical media.
  • Exports (audit log, users, devices) are available only to the roles that may see them, and are recorded in the audit log.

2.2 Input control

  • The audit log records sign-ins, failed sign-ins, admin actions and every connection. Each entry is chained to the one before it, so a later change is detectable (company version).
  • Admins receive alerts for security-relevant changes (new admin, change of sign-in setup or second check, repeated failed checks, use of the emergency account).

3. Availability and resilience (Art. 32 (1) (b) and (c) GDPR)

  • Services run on providers with redundant infrastructure. Connection setup runs on a distributed network; an outage of one location does not stop the service.
  • The database is backed up daily by the provider; [Owner: backup retention period and point-in-time recovery of the PlanetScale plan].
  • Connections that already run between devices do not depend on Awacino's servers.
  • Restore: [Owner: describe restore test and target times].

4. Procedures for regular testing and evaluation (Art. 32 (1) (d) GDPR)

  • Before every major release, Awacino carries out a documented internal security review (threat model, OWASP ASVS level 2 checklist, automated attack tests for row-level security, sign-in, tokens and the second check) and publishes the report. It is an internal review, not an independent attestation.
  • Dependencies and secrets are checked for known vulnerabilities on every release.
  • Vulnerability reports are accepted at security@awacino.com (see /.well-known/security.txt).
  • These measures are reviewed at least once a year and after every significant change.

5. Incident handling

  • Security incidents are recorded, assessed and handled by a named person. [Owner: name.]
  • Customers are informed of a personal data breach without undue delay, at the latest within [48] hours (DPA section 4.5).
  • After an incident, the cause is analysed and the measures are adjusted.

6. Organisation

  • Everyone working with personal data is bound to confidentiality and data protection in writing.
  • Sub-processors are selected with care, bound by a data processing agreement and listed in Annex 2.
  • Customer instructions are documented (DPA section 3).
  • Data protection by design and by default: the product stores as little as possible, and the content of connections never reaches us.