Cookie Policy
Controller: AdWave LTD
Company Number: HE 380370
Date of Incorporation: 23 February 2018
Registered Address: Eleftherias 113, 3042, Limassol, Cyprus
Website: https://adskill.com
Cookie and Privacy Contact: info@adskill.com
Last Revised: 14 August 2026
This Cookie Policy explains how AdWave LTD, operating under the adskill brand (“AdWave”, “adskill”, “we”, “us” or “our”), uses cookies, local storage, pixels and comparable technologies on adskill.com (the “Website”). It describes the purposes for which these technologies are used, the providers that may place or access them, the choices available to Website visitors and the way those choices can be changed later. This Policy concerns technologies used on the Website itself. The operation of advertising accounts and campaign environments provided as part of adskill services is addressed separately in the Privacy Policy and the relevant service documentation.
Some Website technologies store or retrieve identifiers or technical information that can qualify as personal data when they relate to an identifiable device or individual. Where that occurs, the handling of the resulting personal data is also governed by the adskill Privacy Policy. This Cookie Policy should therefore be read together with that document.
1. Cookies and similar technologies
A cookie is a small text file stored by a browser when a website is visited. Similar technologies can perform comparable functions without using a conventional browser cookie. They include local and session storage, pixels, tags, scripts and provider-generated identifiers. Some technologies are placed directly through the adskill domain, while others are supplied by third-party services integrated into the Website.
These technologies can be used to keep the Website secure, remember a visitor choice, maintain language or interface functionality, measure how the Website is used, attribute visits to marketing sources, understand the effectiveness of our communications and support advertising or audience-measurement functions. The legal treatment depends on the purpose and on whether the technology is necessary for the service requested by the visitor.
2. How we classify Website technologies
We use a purpose-based classification so that visitors can understand what a technology does before making a choice. Strictly necessary technologies support functions such as security, fraud and bot prevention, request integrity and the storage of consent preferences. They are required for the relevant Website function and are not used by adskill as a substitute for optional analytics or advertising.
Functional technologies support additional Website features such as language, presentation or interface behaviour. Analytics and measurement technologies help us understand visits, traffic sources, page interaction, performance and the effectiveness of Website improvements. Advertising and attribution technologies can be used to measure marketing sources, support audience or campaign measurement, limit duplication, or enable advertising-related functions provided by third parties. Social and embedded technologies may be used where Website content or functionality relies on an external social or media service.
Where a technology has more than one technical function, we classify it by the purpose for which adskill enables it on the Website. A provider may process the information it receives for additional purposes under its own terms where it acts independently. Those independent activities are governed by the provider’s privacy documentation and applicable law.
3. Consent and Cookie Preference Center
Non-essential technologies that require prior consent under applicable law are intended to remain inactive until the visitor makes a permitted choice through the Website cookie banner or Cookie Preference Center. The preference mechanism allows a visitor to accept non-essential technologies, reject them, or select the categories that the visitor is willing to enable. Strictly necessary technologies remain active to the extent they are required to deliver the Website, maintain security, protect forms, remember the visitor’s privacy choices or provide another function requested by the visitor.
A visitor can change or withdraw a previous choice through the Cookie Preference Center made available on the Website. Withdrawal applies to future use of the relevant non-essential technologies and does not invalidate processing that was lawful before the preference was changed. Where a provider has already stored a cookie on the browser, changing the Website preference can stop further use by adskill but the visitor may also need to delete the existing cookie through browser settings if immediate removal is desired.
Consent is requested separately from ordinary access to Website information. Rejecting analytics, advertising or other optional categories does not prevent a visitor from viewing the ordinary public content of adskill.com, although a feature that depends on a particular optional technology may not operate in the same way.
4. Current technology register
The register below summarizes the principal cookies and similar technologies identified in the current Website configuration. Provider-generated names may contain changing suffixes, account numbers or session values. For that reason, technically related identifiers are grouped where they perform the same function. Durations are approximate because a provider or browser can change technical behaviour, delete storage earlier, or refresh an identifier when the Website is used again.
| Category | Technology / family | Provider | Purpose | Typical duration |
| Necessary | TERMLY_API_CACHE | adskill / Termly | Stores the visitor’s consent result and supports the operation and performance of the cookie preference mechanism. | About 1 year |
| Necessary | csrf_token | adskill / Django | Protects Website requests against cross-site request forgery and related malicious activity. | About 30 days |
| Necessary | _GRECAPTCHA, _grecaptcha, rc::a, rc::f, ri-* | Google reCAPTCHA / adskill | Supports bot detection, form protection, fraud prevention and risk analysis. | Session, persistent, or up to about 6 months depending on the mechanism |
| Functional | wpEmojiSettingsSupports; wp-wpml_current_language | adskill website components | Supports presentation functions such as emoji capability and the current Website language. | Session |
| Analytics | _ga; _ga_* | Google Analytics | Measures visits and sessions and produces Website-usage statistics used to understand performance and visitor interaction. | Up to about 13 months |
| Analytics | _ym_uid; _ym_d; _ym_isad; _ym_visorc; __ym_tab_guid; _ym* request or storage identifiers; counter pixel 89870949 | Yandex Metrica | Measures traffic and user interaction, supports session analysis and helps assess Website and marketing performance. | From session storage to about 12 months or persistent storage, depending on the identifier |
| Analytics | AMP_*; EXP_* | Amplitude | Supports product and Website analytics, technical configuration and experimentation or measurement functions where enabled. | Persistent storage or up to about 12 months, depending on the identifier |
| Analytics / attribution | utm_*; sbjs_* | adskill / source-attribution components | Records marketing-source and referral information so that visits, enquiries and Website performance can be attributed to their source. | From session or 30 minutes to about 6 months; some local-storage values may persist |
| Advertising / measurement | yandexuid; yuidss; ymex; yabs-sid; bh; sync_cookie_csrf; _ym_synced; _ym_retryReqs; i | Yandex services | Supports advertising-related measurement, identifier synchronization, delivery diagnostics and related provider functionality. | From about 10 minutes or a session to longer provider-controlled periods; some identifiers may persist for several years |
| Social / integration | remixlang | VK | Supports VK-related integration and language or social functionality where the relevant third-party component is used. | About 12 months |
The register intentionally groups dynamic storage keys and related provider identifiers where the underlying purpose is the same. Transient network requests and pixels that do not create a separate stored identifier can also form part of the same analytics, security or advertising function. We review the register when Website integrations change and update the Policy where a material new purpose, provider or category is introduced.
5. Third-party providers and information access
Some of the technologies listed above are supplied by external providers, including providers of consent management, security, analytics, advertising measurement, social functionality and technical infrastructure. When a third-party technology is enabled, the provider may receive information such as an IP address, browser or device characteristics, page or event information, approximate location derived from technical signals, referral information and the identifier associated with the relevant cookie or storage mechanism.
AdWave uses third-party technologies for the Website functions for which they are enabled and limits optional providers through the consent mechanism where prior consent is required. A third-party provider can act as our processor for a particular activity, as an independent controller for its own processing, or in another role determined by the actual arrangement. Information about AdWave’s handling of personal data, service providers and international transfers is available in the Privacy Policy. Visitors should also review the privacy information published by Google, Yandex, Amplitude, VK, Termly and any other provider whose service they choose to enable or use.
6. Browser, device and provider controls
The Cookie Preference Center is the primary Website mechanism for controlling optional technologies. Browser and device settings provide an additional layer of control. Most browsers allow users to view stored cookies, delete them, block all or selected cookies, or restrict third-party storage. Similar controls can exist for local storage, tracking prevention and privacy permissions. The location and effect of these settings vary by browser and software version.
Blocking all cookies at browser level can remove or prevent strictly necessary storage as well as optional storage. This can affect form protection, language settings, security controls or the ability of the Website to remember a consent choice. Provider-level advertising or privacy settings may also be available through the relevant provider, but those settings operate independently of the adskill Cookie Preference Center.
7. Retention of technology data and consent records
The technical lifetime of a cookie or local-storage item is shown in the register where it can be stated with reasonable accuracy. A session technology normally expires when the relevant browser session ends, while a persistent technology remains until its stated expiry, replacement or deletion by the user or provider. A provider can refresh an identifier when the Website is revisited, which can affect its practical lifetime.
Information derived from Website technologies can be retained separately from the cookie itself where necessary for analytics, security, fraud prevention, reporting, evidence of consent or other purposes described in the Privacy Policy. We do not treat the expiry of a browser cookie as an automatic retention period for every server-side record generated from that technology. Retention of personal data is instead governed by the purpose, legal basis and retention criteria described in the Privacy Policy.
We may retain a limited record of a visitor’s consent or refusal so that the preference can be respected and, where necessary, demonstrated. That record can include the chosen categories, the time of the choice and a technical identifier associated with the consent-management mechanism.
8. Relationship with the Privacy Policy
Cookies and similar technologies can generate information that is personal data under the GDPR or other applicable data-protection rules. The Privacy Policy explains the identity and role of AdWave, the purposes and legal bases for personal-data processing, categories of recipients, international transfers, retention principles, security measures and the rights available to individuals. Where this Cookie Policy describes a Website technology and the Privacy Policy describes the resulting personal-data processing, both documents apply together.
9. Changes to this Cookie Policy
Website integrations and provider technologies change over time. We may revise this Cookie Policy when we add or remove a provider, change a technology’s purpose, alter the consent mechanism, or need to reflect a legal or operational development. The current version is published on adskill.com and states the date of its latest revision. Where a change requires a new consent choice under applicable law, the relevant optional technology will not be relied upon on the basis of an earlier choice that is no longer sufficient for the changed purpose.
10. Contact
Questions about the technologies used on adskill.com, the operation of the Cookie Preference Center or the processing of personal data associated with Website technologies can be sent to info@adskill.com. Please include enough information for us to understand the issue or request and avoid sending unnecessary sensitive information.
AdWave LTD
Company Number: HE 380370
Registered Address: Eleftherias 113, 3042, Limassol, Cyprus
Brand: adskill
Website: https://adskill.com
Cookie and Privacy Contact: info@adskill.com