Cookie Policy
Gloseg B2B Limited Effective Date: August 16, 2026 Version: 1.2
Definitions
- "Cookie" means a small text file placed on a device when visiting a website, used to remember information between requests.
- "Similar Technologies" means local storage, session storage, pixels, and comparable device or browser storage mechanisms.
- "Local Storage" means browser storage that persists data on a device until explicitly cleared, without a fixed expiry.
- "Session Storage" means browser storage cleared automatically when the browser tab or window is closed.
- "Pixel" means a small tracking image or script, such as the Facebook Pixel, used to record an event such as a page view or conversion.
- "Consent Management Platform" or "CMP" means the tool Gloseg uses to capture, record and let Users manage cookie and marketing consent choices.
- "Strictly Necessary" means a cookie or technology required for the Platform to function and that cannot be switched off through the CMP.
1. Purpose and scope
1.1 What this policy covers
This Cookie Policy explains how Gloseg uses cookies and Similar Technologies across the marketplace, RFQ and messaging systems, community forum, academy and webinar content, market intelligence pages, blog, and live chat support, and how Users can control these technologies.
1.2 Relationship to the Privacy Policy
1.2.1 Companion document
- This policy should be read together with the Privacy Policy, which governs how personal data collected via cookies and other means is used, retained, and protected.
2. What cookies and similar technologies are
2.1 Cookies
2.1.1 Basic mechanics
- Cookies are stored by the browser and sent back to the originating server (first-party) or a different server (third-party) on subsequent requests, enabling features like staying logged in or remembering preferences.
2.2 Local storage and session storage
2.2.1 Difference from cookies
- Local Storage and Session Storage are not automatically sent with every network request; they are read by scripts running on the page. Local Storage persists until cleared; Session Storage clears when the tab closes.
2.3 Pixels
2.3.1 Event tracking
- Pixels record that an event occurred (such as a page view or a completed sign-up) and can be used, subject to consent, for analytics and advertising measurement, including through the Facebook Pixel.
3. Legal basis and consent model
3.1 Consent-first approach
3.1.1 Category-based consent
- Gloseg uses a granular consent model. Strictly necessary technologies operate on the legal basis of legitimate interest and necessity for providing the service requested. Functional, analytics and marketing categories operate on the basis of consent, captured through the CMP before non-essential cookies load.
3.2 Applicable frameworks
3.2.1 Standards referenced
- This model is designed with reference to GDPR, Nigeria's NDPR, Ghana's Data Protection Act, and general ePrivacy expectations for cookie consent.
4. Cookie categories
4.1 Category table
| Category | Purpose | Typical lifetime | Consequence of refusal |
|---|---|---|---|
| Strictly necessary | Authentication, session integrity, load balancing, security, remembering consent choices | Session to a limited number of months | None available to refuse; required for the Platform to operate |
| Functional and preference | Remembering language, display mode preference, saved filters, layout settings | Up to 12 months | Preferences reset each visit; minor inconvenience, core function unaffected |
| Analytics and performance | Understanding usage patterns, page performance, error diagnostics to improve the Platform | Up to 24 months | Gloseg has less visibility into usage issues; User experience on the Platform is not otherwise affected |
| Marketing and advertising | Measuring campaign effectiveness and personalising marketing, including Facebook Pixel events | Up to 12 months | No personalised marketing or off-platform ad measurement; User can still use the Platform fully |
4.2 First-party versus third-party context
4.2.1 Distinction
- First-party cookies are set directly by Gloseg's domains. Third-party cookies and pixels, such as those used for analytics or the Facebook Pixel, are set by or on behalf of a third-party service Gloseg uses, and load only after the relevant consent category is accepted.
5. Consent capture and management
5.1 How consent is captured
5.1.1 CMP banner and settings
- On first visit, a consent banner presents category choices. Users may accept all, reject non-essential categories, or configure categories individually.
5.2 Changing or withdrawing consent
5.2.1 Always available
- Users can change or withdraw consent at any time through the cookie settings link available on the Platform footer or account settings. Withdrawing consent stops future loading of the relevant category's tags; it does not retroactively undo processing already completed under prior consent.
6. Consent record keeping
6.1 Why records are kept
6.1.1 Evidence of compliance
- Gloseg's CMP records the choice made, the timestamp, and the categories accepted or rejected, to demonstrate compliance with consent requirements if required by a regulator or in a dispute.
6.2 Retention of consent records
6.2.1 Retention period
- Consent records are retained for as long as the underlying account or browser session data is retained, and for a reasonable period afterward to evidence historical compliance.
7. Behaviour when consent is refused
7.1 No tags without consent
7.1.1 Technical enforcement
- Analytics and marketing tags, including the Facebook Pixel, do not load or fire until the corresponding consent category is accepted. Refusing these categories does not degrade access to marketplace, RFQ, messaging, or community features.
8. Authentication and session integrity technologies
8.1 Cannot be switched off
8.1.1 Necessity
- Cookies and storage used to keep a User logged in, protect against cross-site request forgery, balance load across servers, and detect fraud are strictly necessary and cannot be disabled through the CMP. Users who wish to avoid all storage entirely must not use the Platform.
9. Do-not-track and global privacy control
9.1 Current handling
9.1.1 Honouring signals where feasible
- Where a browser sends a recognised Global Privacy Control or Do Not Track signal, Gloseg treats this as a request to withhold consent for non-essential categories on that browser, consistent with the CMP's category settings, to the extent technically supported by the CMP in use.
10. Mobile and in-app storage
10.1 Equivalent technologies
10.1.1 Mobile context
- Where Gloseg is accessed through a mobile browser or app, equivalent identifiers and local storage mechanisms may be used, subject to the same consent categories and controls described in this policy, and to platform-level permissions on the device.
11. Cross-border transfer implications
11.1 Where data may travel
11.1.1 Transfer context
- Data collected through analytics or marketing cookies may be processed outside the User's home country, including in jurisdictions where Gloseg's processors operate. Such transfers are handled consistent with the safeguards described in the Privacy Policy.
12. Relationship to data subject rights
12.1 Rights available
12.1.1 Supported requests
- Users may request export, deletion, correction, objection, or restriction of personal data collected via cookies and related technologies, consistent with the Privacy Policy and applicable law (GDPR, NDPR, Ghana Data Protection Act).
12.2 How to exercise rights
12.2.1 Contact point
- Requests can be submitted to legal@gloseg.com. Gloseg will verify identity before acting on a request.
13. Children and non-business users
13.1 Platform is business-directed
13.1.1 No targeting of children
- Gloseg is a B2B platform not directed at children. Cookies and Similar Technologies are not knowingly used to profile or target individuals known to be children.
14. Changes to this policy
14.1 Updates and re-consent
14.1.1 When re-consent is triggered
- Gloseg may update this policy to reflect new technologies, vendors, or legal requirements. Where a change introduces a new cookie category or materially changes the purpose of an existing category, the CMP will prompt Users to re-confirm their consent choices. Minor clarifications do not trigger re-consent.
14.2 Notice of material changes
14.2.1 Communication
- Material changes will also be notified through the Platform or by email at least 14 days before taking effect where feasible.
15. Governing law and jurisdiction
15.1 Governing law
15.1.1 Ghana law
- This policy is governed by the laws of Ghana, without prejudice to mandatory data protection rights under GDPR, Nigeria's NDPR, or Ghana's Data Protection Act applicable to a given User.
15.2 Jurisdiction
15.2.1 Courts
- Subject to mandatory jurisdictional rules, the courts of Ghana have jurisdiction over disputes arising from this policy.
Contact
Legal notices, questions about this document, data protection requests and compliance enquiries: legal@gloseg.com
Data subject requests may also be submitted through the Privacy & My Data surface at /privacy/my-data.
Gloseg B2B Limited Accra, Ghana, West Africa
16. Additional operational detail
16.1 Cookie audit and review cadence
16.1.1 Periodic review
- Gloseg periodically reviews the cookies and Similar Technologies actually deployed on the Platform against the categories described in Section 4, to ensure the CMP configuration remains accurate as features change.
16.2 Vendor changes
16.2.1 New processors
- If Gloseg introduces a new analytics or marketing vendor, that vendor's cookies are mapped into the existing consent categories (analytics and performance, or marketing and advertising) rather than creating hidden new categories, so a User's existing consent choice continues to apply consistently.
17. Practical examples
17.1 Example: strictly necessary in practice
17.1.1 Session cookie example
- When a Member logs in to manage an Organization's listings, a session cookie keeps the Member authenticated across pages. Without it, the Member would be logged out on every page navigation.
17.2 Example: functional preference in practice
17.2.1 Display mode example
- A Member's chosen community display mode and preferred content language may be remembered using a functional cookie, so the Member does not need to reselect it on every visit.
17.3 Example: analytics in practice
17.3.1 Usage pattern example
- Analytics cookies help Gloseg understand which market intelligence pages are most used, informing where to invest in improving content, without being used to identify a specific individual for marketing purposes.
17.4 Example: marketing in practice
17.4.1 Conversion measurement example
- The Facebook Pixel, where consented to, may record that a User who saw a Gloseg advertisement later created an account, helping Gloseg measure the effectiveness of that advertisement.
18. Browser-level controls
18.1 Independent browser settings
18.1.1 Additional layer of control
- In addition to the CMP, Users can configure their browser to block or delete cookies generally. Blocking strictly necessary cookies at the browser level may prevent login and core Platform functions from working, independent of any choice made in the CMP.
18.2 Clearing storage
18.2.1 Effect of clearing
- Clearing local storage or cookies through browser settings will reset consent choices recorded in the browser, and the consent banner will be shown again on the next visit.