01. Introduction
This Privacy Policy describes how TechRise ("we," "our," or "us," operated by Etechrise Infras LLP) handles information in connection with the TechRise Studio desktop software application ("TechRise Studio" or the "Application").
We respect your privacy and are committed to protecting it. TechRise Studio is designed as a client-side, local desktop application for Windows. We do not operate cloud servers to store your personal broadcasting feeds, video recordings, streaming keys, or third-party account credentials.
By downloading, installing, or using TechRise Studio, you agree to the collection and use of information in accordance with this Privacy Policy.
02. About TechRise Studio
TechRise Studio is an all-in-one desktop live production and broadcasting suite. It provides camera switching, preview/program workspace controls, virtual background synthesis, voice-command automation, scene management, and direct integration with live video platforms including YouTube and Facebook.
TechRise Studio runs directly on your computer. Video rendering, audio mixing, encoding, and streaming operations execute locally on your personal device hardware.
03. Information We Collect
Because TechRise Studio operates locally, the information processed by the application is kept on your computer:
- Local Configuration Data: User interface preferences, scene collections, audio volume presets, video resolution settings, and hotkey configurations saved in your local user profile.
- Audio/Video Hardware Feeds: Video from connected USB/HDMI cameras and audio from connected microphones. These media streams are processed entirely in memory on your computer for display, recording, and broadcasting. They are never transmitted to TechRise servers.
- Voice Command Audio: When voice-controlled operation is enabled, microphone audio is analyzed locally on your device by the voice control subsystem to recognize predefined commands (e.g., scene transitions). Voice data is not stored or uploaded to any external server.
04. Information Collected When Connecting Accounts
When you choose to connect third-party broadcasting accounts (such as YouTube or Facebook) to enable one-click live streaming, TechRise Studio utilizes standard OAuth 2.0 authorization flows.
During this process, TechRise Studio receives authorization tokens directly from the third-party platform via a local loopback server (`127.0.0.1`) running temporarily on your machine during the sign-in step. TechRise Studio never asks for, handles, or stores your Google or Facebook account passwords.
05. Google / YouTube Integration
TechRise Studio allows users to connect their YouTube account to manage and start live broadcasts directly from the desktop interface.
OAuth Authorization & Scopes
When connecting YouTube, your default web browser opens Google's official authorization page. TechRise Studio requests only the specific OAuth scopes required for live streaming functionality:
- https://www.googleapis.com/auth/youtube — Used to create live broadcasts, retrieve live stream ingestion URLs, sync broadcast status, and display the live chat popout dock.
- openid — Used to verify the authenticated user session.
- email — Used to identify the connected Google user account in the application interface.
How YouTube Data is Handled
- TechRise Studio retrieves your YouTube channel name, custom handle, and channel thumbnail to display the connected channel identity in the application workspace.
- The retrieved OAuth refresh token is encrypted using Windows DPAPI and stored locally in your Windows configuration.
- No YouTube data, tokens, or live stream content are shared with or stored on TechRise servers.
- Google and YouTube independently process your broadcast data according to the Google Privacy Policy and the YouTube Terms of Service.
06. Facebook / Meta Integration
TechRise Studio provides integration with Facebook Live to broadcast live video feeds to Facebook Pages managed by the user.
Meta OAuth Permissions Requested
When connecting Facebook, Meta's authorization dialog requests the following specific permissions:
- public_profile — Used to identify the authenticated Facebook account name.
- pages_show_list — Used to retrieve the list of Facebook Pages that you manage so you can select your streaming destination.
- pages_read_engagement — Used to verify page administrative permissions for broadcasting.
- pages_manage_posts — Used to publish and manage the live video stream post on the selected Facebook Page.
- publish_video — Used to create live video objects and stream video content to the target Page.
How Facebook Data is Handled
- TechRise Studio queries the Meta Graph API to discover your managed Pages, Page names, and Page Access Tokens.
- Page Access Tokens and long-lived User Access Tokens are encrypted using Windows DPAPI and stored exclusively in your local Windows user configuration.
- No Facebook account data, passwords, or video feeds are sent to TechRise servers.
- Meta independently processes information in accordance with the Meta Privacy Policy.
07. How We Use Information
Any information accessed by TechRise Studio is used strictly to deliver the functional features of the application on your computer:
- To switch camera inputs and composite scenes according to your commands.
- To initiate, configure, and maintain live video streams to your connected platforms.
- To maintain your connected account session across application restarts without requiring repeated logins.
- To render the live chat dock and stream status diagnostics on your screen.
08. Authentication and Access Tokens
OAuth tokens (including Google OAuth refresh tokens, Meta user access tokens, and Facebook Page tokens) represent authorization grants from third-party platforms.
TechRise Studio handles these tokens exclusively inside the desktop application memory and through the local secure credential manager. Short-lived access tokens are refreshed automatically in the background directly against Google and Meta token endpoints.
09. Local Storage and Credential Security
We employ industry-standard, hardware-backed local security mechanisms:
- Windows DPAPI (Data Protection API): Sensitive tokens are encrypted using Windows CryptProtectData tied cryptographically to your current Windows user profile with the
CRYPTPROTECT_UI_FORBIDDENsecurity flag. - Isolation: Encrypted credentials are saved in the local Windows Registry configuration under
TechRiseStudio\StreamCredentials. They cannot be decrypted by unauthorized user profiles on the same device. - Zero Cloud Transmission: Your OAuth tokens, stream keys, and personal credentials are never uploaded to, transmitted across, or stored upon TechRise servers.
10. Third-Party Services
TechRise Studio interacts with external APIs when you choose to connect streaming services:
- Google LLC / YouTube: Google Privacy Policy
- Meta Platforms, Inc. / Facebook: Meta Privacy Policy
We encourage you to review the privacy policies and terms of service of any third-party service provider with which you connect the Application.
11. Data Retention
Because TechRise does not maintain cloud databases of user streams or credentials, we do not retain your personal broadcasting data or OAuth tokens on our servers.
Locally encrypted tokens remain on your computer until you disconnect your accounts, reset your application settings, or uninstall TechRise Studio.
12. Data Deletion and Account Disconnection
You maintain complete control over your credentials and account connections:
A. Disconnecting Inside TechRise Studio
Open the Stream Destinations dialog in TechRise Studio and click Disconnect next to YouTube or Facebook. The application immediately invokes disconnectAccount(), which permanently wipes all DPAPI-encrypted tokens (refresh tokens, user tokens, page tokens) from your local Windows storage and clears memory caches.
B. Revoking Google / YouTube Permissions
You can revoke TechRise Studio's access directly at any time by visiting Google Account Third-party Apps & Services.
C. Revoking Facebook / Meta Permissions
You can revoke TechRise Studio's access directly by visiting Facebook Settings > Apps and Websites.
D. Third-Party Platform Data
Video broadcasts and chats hosted on YouTube or Facebook are managed by Google and Meta respectively. TechRise cannot delete or modify content stored on third-party servers; you can manage or delete such content directly through YouTube Studio or Facebook Creator Studio.
13. User Rights
Depending on your location, you may have statutory rights regarding your personal data (such as rights of access, rectification, objection, or deletion under applicable data protection laws). Because we do not store your data on remote servers, you can exercise these rights directly on your own device by modifying or removing local configuration files and disconnecting third-party accounts.
14. Children's Privacy
TechRise Studio is intended for creators, educators, institutions, and broadcasting professionals. The Application is not directed toward children under the age of 13. We do not knowingly collect personal information from children.
15. Changes to This Privacy Policy
We may update this Privacy Policy periodically to reflect improvements in TechRise Studio or updates to third-party platform API requirements. Any updates will be posted on this page with an updated "Last Updated" revision date.
16. Contact Us
If you have questions, inquiries, or data privacy requests concerning TechRise Studio or this Privacy Policy, please contact our support team:
Etechrise Infras LLP (TechRise)
Official Email: info@etechriseinfras.com
WhatsApp / Phone: +91 8696960596
Address: Vaishali Nagar, Jaipur, Rajasthan, India
Website: https://techrise.co.in/