How Nexoverse uses cookies and related storage.

1. Scope and Definitions

This Cookie Policy explains cookies and similar technologies that may be used when you visit nexoverse.in or use Nexoverse features. A cookie is a small value stored by a website or service in your browser. Similar technologies include local storage, session storage and provider-managed browser identifiers.

Cookies and browser storage are not the same. Local storage generally remains in the browser until cleared; session storage is generally limited to a browser tab or session; cookies are sent with requests to the domain that set them according to their attributes. Each can support different functions.

Nexoverse application code does not directly create or read first-party cookies for its own features. Firebase and Google services integrated into the site may use cookies or similar technologies as described below.

2. Firebase Authentication and Essential Storage

The sign-in flow uses Firebase Authentication and selects persistent browser-local authentication when “remember me” is selected, or browser-session persistence otherwise. The Firebase SDK manages the storage needed to maintain that sign-in state using browser-supported mechanisms. The exact storage mechanism can depend on the browser and SDK.

The application also uses local storage for a “remember me” preference and last sign-in method, and a random visitor identifier used by the analytics module to deduplicate events. It uses session storage for temporary return-navigation information, such as taking you back to a page after sign-in. These values are not cookies.

Blocking or clearing authentication storage may sign you out or prevent sign-in from being retained. Clearing session storage can remove temporary navigation state; it does not delete your account or records stored by Nexoverse.

3. Google Analytics 4

Google Analytics 4 is configured on selected pages that load the analytics module. It may process page paths and views, referrers, browser or device information, identifiers, and supported event or community interactions. Some event information can include category, whether an event is marked free or paid, and whether it is online or offline. The module also stores a random visitor identifier in local storage to help deduplicate analytics events.

Google Analytics may use first-party cookies (often with names such as _ga and _ga_…) or similar identifiers, depending on configuration and browser behavior. Exact identifiers, retention and collection can vary. Analytics does not initialize on every page, but on pages where it is configured its initialization is not currently gated by a Nexoverse cookie-consent banner.

4. Google AdSense

Google AdSense is configured for a placement on the Student Ambassador Programs page. Its script is loaded only when a published program is available and the placement is rendered. It is not loaded on every Nexoverse page, and a configured placement does not mean that every visitor receives or sees an advertisement.

Google and other advertising vendors may use cookies or similar technologies to deliver and measure ads, including ads selected based on a user's prior visits to this or other sites. Personalization and measurement depend on provider settings, location and applicable consent signals. See Google's AdSense information about cookies, Ads Settings, and the Digital Advertising Alliance opt-out page.

5. Consent and Preferences

Nexoverse does not currently provide a consent-management platform or site-wide cookie-preference center. Google Analytics on configured pages is not gated by a Nexoverse consent interface. We have not verified that the AdSense integration collects or passes consent signals for users in the EEA, UK or Switzerland.

Google's EU user consent policy requires valid consent for cookies or local storage where legally required and for personal-data use for ad personalization. Google requires a Google-certified CMP integrated with the IAB Transparency and Consent Framework when serving personalized ads to users in the EEA, UK and Switzerland. See Google's CMP requirements and EU user consent policy. Browser settings and opt-out links do not replace a required consent flow.

6. Managing Cookies and Site Storage

You can use your browser or device settings to review, block or clear cookies and site data, including local and session storage. Browser controls differ, particularly for third-party cookies and mobile browsers. Google's privacy controls may also let you manage some Google-related data or advertising choices.

• Blocking or deleting Firebase authentication storage may sign you out or prevent the service from remembering your sign-in.
• Blocking local or session storage may affect analytics deduplication, the remembered sign-in choice or temporary return navigation.
• Blocking third-party cookies or scripts may affect Google services or advertising, but does not necessarily prevent all data processing by those providers.
• Clearing browser storage does not itself delete account, community, event or registration data already held by Nexoverse or its service providers. For account or privacy assistance, email hello@nexoverse.in.

7. Google Information

For more detail about Google's services and controls, see:

• Google Privacy Policy
• How Google uses cookies and similar technologies
• Google Analytics cookie and identifier information
• Google AdSense information about cookies
• Google ad personalization settings

These are third-party resources and may change. Their operators determine their own technologies and privacy practices.

8. Updates and Contact

We may update this policy when the platform, browser storage or integrated services change. The “Last updated” date above identifies this version. For cookie, storage or sign-in questions, contact:

Platform: Nexoverse
Email: hello@nexoverse.in
Website: https://nexoverse.in/

See also our Privacy Policy and Terms of Service.