NetQnect Cookie Notice

Draft status: for legal review before publication.

Effective date: 2026-05-03

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 currently approved for use unless separately configured, disclosed and consented to.

4. Current Website Position

Non-essential website analytics must not load for UK or EU users until consent is collected. If analytics is enabled later, the website must use a consent banner or equivalent consent control before analytics cookies, analytics storage or similar tracking starts.

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. These settings must be verified against each submitted release build.

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.

NetQnect's target for Google Analytics user-level and event-level data is no more than 14 months. Standard aggregate reports may remain available for longer where they no longer identify a user. The property retention and data-sharing settings must be configured and verified before production enablement.

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 and until a legally approved alternative process is implemented.

7. Third-party Cookies

Some third parties may set cookies or use similar technologies when their services are enabled. This may include analytics, authentication, payment, support, hosting, video, social, advertising or embedded content providers.

The Subprocessors list explains the main provider categories.

8. Changes

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