dobo AppRelay – Privacy information

1. Provider and contact

dobo-it – Dominique Bös Sole proprietorship (small business) Neustraße 4, 54579 Üxheim, Germany Email: info@dobo-it.de Provider information (German): https://dobo-it.de/impressum/

This information describes the dobo AppRelay macOS host and iPad client. Website visits and contact enquiries through dobo-it.de are also covered by the separate website information at https://dobo-it.de/datenschutz/ (German).

2. Window streaming and remote input

dobo AppRelay connects your own Mac directly to a paired iPad over a local network or a VPN you configure. The devices exchange the list of available windows, information about the selected window, its image and the associated keyboard and pointer input. Window lists can include application names and window titles. Window images and input can contain personal or confidential application data.

Regular connections are encrypted and mutually authenticated. dobo AppRelay does not operate a cloud relay for this transfer. The regular product path does not send the direct window stream or its associated input to dobo-it. You choose the window to share and the devices to pair. Other applications and VPN services you choose process data under their own terms.

Screen Recording and Accessibility permissions are needed for capture and input. You grant and can revoke these permissions in macOS System Settings. A system permission does not replace a legal basis for processing the content you use with AppRelay.

3. Pairing and locally stored data

Devices store cryptographic identities and trust information for authentication. The host uses Apple Keychain for this purpose. Trust records can include device names, public keys, technical certificate bindings and pairing, contact and revocation timestamps. Host network configuration is also stored locally.

The iPad stores host profiles with names, connection addresses, ports and trust references, together with display and language preferences. Security-sensitive device keys are managed separately from ordinary profile preferences. A short-lived QR code is used for initial pairing and should not be shared.

Revoking a paired device on the host blocks its subsequent regular connections. It does not remotely erase data on that device. Local profiles, trust records and preferences can persist across sessions and restarts. App updates do not deliberately erase them; uninstalling the app does not prove that every Keychain item has been removed.

4. Online content and version policies in the iPad client

If a Payload content origin is configured in the build, the iPad client can fetch public information pages, images and version policies over HTTPS. These requests are separate from the direct window stream. Public requests do not require app user accounts or editorial credentials. Config requests include the language and app version in the request path; page requests include the language and page identifier. Image servers receive technical connection information. External links open following a user action and are subject to the destination provider's information.

The contacted server receives at least the IP address needed for the connection, the requested address and the time of the request. The content and config request code does not include window images, keyboard input or private pairing keys in these requests. The server origin depends on the build configuration. These Payload requests do not occur without a configured content origin.

dobo-it provides public dobo AppRelay content through Payload at https://apprelay-api.dobo-it.de. The product website is available at https://dobo-it.de/apprelay/. Hetzner Online GmbH is the hosting provider; Germany is the confirmed hosting location. No additional CDN is planned for this service. No analytics or advertising SDK is planned for the app. Information and available host packages are listed on the download page https://dobo-it.de/apprelay/en/download/. The production CMS address does not establish that every iPad build uses it; the content origin configured in each build determines this.

The confirmed operating rule limits retention of central access and error logs relating to dobo AppRelay to no more than 14 days. Its technical implementation has not yet been verified. Shared proxy logs can also contain dobo AppRelay-related entries. Their retention has not been changed to 14 days; a separate solution for these entries remains unresolved. Logs should contain only necessary technical information, including the IP address, timestamp, requested path and response status. Request bodies, private keys, access tokens and pairing codes should not be logged. Necessary extracts may be retained separately for a documented security incident; their necessity will be reviewed at least every 30 days and they will be erased when no longer required.

Known version policies and notice display state are stored locally. A known mandatory update policy can therefore remain effective offline and after a restart. This storage is not a general usage history or a continuous online requirement.

5. Operation, diagnostics and support

The host writes technical status and error messages through local macOS logging. Retention depends on the operating system and diagnostic configuration. The reviewed product path does not configure automatic uploads of these host logs to dobo-it. Separately enabled development and acceptance tests are outside regular product operation.

