About this Policy
This Cookie Policy explains how Malaka may use cookies and similar technologies across its website and platform surfaces. It describes the categories of technology that may be involved, how you can review and manage optional preferences where applicable, and where the verified list of technologies actually in use will appear once confirmed.
This document focuses specifically on cookies and similar technologies. Broader information about how personal data is collected and processed is covered in the Privacy Policy.
This page describes the types of browser and device technologies Malaka may use and how you can manage optional ones. The exact list must be confirmed against the live product before publication.
Final wording must reflect the verified production implementation and applicable law. [Final legal/privacy wording to be approved.]
What cookies are
Cookies are small pieces of information that a website can store or read through a browser. They are commonly used for functions such as maintaining a session, remembering preferences, or measuring how a site is used.
A cookie generally holds a small amount of data associated with a website and the browser being used. Depending on its purpose and settings, a cookie may last only for the duration of a browsing session or may persist for a defined period.
[Final legal/privacy wording to be approved.]
Similar technologies
Beyond cookies, websites and apps may use other technologies to store or read information on a device. These can include:
- local storage and similar browser storage mechanisms;
- pixels or similar embedded markers;
- software development kits (SDKs) in mobile contexts;
- other similar browser or device technologies.
Throughout this Policy, references to "cookies" should be read as including these similar technologies where relevant. Which of these Malaka actually uses is not asserted here.
[Actual technologies used by Malaka to be verified.]
How Malaka may use them
Where these technologies are used, they may serve purposes such as keeping you signed in, supporting the security and technical delivery of the platform, remembering choices you make, or helping understand how the product is used in aggregate.
The specific purposes that apply to Malaka, and whether each is essential or optional, depend on the technologies actually deployed. Those details belong to the verified inventory and are marked accordingly below.
[Actual purposes and technologies to be confirmed from the production implementation.]
Cookie categories
Cookies and similar technologies are commonly grouped into high-level categories. The categories below describe the model Malaka's inventory will follow. Optional categories are only applicable if enabled in the production implementation.
Strictly Necessary / Essential
RequiredNeeded for core technical operation and security where applicable. These cannot be switched off in the preference centre because the platform relies on them to function.
Preferences / Functionality
Optional where applicableRemember choices such as language, region or display, if such technologies are used. Only applicable if enabled in the production implementation.
Analytics / Measurement
Optional where applicableHelp understand aggregate product and site usage, if such measurement is enabled. Only applicable if enabled in the production implementation.
Marketing / Advertising
Not confirmedAdvertising or personalisation technologies, if used. [Not confirmed for this prototype] — no advertising or retargeting technology is assumed.
Essential cookies
Essential technologies are those a platform may need to operate and to keep users secure. Depending on the actual implementation, possible purposes in this category can include:
- authentication and session continuity;
- security;
- load balancing and technical delivery;
- remembering your privacy choices.
These are examples of the kinds of purposes that may fall into this category. The actual essential technologies, their names and durations belong to the verified inventory and are not invented here.
If a technology is truly essential, the platform may not work correctly without it, so it is not offered as an optional toggle.
Preference cookies
Preference technologies, where used, remember non-essential choices to make the experience more convenient. Possible purposes can include remembering:
- language;
- region;
- display preferences;
- other remembered non-essential choices.
These are examples only. This Policy does not claim that Malaka currently uses preference technologies; that must be confirmed from the production implementation.
Analytics cookies
Analytics technologies, where used, help understand aggregate product and site usage so the experience can be improved. This Policy does not name any specific analytics provider, and does not claim any particular measurement, anonymisation or aggregation behaviour.
If analytics are enabled in production, the specific provider, purpose, data handled and duration must be documented in the verified inventory.
Provider-neutral until confirmed. [Analytics provider(s) and behaviour to be verified.]
Marketing cookies
Marketing / advertising technologies — [Not confirmed for this prototype]
This Policy does not assume that Malaka uses advertising or retargeting technologies. This category is presented as conditional. If no implementation data is supplied, no vendors are listed and none should be inferred.
[Whether any marketing or advertising technologies are used to be confirmed.]
Third-party technologies
First-party vs third-party
A first-party cookie is set by the website you are visiting. A third-party cookie is set by a different domain, typically a connected service embedded in or used by the site. Whether any given technology is first- or third-party depends on the actual implementation, and no specific provider relationships are claimed here.
Connected service categories
A marketplace platform may connect to service categories such as:
- payments;
- maps;
- identity verification;
- analytics;
- media;
- communications.
The presence of a service category does not imply it sets cookies.
Whether a connected service places or accesses cookies must be confirmed from the actual implementation and provider documentation.
Payments
NeutralProvider-neutral. No payment provider is named, and payment-related storage is not claimed to be essential unless verified.
Maps
NeutralNo mapping provider is assumed. If maps are embedded in production, their cookie and storage behaviour must be verified.
Identity verification
NeutralNo identity provider is claimed to set cookies. Implementation placeholder only.
Media & embedded content
NeutralIf external media, maps or social content is embedded in future, its storage and cookie behaviour must be documented from the actual integration.
Cookie inventory
The table below defines the structure of the published cookie inventory. It is presented in an empty state because no verified production cookie inventory has been supplied. The columns remain visible to show the required structure. Use the scenarios control to preview an example structure — every example row is explicitly marked and is not a production cookie.
Inventory preview
Production cookie inventory pending verification
Before publication, this table must be populated from the actual deployed site and connected third-party services. Verified production cookie inventory has not yet been supplied.
| Name | Provider | Purpose | Category | First / third party | Duration | Status |
|---|---|---|---|---|---|---|
| [Cookie name] | [Provider] | [Purpose] | [Category] | [First / third] | [Duration] | Pending verification |
No verified production cookie inventory has been supplied. This is preferable to placeholder data being mistaken for real cookies.
When a verified row exists, a detail view can present: name, provider, domain, purpose, category, first/third party, duration, when set, data accessed or stored, and preference dependency. In this prototype, placeholder data only.
Consent history is part of the production privacy implementation and is not represented in this prototype.
Managing your choices
Where consent or preferences apply, you can review and manage optional categories in the cookie preference centre. Optional categories are off by default. Essential technologies remain active because the platform relies on them and they are not offered as optional toggles.
The preference centre distinguishes a control surface (where you make choices) from this Policy (which explains the technologies). Opening it does not change any production setting in this prototype.
[Legal basis and consent requirements for each category to be confirmed based on actual technologies and applicable jurisdictions.]
Prototype only — this preference control is not connected to Malaka's production consent system. No production consent preference is changed here.
Browser controls
Most browsers provide their own controls for blocking or deleting cookies and clearing stored site data. These controls are separate from Malaka's preferences and are usually found in the browser's settings or privacy sections.
Because browser interfaces change over time, this Policy does not provide version-specific instructions. Your browser's help resources describe how to view, block and remove cookies for the browser and version you use.
Blocking or deleting some browser storage may affect how parts of the site function. This is described cautiously because the specific effects depend on the verified implementation.
Changes to this Policy
This Policy may be updated to reflect changes in the technologies used or in applicable requirements. When it changes, the version and dates shown at the top and bottom of this page will be updated.
[Policy update process to be provided.]
Contact
For questions about this Cookie Policy or cookie-related choices, use the contacts below once confirmed. Requests to access, correct or delete personal data are handled separately — see Data & Account Requests (Page 104).
Privacy contact
[To be provided]
Cookie / privacy questions
[To be provided]