سياسة ملفات تعريف الارتباط

1. Overview

This Cookies Policy explains how Onicore Technologies Ltd ("Onicore", "we", "us", "our") uses cookies and similar technologies on the website where this Cookies Policy is published (the "Website").

‍

Cookies can be useful and harmless (for example, keeping the Website secure or remembering a preference), but they can also be used for analytics and marketing. This policy is designed to be transparent and practical: it describes what we use, why we use it, and how you can control it.

If you are looking for the broader picture of how we handle personal data, please see the Privacy Statement in Document 2 of this pack.

‍

2. Who we are and how to contact us

Controller/operator (for Website cookies): Onicore Technologies Ltd (DIFC License No. CL11444)

Contact point for cookies and privacy

• Email: info@onicore.ae
• Telephone: +971 54 201 3311
• Address: IH-00-01-02-OF-01, Level 2, Innovation Hub 05, Dubai International Financial Centre, Dubai, United Arab Emirates

‍

If you contact us about cookies, it helps if you include:

• the web page you were visiting,
• the date and approximate time,
• the browser and device you used, and
• a screenshot of the cookie banner or settings page (if relevant).

‍

3. Quick practical summary 

• We use cookies and similar technologies to keep the Website working, secure, and measurable.
• Some cookies are strictly necessary and will be set automatically because the Website cannot function properly without them.
• Other cookies (for example, analytics and marketing cookies) are optional and are used only when enabled through your preferences, where required.
• You can manage cookies through our cookie banner and through your browser settings.

‍

4. Definitions used in this Cookies Policy

To keep language consistent across our legal documents, we use these key terms:

• Cookie: a small text file stored on your device by your browser when you visit a website.
• Similar technologies: technologies that store or read information on your device or interact with it, such as local storage, pixels, SDKs, tags, beacons, and scripts.
• First-party cookie: set by the Website domain you are visiting.
• Third-party cookie: set by another domain (for example, when we embed a video, analytics tool, or social media widget).
• Session cookie: exists only while your browser session is open and is deleted when you close the browser.
• Persistent cookie: remains until it expires or you delete it.
• Personal Data: information relating to an identified or identifiable natural person. Some cookie identifiers can be Personal Data when they can be linked to an individual.
• Controller and Processor: used in the same broad sense as under applicable data protection laws. For Website cookies, Onicore generally acts as the controller.

‍

5. What cookies are and how they work

When you open a website, the site can send a cookie to your browser. Your browser stores it and returns it to the site on later requests.

Cookies can store values such as:

• a randomly generated identifier,
• the fact that you accepted or declined a cookie category,
• language preferences,
• session state and security flags.

Cookies typically do not store "documents" or large amounts of data. They usually store short identifiers and preferences that help a website behave consistently.

‍

5.1 First-party and third-party cookies

• First-party cookies are set by Onicore (the Website domain) and are generally used for operation, preferences, and security.
• Third-party cookies are set by third parties whose tools are embedded on the Website (for example, analytics, customer support chat, video hosting, or social media).

Third-party cookies are controlled by third parties. We do not control the full lifecycle of third-party cookies, but we can decide whether to embed the relevant tools and we can provide settings and transparency where feasible.

5.2 Cookie attributes that matter

Some cookie attributes affect privacy and security:

• Secure: the cookie is transmitted only over HTTPS.
• HttpOnly: the cookie cannot be accessed by browser scripts (reducing the risk of theft through certain attacks).
• SameSite: helps control whether cookies are sent with cross-site requests.

As a general security practice, we aim to use Secure and SameSite attributes where appropriate, and HttpOnly for server-managed session cookies.

‍

6. Similar technologies we may use

The Website may use other technologies that are not "cookies" in a strict sense but can have similar effects.

Examples include:

• Local storage/session storage: browser storage that can retain preference values or state information.
• Pixels/tags/beacons: tiny resources that notify a server that a page was viewed or an action occurred.
• Scripts and SDKs: code used to run analytics, load fonts, provide embedded widgets, or enable performance monitoring.
• Server logs: when your browser requests a page, our servers may store a log entry (for example, time, URL, status codes, IP address, and user agent).

Where these technologies relate to an identified or identifiable person, they may constitute Personal Data and will be covered by our Privacy Statement.

