StreamLens

Using the service

Terms of service

Last updated: 31 October 2026

These terms cover the StreamLens public website and application, including limited-access testing. The operator is Volodymyr Andriiovych Khandiuk, Sole Proprietor (Ukraine) (“we”, “us”). By using the service, you agree to these terms. Read the Privacy policy for how information is processed. Contact support@streamlens.io with questions or complaints.

1. Availability and early access

Public access to StreamLens has not launched. Application access may be limited to invited or otherwise authorised participants. An informational website or an invitation does not promise general availability, any launch date or access to every feature.

The service supports shared workspaces, Twitch live announcements to Discord, Twitch chat/reward interactions with OBS overlays, and preparation and delivery of completed Twitch recordings to YouTube. Availability depends on the functions enabled for your workspace, installation settings and connected providers. Features and limits can change during testing.

2. Accounts and workspace authority

You must be legally able to enter this agreement and meet the eligibility and age rules of the providers you use. If you act for a creator, channel owner or organisation, you must have their authority. Supply accurate account information, secure your login and recovery methods, and report suspected unauthorised access promptly.

Workspace owners and managers control membership, roles, channel access and connections. Editors and viewers have the permissions assigned to them. You are responsible for the invitations and permissions you grant and for your own use of those permissions. Do not connect an account, server or channel you are not entitled to manage, or use another workspace's media or credentials without permission.

3. Connected platforms and authorisation

Connecting a service authorises StreamLens to perform the disclosed operations you request and those covered by settings you explicitly enable. This may include background events, announcements, media transfers and eligible automatic publication. Workspace members can act within their assigned permissions; only connect destinations to a workspace whose authorised members you trust.

StreamLens uses YouTube API Services. By using its YouTube features, you also agree to be bound by the YouTube Terms of Service. Twitch and Discord integrations are also subject to the Twitch Terms of Service and Discord Terms of Service, as applicable. Providers control their own accounts, permissions, policies and availability.

You can withdraw Google access through Google Account permissions and manage other provider permissions in their own account settings. Local StreamLens disconnect controls, provider-side revocation and stored-data deletion are different actions; see the privacy policy for their effects.

4. Alerts, interactions and OBS overlays

Review Discord destinations and message templates before enabling live announcements. Announcements appear in the selected server/channel and can be visible to its members or other people with access. Provider outages or ambiguous delivery results can delay or duplicate a message; delivery is not guaranteed.

For Twitch chat/reward interactions, you choose the triggers, eligible roles, cooldowns, uploaded media, effect layout and playback settings. You are responsible for the material you display or play and its suitability for your audience. OBS overlays and local previews are tools you control; check your broadcast before making it available to viewers.

Protect overlay credentials and replace them if disclosed. Sharing a credential can let another client receive that area's media or playback information. Queued effects can expire, be skipped, or fail when a source disconnects. Playback acknowledgements are client reports and do not guarantee that a viewer saw an effect.

StreamLens observes supported Twitch rewards and triggers effects; it does not create or edit those rewards or fulfil/refund redemptions. Resolve reward handling and viewer disputes through the appropriate Twitch controls.

5. Recordings and publication

You authorise the source recording transfer and processing needed for enabled workflows, including temporary storage, technical validation, frame extraction, cover rendering and delivery to your chosen YouTube destination. You are responsible for the source recording permissions and for reviewing generated or selected images and metadata.

YouTube uploads begin private and manual review is the default. Review titles, descriptions, covers, audience settings and synthetic-content/paid-promotion disclosures before approving a release. Automatic publication requires explicit channel opt-in and installation eligibility. A private upload still sends content to YouTube and is subject to Google's processing and rules.

Publication depends on provider processing, quota, channel eligibility, API-project approval and your settings. Do not rely on an exact publication time or assume an interrupted request had no effect. Accepted uploads, ambiguous provider actions and scheduled publication may require resolution before disconnecting or deleting related records.

Removing a StreamLens recording, closing an account or deleting a workspace does not delete an uploaded YouTube video. Manage existing videos directly on YouTube when needed. Existing provider schedules or operations may continue until you resolve them with the relevant provider or available application controls.

6. Content rights and permitted use

You retain your rights in the content you provide. You grant us the limited permission to host, copy, process, transmit and display it as needed to operate the service and carry out your authorised workflows. This includes sending content to chosen providers and overlay clients and retaining the operational copies described in the privacy policy.

You must have the copyright, music, image, privacy and other permissions needed for the material you upload, transfer, announce or broadcast. Do not use the service for unlawful activity, infringement, harassment, spam, fraud, credential theft, unauthorised access, or attempts to bypass provider rules, security controls or quotas. Do not disrupt other users' workspaces or the service.

7. Storage, stopping use and suspension

StreamLens is a processing and delivery service, not a guaranteed backup or permanent recording archive. Source media can be cleaned up after processing; quotas, retention settings and cleanup affect what remains available. Keep independent copies of content you need.

You may stop using the service, revoke provider permissions, leave a workspace or use the available account/workspace deletion controls. Ownership and unfinished external operations may need to be resolved first. Shared workspace records, historical references and audit information are not all erased by those controls. Request personal-data deletion or clarification through support@streamlens.io as described in the privacy policy.

We may restrict or suspend access to address security risks, abuse, legal obligations or breaches of these terms. We may update, limit or discontinue functions. Restrictions or service changes do not remove copies already held by connected providers or broadcast audiences.

8. Responsibility and mandatory rights

To the extent permitted by applicable law, StreamLens is provided “as is” and “as available”, without guarantees of uninterrupted operation, successful alerts/uploads/effects, publication timing or preservation of content. Third-party services and your broadcasting setup are outside our control.

To the extent permitted by law, we are not liable for indirect or consequential loss caused by interruptions, failed workflows or third-party platform actions. Nothing in these terms excludes liability, consumer protections, privacy rights or remedies that cannot lawfully be excluded.

Raise problems or disputes with support@streamlens.io, identifying the relevant account/workspace and issue without including credentials.

9. Changes to these terms

We may update these terms as the service changes. The current version and revision date appear here. Where required by law or the nature of a change, we will give notice or request agreement before it applies.