RTSP Mixer

Privacy

Last updated: 4 October 2026 · Deutsche Fassung

Who is responsible

Dominik Peuscher
c/o MDC#1496
Welserstraße 3
87463 Dietmannsried
Germany
E-mail: business@dpeuscher.de

What stays on your device

Everything you set up is stored on the device. It only leaves the device if you write a backup file or switch on iCloud sync, both described below.

Camera addresses, user names, names and views

In the app's own settings on the device.

Camera passwords

In the system keychain, not in the settings.

Settings such as buffer sizes or the alert tone

Also local only.

Replay and event clips

The last few seconds of each camera are held in memory only and are gone when the app quits. A video file is created only when you share a clip; it reaches your photo library only if you choose “Save Video” there.

Notifications

Notifications, such as a sound alert, are created by the app on the device itself. There is no push service and no server that sends them.

Connections the app makes

To the cameras whose address you entered: RTSP over TCP or UDP, and, depending on the address, a continuous MPEG-TS stream over HTTP(S) or RTMP(S). Video and audio travel directly between your device and the camera, with no intermediate server, no cloud and no relay. If you set up a Home Assistant address to steer a camera that does not speak ONVIF, the app also talks directly to that server, using the address and access token you enter yourself. Both are optional; neither is contacted unless you set it up.

Because cameras normally sit on the same network, the system asks on first launch for permission to find devices on the local network. Without it, cameras on your home network stay dark.

When you start a camera search, the app probes the addresses of your own local network on the usual RTSP ports and asks any device it finds for its ONVIF details. The search runs only when you tap it and never leaves your network.

The encrypted backup

You can write your setup, meaning cameras including passwords and views, into a file, to share or keep elsewhere. Optional, and only when you ask for it.

• The contents are encrypted with AES-GCM. The key is derived from your passphrase (PBKDF2 with HMAC-SHA256 and 600,000 rounds).
• The passphrase is stored nowhere, neither on the device nor in the backup. Without it the file cannot be read, not by us and not by Apple.

iCloud sync

A separate switch keeps cameras, views and your shared settings in step across your own devices. That is handy for an Apple TV, which has no file picker. Unlike the backup file above, this one carries no passphrase: turning the switch on is enough. That also means the setup travels unencrypted through your private iCloud key-value storage, the same trust boundary iCloud Keychain already uses for the app's own keychain items. It is off by default, lives only in your own iCloud account, and we have no access to it. The switch itself never travels: each device decides for itself whether it takes part.

What travels with it:

• Cameras and views, camera passwords included.
• The Home Assistant address and its long-lived access token. It sits in the same trust boundary as the camera passwords, so the camera control works on your other devices without typing it again.
• Settings that express a preference: the alarm tone policy and which control overlays a full-screen camera shows.

What stays on the device is everything that describes this device: timeouts and reconnect behaviour, audio buffering, volume and mute, keeping the screen awake, the debug overlay, the diagnostic log, the experimental wall, and the iCloud switch itself.

The diagnostic log

For chasing down a troublesome camera, a verbose log can be switched on. It is off by default, writes to your device's system log and is never sent anywhere. It contains camera addresses and connection history, but no passwords.

No third parties

The app contains no third-party libraries, no analytics kits, no advertising networks and no third-party crash reporters. No tracking in the sense of Apple's App Tracking Transparency takes place.

What Apple collects

Distribution through the App Store and TestFlight runs through Apple. What Apple processes is determined by Apple and governed by Apple's privacy policy. If you agree to share analytics in your system settings, we may see aggregated, non-personal figures about installations and crashes. They do not allow any conclusion about individual people.

The in-app purchase is handled entirely by Apple as well. The app only asks the App Store whether the purchase exists on your Apple Account; we receive no payment details and no account information.

Your rights

The GDPR gives you rights to information, correction, deletion, restriction, data portability and objection. Since we process and store no personal data through this app, there is nothing to disclose and nothing to delete. Your data lives on your device: it disappears completely when you delete the app.

For questions or a complaint, reach us at the address above. You also have the right to complain to a data protection supervisory authority.

Changes

If something about the app changes that affects this notice, it will be updated here. The date at the top says when.