Accelerate Your Digital Transformation: Data Mesh Implementation Roadmap

Accelerate Your Digital Transformation: Data Mesh Implementation Roadmap

Dorota Owczarek - July 30, 2023

Data management is evolving rapidly, with the concept of a data mesh revolutionizing how we understand and use our data. This shift towards a data mesh architecture decentralizes data governance, treating data as a product rather than storing it in traditional data warehouses. But how does this transition work, and what does it mean for your business?

In this article, we unpack the principles of a data mesh and provide a comprehensive, step-by-step guide to its successful implementation. From assembling your data platform team and promoting domain ownership, to scaling your data product catalog and refining your data mesh approach, each stage of this journey is vital to accelerating your digital transformation.

So whether you’re a business leader, a data product owner, or part of a domain team, join us as we navigate the data mesh world, equipping you with the knowledge to implement this innovative approach in your organization successfully.


Data mesh is an innovative data architecture that promotes a decentralized approach, treating data as a product. It’s an ideal solution for large enterprises struggling with monolithic and siloed data systems.

Your journey to data mesh implementation starts with building a team. It’s crucial to form an enabling team with members from across different domains, fostering collaboration and shared responsibility.

Next, focus on setting up a self-service data platform and defining an initial set of data products. This pilot phase allows you to gain buy-in from stakeholders, test the process, and showcase the potential of the data mesh approach.

Scale your data product catalog and enhance your self-service data platform iteratively, expanding the data mesh to cover more domains. Foster a culture of data ownership, encouraging domain experts to define and manage their data products.

As your data mesh matures, nurture it through clear governance and data stewardship practices. Regularly monitor and refine the data mesh, incorporating user feedback and business needs.

Embrace an agile mindset and culture of continuous improvement to keep refining your data mesh. Leverage cutting-edge technologies, and foster a thriving, data-driven culture in your organization.

Remember, the transition to data mesh architecture is organic and agile. It doesn’t require refactoring every system, rather, integrate your existing systems into the data mesh where it makes sense.

Implementing a data mesh is a transformative journey, one that requires careful planning, commitment, and expertise. At nexocode, our data architects have extensive experience in implementing scalable data platforms and are ready to guide you through your data mesh journey. Contact us today to start exploring the power of data mesh for your organization.

Embracing the Data Mesh World: What Does It Mean?

The advent of the data mesh architecture has transformed our perception of data management, moving away from the centralized model of data warehouses to a more distributed approach. But what does embracing the data mesh world really mean?

Centralized data platform like data warehouse or data lake and the move towards decentralized data architecture that data mesh introduces

Centralized data platform like data warehouse or data lake and the move towards decentralized data architecture that data mesh introduces

In essence, a data mesh considers data as a product, encouraging data product owners and domain teams to manage data products within their own business domain. This paradigm shift underlines the core principles of domain-driven design, enabling organizations to operate more effectively in the era of big data.

The Shift from Data Warehouse to Data Mesh Architecture

Traditionally, data warehouses have served as the central repositories for all organizational data. They’ve held the responsibility for processing and storing analytical data, resulting in a centralized model often bogged down by bottlenecks and inefficiencies.

Data warehouse architecture with ETL pipelines that are saving data to central data warehouse and data analysts accessing the centralized data platform though SQL-queries and direct DB connections

Data warehouse architecture with ETL pipelines that are saving data to central data warehouse and data analysts accessing the centralized data platform though SQL-queries and direct DB connections

In contrast, the data mesh architecture, a logical extension of the data lake concept, decentralizes data assets management. Each business domain within an organization operates its own data products, with its respective domain teams having data ownership and managing the complete data product lifecycle. This allows data engineers to work more closely with the data producers and data consumers, ensuring better alignment with the business strategy and outcomes.

Data mesh architecture and the responsibilities of domain team and supporting central teams in enterprise data mesh model

Data mesh architecture and the responsibilities of domain team and supporting central teams in enterprise data mesh model

Understanding Data Mesh Principles

Data mesh principles dictate that each business domain should own and manage its data products, but it’s more than just about assigning responsibility. Data product owners are also accountable for the data quality, ensuring it meets the service level agreements, and is easily accessible to other teams.

