NetQnect Cookie Notice

Version date: 16 September 2026.

Effective date: 16 September 2026, applying only when this exact revision is published.

Contact: legal@netqnect.com

1. About This Notice

This Cookie Notice explains how NetQnect uses cookies and similar technologies on the website, web app, mobile apps and related online services.

2. What Cookies Are

Cookies are small files stored on a device. Similar technologies include local storage, pixels, SDK identifiers and analytics tags.

3. Cookie Categories

NetQnect may use:

• Strictly necessary cookies and storage: needed for login, security, routing, session integrity, fraud prevention, load balancing, consent records and service operation.
• Preference cookies and storage: used to remember user choices such as language, display settings, privacy settings and consent choices.
• Analytics cookies and SDKs: used to understand website and app performance, feature use and reliability. These are non-essential and require consent where required by law.
• Performance and diagnostics SDKs: used to understand crashes, latency and technical reliability. These are controlled through app privacy settings where available.
• Marketing cookies and pixels: not used in the current service.

4. Current Website Position

The website presents choices for non-essential technologies. Optional analytics is off until you accept it. Rejecting optional technologies does not prevent access to public legal information. Use Cookie settings in the footer to reopen the controls and change your choice. Clearing browser storage removes the saved choice, and using another browser or device requires a separate choice.

NetQnect consent choices

• Storage: netqnect_cookie_consent_v1 in browser local storage.
• Purpose: record your consent choices, policy version, choice time and applicable GPC signal.
• Duration: no automatic time expiry in the current implementation. The record is replaced when you change choices or removed when you clear site storage. A policy-version change requires a fresh choice.

Authentication and security storage

• Provider: Firebase and NetQnect, where signed-in app features are used.
• Purpose: maintain and protect account sessions.
• Duration: the session or configured sign-in persistence; sign-out and browser controls apply.

Google Analytics browser cookies, if enabled and consented

• Names: _ga and property-specific _ga_ cookies.
• Purpose: distinguish browser visits and store analytics state.
• Duration: provider/configuration-dependent, commonly up to two years. This is distinct from Analytics server retention.

NetQnect chooses prior consent for optional analytics; this is the product policy even where a narrowly defined statutory exception might be available. Choosing analytics does not enable marketing pixels.

We do not use your data to train AI models. If we ever propose an optional programme, we will explain it in Privacy Settings and ask you first.

5. Current App Analytics Position

Firebase Analytics for Google Analytics is present in the app but disabled by default. It may collect data only after the user enables app analytics in NetQnect's privacy settings.

Where enabled, the SDK and NetQnect's bounded custom events may process:

• an app-instance identifier used to distinguish an installation;
• session statistics, approximate location, app version and device information supplied by the standard SDK;
• bounded feature-use values such as method, source surface, type, tier, cycle or success/failure category; and
• screen views and other standard Analytics events where enabled.

NetQnect custom analytics parameters must not contain names, email addresses, prompts, free-text content, access tokens, event or connection identifiers, or other direct entity identifiers. Android advertising-ID and Android ad-services identifier permissions are removed from the NetQnect app manifest. The iOS Firebase Analytics dependency is configured without Apple's AdSupport framework or IDFA capability; IDFV collection, Apple ad-network attribution registration and advertising-personalisation signals are also disabled.

Withdrawing app analytics consent disables future collection, clears any explicit Analytics user association and resets local Analytics app-instance state. It does not delete processing that occurred before withdrawal. Requests concerning provider-held data can be made through the routes in the Privacy Notice.

Our retention limits are two months for Analytics event data and 14 months for user data where the provider offers separate controls. Standard aggregate reports may remain available for longer where they no longer identify a user.

6. Managing Choices

Users can manage cookies through browser controls. Where NetQnect provides a consent banner, users can accept, reject or change non-essential choices through that control.

App users can manage analytics, crash reporting, performance reporting and related privacy settings inside the app where available.

Where the website receives a browser Global Privacy Control or equivalent legally recognised opt-out preference signal, NetQnect treats that signal as a request to keep optional analytics and marketing technologies off for that browser unless you change the applicable choice through an available lawful process.

7. Third-party Cookies

An optional provider may use its own storage when you visit or authorise its service. Its own notice applies to that independent activity. We identify embedded third-party technology before it loads and request consent where required.

The Subprocessors list explains the main provider categories. The Privacy Notice explains purposes, rights and how to contact us.

8. Changes

We may update this Cookie Notice when cookies, SDKs or tracking technologies change.