‍

7. Why we use cookies and similar technologies

We use cookies and similar technologies for the following broad purposes:

7.1 Strictly necessary 

These cookies help the Website function and stay secure. Without them, the Website may not work properly.

Examples of use:

• maintaining a secure session (where the Website has gated areas),
• preventing fraud and abuse,
• load balancing,
• basic settings that are required to render pages correctly.

7.2 Preferences and functionality

These cookies support convenience and user experience.

Examples of use:

• remembering language and region,
• remembering cookie preferences,
• remembering selections in a form (where the Website provides such a feature).

7.3 Performance and analytics

These cookies help us understand how visitors use the Website, so we can improve performance, content, and navigation.

Examples of use:

• counting visits and traffic sources,
• understanding which pages are popular,
• diagnosing errors and slow pages,
• improving usability (for example, reducing confusing steps).

We aim to use analytics in a proportionate way. Where feasible, we consider settings that reduce data collection and avoid unnecessary identification.

7.4 Marketing, campaign measurement, and communications

These cookies help measure marketing campaigns and, where enabled, provide content that is more relevant.

Examples of use:

• knowing whether a visitor came from a particular campaign link,
• measuring conversions from a marketing page to a contact request,
• limiting the number of times an advertisement is shown (frequency capping) when used.

We do not intentionally use cookies to deliver marketing to children or to build sensitive profiles.

7.5 Product research and testing (A/B testing)

From time to time, we may run controlled tests to understand whether a page change improves clarity.

Examples of use:

• showing slightly different versions of a page to different visitors,
• measuring whether a page change improves performance or reduces confusion.

When testing goes beyond what is strictly necessary, we treat it as optional and handle it consistently with your preferences.

‍

8. Cookie consent and preference management

8.1 Cookie banner and settings

If the Website uses optional cookies, we may show a cookie banner and provide a cookie settings tool.

The cookie settings tool typically allows you to:

• accept all cookies,
• reject non-essential cookies,
• enable only selected categories.

8.2 Withdrawing consent and changing settings

You can change your cookie preferences at any time by:

• using the cookie settings tool (if available on the Website), and/or
• deleting cookies in your browser and revisiting the Website.

Please note:

• deleting cookies may reset your preferences,
• some cookies are necessary for the Website to function, and
• if you block all cookies, parts of the Website may not work.

8.3 Global privacy signals 

Some browsers and extensions provide privacy signals such as "Do Not Track" or the "Global Privacy Control" signal.

Because these signals are not implemented consistently across the industry, we treat them as an additional indicator rather than a universal standard. Where feasible, we will evaluate and support recognised signals in a practical way, especially where they align with consent management features of the Website.

‍

9. Cookie categories and examples

The cookies used on a website can change over time depending on features, integrations, and updates.

For transparency, we use a category model. Below are typical examples. The exact cookies in use should be shown in our cookie banner or cookie register where available.

9.1 Strictly necessary cookies

Typical examples include:

• Cookie preference storage (for example, storing that you have made a choice)
• Security cookies (for example, preventing cross-site request forgery)
• Load balancing cookies (for example, routing traffic to keep the site stable)

These cookies are usually set automatically because the Website cannot function properly without them.

9.2 Preference and functionality cookies

Typical examples include:

• language selection
• region settings
• remembering UI settings (for example, collapsed navigation)

9.3 Analytics cookies

Typical examples include:

• a random identifier used to recognise a returning browser (not necessarily a named person)
• page view counts
• event tracking for interactions (for example, clicking a "Contact" button)

We may use either first-party analytics or third-party analytics tools. Where third-party tools are used, they may also set their own cookies.

9.4 Marketing cookies

Typical examples include:

• campaign measurement cookies (for example, to determine that a visitor came from an advertising platform)
• remarketing cookies (for example, to show follow-up ads in third-party networks)

Marketing cookies are optional and, where applicable, are enabled only after you allow them.

9.5 Embedded content cookies (third-party)

If we embed content such as:

• videos,
• maps,
• social media posts,
• interactive forms hosted by third parties,

the embedded provider may set cookies and collect data through their own tools. We treat these as third-party cookies and, where feasible, we provide choice controls and transparency.

‍

10. Cookie register and transparency