This is where the principle of self-service comes in. A well-implemented data mesh encourages a self-service operating model, providing data consumers with easy access to data products. It does away with the bottlenecks of moving data from one centralized location to multiple functional teams, resulting in a more efficient data infrastructure.

Another core principle is federated governance, which promotes decentralized data governance across business domains. Instead of having a central authority control data quality and security, these responsibilities are shared among domain owners.

Finally, a data mesh journey is not a one-off implementation but an ongoing process. It involves continually refining the data mesh roadmap, learning from the existing structure, and adjusting the core components and the logical and business architecture to align with the evolving business needs.

Data Mesh Principles

Data Mesh Principles

The shift to a data mesh world is about acknowledging the distributed nature of data in modern organizations. It’s about empowering domain teams to take ownership of their data products, thereby enabling more effective and efficient use of data assets across the organization.

Your Data Mesh Implementation Journey: A Step-by-Step Roadmap

Navigating the world of data mesh architecture can feel like a complex endeavor, especially when it comes to practical implementation. But worry not – every successful journey begins with a single step. This section will offer you a comprehensive, step-by-step roadmap to guide your data mesh implementation process, easing your transition from a traditional data warehouse or data lake model to a robust, efficient data mesh structure.

The key phases of data mesh roadmap

The key phases of data mesh roadmap

Step 0 - Setting the Data Strategy Stage: Preparing for Data Mesh Implementation

Your data mesh journey begins with the crucial step of setting the data strategy stage. This initial phase typically spans 1-2 months and focuses on assembling cross-functional teams, fostering domain ownership, and building collaboration between departments – all core principles of a domain-driven design.

Assembling Your Data Platform Team

Achieving big data goals starts with bringing together the right people. The data platform team, a cross-functional group composed of data engineers, data architects, data analysts, and data scientists, is pivotal to the process. Their collective expertise and collaboration will shape the roles and responsibilities within the team, ensuring smooth coordination and effective communication. As the torchbearers, this team will take ownership of the proof of concept in the next phase, thereby enabling other teams in different domains to secure necessary resources.

Domain Teams: The Heart of a Data Mesh

Domain teams, often the unsung heroes in most enterprises, form the heartbeat of the data mesh architecture. Recognize their vital role and identify these teams within your organization. You’ll likely discover they have been managing data assets without formally being acknowledged as domain teams (e.g., within their own departments). By promoting a culture of data ownership, these domain experts can independently manage and govern their data products. It’s a decentralized approach that resonates with the ethos of domain-driven design.

Domain team with data product owner and responsibilities shown

Domain team with data product owner and responsibilities shown

Promoting Domain Ownership in Data Infrastructure

One of the essential steps in the data mesh journey involves encouraging domain ownership across your data infrastructure. Empower domain teams to take control and make data-driven decisions that align with their business goals. Collaborate with these teams to identify their unique data needs and ensure that the data products match their specific requirements.

Recognizing the Importance of a Strong Data Platform

At the heart of data mesh implementation is a robust, scalable, self-serve data platform. It’s an essential building block in creating value from big data and meeting the needs of different domains. Begin by planning investments in technologies and tools that facilitate easy data discovery, access, and collaboration across the organization. At this step, we only talk about preparations, early architecture, or evaluating different tools and services.

Step 1 - Data Product Proof of Concept

A pivotal step in your data mesh implementation journey is the execution of a proof of concept (PoC), which typically spans a month. This PoC, focusing on a specific data product or domain, provides a vital pilot project to validate the feasibility and benefits of a data mesh architecture.

Select a Specific Data Product or Domain as a Pilot for the Proof of Concept (PoC)

Begin by identifying a well-defined data product or domain that aligns with your organization’s business priorities. Opt for a domain with clear use cases and data requirements to effectively showcase the data mesh approach. As the Enabling Team, your role is to secure the necessary time and resources to run the PoC within this selected domain.

Define the Scope and Requirements of the PoC, Considering Both Technical and Business Aspects

In collaboration with domain experts and stakeholders, outline the scope of the PoC clearly. Involve data consumers in stating their needs and requirements for the PoC data product. Keep both technical and business aspects in mind, ensuring that the PoC tackles critical data challenges and delivers valuable insights.

Architect the Necessary Infrastructure, Including Data Pipelines, Storage, and Access Mechanisms

