1. Account, billing and support information
- Account name, email, account ID, login provider identifiers, verification status, password hashes and salts for password accounts, login/session records, and temporary verification or recovery artifacts. These support registration, authentication, security and recovery.
- Saved profile details such as country, time zone, language/locale, reminder settings and onboarding preferences. These configure your account and service messages.
- Billing name, address, email, contact number, country and applicable GST details you provide; plan, payment/order references, subscription status, invoices and usage records. These support checkout, payment reconciliation, tax/accounting and quota enforcement. Payment providers handle payment credentials through their own checkout services.
- Support tickets, messages, attachments you submit and relevant account or diagnostic context. These help us answer requests and investigate problems. Do not include passwords or stream keys in support messages.
2. Streaming data and media
- We process live audio/video you send, source and destination settings, ingest addresses and stream keys to receive, compose or transcode where enabled, and distribute your stream to the destinations you select.
- We store destination names and credentials, platform targets, event titles/descriptions, scheduled times, audience/visibility choices, remote event or video identifiers, publication status, errors, session times/duration and quota or worker usage history to operate and troubleshoot those features.
- Browser-source features use the camera, microphone, screen or computer audio you choose through browser permissions. Captured media is transmitted when you connect that source. Screen sharing may reveal personal information visible or audible in the selected source; check it before sharing and stop capture when finished.
- Uploaded background/fallback images and enabled recording features involve storing media and related metadata. Recording availability and expiry depend on the feature and account configuration. A destination platform may independently retain your live video or replay.
You choose the content, audience and destination. You must obtain the necessary rights and notices for people whose information you broadcast. This does not remove our own duties when processing information through the service.
3. Google sign-in and YouTube are separate
Google sign-in provides your Google account identifier, name, email and email-verification status to create or authenticate your StreamToWorld account. Signing in with Google does not by itself connect a YouTube channel or authorize publication.
If you separately connect YouTube, StreamToWorld uses YouTube API Services. We obtain and store channel ID/name, authorization access and refresh tokens and expiry information, and the live broadcast/stream identifiers, settings and status needed for the features you request. We use them to identify the connected channel, prepare or manage live events, obtain ingest details, publish your stream and check its status. Your selected event details and live media are sent to YouTube to perform those actions.
YouTube API data is used for these user-facing features, not sold or used for advertising. Our use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements where applicable. Human access to that data is limited to your affirmative permission for specific data, necessary security investigation, legal requirements, or permitted aggregated internal operations.
Read the Google Privacy Policy, YouTube Terms of Service and YouTube API Services Developer Policies. You can revoke access through Google account permissions. See deletion instructions below for data held by us.
4. Facebook / Meta
When you connect Facebook for live publishing, we obtain and store your profile ID/name, access authorization and expiry information and, where Page permissions are granted and supported, the Page IDs/names and Page access tokens. We also store live-video/event identifiers, settings, ingest details and status for the publishing actions you request.
We use this information to show eligible connected targets and prepare, publish, update or end supported Facebook live events. Facebook receives the event information and media needed for your selected publication. Available targets depend on Meta permissions and eligibility; connection alone does not make a video public. If Facebook sign-in is offered separately, it supplies identity details, including email where provided, for authentication.
Read the Meta Privacy Policy and Facebook Terms. Review or remove access in Facebook Settings under Apps and websites or Business integrations, as applicable. To request deletion of Facebook data held by StreamToWorld, follow section 10.
5. LinkedIn
For a connected LinkedIn Profile or Company Page, we obtain and store the authorized member or organization identifier, name, owner reference, granted authorization token and expiry, available organization targets and relevant live eligibility. We store the live event/video identifiers, event settings, ingest information and publication status needed to operate the connection.
We use these details to display the targets you can manage, check eligibility and prepare or manage the live publication you request. LinkedIn receives the event details and media needed for that action. Connecting a Profile or Page is distinct from authorizing a particular event or publication.
Read the LinkedIn Privacy Policy, User Agreement and Event Terms. Revoke access through LinkedIn Settings & Privacy → Data privacy → Other applications → Permitted services; LinkedIn's instructions explain removal. Request deletion of data held by us under section 10.
6. Twitch and custom RTMP destinations
For Twitch connection, we retrieve account ID, display name/email where provided and the stream key through authorized API access. We store account connection details and the stream key/ingest address to create and operate your Twitch destination. OAuth authorization is used during connection; the current Twitch connection record does not persist the OAuth access token.
For custom RTMP/RTMPS destinations, including manually configured platforms, we store the label, server address, stream key and settings you enter, and send your media to that address when you start the output. The recipient's handling of the stream is governed by its own policies.
Read the Twitch Privacy Notice and Terms of Service. Manage Twitch access in Twitch Connections. Because a saved stream key can remain usable after OAuth access is removed, stop the destination and rotate the key at Twitch or your custom provider when you want to invalidate it.
7. Logs, cookies, analytics and email
Service and infrastructure logs can include request times, network/IP information, browser/user-agent information, account or session references, security events, errors and streaming performance measurements. Browser-source diagnostics can store technical capture/connection states, track settings, timing, bitrate and quality statistics with pseudonymous identifiers. These diagnostics are distinct from a media recording; information you submit to support may include media.
We use browser session cookies for sign-in and browser storage for preferences and campaign attribution. Attribution can include UTM campaign parameters and advertising click identifiers. Where configured, Google Analytics or Google Tag Manager receives website page-view and interaction events and associated browser/network information, and may use cookies. These services are not the same as YouTube account access. Browser settings can restrict cookies or storage, but blocking essential session cookies can prevent sign-in.
We send account, security, billing and stream-related service messages. Streaming tips and marketing emails have an unsubscribe link; you can also contact us to stop them. Marketing delivery records may include delivery, open and link-click events, including tracking pixels where enabled. Unsubscribing from marketing does not stop necessary service messages.
8. Sharing, access and international processing
Information is shared with the destination platforms you choose, and with hosting, media-processing/storage, email, support, analytics and payment providers as needed for their respective functions. Authorized staff and service providers may access relevant information for service operations, security, support and legal obligations. Platform-specific restrictions, including the Google API restrictions above, also apply.
Your chosen audience and destination platform may receive, store or redistribute your content under that platform's settings and policies. We may disclose information when lawfully required by a court or public authority, or as necessary and lawful to address fraud, abuse or threats to rights or safety. A business transfer involving personal information must remain subject to applicable law and provider restrictions, including any required consent.
We do not sell connected-platform API data. Service providers and destinations may process information in countries outside India. This notice does not promise exclusive storage in India; applicable legal and platform restrictions on transfers still apply.
9. Retention and security
Retention depends on the record's purpose, account and connection status, configured feature expiry, applicable platform rules, billing/tax requirements, security investigation, dispute resolution and legal preservation requirements. Temporary authentication artifacts expire under the service configuration. Recordings have feature-specific expiry; session, usage, billing, support and diagnostic records can follow different retention processes.
Disconnecting, stopping a stream or logging out does not itself erase all historical records, saved outputs, diagnostics or backup copies. Deletion requests require review of those separate records. Provider-specific deletion requirements apply to API data and must not be displaced by general operational retention. Where information must lawfully be retained, its further use should be restricted to the reason for retention.
Access controls and authentication help protect the service. No internet service can guarantee absolute security. Keep credentials and stream keys confidential; report suspected exposure promptly using the contact below. Do not treat StreamToWorld or a destination platform as your only archive or backup.
10. Access, disconnection and deletion requests
- You can edit supported profile and billing fields in the console. For access, correction, export, deletion, withdrawal of consent or a privacy complaint, email admin@streamtoworld.com from your registered address, or identify the account and platform concerned if you cannot access it. Use a subject such as "Privacy request" or "Platform data deletion". Do not send your password, token or stream key.
- Specify whether you want to disconnect a platform, delete that platform's data held by us, or request closure/deletion of your StreamToWorld account. These are different requests. We may need proportionate identity/authority verification and clarification of the requested scope before acting.
- Where available, Disconnect removes the saved platform connection in StreamToWorld. It is not a complete provider revocation or account-deletion tool: related destinations, event records and history can remain. Stop active outputs and revoke access in the provider's settings as well. Request deletion of data held by us separately through the email above.
- Deletion requests are handled through support review; this notice does not promise an automated account-deletion feature or a fixed completion time. Applicable legal and platform deadlines still apply. Ask for confirmation of what was deleted, what must be retained and why, and any remaining action you need to take.
- Revoking platform access or deleting data held by us does not delete your Google, YouTube, Facebook, LinkedIn or Twitch account, or videos, replays or posts already held by a destination. Manage those directly with that provider; a separate supported event-deletion action, if offered, requires your specific instruction.
Withdrawing access can prevent the connected feature from working. You retain any rights and complaint routes available under applicable law; using our support process does not waive them.
11. Contact and notice changes
For privacy, deletion and content grievances, contact Amitkumar Narote, Director, at admin@streamtoworld.com (primary) or info@24framesdigital.com (alternate), addressed to TFD Communications Private Limited / 24 Frames Digital, 5th floor, 511-C, Shatrunjay Darshan, Motisha Cross Lane, Byculla, Mumbai Suburban - 400027. Maharashtra, India.
We will identify the version and effective date when a revised notice is published and provide notice or obtain fresh consent where required for a changed purpose or use. Publication alone does not authorize a new use of your data or replace any legally required consent. Please also read our Terms of Use.
