Cookie Preferences
This notice explains how Bhaasa uses cookies and similar browser technologies to provide secure access, remember choices, support newsroom and subtitle workflows, and deliver hosted content.
Table of Contents
| # | Section | Description |
|---|---|---|
| 1 | Scope | Where this notice applies across Bhaasa websites, subdomains, dashboards, and players. |
| 2 | Cookies and similar technologies | What cookies, local storage, session storage, and browser caches do. |
| 3 | Categories we use | Strictly necessary, preference, functionality, and operational technologies. |
| 4 | Service providers and external pages | How sign-in, checkout, embeds, and connected services may use their own storage. |
| 5 | Your choices | How to clear, block, or manage browser storage and what happens when you do. |
| 6 | Subdomains and organization access | Why a secure session may be recognized across Bhaasa services and organization domains. |
| 7 | Updates and contact | How this notice changes and how to ask questions. |
1. Scope
This notice applies to Bhaasa websites and subdomains, personal and organization sign-in, dashboards, News Studio, subtitle tools, media and developer features, and Bhaasa-hosted players. A third-party website that embeds a Bhaasa player may also use its own cookies under its own policy.
For more information about the personal data associated with these technologies, read our Privacy Policy.
2. Cookies and similar technologies
Cookies are small values a website asks your browser to store and return. Bhaasa may also use local storage, session storage, and browser media caches. These technologies can maintain a secure session for up to 24 hours, remember a setting, retain a pseudonymous security device identifier, complete a redirect, retain temporary workflow state, or avoid repeatedly downloading the same media.
Session storage usually lasts until the relevant browser tab or session ends. Persistent storage remains until it expires or you clear it. Cached media remains on your device according to browser storage rules and available space.
3. Categories we use
Strictly necessary
Required to authenticate users, maintain sessions, refresh access securely, protect requests, complete sign-in and sign-out, route organization users to the correct workspace, remember a requested destination during authentication, and provide security or load-management functions. Blocking these technologies may prevent account and dashboard features from working.
Preferences
Used to remember choices such as light or dark theme, selected organization workspace, dashboard sections, connector views, and other interface preferences. These reduce repeated setup but are not used to build advertising profiles.
Workflow functionality
Used to preserve temporary redirect state, publishing or scheduling notices, selected workflow tabs, and similar information needed to complete an action. Browser caching may store media or thumbnails you have opened so projects can load more efficiently.
Operational measurement
Server requests and hosted-player delivery may create basic operational records such as time, address, device or browser information, status, and errors. These records help secure, troubleshoot, meter, and maintain the Service. They do not require Bhaasa to place a behavioral advertising cookie on your device.
Bhaasa does not use cookies to sell personal data or serve third-party behavioral advertising. If we introduce optional advertising or non-essential tracking cookies, we will update this notice and provide consent controls where required.
4. Service providers and external pages
Providers supporting authentication, payments, security, media delivery, support, or other requested features may set or read cookies when necessary to perform their service. A checkout, connected publishing service, or other external page may be governed by that provider’s own cookie and privacy notices.
When a Bhaasa player is embedded on another website, the host website may collect information or set its own cookies independently. Bhaasa does not control the host website’s practices.
5. Your choices
Browser settings generally let you view, delete, restrict, or block cookies, local storage, and cached site data. Controls vary by browser and device. You can also use private browsing or clear site data after a session.
- Clearing authentication storage will sign you out and may require you to verify access again.
- Clearing preference storage resets theme, workspace, and interface choices.
- Clearing cached media can make project previews download again.
- Blocking all storage may prevent organization routing, sign-in, checkout, editor, connector, or hosted-player features from functioning correctly.
Because the current browser storage is necessary or user-requested functionality, Bhaasa does not currently present a separate advertising-cookie consent switch. We will add appropriate controls before using optional cookies where consent is legally required.
6. Subdomains and organization access
Bhaasa provides services through its primary website, service-specific subdomains, and customer organization subdomains. Where supported, an essential authentication session may be recognized across these Bhaasa-controlled domains so users can move securely between the landing page, subtitles, organization sign-in, and dashboard without unnecessary repeated authentication.
Organization routing may use the requested hostname together with account and membership information. This does not make one organization’s private workspace available to another; access remains subject to membership, role, and permission checks.
7. Updates and contact
We may update this notice as browser practices, features, legal requirements, or our use of service providers changes. We will revise the date above and provide additional notice or controls when required.
Questions can be sent to hello@bhaasa.io. You can also review our Terms and Conditions and Privacy Policy.