Design and build the data pipelines, storage solutions, and access mechanisms required to support the data product’s operations. Utilize your self-serve data platform, enabling domain teams to manage their data independently. Remember, at this stage, the emphasis is on the architecture part to be better prepared for the following steps.

Evaluate the Outcomes of the PoC, Gather Feedback, and Refine the Approach as Needed

Implement the PoC using a data-driven approach, closely monitoring its usage. Encourage data consumers to grade the data product along with its meta description to evaluate its usefulness, quality, and freshness. Collect feedback from domain teams, end-users, and stakeholders to assess the effectiveness and efficiency of the data mesh approach.

After the evaluation, analyze the PoC outcomes and make iterative improvements to your data mesh architecture and its implementation. Identify and address any challenges or shortcomings that emerged during the PoC, using this valuable feedback to refine and enhance your overall data mesh strategy.

Step 2 - Implementing First Data Products MVP

Having validated the data mesh approach in the PoC, Step 2 entails a significant expansion. Over the course of 3 - 4 months, you will build upon the initial success and extend the data mesh implementation to include Minimum Viable Products (MVPs) for additional data products or domains. This step aims at delivering tangible value to your organization by fostering self-serve capabilities and forging a robust data platform.

Identify Additional Data Products or Domains for MVP Development Based on Business Priorities

Work with domain teams and stakeholders to identify high-priority data products or domains that align with the organization’s strategic objectives. Each data product’s potential business impact and value should be considered to prioritize development efforts. Cross-functional representation in the selection process ensures a diversity of data needs are captured.

Design and Develop a Self-Serve Data Platform With a Basic Product Catalog to Enable Easy Discovery and Access to Data Products

Designate a dedicated team of data engineers, architects, and experts to design and develop the self-serve data platform. The requirements and functionalities of the platform should be clearly defined, including features like data cataloging, data lineage, access controls, and data discovery capabilities. Use industry best practices and modern data technologies to build a platform that is both scalable and flexible.

Develop a basic product catalog within the self-serve data platform, creating an organized, user-friendly interface for data consumers to discover available data products. Implement search and filtering mechanisms to enable users to find relevant data products based on their specific needs. Each data product in the catalog should include comprehensive metadata, encompassing data descriptions, data sources, and data quality indicators.

Implement Production Deployment for the Data Product, Ensuring Scalability, Security, and Governance

Move the MVP data products into production, ensuring they are accessible to the appropriate users and stakeholders. The scalability of the self-serve data platform should be validated to accommodate the growth of data products and increasing user demands. Put rigorous data security and access controls in place to protect sensitive information within the platform. Data governance practices must be established to maintain data quality, compliance, and regulatory standards.

Iterate on the MVP Development Based on User Feedback and Evolving Business Needs

Regular feedback sessions with domain teams and data consumers are instrumental in gathering insights into the effectiveness and usability of the MVP data products. User feedback should be incorporated into the iterative development process, emphasizing continuous improvement and optimization. Stay attuned to evolving business needs, adjusting the data mesh architecture and platform to accommodate new requirements. Leverage data analytics to monitor the usage and performance of MVP data products, identifying areas for enhancement.

Data mesh implementation roadmap - iterative PoCs and MVPs development over time

Data mesh implementation roadmap - iterative PoCs and MVPs development over time

Step 3 - Scaling Data Product Catalog and Deploying Self-Service Data Platform

Step 3 is all about growth and maturation. The process involves expanding the data mesh to cover more domains and data products, fostering a culture of data ownership among domain experts, and enhancing the self-serve data platform with advanced features. This step is ongoing and iterative, adapting to the organization’s evolving needs.

Expand the Data Mesh Implementation to Cover More Domains and Data Products Iteratively

Identify additional domains and data products that could benefit from the data mesh approach. Collaborate closely with domain teams to integrate them into the data mesh ecosystem. Encourage these teams to adopt data ownership and manage their respective data products independently, fostering a decentralized approach that aligns with the core principles of the data mesh.

Empower Domain Experts for Data Ownership and Autonomy

Cultivate a culture of data ownership and autonomy by underscoring the pivotal role of domain teams in data management. Provide training and support to domain experts to enhance their data product management skills. Facilitate collaboration and knowledge sharing between domain teams, fostering a data-driven culture that extends beyond the technical sphere to pervade the entire organization.

Responsibilities of various teams working on data mesh

Responsibilities of various teams working on data mesh

