Who Owns a CRM Built by an Employee Through Vibe Coding? Copyright Questions in Hungary

A single key made of two different metals with a thin red joint, against a light grey background.

An administrative employee grows tired of customer spreadsheets and builds a CRM with an AI tool over a few afternoons. Colleagues start using it, customer data is entered, and six months later the employee resigns. Only then does someone ask: who owns the system, and can it keep running without its creator? The answer does not automatically follow from the fact that it was built on a company laptop during working hours.

In short: the rights to every component of the CRM do not necessarily belong to the same party. For AI-generated code, the first step is to establish which parts may qualify for copyright protection. As a general rule, the employer acquires the economic rights to protected parts upon delivery if creating them was part of the employee’s duties arising from employment and there is no agreement to the contrary. In other cases, the company’s right to use the software must be examined separately; licences also matter for external components. Alongside clarifying the rights, the data processing and operational requirements for continued use must also be met.

1. The job description alone does not determine who owns the CRM

Act LXXVI of 1999 provides the basic framework for Hungarian copyright law. As a general rule, for works created in the course of employment, unless otherwise agreed, the employer acquires the economic rights upon delivery of the work, if creating the work was part of the employee’s duties arising from employment. Software is also subject to specific rules; the provisions of Sections 30 and 58 of the Act must be considered together in each particular case.

This does not mean that everything someone creates during working hours automatically belongs to the employer. Equally, the absence of the word “software development” from the job description does not, on its own, settle the question in the employee’s favour.

What needs to be examined?

  • The employment contract and job description: what duties did the employment relationship cover?

  • The specific assignment or instruction: was the employee tasked with building the system, and under what conditions?

  • The actual circumstances: was this an independent initiative, an approved project or a solution adopted after it was built?

  • The agreements and handover: were the rights addressed, and what was transferred to the company?

The use of company equipment and management’s awareness may be important evidence, but they do not replace the legal requirements. If development was not a duty arising from employment and there is no other legal basis for acquiring the rights, the company cannot automatically consider itself the holder of the economic rights. In such cases, a licence or another appropriate agreement may be necessary.

2. AI wrote the code: is there any copyright at all?

In vibe coding, the user asks an AI tool to create and modify code through natural-language requests. Before examining whether the employer acquires the rights, a fundamental question must therefore be clarified: which parts qualify as human creations? Hungarian copyright law protects individual, original works resulting from the creator’s intellectual activity. AI does not become an author, and purely machine-generated output does not, in itself, establish human copyright.

The employee may nevertheless carry out creative work that qualifies for protection. They may write their own code, substantially rework generated sections or create individual, original structural solutions. However, the number of prompts and the time spent on development do not, on their own, prove authorship. Defining requirements does not necessarily constitute a copyright-protected contribution to the resulting program either.

Moreover, a CRM may consist of several legal layers:

  • original and AI-generated code snippets;

  • open-source libraries and other external components;

  • interface designs, documentation and database structures;

  • cloud services subject to separate terms of use.

The AI provider’s terms of use do not resolve everything either. Contractual permission to use the output does not guarantee copyright protection, exclusivity or freedom from third-party rights. The licences for incorporated components must also be checked separately.

Two colleagues at an office workstation review documents and CRM components; their faces are not identifiable.

3. The danger of shadow IT: a working CRM is not necessarily a secure CRM

Having the rights to use the CRM in order does not guarantee that it can be operated without its creator. Shadow IT increases this risk: the use of IT solutions that operate outside the organisation’s approval, security or operational controls. These solutions are not necessarily secret: everyone may know about the CRM, yet it has no designated owner, review process or documentation.

A well-intentioned initiative can thus become a business-critical system without anyone noticing. The ability to register customers and track quotes does not tell us whether access controls are adequate, the database is secure or the system can be restored after a faulty update.

Typical risk areas

  • Personal accounts: the hosting, code repository or AI subscription is tied to a single employee’s personal account.

  • Access control flaws: the interface hides the data, but the back-end system does not properly check permissions.

  • Leaked secrets: passwords, API keys or customer data end up in code, logs or AI conversations.

  • Lack of maintenance: no one monitors dependencies for vulnerabilities, and there is no tested recovery procedure.

If personal data enters the system, GDPR obligations do not disappear simply because the CRM started as an internal experiment. The purposes of processing, legal basis, retention, access rights and service providers’ roles must be clarified. A data processing agreement and an assessment of the conditions for international data transfers may also be required. An employee’s personal subscription does not address these matters on the company’s behalf.

