Privacy Policy

Who operates Nexus

Nexus is an internal operations application of ELSAQ EDUCATIONAL SERVICES PVT. LTD. It is intended for authorized staff and approved collaborators, rather than public registration or student use. This notice covers Nexus, including its Google and YouTube integrations; it does not replace separate notices for our learning products.

The company address and privacy contact appear below. This is a proposed notice for review. It is not evidence that the application has passed a Google compliance review.

Information the application handles

Sign-in and access: Google account name, email address and profile image, session information, assigned roles and channel or department access. Google handles the Google password; Nexus uses authorization credentials and session cookies.

Internal work: records entered or imported by authorized staff, which can include employee and faculty information, attendance, payroll and expenses, customer or lead contact information, transactions, learning content, uploaded files and activity records. Available records depend on the enabled module and the user’s permissions.

YouTube API Services: public channel and video identifiers, titles, thumbnails, publication dates, live-stream information and available public statistics. For company-owned channels connected with appropriate authorization, Nexus can read analytics such as views and watch time, and estimated revenue where monetary reporting permission is granted. Competitor public statistics do not provide competitors’ private Analytics or revenue.

Connections: channel identifiers, granted scopes and access/refresh credentials required to maintain an authorized integration. Provider requests and operational logs can include timestamps, errors and request metadata.

Why information is used

Nexus uses information to authenticate staff, enforce access permissions, support company administration, reconcile operational records, prepare reports and assist content planning. YouTube information supports channel reporting, publishing-activity review and the Competitor Radar watchlist.

Only connect accounts and supply records you are authorized to use. Additional integration permissions should be requested when the corresponding feature is connected.

Access and service providers

Authorized company personnel can access information according to their assigned responsibilities. Hosting, database, file-storage and connected-service providers process the information needed to operate their respective services. Google and YouTube receive requests necessary for sign-in and connected channel features. vidIQ may receive public channel identifiers and requested date ranges when its historical-statistics integration is enabled.

AI-assisted features can send the task text and selected context to the configured AI provider; existing YouTube Brain features include Anthropic-based title suggestions and public-notice classification. Do not put credentials or unrelated private records into prompts. The deployment’s provider inventory and permitted AI input categories must be confirmed before this notice is adopted.

Proposed data-use commitments: do not sell Google user data, use it for advertising targeting, or use it to train general-purpose AI models. Google-derived information must be used only for disclosed, authorized functionality. These commitments require implementation review before adoption.

Cookies, local storage and external content

Nexus uses authentication/session cookies and browser storage for application state and cached responses. Its installable web-app features may cache application assets. Shared devices should not be used for sensitive company work; sign out and clear the site’s stored data when handing over a device.

YouTube thumbnails, external links and any enabled embeds can involve requests to third-party services. Those services apply their own privacy notices.

Retention and deletion

The local Competitor Radar currently excludes expired observations from usable results and includes cleanup of public statistical observations older than 30 days unless the approved extended-retention configuration is present. Video metadata has a separate 30-day refresh/removal rule. The cleanup schedule must be active and verified in the deployed service; manual local testing is not proof of scheduled production deletion.

Authorized channel analytics, credentials, other company records, browser caches and backups have separate lifecycles. Their retention periods and complete deletion procedures are not yet verified by this draft. Do not treat the Radar’s 30-day rule as an application-wide guarantee. These details must be resolved before adoption.

To request access, correction or deletion, contact the company privacy contact below from the relevant account, identify the affected Nexus module/account or channel, and describe the request. Do not send passwords or API keys. The company must verify authority and identify the affected stores before processing a request.

Your Google account controls

You can revoke Nexus’s Google access through Google Account permissions. Revocation stops subsequent authorized access but does not itself prove that previously stored copies have been removed. Contact the company to request deletion of stored data as well. Publicly available competitor information is separate from your authorized account data.

Manage Google Account permissions ↗

Google Privacy Policy ↗

Security, updates and contact

Nexus restricts operational features through sign-in and module permissions. Server credentials must remain outside browser code and shared documents. Access, retention, incident handling and provider configurations require ongoing review; this draft makes no security certification or guarantee.

Material changes to data use should be reflected in this notice and communicated before new uses begin. The review date and version identify this draft, not an effective date. For privacy questions, complaints or deletion requests, contact the company using the details below.