Enhance the Self-Serve Data Platform With Advanced Features Such as Data Cataloging, Data Lineage, and Data Discovery Capabilities

Gather feedback from domain teams and data consumers to identify areas for improvement in the existing self-serve data platform. Prioritize the implementation of advanced features, including comprehensive data cataloging for easy data product discovery, data lineage tracking for transparency and traceability, and data discovery capabilities to support users in exploring datasets and finding relevant data products. Furthermore, integrate data quality monitoring tools to ensure the reliability and accuracy of data products, aligning with global standards.

Implement Continuous Improvement and Iterative Development

Establish a feedback loop with domain teams and data consumers to collect ongoing feedback and suggestions. Regularly review the data mesh implementation to identify areas for optimization and enhancement. Commit to continuous iterative development of the self-serve data platform and data products, aligning with changing business needs and creating more value for the organization.

Iterative development of domain products with autonomous domain squads

Iterative development of domain products with autonomous domain squads

Promote Collaboration and Knowledge-Sharing

Organize regular cross-domain meetings and workshops to encourage collaboration and knowledge sharing. Foster an environment of open communication by creating forums and platforms where domain teams can share best practices, success stories, and lessons learned. Consider organizing data summits or conferences to showcase the value of data products and cultivate a data-driven community.

Measure Success and Impact

Define key performance indicators (KPIs) to measure the success and impact of the data mesh implementation. Monitor the adoption and usage of data products across domains, tracking improvements in data accessibility, data quality, and data-driven decision-making. These KPIs will serve as critical markers of progress and success, providing insights into how the data mesh strategy adds value to the organization and achieves business goals.

Step 4 - From Implementing to Managing: Nurturing Your Data Mesh

Step 4 signals the transition from initial implementation to ongoing management and nurturing of the data mesh. During this stage, the emphasis is on establishing robust governance and data stewardship practices and creating mechanisms for continuous monitoring and refinement of the data mesh. The objective is to maintain data quality, compliance, and security while adapting to evolving business needs and user feedback.

Establish Clear Governance and Data Stewardship Practices to Ensure Data Quality, Compliance, and Security

  • Implement Data Quality Framework: Define and enforce consistent data quality standards across all data products and domains. Implement data profiling, validation, and cleansing processes to ensure data accuracy and reliability.
  • Data Security and Compliance: Deploy comprehensive data security protocols and maintain compliance with applicable data privacy regulations. Establish stringent access controls, and apply data encryption and masking techniques to protect sensitive information.
  • Metadata Management: Develop a solid metadata management practice to preserve data lineage, data definitions, and data cataloging. This practice enhances data discoverability and understanding, enabling users to make better-informed decisions.
  • Data Ownership and Accountability: Clearly delineate data ownership roles and responsibilities within domain teams. Foster a sense of accountability and ownership of data products, ensuring they are well-maintained and meet user requirements.

Continuously Monitor and Refine the Data Mesh Implementation, Incorporating Feedback From Users and Stakeholders

  • Feedback Mechanisms: Establish channels for users to share feedback on data products and the data mesh platform. Regularly collect feedback to identify areas for improvement and optimize user experiences.
  • Performance Monitoring: Implement mechanisms to track the performance of data products and the self-serve platform. Monitor data availability, response times, and usage patterns to identify and address bottlenecks.
  • Iterative Development: Embrace an iterative development approach to continuously improve the data mesh implementation. Incorporate feedback and insights gained from monitoring into platform enhancements and updates.
  • Scalability and Resilience: Keep a close eye on the scalability and resilience of the data mesh architecture. Ensure it can accommodate growing data volumes and user demands while maintaining high performance and reliability.
  • Data Governance Review: Conduct regular reviews of data governance practices and policies to ensure alignment with evolving business needs and regulations. Adjust governance frameworks as necessary to address new challenges and requirements.
  • Collaborative Improvement: Foster collaboration between domain teams, the self-serve platform team, and the governance team to drive continuous improvement. Nurture a culture of learning and knowledge sharing to enhance data management capabilities across the organization.

Step 5 - Continually Refining Your Data Mesh

Step 5 is the start of a transformative journey where the data mesh, now fully established, begins to evolve to meet the ever-changing needs of your organization organically. The data mesh becomes a living, thriving ecosystem, expanding and adapting in response to shifting business priorities and technological advancements.