To improve transparency, we aim to maintain a cookie register. Because cookies can change, we treat the cookie register as a "living list".

10.1 Example cookie register template

The table below is an example format. The actual cookies in use should be confirmed by a technical scan and a review of your current vendors.

• Cookie name / identifier
• Provider (first-party or third-party vendor)
• Purpose
• Category (necessary, functional, analytics, marketing)
• Duration (session or number of days/months/years)
• Notes (for example, whether it is essential, whether it uses cross-site tracking)

10.2 Example entries

These entries are examples of what a cookie register might look like. They may not reflect the cookies actually in use on your Website.

• Cookie name: cookie_preferences
  Provider: first-party (Onicore)
  Purpose: store cookie category choices
  Category: strictly necessary
  Duration: 6 to 12 months (typical)
• Cookie name: session_id
  Provider: first-party (Onicore)
  Purpose: maintain secure session state for logged-in areas
  Category: strictly necessary
  Duration: session
• Cookie name: analytics_id
  Provider: analytics tool (first or third-party)
  Purpose: measure Website usage and performance
  Category: analytics
  Duration: 1 day to 24 months (varies by tool and configuration)

‍

• Cookie name: campaign_source
  Provider: first-party or marketing tool
  Purpose: attribute visits to campaigns (where enabled)
  Category: marketing
  Duration: 7 to 90 days (varies)

‍

11. How to manage cookies in your browser

Most browsers allow you to:

• view cookies,
• delete cookies,
• block all cookies,
• block third-party cookies,
• set rules for specific sites.

Because browser interfaces change over time, we recommend using the official help pages of your browser.

General guidance:

• If you disable cookies completely, the Website may not function correctly.
• If you block third-party cookies, embedded content or analytics may not work as expected.

11.1 Common browser settings areas

You typically find cookie controls in areas such as:

• "Privacy and security"
• "Site settings"
• "Cookies and site data"
• "Tracking prevention"

‍

12. Mobile devices, in-app browsers, and apps

If you access the Website through:

• an in-app browser (for example, within a social media app), or
• a managed corporate device,

cookie controls may behave differently. Some in-app browsers have their own privacy settings.

If you use Onicore services through a dedicated application (if any), app analytics and SDK permissions may be controlled through the app settings and your device operating system.

‍

13. Third-party providers and embedded features

We may use third-party providers for functions such as:

• website hosting and content delivery networks (CDNs),
• security services (for example, to reduce bots and abuse),
• analytics,
• communications tools (for example, forms, CRM, newsletters),
• customer support chat.

Third-party providers may process information on our behalf as processors, or may process information as independent controllers depending on the tool and the context.

We aim to:

• select vendors with appropriate privacy and security practices,
• configure tools in a privacy-conscious way where feasible, and
• use contracts and safeguards as appropriate.

‍

14. International transfers and cross-border processing

The internet is global. Depending on our hosting, vendors, and team locations, cookie data and related identifiers may be processed outside the DIFC or outside the United Arab Emirates.

Where Personal Data is transferred internationally, we implement safeguards consistent with our Privacy Statement, including contractual and organisational measures where appropriate.

‍

15. Changes to this Cookies Policy

We may update this Cookies Policy to reflect:

• changes to the Website,
• changes to our vendors or tools,
• changes in applicable laws or guidance, or
• improvements in transparency and user choice.

We will update the "Last updated" date at the top of this document when we make changes.

If a change materially affects how we use optional cookies, we may also provide additional notice on the Website.

‍

16. Questions, requests, and complaints

If you have questions about cookies, you can contact us using the details above.

If your request concerns Personal Data, you may also have rights under applicable data protection law. Please see our Privacy Statement.

Where applicable, you may have the right to raise concerns with the DIFC Commissioner of Data Protection.

‍

17. Legal and guidance references 

This Cookies Policy is prepared with reference to:

• DIFC Data Protection Law, DIFC Law No. 5 of 2020 (as amended)
• DIFC Data Protection Regulations (Consolidated Version No. 2, in force on 1 September 2023)
• DIFC Commissioner of Data Protection guidance and publications (where relevant)
• Relevant UAE federal laws where applicable (for example, cybercrime and consumer protection)
• Recognised international best practices on consent management and transparency

A consolidated list with official sources is provided in Appendix A.

‍