Cookie Policy

In Summary

This Cookie Policy explains how Anchor by Aurelo uses cookies and similar technologies when you access or use the Platform.

Anchor currently uses cookies and related technologies for:

• authentication;
• session management;
• security;
• fraud prevention;
• remembering preferences;
• analytics; and
• improving Platform performance.

Some cookies are necessary for Anchor to function. Others, such as analytics cookies, may be optional depending on your location and applicable law.

This Cookie Policy should be read together with the Privacy Policy, Terms & Conditions, and Legal Notice.

---

Table of Contents

1. Scope
2. What Cookies Are
3. Similar Technologies
4. Why Anchor Uses Cookies
5. Categories of Cookies
6. Essential Cookies
7. Functional Cookies
8. Analytics Cookies
9. Authentication Technologies
10. Third-Party Cookies
11. Cookie Duration
12. Consent and Legal Bases
13. Managing Cookie Preferences
14. Browser Controls
15. Google Analytics
16. Do Not Track and Global Privacy Signals
17. Mobile Applications and Similar Technologies
18. Cookie Inventory
19. Cookie Banner Language
20. Cookie Preference Center
21. Default Consent Behaviour
22. Consent Records
23. Consent Renewal
24. Withdrawal of Consent
25. Region-Specific Behaviour
26. Embedded Content and Event Organizer Tools
27. Event Organizer Responsibilities
28. Security Requirements
29. Data Minimization
30. Analytics Configuration
31. Authentication and Session Expiry
32. Payment and Ticketing Flows
33. Cookie Audit Process
34. Cookie Change Management
35. Implementation Notes
36. Changes to this Cookie Policy
37. Contact
38. Related Documents

---

1. Scope

This Cookie Policy applies when you access or use Anchor websites, web applications, embedded Event experiences, livestream pages, ticketing pages, Organization dashboards, and other browser-based Services operated by Aurelo Technologies.

It explains how Anchor and certain trusted service providers use cookies and similar technologies.

This Policy does not govern cookies or technologies placed independently by:

• Event Organizers;
• Organizations;
• advertisers;
• embedded third-party services;
• payment providers;
• external websites; or
• other third parties that operate under their own terms and privacy practices.

Where an Event Organizer or Organization uses its own integrations, tracking tools, embedded content, or third-party services, that party is responsible for providing any legally required notices and obtaining any required consent.

---

2. What Cookies Are

Cookies are small text files that websites store on your browser or device.

They allow a website to recognize a browser, maintain a session, remember certain information, and understand how a service is being used.

Cookies may store or reference information such as:

• a session identifier;
• an authentication state;
• a security token;
• a language preference;
• a device or browser identifier;
• a consent choice;
• pages visited;
• interaction events; or
• technical performance information.

Cookies do not always directly identify a person. However, information associated with cookies may constitute Personal Information where it can identify, relate to, or reasonably be linked with an individual or device.

---

3. Similar Technologies

Anchor may also use technologies that perform functions similar to cookies.

These may include:

• local storage;
• session storage;
• software development kits;
• pixels;
• tags;
• scripts;
• device identifiers;
• log files;
• cached data;
• server-side analytics;
• browser fingerprinting protections;
• embedded media technologies; and
• authentication tokens.

References to "cookies" in this Policy include similar technologies where appropriate.

---

4. Why Anchor Uses Cookies

Anchor uses cookies and similar technologies to:

• keep users signed in;
• authenticate Accounts;
• maintain secure sessions;
• remember user preferences;
• protect Accounts and the Platform;
• detect suspicious or unauthorized activity;
• prevent fraud and abuse;
• maintain shopping, ticketing, or registration flows;
• measure Platform usage;
• diagnose technical problems;
• improve performance;
• understand feature adoption;
• support livestream delivery;
• remember consent choices; and
• provide a consistent user experience.

Anchor does not use cookies to sell Personal Information.

---

5. Categories of Cookies

Anchor may use the following categories of cookies:

The availability and classification of particular cookies may change as the Platform evolves.

---

6. Essential Cookies

Essential cookies are necessary for Anchor to operate securely and provide core Services.

They may be used to:

• authenticate users;
• maintain login sessions;
• prevent session hijacking;
• store security tokens;
• detect fraudulent activity;
• remember whether a user has accepted required notices;
• maintain Event registration and ticketing workflows;
• balance traffic across infrastructure;
• protect forms and application requests;
• enforce rate limits; and
• maintain Platform stability.

Because these cookies are necessary for the Platform to function, they generally cannot be disabled through Anchor's cookie controls.

You may be able to block them through your browser, but doing so may prevent parts of Anchor from working correctly.