Exploring Cutting-Edge Technologies

As your data mesh expands, it’s crucial to stay abreast of technological advancements. The self-serve data platform should continually evolve to incorporate advanced data cataloging, data lineage, and data discovery capabilities. Foster a culture of curiosity and experimentation within domain teams, enabling them to explore new tools and techniques that enhance the value of their data.

A Flourishing Data-Driven Culture

With data mesh at the heart of your organization, a thriving data-driven culture develops. Data literacy becomes a critical organizational competency, empowering every team member to navigate and utilize data products confidently. The culture of data-driven decision-making pervades the organization, fostering a proactive and informed approach to strategy and growth.

The Organic and Agile Nature of a Successful Data Mesh Implementation

Transitioning to a data mesh architecture is an organic and agile process that aligns seamlessly with the progressive and iterative ethos of contemporary business practices. Even organizations that have traditionally relied on siloed data architectures can successfully leverage the benefits of data mesh.

Starting with a few key data products, the implementation of the data mesh can be conducted incrementally, gradually adding new domains and data products as the organization’s confidence and competence in managing a distributed data ecosystem grow. The selection of subsequent domains to be incorporated into the data mesh is strategically driven by business goals and priorities, ensuring the effort aligns with the organization’s overall strategic direction.

Importantly, implementing a data mesh doesn’t necessitate a wholesale refactoring of existing systems within the organization. Where legacy systems continue to deliver value and function effectively, they can be retained. The crucial aspect is to develop connectors that expose data products from these systems for further analysis and utilization, seamlessly integrating them into the data mesh. This approach respects the value of existing investments while enabling the organization to innovate and adapt in a rapidly changing business environment. The result is a resilient, agile, and organic data architecture that can evolve and grow in sync with the organization’s needs and ambitions.

Concluding Thoughts on the Data Mesh Roadmap

The journey toward a successful data mesh implementation is not a leap but a series of calculated steps. It requires a carefully crafted roadmap guided by a deep understanding of the organization’s unique landscape and a commitment to fostering a data-centric culture. The promise of a data mesh — an agile, adaptable, and resilient data architecture — is a transformative force that can propel an organization into a new era of data-driven innovation and growth.

However, this path, while rewarding, is not without its complexities and challenges. Implementing a data mesh requires navigating numerous technical intricacies and cultural shifts. To ensure a successful transition, having a trusted partner guiding you through the process is beneficial.

At nexocode, our team of data engineering experts stands ready to assist you at every step of your data mesh journey. Leveraging our in-depth knowledge and experience, we can help you build a customized data mesh roadmap, manage its implementation, and navigate the ongoing evolution of your data architecture. Don’t hesitate to contact us today and unlock the transformative power of the data mesh for your organization. Let’s navigate the future of data together!


What is a data mesh?

A data mesh is a decentralized, domain-oriented approach to data architecture. It treats data as a product and promotes data ownership within individual business domains. This enables large enterprises to overcome challenges associated with traditional, monolithic data architectures.

What are the benefits of implementing a data mesh?

Implementing a data mesh can help organizations improve data accessibility, enable data autonomy, enhance data quality, and accelerate data-driven decision-making. By treating data as a product, it encourages a more holistic and efficient approach to data management and usage.

How to start with data mesh implementation?

Start with assembling an enabling team that includes representatives from various business domains. Then, pick a domain and define an initial set of data products for a pilot phase. This phase should serve as a proof of concept to demonstrate the potential of the data mesh approach.

How to scale a data mesh implementation?

Scaling a data mesh involves iteratively expanding the data product catalog and enhancing the self-service data platform to cover more domains. It's crucial to foster a culture of data ownership and autonomy among domain experts to manage and define their data products.

Can legacy systems be integrated into a data mesh?

Yes, the transition to a data mesh architecture doesn't necessarily require refactoring all existing systems. Legacy systems can be integrated into the data mesh through connectors that expose data products for further analysis.

How can nexocode help with data mesh implementation?

At nexocode, our data architects have extensive experience in implementing scalable data platforms, including data mesh architecture. Our data experts can run a dedicated Data Strategy Bootcamp to create your organization's data strategy and implementation roadmap. We guide you through your data mesh journey, helping you navigate from planning to execution and continuous refinement.

