Privacy Policy

This policy applies to the Cue Monitor iPad and iPhone app, to the Cue Monitor server (the macOS app and the Docker package), and to this product page on riegergeri.com. The developer is Rieger Gergő, a private individual in Hungary; there is no company behind it. Contact: gergo@riegergeri.com.

Cue Monitor is a show tool, not an online service. The app communicates only with a Cue Monitor server running on your own local network. There is no user account, no login, no cloud sync and no remote database.

• No personal data is collected — no name, no email, no device identifier, no location.
• No analytics or ad tracking, in either the app or the server.
• The server sends nothing to the internet. Its network traffic stays on the local network: the HTTP/SSE connection that feeds the displays, the Bonjour advertisement (_pyromonitor._tcp), and — only if you turn it on — OSC messages to your lighting console, cue light or Companion.
• The microphone is for timecode only. The server reads SMPTE (LTC) timecode out of the audio signal. No recording is made, the audio is not stored, and it goes nowhere.

Everything stays on your own machine and your own device. The developer has no access to any of it.

• On the server machine — the timecode XML exported from the console, the notes attached to cues, the timecode offset overrides, the button-grid layout, the material-usage counters, and the fire and operations logs. These are plain files in the server's data folder (in Application Support for the macOS app, or the ./data volume for Docker).
• On the iPad — the display settings (flash and haptics on or off, timeline zoom) and the addresses of the servers you used last, so it reconnects on its own next time.

All of it can be cleared: the logs and counters reset from the interface, the files can be deleted by hand, and removing the app deletes the settings held on the device.

The app is free. Optional subscriptions (Basic, Pro, Advanced) are sold through the App Store and only raise how many displays your own server serves at once. Apple handles the transaction — the developer never sees your payment details, name or address, and receives only anonymous sales figures from Apple that cannot be traced to an individual buyer.

When the app has an active subscription, the server verifies the App Store receipt locally to unlock the higher device limit. That check confirms the receipt is genuine and current; it is not used to identify you, and it is the reason the limit is never taken from the app's word alone.

This page is served as part of a small static site. It sets no cookies of its own, so there is no consent banner. Like any web server, the host may keep technical access logs (IP address, timestamp, the file requested) for operation and security; the developer does not analyse those logs, tie them to individuals, or hand them to anyone else.

Because the app and the server process no personal data, there is no GDPR data processing attached to them. For the host's access logs, the legal basis is the developer's legitimate interest [GDPR Art. 6(1)(f)] in running the site securely. Those logs are rotated and deleted by the hosting provider on its own schedule; the developer keeps no further copy.

This is a professional pyrotechnics tool with no social features, no user content and no data collection of any kind. There is nothing here specific to children, and it is not directed at them.

If the app ever gains a feature that changes any of the above — it will not gain analytics — this page will be updated and the date at the top will change. Because nothing is collected, there is no historical data a later policy could apply to retroactively.

Questions about this policy, or about the app: gergo@riegergeri.com. If you email, your message and address are used only to reply and go to no one else.

Rieger Gergő, Hungary.