PrideSpins Ghana: Cookie Policy

Cookies are small records that a website can ask a browser to store and return on later visits. They can support sessions, remember a chosen language or help measure how pages perform. Similar functions may use local storage, software development kits, pixels or other device identifiers. These technologies are not identical, and not every tracker stores a traditional cookie. What matters is the information collected, who receives it and why it is used. A cookie notice should explain observable behaviour rather than listing technical labels without meaning. This draft describes common categories but does not assert that any particular vendor or cookie is installed. An accurate final inventory requires inspection of the actual site and app.

Some technologies are used to maintain a session, protect forms, balance traffic or defend against abusive requests. A sign-in service may rely on an identifier so users do not need to authenticate after every page transition. Security systems may use temporary markers to distinguish legitimate activity from repeated automated requests. These purposes can be necessary for core functions, but the label ‘essential’ should not be used as a blanket justification for unrelated advertising or audience profiling. The website owner must review each cookie’s purpose and decide whether it genuinely belongs in this category. If an essential cookie is blocked, users may have difficulty signing in or using account functions, although the precise impact depends on the implementation.

A session cookie is commonly removed when a browser session ends, whereas a persistent cookie can remain until its stated expiry or manual deletion. Some browsers restore sessions, and local-storage records can behave differently from traditional cookies, so these labels are not a complete explanation of duration. For each deployed technology, the final cookie schedule should state its name, provider, category, purpose and lifespan. An assertion that all cookies expire at logout is risky unless technically verified. The retention period should be no longer than justified by the purpose. Users need a practical explanation of what remains after signing out, changing devices or clearing stored site data.

Functional storage can remember interface choices such as language, display settings or whether a notice has already been dismissed. It can make repeated visits more consistent, especially when someone moves between a home page, game area and help pages. These settings are different from gathering behavioural information to target promotions. The final notice should identify whether the preference is retained only during a session or across visits. Users also need to understand that clearing browser data can remove a choice and cause the website to ask again. A convenience feature should collect no more information than is necessary for its stated purpose and should not be described as strictly necessary without a documented reason.

Analytics can help identify slow pages, broken navigation, common device sizes and general visitor trends. Depending on configuration, a measurement tool may receive timestamps, page paths, approximate locations or pseudonymous identifiers. Some systems aggregate results while others retain event-level data that can be connected across visits. The operator should verify whether consent is needed for the deployed configuration and whether privacy-enhancing settings are available. A claim that analytics is ‘anonymous’ requires technical evidence, not just an intention to avoid names. Readers should be able to tell whether analytics is optional, what disabling it changes and whether a separate third-party provider may receive data from their device.

Marketing technologies may record whether an advert was viewed, a link was followed or a campaign resulted in a visit. Some can build profiles across websites or devices. These uses deserve especially clear notice because they are not required simply to display public pages or maintain a signed-in session. The site owner should identify the advertising partners actually engaged and ensure that user choice is respected where applicable. A tracking pixel must not be hidden under a vague term such as website improvement. Readers should also understand that declining optional tracking need not remove all advertising; it may change whether adverts are personalised or measured using identifiable signals.

A first-party cookie is normally associated with the website being visited, while a third-party component may involve another service provider. This technical distinction does not decide whether data is personal or whether consent is required. A third-party script may receive information as soon as a page loads, before a user clicks a visible button. Conversely, some externally supplied services can be configured to minimise data flows. The operator should check scripts, embedded content, app modules and server-side integrations rather than relying only on what appears in the browser’s cookie list. The final notice should identify meaningful third-party categories and link to provider documentation where that genuinely helps users.

Where optional tracking relies on consent, people should receive a real choice before the relevant technologies activate. A clear explanation should distinguish necessary functions from analytics and promotional uses instead of treating all categories as one mandatory bundle. Rejecting optional cookies should be straightforward, and withdrawing consent should be reasonably accessible. Do not claim that a specific cookie banner or preference centre exists before checking the production website. The owner must document the consent design actually implemented, including what happens when a visitor takes no action. Acceptance should not be inferred from silence or from scrolling past a notice when valid consent is required.

Most modern browsers let users inspect stored site data, block some third-party cookies, clear records or use private browsing modes. Menu names differ by browser and can change after software updates, so the cookie notice should not depend on one rigid set of clicks. Removing all site data may sign a user out and erase saved preferences. Device-level privacy controls can also limit advertising identifiers, but they do not necessarily block every tracking method. People should understand that changing settings in one browser may not update another browser or app. A site preference tool, when present, should complement rather than replace independent browser controls.

A login-related cookie may help connect authenticated requests with an active session. It should be protected against common session risks and used only as necessary for the authorised function. Logging out can invalidate access without instantly deleting every browser record. The actual behaviour depends on technical configuration, so a blanket assurance about complete removal should be avoided. Users should sign out of shared devices, avoid saving passwords on public computers and check for imitation websites before providing credentials. A cookie notice should explain that authentication storage has a different purpose from advertising trackers. Mixing those categories makes it harder to understand which features a person can realistically decline.

A mobile browser and a dedicated application do not necessarily store information in the same way. An app may use local storage, secure account tokens, crash reports or operating-system identifiers, while the browser may rely on conventional cookies. The final policy must distinguish these systems if both are offered. Simply copying a desktop cookie table into an app notice may omit important software components. Users should be told which settings control optional functions and which settings are managed by Android, iOS or the service itself. An application should request permissions only for legitimate documented purposes, and the notice should not claim to use a permission merely because it is common among other apps.

Interactive games may use technology from a game supplier or a separately hosted interface. Such components can create technical records needed for loading a session, applying preferences or diagnosing errors. Whether the supplier can identify a player, access a device identifier or use information for other purposes depends on the integration. The operator should review game-provider contracts and scripts instead of suggesting all games use identical storage. A high-frequency game can generate many events, but event volume alone does not show why each record is retained. The final notice must clearly separate operational game data from optional marketing analytics and provide provider-specific details when those details are required.

Payment journeys can involve a bank, mobile-money service or other provider whose interface uses its own security markers. Fraud-prevention mechanisms may analyse patterns to identify suspicious activity, but the precise inputs and decisions must be verified. These records should not be casually described as advertising cookies simply because they record a device or event. Nor should a security label excuse indefinite storage or undisclosed data sharing. When a user leaves the site for a payment service, the provider’s separate privacy and cookie explanations may become relevant. The notice should make the boundary clear and identify which parts of the process are controlled by the website operator.

An accurate cookie table should be based on testing rather than assumptions. The owner should inspect the site before consent, after consent, during login and after logout, using relevant devices and browsers. Each entry needs a recognisable name, provider, purpose, category and lifespan. The same review should examine local storage and network requests for non-cookie trackers. Repeat testing when plugins, advertising campaigns, payment services or game integrations change. The page should display an effective date and refer to a maintained inventory. Avoid inserting sample cookie names into a live policy because readers may mistake hypothetical examples for an actual technical disclosure.