---

7. Functional Cookies

Functional cookies support enhanced features and remember user choices.

They may be used to remember:

• language settings;
• interface preferences;
• accessibility settings;
• display choices;
• selected Event views;
• notification preferences;
• recently used features; and
• other non-essential settings.

Functional cookies may improve your experience but are not always required for basic Platform operation.

Where required by applicable law, Anchor will request consent before placing non-essential functional cookies.

---

8. Analytics Cookies

Analytics cookies help Anchor understand how users interact with the Platform.

They may collect information about:

• pages viewed;
• session duration;
• navigation paths;
• feature usage;
• button and link interactions;
• referring websites;
• browser and device type;
• approximate location derived from an IP address;
• technical errors;
• livestream performance;
• loading times; and
• aggregated usage patterns.

Anchor uses this information to:

• improve navigation;
• identify technical issues;
• optimize Platform performance;
• understand feature adoption;
• improve accessibility;
• develop new features; and
• evaluate the reliability of the Services.

Where required by law, analytics cookies will be used only after consent has been obtained.

---

9. Authentication Technologies

Anchor uses authentication-related cookies and tokens to support:

• email and password sign-in;
• Google Sign-In;
• multi-factor authentication;
• secure Account recovery;
• session validation; and
• protection against unauthorized access.

Authentication cookies may contain:

• session identifiers;
• token references;
• expiry information;
• device information;
• security states; or
• anti-forgery values.

Anchor uses secure password hashing and does not store passwords in readable form.

Authentication tokens are designed to expire or be revoked in accordance with Platform security controls.

---

10. Third-Party Cookies

Some cookies or similar technologies may be placed or accessed by third-party providers that support Anchor.

These providers may include services for:

• analytics;
• authentication;
• cloud infrastructure;
• payment processing;
• email delivery;
• embedded content;
• livestream delivery;
• security monitoring; and
• customer support.

Third-party providers may process information under agreements with Anchor or under their own independent terms.

Anchor takes reasonable steps to work with trusted providers, but does not control cookies placed independently by third parties.

Users should review the privacy and cookie practices of relevant third-party providers where appropriate.

---

11. Cookie Duration

Cookies may be either session cookies or persistent cookies.

Session Cookies

Session cookies usually expire when you close your browser or end your session.

They may be used for:

• temporary authentication;
• navigation state;
• security controls;
• registration flows; and
• short-lived Platform functions.

Persistent Cookies

Persistent cookies remain on a device for a defined period or until they are deleted.

They may be used for:

• remembering preferences;
• maintaining consent choices;
• recognizing returning browsers;
• analytics;
• fraud prevention; and
• security.

The exact duration of a cookie depends on its purpose and technical configuration.

Anchor aims to retain cookies only for as long as reasonably necessary for the purpose for which they are used.

---

12. Consent and Legal Bases

Anchor relies on different legal bases for using cookies depending on their purpose and the laws that apply.

Essential cookies may be used because they are necessary to:

• provide the Services;
• maintain security;
• perform a contract;
• prevent fraud;
• protect users; or
• comply with legal obligations.

Non-essential cookies may be used based on:

• user consent;
• legitimate interests, where permitted; or
• another lawful basis recognized under applicable law.

Where consent is required, Anchor will provide a cookie notice or preference control before placing non-essential cookies.

You may withdraw consent at any time through available cookie controls.

Withdrawal does not affect the lawfulness of processing carried out before consent was withdrawn.

---

13. Managing Cookie Preferences

Where available, Anchor's cookie preference tools allow you to:

• accept all cookies;
• reject non-essential cookies;
• choose specific cookie categories;
• review your current preferences; and
• change or withdraw consent.

Changes may not apply retroactively to information already collected.

After changing your preferences, some cookies may remain until they expire or are deleted through your browser.

Essential cookies will continue to operate where necessary to provide the Services.

---

14. Browser Controls

Most browsers allow you to:

• view cookies;
• delete cookies;
• block all cookies;
• block third-party cookies;
• receive alerts before cookies are placed; and
• clear local storage or browsing data.

Browser settings vary by browser and device.

Blocking or deleting cookies may affect:

• login sessions;
• saved preferences;
• Event registration;
• ticketing flows;
• payment processes;
• livestream access;
• Organization dashboards; and
• other Platform features.

Anchor is not responsible for functionality lost because a browser blocks technologies necessary for the Platform to operate.

---

15. Google Analytics

Anchor currently uses Google Analytics to understand Platform usage and improve the Services.

Google Analytics may process information such as:

• device and browser information;
• IP address;
• pages visited;
• session activity;
• interaction events;
• referral information; and
• technical performance data.

Where available and appropriate, Anchor may configure analytics settings to support privacy protections, including data minimization, retention controls, IP-related protections, or consent-based activation.

Google may process information in accordance with its own privacy terms and service documentation.

Where legally required, Google Analytics will not be activated until the user has provided consent.

---

16. Do Not Track and Global Privacy Signals

Some browsers and devices allow users to send privacy signals, including:

• Do Not Track signals;
• Global Privacy Control signals; or
• similar preference indicators.

There is no single universally accepted technical or legal standard governing all such signals.

Anchor may respond to legally recognized signals where required by applicable law and where technically feasible.

A browser signal may not disable cookies that are necessary for security, authentication, fraud prevention, or core Platform functionality.

---

17. Mobile Applications and Similar Technologies

If Anchor provides mobile applications, installed applications, or device-based Services, similar technologies may be used instead of browser cookies.

These may include:

• device identifiers;
• application storage;
• software development kits;
• push notification tokens;
• mobile analytics;
• crash reporting tools; and
• authentication tokens.

Users may manage certain permissions through their device or application settings.

Disabling permissions may affect application functionality.

---

18. Cookie Inventory

The table below provides Anchor's current publication framework for its cookie inventory.

The exact cookie names, domains, expiration periods, and providers should be confirmed against the production environment before publication. Cookie names may vary between development, staging, and production systems.

The cookie inventory should be reviewed whenever Anchor:

• adds or removes a third-party integration;
• changes its authentication architecture;
• introduces new analytics tools;
• launches new mobile or web applications;
• adds embedded media providers;
• changes payment or fraud-prevention systems; or
• modifies consent-management technology.

---

19. Cookie Banner Language

The following language may be used for Anchor's primary cookie banner.

Recommended Banner Copy

We use cookies

Anchor uses essential cookies to operate securely and provide core functionality. With your permission, we also use analytics and functional cookies to understand usage, improve performance, and remember your preferences.

You can accept all cookies, reject non-essential cookies, or manage your preferences.

Recommended Buttons

• Accept All
• Reject Non-Essential
• Manage Preferences

The banner should also include a link to this Cookie Policy.

---

20. Cookie Preference Center

The cookie preference center should allow users to make category-level choices.

Essential Cookies

Always active

These cookies are required for authentication, security, fraud prevention, session management, ticketing, payments, and core Platform functionality. They cannot be disabled through Anchor's preference center.

Functional Cookies

Optional where required by law

These cookies remember preferences and support enhanced features, such as language settings, accessibility choices, and interface options.

Analytics Cookies

Optional where required by law

These cookies help us understand how Anchor is used, identify technical issues, measure feature adoption, and improve Platform performance.

Third-Party Service Cookies

Varies by service

Certain embedded or integrated services may use their own cookies or similar technologies. Where required, these services will remain inactive until you provide consent.

The preference center should include:

• a clear explanation of each category;
• the current consent status;
• controls to enable or disable optional categories;
• a link to this Cookie Policy;
• a date showing when preferences were last updated; and
• a method for withdrawing or changing consent.

---

21. Default Consent Behaviour

Anchor's recommended default behaviour is:

• essential cookies are enabled automatically;
• non-essential analytics cookies remain disabled until consent is obtained where required;
• optional functional cookies remain disabled until consent where required;
• refusal of non-essential cookies does not prevent access to the core Platform;
• cookie choices are recorded and respected across future visits where technically possible; and
• users can reopen the preference center at any time.

Anchor should not:

• preselect optional cookie categories where affirmative consent is required;
• make the "Reject" option materially harder to find than the "Accept" option;
• use misleading button labels;
• treat inactivity as consent where prohibited;
• prevent access solely because a user refuses analytics cookies, unless a feature genuinely depends on the selected technology; or
• reactivate declined cookies without obtaining valid consent.

---

22. Consent Records

Where consent is required, Anchor may maintain a record of:

• the consent identifier;
• the date and time of the choice;
• the cookie categories accepted or rejected;
• the version of the cookie notice or preference interface shown;
• the region or legal framework applied;
• the device or browser context;
• whether consent was later withdrawn or changed; and
• technical information needed to demonstrate that the choice was respected.

Consent records should be retained only for as long as reasonably necessary to:

• demonstrate compliance;
• resolve disputes;
• investigate technical issues; or
• maintain the user's current preferences.

Consent records should not include unnecessary content from a user's browsing activity.

---

23. Consent Renewal

Anchor may ask users to review their cookie choices again where:

• the Cookie Policy changes materially;
• a new cookie category is introduced;
• the purposes of existing cookies change;
• a new third-party provider is added;
• applicable law requires renewed consent;
• the existing consent record has expired; or
• technical changes make the previous choice unreliable.

Where consent has not materially changed, Anchor may retain the existing preference for a reasonable period.

A recommended review period is no longer than 12 months for optional cookie consent, unless a shorter period is required by law or implementation.

---

24. Withdrawal of Consent

Users should be able to withdraw consent as easily as they gave it.

Anchor should provide a persistent method to reopen cookie settings, such as:

• a Cookie Settings link in the website footer;
• a privacy settings page;
• an Account preference control; or
• a floating privacy control where appropriate.

After consent is withdrawn:

• optional cookies should no longer be placed;
• existing optional cookies should be deleted where technically feasible;
• related third-party scripts should be disabled;
• future analytics events should stop being sent; and
• the updated preference should be recorded.

Withdrawal does not require Anchor to delete aggregated or de-identified analytics that were lawfully created before withdrawal.

---

25. Region-Specific Behaviour

Cookie requirements differ across jurisdictions.

Anchor may apply different consent experiences based on the user's location, provided the approach is lawful, transparent, and technically reliable.

European Economic Area and United Kingdom

Where applicable, non-essential cookies should not be placed before valid consent is obtained.

Consent should be:

• freely given;
• specific;
• informed;
• unambiguous;
• based on an affirmative action; and
• capable of being withdrawn.

Ghana

Anchor should process cookie-related information in accordance with applicable Ghanaian privacy and data-protection requirements, including transparency, purpose limitation, and appropriate security.

United States

Requirements may vary by state. Anchor may need to recognize legally applicable opt-out signals or provide additional disclosures where cookie-based activity qualifies as targeted advertising, sharing, or sale under applicable law.

Anchor currently states that it does not sell Personal Information. If future advertising or data-sharing practices change, the Cookie Policy and consent interface must be updated before those practices begin.

---

26. Embedded Content and Event Organizer Tools

Organizations and Event Organizers may embed or connect third-party services within Event pages.

These may include:

• video players;
• social media content;
• chat tools;
• marketing platforms;
• audience engagement tools;
• external registration forms;
• donation widgets;
• advertising tools; or
• other integrations.

Those services may place their own cookies or similar technologies.

Where an Organization controls the integration, that Organization is responsible for:

• determining whether the technology is appropriate;
• providing any legally required notice;
• obtaining any legally required consent;
• maintaining an accurate cookie inventory; and
• complying with applicable privacy laws.

Anchor may restrict or remove integrations that create security, privacy, legal, or Platform-integrity risks.

---

27. Event Organizer Responsibilities

An Event Organizer must not use Anchor to deploy cookies, pixels, scripts, tags, device identifiers, or similar technologies in a way that:

• violates applicable law;
• collects information without required notice or consent;
• tracks users across unrelated services without authorization;
• circumvents Anchor's cookie controls;
• introduces malicious or deceptive code;
• interferes with Platform security;
• collects sensitive information without a lawful basis;
• misrepresents the purpose of the technology; or
• causes Anchor to breach its legal obligations.

Anchor may require an Organizer to provide information about any tracking or embedded technology used through an Event.

---

28. Security Requirements

Cookie and token security should be implemented according to the sensitivity and purpose of the technology.

Appropriate controls may include:

• Secure attributes for cookies transmitted over HTTPS;
• HttpOnly attributes where client-side script access is not required;
• suitable SameSite settings;
• limited expiration periods;
• token rotation;
• session revocation;
• encryption in transit;
• protection against cross-site request forgery;
• protection against session fixation;
• scoped cookie domains and paths;
• access logging; and
• monitoring for suspicious session activity.

Authentication credentials, complete payment card information, and highly sensitive Personal Information should not be stored directly in ordinary browser cookies.

---

29. Data Minimization

Anchor should configure cookies and similar technologies to collect no more information than reasonably necessary.

Where practical, Anchor should:

• avoid storing direct identifiers in cookie values;
• use pseudonymous identifiers;
• reduce retention periods;
• limit third-party access;
• disable unnecessary advertising features;
• minimize event-level analytics data;
• avoid collecting sensitive information;
• restrict cross-service tracking; and
• use aggregated or de-identified reporting.

Cookie values should not contain readable passwords, complete payment card numbers, private chat content, or unnecessary user profile information.

---

30. Analytics Configuration

Google Analytics and any future analytics tools should be configured in a privacy-conscious manner.

Recommended controls include:

• consent-based activation where required;
• disabling advertising features unless specifically approved;
• restricting data sharing with the provider;
• configuring suitable retention periods;
• excluding sensitive form fields from analytics events;
• preventing full URLs from exposing sensitive query parameters;
• filtering internal development and testing traffic where appropriate;
• limiting user-level identifiers;
• reviewing custom event names and properties;
• ensuring ticket, donation, chat, and payment data are not inadvertently included; and
• documenting the lawful purpose of each analytics event.

Analytics events should not include:

• passwords;
• authentication tokens;
• complete payment card details;
• private messages;
• sensitive attendee responses;
• uploaded identity documents; or
• other unnecessary Personal Information.

---

31. Authentication and Session Expiry

Authentication cookies and tokens should use expiration periods appropriate to the security risk.

Anchor may:

• end sessions after inactivity;
• require re-authentication for sensitive actions;
• revoke sessions following password changes;
• revoke sessions after suspected compromise;
• require multi-factor authentication;
• rotate access or refresh tokens;
• limit concurrent sessions; and
• invalidate tokens after Account deletion or suspension.

Sensitive actions may include:

• changing an email address;
• resetting authentication methods;
• transferring Organization ownership;
• modifying payment settings;
• accessing restricted Event data; and
• submitting an Account deletion request.

---

32. Payment and Ticketing Flows

Cookies used during ticket purchases, donations, subscriptions, and payments should be limited to what is needed to:

• maintain transaction state;
• prevent duplicate submissions;
• detect fraud;
• associate a payment confirmation with the correct user or Event;
• preserve registration progress; and
• return the user to the correct Platform page.

Payment cookies should not contain complete card numbers or card security codes.

Where Paystack or another payment provider places its own technologies, those technologies may be governed by the provider's policies.

---

33. Cookie Audit Process

Anchor should perform periodic cookie audits.

A cookie audit should review:

1. all cookies and similar technologies deployed in production;
2. the provider responsible for each technology;
3. the purpose and legal basis;
4. the information collected;
5. the domain and path;
6. whether the cookie is first-party or third-party;
7. the expiration period;
8. the consent category;
9. whether the cookie activates before consent;
10. whether the published inventory is accurate;
11. whether any technology is no longer needed; and
12. whether security attributes are correctly configured.

Audits should also be conducted before major product launches or changes to analytics, authentication, payments, or embedded services.

---

34. Cookie Change Management

New cookies or similar technologies should not be deployed to production without:

• identifying the purpose;
• confirming the provider;
• reviewing the information collected;
• determining the lawful basis;
• assigning the correct consent category;
• confirming the retention period;
• reviewing security attributes;
• updating the inventory;
• testing consent behaviour; and
• obtaining appropriate internal approval.

Engineering, legal, security, product, and analytics teams should coordinate where a new technology has privacy or compliance implications.

---

35. Implementation Notes

The following implementation requirements are recommended for the Anchor cookie-management system:

• load only essential scripts before consent where prior consent is required;
• prevent analytics events from firing until the relevant category is enabled;
• store a version number with each consent record;
• re-request consent after material changes;
• provide equally visible Accept and Reject options;
• allow users to save granular preferences;
• keep a persistent Cookie Settings link in the website footer;
• apply choices across Anchor subdomains where technically appropriate;
• avoid storing unnecessary Personal Information in consent records;
• test behaviour in private browsing and blocked-cookie environments;
• ensure withdrawal stops future analytics collection;
• record implementation changes in the Trust Center Changelog; and
• review the production cookie inventory before every policy release.

Recommended Cookie Banner

Anchor uses cookies

We use essential cookies to keep Anchor secure and working properly. With your permission, we also use functional and analytics cookies to remember preferences, understand how the Platform is used, and improve performance.

Actions: Accept All · Reject Non-Essential · Manage Preferences

Recommended Preference Footer Link

Cookie Settings

This link should remain available on every public Anchor website page and within relevant Account privacy settings.

---

36. Changes to this Cookie Policy

Anchor may update this Cookie Policy to reflect changes in:

• cookies or technologies used;
• Platform features;
• analytics services;
• authentication systems;
• third-party providers;
• legal requirements; or
• privacy practices.

When changes are made, the Last Updated date will be revised.

Material changes may be communicated through the Platform or cookie preference interface where appropriate.

---

37. Contact

Questions about cookies or similar technologies may be directed to:

Aurelo Technologies
Accra, Ghana

Legal and privacy: legal@technologies.aurelo.cc
Support: support@technologies.aurelo.cc
Telephone: +233 532 396 876

---

38. Related Documents

• Privacy Policy
• Terms & Conditions
• Legal Notice
• Account Deletion Policy