Your information

Privacy policy

Last updated: 31 October 2026

This policy covers the StreamLens public website, application and limited-access testing, including accounts, shared workspaces, Twitch integrations, Discord alerts, OBS overlays and recording delivery to YouTube. The service is operated by Volodymyr Andriiovych Khandiuk, Sole Proprietor (Ukraine) (“we”, “us”, or the operator).

Contact support@streamlens.io with privacy questions, complaints, requests to access or correct information, or deletion requests. This policy applies to the information we process even while public access has not launched.

1. Accounts and workspaces

We process the name and contact email associated with your account, verification status, linked login identities, workspace memberships, invitations, roles and assigned channels. For password accounts, we store a password hash rather than the password itself. Account security also uses session records, authenticator settings, recovery-code records and temporary verification or recovery tokens.

If you choose Twitch sign-in or link Twitch to an existing account, we receive the Twitch account identifier, available username, email and email-verification status needed to identify the account. Twitch handles its own sign-in. Linking a login identity and authorising a workspace integration are separate actions.

We use this information to authenticate you, deliver account and invitation emails, apply workspace permissions, support account recovery and keep an audit trail of relevant workspace actions. Inviting another person requires supplying their email address.

2. Twitch events and Discord alerts

For connected Twitch channels, we process broadcaster identifiers and names, authorisation credentials, live status and stream information such as title, category, source links and broadcast times. These support channel ownership checks, live alerts and recording discovery.

When chat or reward interactions are enabled, we process the event identifier, broadcaster and viewer identifiers, message text, applicable viewer roles, reward identifiers and event time to match the configured triggers. General chat messages are not retained as a chat history. Event identifiers and viewer identifiers can be stored for duplicate-event prevention and cooldowns; effect settings, execution snapshots, timestamps and playback outcomes form the interaction history.

Connecting Discord lets us inspect your Discord user identity, servers and relevant management permissions to verify access to the selected server and install the bot. Saved connection data includes the authorising user and server identifiers and the required authorisation credentials. We process available server/channel names and identifiers, destination settings, message templates and alert delivery history. The bot sends the configured stream announcements to the selected Discord channel.

3. OBS overlays and uploaded media

We store uploaded interaction images and audio, their technical metadata, effect and trigger settings, overlay area configuration and execution history. An authorised OBS browser source or overlay client receives the media and playback instructions needed for its assigned area and reports readiness and playback status.

Overlay access uses an area credential. Anyone receiving that credential may be able to access that area's overlay content until it is replaced or revoked. Media shown through OBS can become visible or audible to your stream audience. We do not control the subsequent broadcast or copies made by viewers.

4. Recordings, covers and YouTube

Recording workflows process completed Twitch recordings, source identifiers and metadata, temporary or retained video files, extracted frame previews, uploaded or rendered covers, metadata templates and saved designs. We also store the titles, descriptions, audience/content disclosures, destination choices, approvals, review holds, schedules and delivery results needed to operate and recover the workflow.

StreamLens uses YouTube API Services. Google handles authorisation when you connect a channel. We receive OAuth credentials, including a refresh token for background work, and the connected YouTube channel's identifier, title and available handle. We do not receive your Google password.

The requested permission is https://www.googleapis.com/auth/youtube.force-ssl. Google's consent screen grants broad YouTube management access. StreamLens uses it to identify the destination channel, upload recordings privately, apply selected covers, inspect video metadata and processing/publication status, and update metadata, content disclosures, privacy or publication schedules according to authorised actions and settings.

Uploads start private. Manual review is the default. Automatic publication requires explicit channel opt-in and installation eligibility. Your chosen files, covers and relevant metadata are sent to YouTube when this workflow is used; published content may be available to the audience permitted by the video's YouTube settings.

We use and transfer Google user data for these disclosed user-facing features in accordance with the Limited Use requirements of the Google API Services User Data Policy. We do not sell Google/YouTube data, use it for advertising or train general-purpose AI models with it. Human access is limited to people you authorise and the support, security or legal circumstances permitted by Google's policies.

5. Sharing and service providers

Workspace information is available to members according to their roles and channel assignments. Owners and managers can manage membership and provider connections; authorised editors can operate their assigned channels. Connect a provider only to a workspace whose authorised members you trust.