About the author

Dorota Owczarek

Dorota Owczarek

AI Product Lead & Design Thinking Facilitator

Linkedin profile Twitter

With over ten years of professional experience in designing and developing software, Dorota is quick to recognize the best ways to serve users and stakeholders by shaping strategies and ensuring their execution by working closely with engineering and design teams.
She acts as a Product Leader, covering the ongoing AI agile development processes and operationalizing AI throughout the business.

Would you like to discuss AI opportunities in your business?

Let us know and Dorota will arrange a call with our experts.

Dorota Owczarek
Dorota Owczarek
AI Product Lead

Thanks for the message!

We'll do our best to get back to you
as soon as possible.

This article is a part of

Becoming AI Driven
92 articles

Becoming AI Driven

Artificial Intelligence solutions are becoming the next competitive edge for many companies within various industries. How do you know if your company should invest time into emerging tech? How to discover and benefit from AI opportunities? How to run AI projects?

Follow our article series to learn how to get on a path towards AI adoption. Join us as we explore the benefits and challenges that come with AI implementation and guide business leaders in creating AI-based companies.

check it out

Becoming AI Driven

Insights on practical AI applications just one click away

Sign up for our newsletter and don't miss out on the latest insights, trends and innovations from this sector.


Thanks for joining the newsletter

Check your inbox for the confirmation email & enjoy the read!

This site uses cookies for analytical purposes.

Accept Privacy Policy

In the interests of your safety and to implement the principle of lawful, reliable and transparent processing of your personal data when using our services, we developed this document called the Privacy Policy. This document regulates the processing and protection of Users’ personal data in connection with their use of the Website and has been prepared by Nexocode.

To ensure the protection of Users' personal data, Nexocode applies appropriate organizational and technical solutions to prevent privacy breaches. Nexocode implements measures to ensure security at the level which ensures compliance with applicable Polish and European laws such as:

  1. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation) (published in the Official Journal of the European Union L 119, p 1); Act of 10 May 2018 on personal data protection (published in the Journal of Laws of 2018, item 1000);
  2. Act of 18 July 2002 on providing services by electronic means;
  3. Telecommunications Law of 16 July 2004.

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet.

1. Definitions

  1. User – a person that uses the Website, i.e. a natural person with full legal capacity, a legal person, or an organizational unit which is not a legal person to which specific provisions grant legal capacity.
  2. Nexocode – NEXOCODE sp. z o.o. with its registered office in Kraków, ul. Wadowicka 7, 30-347 Kraków, entered into the Register of Entrepreneurs of the National Court Register kept by the District Court for Kraków-Śródmieście in Kraków, 11th Commercial Department of the National Court Register, under the KRS number: 0000686992, NIP: 6762533324.
  3. Website – website run by Nexocode, at the URL: whose content is available to authorized persons.
  4. Cookies – small files saved by the server on the User's computer, which the server can read when when the website is accessed from the computer.
  5. SSL protocol – a special standard for transmitting data on the Internet which unlike ordinary methods of data transmission encrypts data transmission.
  6. System log – the information that the User's computer transmits to the server which may contain various data (e.g. the user’s IP number), allowing to determine the approximate location where the connection came from.
  7. IP address – individual number which is usually assigned to every computer connected to the Internet. The IP number can be permanently associated with the computer (static) or assigned to a given connection (dynamic).
  8. GDPR – Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals regarding the processing of personal data and onthe free transmission of such data, repealing Directive 95/46 / EC (General Data Protection Regulation).
  9. Personal data – information about an identified or identifiable natural person ("data subject"). An identifiable natural person is a person who can be directly or indirectly identified, in particular on the basis of identifiers such as name, identification number, location data, online identifiers or one or more specific factors determining the physical, physiological, genetic, mental, economic, cultural or social identity of a natural person.
  10. Processing – any operations performed on personal data, such as collecting, recording, storing, developing, modifying, sharing, and deleting, especially when performed in IT systems.

2. Cookies

The Website is secured by the SSL protocol, which provides secure data transmission on the Internet. The Website, in accordance with art. 173 of the Telecommunications Act of 16 July 2004 of the Republic of Poland, uses Cookies, i.e. data, in particular text files, stored on the User's end device.
Cookies are used to:

  1. improve user experience and facilitate navigation on the site;
  2. help to identify returning Users who access the website using the device on which Cookies were saved;
  3. creating statistics which help to understand how the Users use websites, which allows to improve their structure and content;
  4. adjusting the content of the Website pages to specific User’s preferences and optimizing the websites website experience to the each User's individual needs.

