Terms and use boundaries

This page explains the practical rules around using RTSP.RUN as a self-service browser player and embed utility for publicly reachable RTSP/RTSPS streams.

The goal is not to introduce heavyweight legal text that claims capabilities or support levels the product does not have. The goal is to say clearly what kind of use the public website is designed for, what remains your responsibility, and when the product is not the right fit.

Read this before you rely on the public flow

  • You are responsible for the camera, stream, credentials, and public reachability you submit.
  • RTSP.RUN is meant for live playback and website embed, not for recording, retention, or surveillance management.
  • If your use case requires contractual assurances, enterprise support, or private CCTV handling, the default public flow is not enough.
Check fit and limits Support and what to expect

What remains your responsibility

  • Making sure the camera or stream may be exposed publicly at all.
  • Verifying camera credentials, network reachability, and the correctness of the RTSP/RTSPS URL.
  • Deciding whether the public-RTSP model is acceptable for your security and business context.

What RTSP.RUN does not promise

  • No SLA, enterprise support, or managed onboarding in the default public flow.
  • No recording, analytics, compliance framework, or internal CCTV governance layer.
  • No claim that every camera, every network, or every rollout can be made to fit this model.