Section 1
About this Notice.
1.1 This Cookie and Tracking Notice describes the cookies and similar tracking technologies used on the Avenor website. It is part of Avenor's privacy disclosures and supplements the Privacy Policy (section 10 of which refers to this Notice).
1.2 The Notice applies to the public Avenor website, including the application form and the public-facing pages. The member portal — accessed after activation — operates under the same principles but uses additional cookies necessary to authenticate Members and maintain their sessions.
1.3 Avenor uses cookies and tracking technologies sparingly and on purpose. The website does not use cookies for advertising, profiling, lookalike-audience generation, or cross-site tracking. This is consistent with the Privacy Policy's clause 3.8.
1.4 Version: 1.0. Date: [date of issue]. Earlier versions, where they applied to a current Member's term, are available on request to hello@avenor.club.
Section 2
What we mean by cookies and tracking.
2.1 Cookies are small text files set in a visitor's browser by a website or by a service the website uses. They allow the website to remember information about the visitor's interaction with it — for example, that they are logged in, that they prefer a certain language, or that they have given consent to certain tracking.
2.2 Similar tracking technologies include local storage (a way for the browser to store information beyond a single session), pixels or web beacons (small image files used to count visits or detect specific events), and fingerprinting techniques (methods that identify a browser by its specific configuration without setting a cookie). This Notice covers all of these together as cookies and tracking technologies.
2.3 First-party cookies and tracking are set by the Avenor website directly. Third-party cookies and tracking are set by services that the Avenor website uses (for example, a hosted analytics service). NDPA applies the same standards to both, but the distinction matters when a visitor wants to know who specifically holds their data.
2.4 Strictly necessary cookies are required for the website to function — for example, the cookie that maintains a logged-in Member's session, or a cookie that prevents a form submission from being submitted twice. Strictly necessary cookies do not require consent under NDPA. All other cookies — analytics, preferences, and any third-party tracking — require consent.
Section 3
What the Avenor website uses.
The Avenor website uses the following cookies and tracking technologies. The list is current as of the date of this Notice and is updated whenever cookies are added, removed, or changed.
3.1 Strictly necessary cookies — first-party. The following cookies are set by the Avenor website directly and are required for the website to function:
(a)[session_id] — maintains a visitor's session and Member authentication where applicable; deleted when the browser is closed.
(b)[csrf_token] — prevents cross-site request forgery on form submissions; deleted when the browser is closed.
(c)[consent_state] — records the visitor's consent preferences for non-essential cookies; retained for 12 months.
Strictly necessary cookies do not require consent under NDPA section 22 and cannot be disabled through Avenor's consent mechanism. They can be cleared through the visitor's browser settings (section 5 below), though doing so may prevent the website from functioning normally.
3.2 Analytics cookies — first-party. Avenor uses [name of analytics provider — e.g. Plausible, Fathom, or first-party Matomo] to understand aggregate patterns of website use — which pages are read, which application steps are completed, and which routes through the site work well. The analytics provider in use is selected for its privacy-respecting approach: it does not set persistent identifiers, does not share data with third parties, and does not enable profiling of individual visitors.
The analytics in use processes data on an aggregate basis and does not personally identify visitors. Where any analytics technology that personally identifies visitors or shares data with third parties is added in the future, this Notice will be updated and consent re-requested.
3.3 Functional cookies — first-party. The following cookies remember a visitor's preferences across sessions:
(a)[preference_locale] — remembers the visitor's language or regional preference; retained for 12 months.
Functional cookies are not strictly necessary but improve the visitor's experience on return visits. They require consent under NDPA.
3.4 Third-party cookies and tracking. The Avenor website does not currently set third-party cookies. Where third-party services are required in the future — for example, a payment processor on the activation flow — those services may set their own cookies under their own privacy notices. The activation flow is operated by [name of payment processor], whose cookie practices are described at [link to payment processor's cookie notice].
3.5 No advertising tracking. The Avenor website does not use cookies or tracking technologies operated by advertising platforms (including but not limited to Meta, Google Ads, TikTok, LinkedIn, or any similar service). This is consistent with the Privacy Policy's commitment in clause 3.8.
Section 4
Your consent and how to change it.
4.1 Strictly necessary cookies do not require consent and are set on first visit. The Avenor website cannot be operated without them.
4.2 All other cookies are set only with the visitor's consent. On a visitor's first visit to the Avenor website, a consent mechanism is shown. The visitor may:
(a)accept all cookies — strictly necessary, analytics, and functional;
(b)accept only strictly necessary cookies;
(c)customise their preferences by category.
4.3 Withdrawing or changing consent. A visitor may withdraw or change their consent at any time by:
(a)clicking the Cookie preferences link in the footer of any page of the Avenor website, which reopens the consent mechanism;
(b)clearing their browser's cookies for the Avenor website, which will cause the consent mechanism to be shown on the next visit;
(c)changing their browser-level cookie controls (section 5 below).
Withdrawal of consent applies prospectively. Data already collected on the basis of prior consent is handled in accordance with the Privacy Policy.
4.4 Record of consent. Avenor records each visitor's consent preferences in the [consent_state] cookie so the consent mechanism is not re-shown on every page. The record contains the date and the specific categories accepted. Avenor does not link this consent record to any other identifier without additional consent.
Section 5
Browser-level controls.
5.1 In addition to the Avenor-specific consent mechanism, every modern browser provides controls to:
(a)view the cookies that have been set;
(b)delete specific cookies or all cookies;
(c)block cookies entirely or from specific websites;
(d)set the browser to inform the visitor when a cookie is set;
(e)enable a "Do Not Track" signal that some websites recognise.
5.2 Browser-level controls override Avenor's consent mechanism. A visitor who has blocked cookies at the browser level will not have any cookies set, regardless of what they accept in Avenor's consent mechanism.
5.3 Blocking all cookies, including strictly necessary cookies, prevents the Avenor website from functioning normally. In particular, Members will not be able to log in to the member portal without the session cookies.
5.4 Each browser has its own controls. Documentation for the most common browsers is published by the browsers themselves and is available through searches for "manage cookies in [browser name]".
Section 6
Changes to this Notice.
6.1 Avenor updates this Notice when the cookies or tracking technologies on the website change. Updates are issued as new versions of the Notice and dated.
6.2 Material changes — including the introduction of a new category of tracking (such as analytics that personally identify visitors, or any third-party tracking) — require fresh consent. Where a material change is made, the consent mechanism is re-shown to visitors on their next visit, and consent given before the change does not extend to the new category.
6.3 Non-material changes — clarifications, corrections, or updates to provider names where the function of the tracking has not changed — are made by issuing a new version of the Notice with an updated date. Visitors are not re-asked for consent in this case.
6.4 Archive. Earlier versions of this Notice are maintained in Avenor's archive and are available to a current Member, where the earlier version applied during their term, on request to hello@avenor.club.
Section 7
Contact us.
7.1 Questions or concerns about cookies and tracking on the Avenor website are addressed by writing to hello@avenor.club. Avenor responds within fourteen days.
7.2 A visitor who is dissatisfied with how Avenor handles cookies and tracking may complain to the Nigeria Data Protection Commission, in accordance with section 12.3 of the Privacy Policy.