Operational rules for trial activation, device use, streaming behavior, payment, abuse prevention and support handling.
1. Purpose of the rules
These Service Rules explain the day-to-day operational requirements for using Ad&Vi TV in a fair, secure and technically stable manner.
Where these Rules and the User Agreement overlap, both documents apply together; the stricter operational requirement may be enforced to protect the service and rights holders.
2. Free trial rules
The 24-hour trial is available only to qualifying new customers and may include only the channels and features designated by the service at the time of activation.
Trial activation may be refused if the service detects duplicate accounts, payment-method recycling, suspicious device reuse, proxy abuse or other signals of promotion abuse.
3. Devices and concurrent use
The user may sign in only on supported client applications and compatible devices. The service may limit the number of active devices and simultaneous streams according to the selected plan and risk controls.
The service may require logout, re-authorization or device cleanup when the maximum allowed device count is reached.
4. Streaming quality and technical conditions
Playback quality depends on network speed, Wi-Fi stability, device capabilities, DRM support, app version, CDN routing and source availability. The service may dynamically reduce bitrate or disable a stream to preserve stability.
Use of outdated, rooted, modified or unsupported devices may reduce functionality or block playback.
5. Billing conduct and payment responsibility
The user must maintain a valid payment method for paid renewal flows where automatic billing has been enabled. Failed charges may lead to downgrade, suspension or cancellation of paid access.
Chargebacks, payment disputes raised in bad faith or intentional payment evasion may result in account restrictions and the denial of future promotions.
6. Acceptable use restrictions
The user must not copy, decode, capture, relay, mirror, embed, restream, publish or monetize the service or any part of the content without prior written authorization.
The user must not overload APIs, automate login attempts, share credentials publicly or attempt to reverse engineer security or entitlement controls.
7. Rights-holder and territorial compliance
Some channels or features may be restricted by territory, platform or device because of licensing or compliance obligations. The user must not attempt to evade territorial or contractual restrictions using technical workarounds.
Upon rights-holder request or legal necessity, the service may remove, replace or block access to specific streams immediately.
8. Support, notices and complaints
Users should submit technical issues, billing disputes and access problems through the designated support flow with sufficient detail for investigation.
The service may set response windows, incident priorities and evidence requirements for refunds, technical claims or abuse reports.
9. Enforcement measures
The service may warn, rate-limit, suspend or terminate an account, device or IP range when necessary to protect the platform, other users, payment flows or rights-holder obligations.
Enforcement may occur automatically or manually and does not limit any other legal or contractual remedy available to the service.
These texts are original product drafts for the prototype and should be reviewed and localized by qualified counsel before public launch.
The structure is service-ready, but the wording is newly written for this project and should not be treated as legal advice.
