Cookie Policy
This Cookie Policy explains how MekaVerse NFT uses cookies and similar storage or access technologies when you visit mekaverse-nft.com or interact with its forms, verification interfaces and embedded services.
1. Purpose of this Policy
This Policy provides information about technologies that may store information on your browser or device, or access information already stored there, when you use the MekaVerse NFT Website.
It should be read together with our Privacy Policy, which explains how personal information collected through the Website is processed.
The technologies actually activated during a visit may depend on your consent choices, browser settings, the pages you access and the Website functions you use.
2. What cookies are
A cookie is a small data file that a website places on or reads from a browser or device. Cookies can contain identifiers, preferences, security information, session information or records of how a website is used.
Cookies do not normally contain an entire document or software program. They may, however, contain an identifier that can be connected with other information.
Cookies can be used to:
- maintain a secure Website session;
- remember consent and privacy choices;
- protect forms against abuse or automated submissions;
- remember selected settings;
- measure Website performance and usage;
- support external media or embedded tools;
- provide advertising or audience-measurement functions.
3. Similar technologies
The legal rules applying to cookies may also apply to other technologies that store information on or access information from a user’s device.
These technologies may include:
- local storage and session storage;
- tracking or measurement pixels;
- software development kits;
- scripts, tags and embedded code;
- link decoration or navigational identifiers;
- device or browser fingerprinting techniques;
- cached identifiers;
- embedded media and external widgets.
References to “cookies” in this Policy include these similar storage and access technologies where appropriate.
4. Why we use these technologies
MekaVerse NFT may use cookies and similar technologies to operate, protect, improve and understand the Website.
The principal purposes may include:
- delivering pages and essential Website functions;
- maintaining security and preventing fraudulent activity;
- processing contact, verification and tokenization forms;
- remembering privacy and cookie consent selections;
- maintaining user-interface preferences;
- understanding technical errors and Website performance;
- measuring which pages and guides are used;
- displaying authorised third-party content;
- supporting integrations selected for an NFT project.
We aim to limit cookie use to technologies that are proportionate to the relevant Website function.
5. Strictly necessary technologies
Strictly necessary technologies support functions that are required to provide a Website feature requested by the user, maintain security or record privacy choices.
They may be used to:
- deliver Website pages and maintain technical sessions;
- protect forms against spam, fraud or malicious requests;
- remember cookie consent or rejection choices;
- balance Website traffic and maintain service availability;
- support authentication where a protected function is introduced;
- maintain shopping, payment or transaction steps where applicable;
- protect the Website against cross-site request attacks;
- apply security and network-management controls.
Where a lawful exception applies, these technologies may operate without optional consent because disabling them could prevent the requested function or undermine Website security.
Strictly necessary technologies are not used merely because they are convenient for MekaVerse NFT.
6. Preference technologies
Preference technologies remember selections that affect how the Website appears or behaves.
They may remember:
- language or regional preferences;
- interface and accessibility settings;
- previously selected Website options;
- form or navigation preferences;
- display settings for embedded content.
Depending on the function and applicable legal exception, preference technologies may require consent before they are used.
When preference technologies are disabled, the Website may still function, but selected settings may need to be entered again.
7. Analytics technologies
Analytics technologies help us understand how visitors use the Website and whether pages are functioning as intended.
Analytics information may relate to:
- pages viewed and navigation paths;
- approximate visit duration;
- referral source;
- browser, device and operating-system type;
- general geographic region derived from technical data;
- loading performance and technical errors;
- interaction with forms, links and Website features.
Where consent is required, analytics technologies will not be activated until the relevant choice has been made.
Analytics reports may use aggregated or pseudonymised information, but identifiers may still constitute personal information where they can be connected with an identifiable user.
8. External content and integrations
Some Website pages may connect to external tools or resources, including blockchain explorers, NFT marketplaces, media players, social platforms, maps, payment tools or technical widgets.
Loading external content may allow the third-party provider to receive technical information or place its own cookies.
External integrations may process:
- IP address and browser information;
- device and operating-system information;
- the referring Website page;
- external-account or platform identifiers;
- interaction with embedded content;
- public blockchain or wallet information entered by the user.
Where required, optional external content should remain blocked until the relevant consent category is accepted.
Opening an external link may take you to a separate service governed by that provider’s own cookie and privacy policies.
9. Advertising technologies
The Website does not need advertising technologies to provide its essential tokenization, verification or contact functions.
If advertising, retargeting or cross-site audience technologies are introduced, they may be used to:
- measure advertising campaigns;
- limit how frequently an advertisement is displayed;
- create or use audience segments;
- connect Website activity with an advertising platform;
- measure actions following an advertisement;
- display content based on previous online activity.
Such technologies will be treated as non-essential and will require the appropriate prior consent where required by law.
Rejecting advertising technologies will not prevent access to the core public Website content.
10. Cookie category summary
The following table describes the main categories that may be relevant to the Website. It does not claim that every category is active during every visit.
| Category | Typical purpose | Consent position | Typical duration |
|---|---|---|---|
| Strictly necessary | Security, session operation, form protection, traffic management and consent-choice storage. | May operate without optional consent where a lawful exception applies. | Session-based or retained only for the period needed for the relevant essential function. |
| Preferences | Remembering language, interface or display choices. | Consent may be required unless a lawful exception applies to the requested function. | Session-based or retained for a limited preference period. |
| Analytics | Measuring Website use, performance, navigation and technical errors. | Disabled until consent where consent is required. | Varies according to the analytics configuration and provider. |
| External content | Loading media, maps, explorers, widgets or other third-party resources. | May require consent before external content is loaded. | Determined partly by the relevant third-party provider. |
| Advertising | Campaign measurement, retargeting or audience profiling. | Non-essential and subject to prior consent where required. | Varies according to the advertising provider and campaign configuration. |
The precise technologies in use may change when Website plugins, hosting, security tools or approved external integrations are updated.
11. Session and persistent cookies
11.1 Session cookies
Session cookies are generally temporary and are removed when the browser session ends. They may support navigation, security or a temporary Website process.
11.2 Persistent cookies
Persistent cookies remain on the browser or device after the session ends until their expiry date, deletion by the user or removal by the relevant service.
They may remember consent, preferences, analytics identifiers or other settings over multiple visits.
Retention periods should be limited to what is appropriate for the purpose of the technology.
12. First-party and third-party cookies
12.1 First-party cookies
First-party cookies are set through the domain that you are currently visiting. They may support Website operation, security, preference storage or first-party measurement.
12.2 Third-party cookies
Third-party cookies are set or controlled by an external service connected to the Website.
They may be associated with:
- embedded media;
- analytics providers;
- payment services;
- blockchain explorers or NFT platforms;
- social networks;
- security and anti-abuse services;
- advertising platforms.
Third-party providers determine some of their own cookie purposes, retention periods and processing practices.
13. Consent and lawful exceptions
Where consent is required, MekaVerse NFT should request it before the relevant non-essential technology stores or accesses information on the user’s device.
Consent should be:
- freely given;
- specific to the relevant purpose;
- informed by clear information;
- indicated through an affirmative choice;
- capable of being withdrawn.
Continuing to browse without making an affirmative choice is not treated as consent to non-essential cookie categories.
Rejecting non-essential technologies should be available without preventing access to ordinary public Website content.
Consent is not required where a valid legal exception applies, such as a technology that is strictly necessary to provide a function expressly requested by the user.
A technology is not automatically “strictly necessary” merely because it is useful for analytics, commercial optimisation or general business convenience.
14. Managing your choices
Where a cookie preference interface is available, you may use it to accept, reject or change non-essential cookie categories.
Your options may include:
- accepting all optional categories;
- rejecting all optional categories;
- selecting individual purposes;
- withdrawing previously provided consent;
- reviewing information about active categories.
Changing your choice does not make earlier lawful processing unlawful. It should prevent future use of the relevant optional technologies after the preference is applied.
Some third-party information already received before consent was withdrawn may be retained under that provider’s own lawful retention rules.
15. Browser and device settings
Most browsers allow users to view, delete, block or restrict cookies through their privacy or security settings.
Browser controls may allow you to:
- delete existing cookies;
- block all cookies;
- block third-party cookies;
- allow cookies only for selected websites;
- remove local-storage information;
- clear browsing data when the browser closes;
- send supported privacy preference signals.
The available steps depend on the browser, operating system and device. Refer to the official support information for the software you use.
Browser controls operate separately from any consent interface provided by the Website.
16. Effect of disabling technologies
Blocking optional cookies should not prevent access to the main public information on the Website.
However, blocking or deleting certain technologies may affect:
- remembered privacy or language settings;
- form security and submission processes;
- external media and embedded tools;
- protected or authenticated functions;
- payment or transaction steps;
- performance and error reporting;
- the ability to preserve choices between visits.
When a strictly necessary technology is blocked through browser settings, the relevant Website feature may not operate correctly.
17. Cookie consent records
Where consent is requested, we may maintain a limited record showing that a choice was made.
This record may include:
- the selected cookie categories;
- the date and time of the choice;
- the version of the consent information presented;
- a consent or preference identifier;
- limited technical information needed to demonstrate the choice.
Consent records are retained only for an appropriate period needed to respect preferences, demonstrate compliance and resolve relevant complaints.
The Website may request a renewed choice when technologies, purposes, providers or consent information change materially.
18. Personal information
Information collected through cookies may constitute personal information when it identifies a person directly or can reasonably be connected with other identifying information.
This may include:
- IP addresses;
- device or browser identifiers;
- online account identifiers;
- Website usage records;
- approximate location information;
- consent and preference records;
- external-platform identifiers.
Personal information collected through these technologies is processed in accordance with the Privacy Policy.
The lawful basis for subsequent processing may differ from the requirement to obtain consent before storing or accessing information on a device.
19. Third-party services
Third-party providers may update their own cookies, identifiers, retention periods and privacy practices independently.
MekaVerse NFT does not control every storage or access technology used after a user leaves the Website or independently activates an external service.
Before interacting with an external wallet, blockchain explorer, marketplace, media platform or payment service, review the provider’s:
- cookie policy;
- privacy notice;
- terms of service;
- security information;
- available opt-out controls.
A link or integration does not mean that MekaVerse NFT guarantees the third party’s compliance, security or continued availability.
20. Policy updates
We may update this Cookie Policy when Website technologies, plugins, service providers, legal requirements or business practices change.
The revised version will be published on this page with an updated “Last updated” date.
A renewed consent choice may be requested where an update introduces a materially different purpose or optional technology.
Users should review this Policy periodically for current information about Website storage and access technologies.
21. Contact
Questions about cookies, consent choices or the processing of information collected through Website technologies may be submitted through the official contact page:
When contacting us, describe the browser, device, Website page and cookie-related issue where relevant. Do not submit private keys, wallet recovery phrases, passwords or authentication codes.