Privacy and data handling

Use this page to decide what RTSP.RUN really handles in normal operation and what should be treated as a separate requirement before rollout.

This is not a zero-data or enterprise-governance claim page. It exists to make the operating model explicit before a team assumes promises the product does not make.

Decision points to align early

  • RTSP.RUN is meant for live playback and website embed.
  • It is not a recording, archival, or analytics system.
  • The current flow is suitable only for publicly reachable RTSP/RTSPS streams.
Back to RTSP player Embed a camera on your website

What you can safely treat as in-scope

  • Verify that a public RTSP stream plays in a browser.
  • Share the browser player or use generated embed code on a website.
  • Troubleshoot common RTSP URL and reachability issues.

What should trigger a different product decision

  • It is not a VMS, NVR, or CCTV management platform.
  • It is not built for recording, retention, or analytics.
  • It is not the right fit for closed internal camera networks in the default public flow.

What exists in the product flow during normal operation

  • Contact form submissions are written to local inquiry storage so product and business requests can be answered.
  • Basic product events such as stream start attempts, embed opens, and contact submits are written to local marketing metrics.
  • Active and recent stream metadata exists in application memory for playback, admin review, and troubleshooting.

What this page does not promise as a media archive or governance layer

  • RTSP.RUN is not presented as a recording or archive platform for your camera footage.
  • The public product flow is not sold as analytics, retention, or long-term surveillance storage.
  • If contractual data-processing, retention, or audit guarantees are mandatory, treat that as a separate fit question before rollout.