Enabled integrations send the requests and content needed for their functions to Twitch, Discord and Google/YouTube. Selected overlay content is delivered to the connected overlay client. Our infrastructure providers process information on our behalf for website/application hosting, network security, account email delivery and, where configured, private object storage and Sentry error/performance monitoring. Providers may process information in countries different from your own; contact us for information about the providers used for your service.

We do not sell personal information or use connected-account data for advertising. We may access or disclose relevant information to handle support you request, investigate abuse or security incidents, protect the service, or comply with applicable legal obligations. There are no third-party advertising placements in these public pages.

The connected platforms process information under their own policies: Twitch Privacy Notice, Discord Privacy Policy and Google Privacy Policy.

6. Security and storage

Account, workspace, configuration and workflow records are stored in the application database. Saved provider credentials and sensitive upload-session information are encrypted using the installation's encryption key. Media is held on the application server or in configured private S3-compatible object storage, with local files used for processing. Operational backups may contain copies of stored information.

Public traffic uses HTTPS. Application access is controlled by accounts, workspace permissions and channel assignments; overlays have their separate area credentials. This does not mean every database field, media file or backup is encrypted by StreamLens. No storage or transmission method guarantees absolute security.

7. Cookies, local storage and diagnostics

The application uses session cookies and temporary authorisation cookies to maintain sign-in and secure provider connections. Browser session storage can retain your selected workspace and pending invitation context. You can remove browser storage or cookies, but this may end a session or interrupt those flows.

The public website has no application sign-in form or application monitoring SDK. It is served through Cloudflare, which processes connection and request information, including IP addresses and network/security diagnostics, to deliver and protect it. These pages do not add advertising or analytics scripts.

Where application monitoring is enabled, Sentry receives sanitised error and performance information such as stack frames, operation names and request/navigation timings. The configured integration excludes request bodies, cookies, headers, user context and breadcrumbs from captured events; session replay is not enabled. Hosting/network providers and operational logs may separately process connection information for delivery, security and troubleshooting.

8. Retention and deletion controls

Account and workspace information is retained for service operation, security and operational history. Temporary authorisation and security records have expiry or cleanup rules. Account email queue items are removed after successful delivery or the configured expiry/attempt limit. Interaction event and cooldown records support duplicate prevention and rate controls; execution history supports troubleshooting.

Recording source files follow the workflow's cleanup rules after destination processing. Frame previews, covers, designs and delivery history can remain after the source video has been removed. Removing a recording deletes retained media through background cleanup, but source identity and audit/history references can remain. Failed storage cleanup retries and may delay removal.

You can manage login methods, security settings and active sessions in account settings. Leaving a workspace removes your membership; it does not erase the workspace's shared content or audit history. Account deletion revokes access and removes login/security records, but is not complete erasure of every shared, historical or audit record. Owners may need to resolve workspace ownership before deleting an account.

Workspace owners can request workspace deletion after resolving active transfers and external publication work. Memberships and invitations are revoked and media cleanup follows, but inaccessible historical records and audit identifiers remain. These controls do not delete videos held by YouTube or announcements already sent to Discord.

9. Withdrawing access and contacting us

Owners and managers can disconnect provider connections in workspace settings, subject to unfinished-operation checks. Disconnecting removes the saved connection credentials used by StreamLens and may clear destination mappings or disable related processing. It retains provider identity and operational history. Local disconnect does not necessarily remove provider-side permissions or installed bots; review authorised applications in the provider's account settings as well.

You can revoke Google authorisation at any time through Google Account permissions. This prevents further authorised API access, but does not itself erase previously stored StreamLens records. Disconnecting or revoking access does not delete uploaded YouTube videos; manage those directly in YouTube.

For access, correction, account closure or deletion of stored personal or Google/YouTube information, email support@streamlens.io with the relevant account email and workspace/channel identifier. Do not send passwords, tokens or recovery codes. We may need to verify your authority, particularly for shared workspaces. Tell us whether you mean a connection, an account or shared workspace information, and ask about retained history or backup copies where relevant. We handle requests subject to applicable privacy rights and legal obligations; a request to us does not remove information independently held by a connected platform.

10. Children and policy changes

StreamLens is intended for creators and their authorised teams and is not directed to children under 13. Contact us if you believe a child has provided personal information through the service. Connected platforms also have their own age requirements.

We update this policy when our information practices change and show the revision date above. Material new uses of connected-account data require the relevant disclosure and consent. You can contact us at support@streamlens.io about the current policy or your information.