Cookies usually contain the name of the website from which they originate, their storage time on the end device and a unique number. On our Website, we use the following types of Cookies:

  • "Session" – cookie files stored on the User's end device until the Uses logs out, leaves the website or turns off the web browser;
  • "Persistent" – cookie files stored on the User's end device for the time specified in the Cookie file parameters or until they are deleted by the User;
  • "Performance" – cookies used specifically for gathering data on how visitors use a website to measure the performance of a website;
  • "Strictly necessary" – essential for browsing the website and using its features, such as accessing secure areas of the site;
  • "Functional" – cookies enabling remembering the settings selected by the User and personalizing the User interface;
  • "First-party" – cookies stored by the Website;
  • "Third-party" – cookies derived from a website other than the Website;
  • "Facebook cookies" – You should read Facebook cookies policy:
  • "Other Google cookies" – Refer to Google cookie policy:

3. How System Logs work on the Website

User's activity on the Website, including the User’s Personal Data, is recorded in System Logs. The information collected in the Logs is processed primarily for purposes related to the provision of services, i.e. for the purposes of:

  • analytics – to improve the quality of services provided by us as part of the Website and adapt its functionalities to the needs of the Users. The legal basis for processing in this case is the legitimate interest of Nexocode consisting in analyzing Users' activities and their preferences;
  • fraud detection, identification and countering threats to stability and correct operation of the Website.

4. Cookie mechanism on the Website

Our site uses basic cookies that facilitate the use of its resources. Cookies contain useful information and are stored on the User's computer – our server can read them when connecting to this computer again. Most web browsers allow cookies to be stored on the User's end device by default. Each User can change their Cookie settings in the web browser settings menu: Google ChromeOpen the menu (click the three-dot icon in the upper right corner), Settings > Advanced. In the "Privacy and security" section, click the Content Settings button. In the "Cookies and site date" section you can change the following Cookie settings:

  • Deleting cookies,
  • Blocking cookies by default,
  • Default permission for cookies,
  • Saving Cookies and website data by default and clearing them when the browser is closed,
  • Specifying exceptions for Cookies for specific websites or domains

Internet Explorer 6.0 and 7.0
From the browser menu (upper right corner): Tools > Internet Options > Privacy, click the Sites button. Use the slider to set the desired level, confirm the change with the OK button.

Mozilla Firefox
browser menu: Tools > Options > Privacy and security. Activate the “Custom” field. From there, you can check a relevant field to decide whether or not to accept cookies.

Open the browser’s settings menu: Go to the Advanced section > Site Settings > Cookies and site data. From there, adjust the setting: Allow sites to save and read cookie data

In the Safari drop-down menu, select Preferences and click the Security icon.From there, select the desired security level in the "Accept cookies" area.

Disabling Cookies in your browser does not deprive you of access to the resources of the Website. Web browsers, by default, allow storing Cookies on the User's end device. Website Users can freely adjust cookie settings. The web browser allows you to delete cookies. It is also possible to automatically block cookies. Detailed information on this subject is provided in the help or documentation of the specific web browser used by the User. The User can decide not to receive Cookies by changing browser settings. However, disabling Cookies necessary for authentication, security or remembering User preferences may impact user experience, or even make the Website unusable.

5. Additional information

External links may be placed on the Website enabling Users to directly reach other website. Also, while using the Website, cookies may also be placed on the User’s device from other entities, in particular from third parties such as Google, in order to enable the use the functionalities of the Website integrated with these third parties. Each of such providers sets out the rules for the use of cookies in their privacy policy, so for security reasons we recommend that you read the privacy policy document before using these pages. We reserve the right to change this privacy policy at any time by publishing an updated version on our Website. After making the change, the privacy policy will be published on the page with a new date. For more information on the conditions of providing services, in particular the rules of using the Website, contracting, as well as the conditions of accessing content and using the Website, please refer to the the Website’s Terms and Conditions.

Nexocode Team


Want to unlock the full potential of Artificial Intelligence technology?

Download our ebook and learn how to drive AI adoption in your business.