If you contact support or provide diagnostic material, the information you send is processed to handle your enquiry. Do not send private device keys, pairing QR codes or confidential window content. dobo-it uses Microsoft 365 to receive and handle email sent to info@dobo-it.de. This includes processing sender and recipient addresses, message content, attachments and technical delivery information. The Microsoft 365 admin center shows EU/EFTA as the current Exchange Online geography and Germany as its committed geography on 5 November 2026. These describe the displayed data residency and do not promise that every processing activity or provider access occurs exclusively in Germany. The operator confirms that the Hetzner data processing agreement and the privacy and contractual documents applicable to their Microsoft 365 subscription are available. Their scope, version and any required safeguards for international transfers were not independently verified as part of the technical release review.

Ordinary support correspondence must be erased no later than six months after the enquiry is closed. Voluntarily supplied diagnostic attachments must be erased no later than 30 days after the enquiry is closed. Records subject to a specific statutory obligation or needed to establish, exercise or defend legal claims are retained separately for that purpose. Exceptions must be justified and reviewed regularly. AppRelay support uses separate folders for open and closed enquiries and for diagnostic material. The closed folders have personal Microsoft 365 deletion policies: 180 days for correspondence and 30 days for diagnostic material, both measured from receipt of the message. These rules do not start when the enquiry is closed. Under the checked mailbox settings, deleted messages remain recoverable for another 14 days. Complete erasure within the specified periods after closure, including other copies and recoverable storage, has therefore not yet been verified.

Daily external CMS backups and an isolated restore test are documented. The backup job installed in production retains seven daily, four weekly and six monthly archives. This does not implement erasure of all backups after 30 days. Local snapshots older than seven days are removed only after a successful external backup. Daily execution, successful pruning and actual archive contents need separate monitoring; the configured archive counts do not guarantee a maximum erasure deadline. Following a restore, known erasures are intended to be reapplied and erased data must not be reused for new purposes. Execution of this erasure reconciliation has not yet been verified. These CMS details do not describe a Microsoft 365 backup or retention configuration; those settings will be checked separately.

The website has separate consent management for website analytics. This website feature does not establish that an analytics SDK is included in the host app.

6. Responsibilities, purposes and legal bases

Local processing serves user-initiated remote control and device authentication. Anyone transmitting their own or another person's data must ensure that this use is permitted. Direct local transfers do not automatically make dobo-it a recipient of window or input content.

Article 6(1)(f) GDPR is the proposed basis for dobo-it's public provision of product content, version policies and downloads, and necessary technical security logs. The legitimate interests are reliable and secure delivery, troubleshooting and preventing misuse. The planned balancing assessment must consider limiting processing to necessary technical data, the specified retention periods and purpose-limited access. Its final review remains outstanding.

Article 6(1)(b) GDPR is the proposed basis for support required to perform a contract or take pre-contractual steps at your request. Article 6(1)(f) GDPR is the proposed basis for other ordinary product enquiries, with the interest of handling correspondence you initiated. Statutory retention must be justified separately against the relevant obligation under Article 6(1)(c) GDPR.

The final review of these assignments against actual operation remains outstanding. Installation and macOS system permissions do not constitute blanket privacy consent. Providing your own diagnostic material for support is voluntary and is not a prerequisite for local window streaming.

7. Your privacy rights

Where dobo-it processes personal data, you may request access, rectification, erasure, restriction and, where applicable, portability under the legal conditions. Depending on the legal basis, you may object or withdraw consent for future processing. You may complain to a data protection supervisory authority. Contact dobo-it at info@dobo-it.de. A support enquiry alone does not enable dobo-it to remotely access or erase data stored only on your devices.

8. Scope and current operating status

This edition describes dobo AppRelay for macOS and iPadOS, version 0.1.0. Updated: 6 November 2026. Central erasure periods are established operating rules. The complete technical operation of logging, erasure and backup settings has not yet been verified. This particularly concerns AppRelay entries in shared proxy logs, final support erasure including recoverable storage, and erasure reconciliation following a CMS restore. Providing the software does not promise that these checks are already complete. Questions about current operation and privacy rights requests can be sent to info@dobo-it.de.