OpenCode Remote

Data Processing Addendum

Version 2026-10-21.1 · English original

This addendum applies where a business customer uses OpenCode Remote with personal data and Fier-App acts as a processor. Because the relay is a blind transport and does not store conversation content, the processing is limited to transport and technical security.

1. Subject matter and duration

Processing lasts for the duration of the customer's use of the relay. The customer decides which data are sent through OpenCode on its own computer.

2. Nature and purpose

Fier-App forwards encrypted WebSocket frames between the customer's agent and paired devices, and processes technical connection metadata for operation, security and fault analysis.

3. Categories of data

Connection metadata (IP address, timestamps, paths, frame sizes) and ciphertext that Fier-App cannot decrypt. No OpenCode session content, credentials or AI-provider data are stored by Fier-App.

4. Security measures

Transport is protected with TLS. Application frames use end-to-end encryption with keys held only by the customer's devices. Device tokens are stored on the customer's computer as hashes. The relay keeps no database of conversations.

5. Sub-processors

Cloudflare provides hosting and network infrastructure. The current list is available on request. Transfers outside the EEA rely on the EU Standard Contractual Clauses and supplementary measures where required.

6. Assistance and deletion

Fier-App assists the customer with data-subject requests and security incidents within the limits of the transport-only service. The customer can delete local browser data and revoke devices at any time; Fier-App has no stored conversation data to delete.

7. Contact

Data-protection questions: support@fier-app.de.