4. Can employees take it with them, shut it down or charge for it when they leave?

These are three separate questions, not consequences of a single decision about ownership. Rights to the software must be distinguished from the processing of customer data, control over access and the employee’s handover obligations.

If the employer has lawfully acquired the economic rights, the departing employee cannot prohibit continued use merely because they are leaving. If the rights remain with the employee, however, the scope of the company’s right to use the software must be examined separately. Previous use and communications between the parties may also matter, but it is unwise to assume that these amount to an unlimited, perpetual licence.

Employees may, for example, charge for a new licence agreement or subsequent support, provided the legal conditions for doing so are met. However, a demand for payment is not automatically justified, nor does it make withholding or deleting data, or arbitrarily obstructing operations, lawful.

Keeping a copy of the source code or using it at another business also requires separate examination. Even if employees own the copyright, confidentiality obligations and trade secret protection may impose restrictions. Nor can they simply take the customer database because they created the software associated with it.

On the left, a cluttered desk with paper-based handover materials; on the right, an organised company workstation with a simple digital handover process.

What should the company address before the employee leaves?

  1. Create an inventory of code, services, accounts, licences and data.

  2. Work with a lawyer to clarify the basis for acquiring the rights and for continued use.

  3. Set out the terms of use, modification, further development and support in writing.

  4. Ensure a proper technical handover, company-controlled access and rotation of secrets.

  5. Plan documented data backups and, if necessary, data export and system replacement.

5. xFLOWer: building workflows instead of new software

Following the legal and technical assessment, it is worth comparing the maintenance of an in-house CRM with the use of an existing platform: which option better ensures the required functionality, maintenance and operation independent of the employee? If the primary needs are to assign responsibility for leads, ensure follow-up and track quote approvals, building workflows is another option to consider. However, this is a decision about how to structure operations, not an answer to the legal questions surrounding the CRM already built.

Building workflows with xFLOWer can offer an alternative here: the focus can shift to defining business steps, roles, responsibilities and exceptions. This can reduce the amount of custom code that needs maintaining and dependence on a single employee, but it does not eliminate the need for contractual or security controls.

With xFLOWer, the legal distinction is that with a proper company licence in place, the legal basis for continued use of the core software does not depend on the departing employee’s authorship. Customisation still requires separate examination: rights to individual, original configurations, documentation and custom-built integrations must still be addressed.

For an xFLOWer solution agreed with the Click On team, it is also advisable to specify in advance:

  • what the platform licence covers and how configurations may be used;

  • who is authorised to modify workflows and integrations;

  • how data processing, export and service termination will be handled;

  • who is responsible for support and custom extensions.

When incorporating xFLOWer.ai, the role of AI, the scope of data shared and human oversight must likewise be clarified. The aim is not to rebrand uncontrolled development, but to establish transparent operations with clearly assigned responsibilities.

An unlabelled editorial data graphic featuring a ring, bars and a data flow passing through a red checkpoint.

6. Summary: settle the rights before going live

The opening example therefore requires separate answers to two questions: on what legal basis can the company continue using the CRM, and can it operate it without the departing employee? The first requires examining the development assignment, human creative contributions, agreements and licences; the second requires reviewing access rights, data processing and operational arrangements. If the CRM is already live, the first step should be an inventory of code, accounts, services and data — do not wait until the employee gives notice.

The identified legal and operational conditions provide the basis for deciding whether to retain or replace the existing CRM. If the requirements can also be met using xFLOWer, this is another alternative to consider. However, switching platforms does not replace the need to resolve rights, data and handover matters relating to the existing system.

This article provides general information, not case-specific legal advice; for a specific matter, it is advisable to consult a lawyer experienced in copyright law.

Does your company already have an in-house CRM? Discuss with the Click On team which workflows would benefit from moving to xFLOWer, and prepare separate legal, data protection and technical checklists for an orderly transition.

This article is part of our comprehensive guide: The top 10 risks of vibe coding: a comprehensive business guide from security to copyright

A miniature corporate environment with a workstation, server, transparent data storage unit, backup unit and red access barrier.

xFLOWer.ai

Design the process behind this article – for free!

AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.

Contact us

Let's talk about your processes

Tell us briefly which process you'd like to automate – we'll get back to you within 1 business day.