Scope and operator
This policy covers the HTNM StreamHub website and application operated by HTNM StreamHub. HTNM StreamHub is the product name. The operator’s registered address, country/state and verified privacy contact must be confirmed before commercial launch. External platforms have their own policies.
Information the service handles
- Account: name, email, profile image and provider identifiers received through connected sign-in, such as Google.
- Configuration: event names, input identifiers, stream keys, destination URLs, credentials and settings.
- Content: uploaded logos, graphics and placement settings; audio and video sent to streaming infrastructure, including recordings where enabled.
- Payments: order and payment references, amounts, currency, verification results and credit records.
- Operations: requests, errors and connection metadata processed by the application and infrastructure providers.
Why information is used
Information supports authentication, event separation, input provisioning, destination routing, graphics storage, payment verification and troubleshooting. Records may also be needed to investigate abuse, resolve disputes and meet applicable obligations. Connecting a sign-in account does not automatically grant access to every streaming platform.
Infrastructure and payments
Cloudflare provides application, database and streaming infrastructure. Razorpay handles supported payment checkout and verification. Your sign-in provider handles authentication. Enabled destinations receive your broadcast under their own terms. HTNM StreamHub’s top-up flow stores payment references, not card numbers or security codes.
Review Cloudflare’s privacy policy, Razorpay’s privacy policy and Google’s privacy policy. Processing may occur outside your country; no specific data-residency commitment is made here.
Credentials and security
The application uses authenticated access, signed sessions and encryption for stored destination credentials. No system is risk-free. Keep your sign-in account secure, rotate exposed keys and never share private connection details with viewers or include them in support screenshots.
Retention and deletion
Configuration and payment records persist unless removed through supported processes. Recordings depend on input settings and provider retention configuration. Stream deletion does not promise immediate removal of every recording, log, payment record or backup. An account-wide deletion schedule and specific retention periods must be finalised by the operator before commercial launch.
Your choices and privacy requests
You can edit supported settings, remove destinations and delete streams. Connected sign-in access can be revoked through your provider. Access, correction, deletion and other rights depend on applicable law and may require identity verification. A verified privacy contact and request process remain pending; this draft does not promise an unimplemented export or response deadline.
Eligibility and changes
The service is intended for people authorised to operate broadcasting accounts, not as a service directed at children. Eligibility rules must be confirmed for the intended market. Material data-handling changes should be disclosed in an updated policy before introduction. Mandatory rights are not waived by this document.