Manufik

Data Processing Agreement

An agreement on the processing of personal data under Article 28 of Regulation (EU) 2016/679 (GDPR). It is part of the contract concluded under the Terms of Service and applies to every customer who puts the personal data of third parties into the Manufik service.

Version 2026-11-14, in effect from 14 November 2026.

1. Parties and subject matter

1.1The customer (“the controller”) and Prinubex s.r.o., Company ID (IČO) 24565369, with its registered office at U rybníčka 268/6, 184 00 Praha 8, Czech Republic, which is referred to as the operator in the Terms of Service (“the processor”), conclude this agreement at the moment when the customer accepts the Terms of Service. The agreement lasts for as long as the processor processes the controller’s personal data.

1.2The processor processes for the controller the personal data that the controller and the controller’s users put into the service. The data about the users themselves — their account, their signing in and the data on their use of the service contained in the operational records — is processed by the processor in its own name, as the controller of that data, in accordance with the Privacy Notice; this agreement does not apply to that data.

1.3If the customer is itself a processor for another controller, this agreement applies by analogy and the customer is responsible for acting in accordance with the instructions of its controller.

1.4If the customer uses the service exclusively for a personal or household activity, the Regulation does not apply to the customer’s processing; the processor nevertheless handles the customer’s data in accordance with this agreement.

1.5The processor’s contact for personal data protection is privacy@manufik.eu.

2. Scope of the processing

Subject matter and purposeProvision of the Manufik service: records of stock, of stock documents and of production, and posting proposals for the accounts.
Nature of the processingStorage, display, search, calculations, exports, backups, the reading of documents on a user’s instruction, and support.
DurationFor the duration of the contract and of the data-retrieval period; copies in the backup storage for no longer than 90 days after the erasure; the file of an attachment a user deleted for 90 days in the main storage and for no longer than two years in the backup storage; operational records under article 3 for no longer than five years.
Types of dataIdentification and contact data (name, business name, identification number and tax number, address, e-mail, telephone, contact person); data on documents and in their attachments (invoices, delivery notes); the names of users on the records they made and on the work they reported; other data that the controller puts into notes and attachments.
Special categories of dataNot processed. The controller must not put them into the service.
Data subjectsThe controller’s vendors and the controller’s own customers who are natural persons, and their contact persons; the controller’s employees and associates; other persons named on documents.

3. The controller’s instructions

3.1The processor processes personal data only on documented instructions from the controller. An instruction is the contract concluded under the Terms of Service, including this agreement, and also every setting made and every act performed in the service by the controller and the controller’s users, and a request that the company’s owner sends to support.

3.2If the processor considers that an instruction infringes data protection legislation, it will inform the controller of this without undue delay.

3.3The processor keeps operational and security records of the use of the service: who carried out which operation, when and with what result. A record of a change also contains a brief description of the change, and therefore in some cases also an item of data that the controller put into the service. A record the content delivery network makes of a request to the service, and a record of a request the service answered with an error, contain the whole address of the request, and therefore in some cases also an item of data that a user of the controller entered in it. To that extent the processor processes the records for the controller, namely in order to secure the service, to correct errors and to provide support. It does not use them for other purposes and keeps them for no longer than five years, and records containing the whole address of a request for 90 days.

3.4If the law of the European Union or of a Member State requires the processor to carry out other processing, the processor will inform the controller of this in advance, unless that law prohibits it.

4. Confidentiality

4.1Within the processor’s organisation, only persons who need such access for the performance of their duties and who are bound to confidentiality by contract or by law have access to the controller’s personal data. The duty of confidentiality continues after their activity for the processor has ended and after this agreement has ended.

5. Access by support

5.1The processor’s staff enter the controller’s company only:

  • at the request of the company’s owner, or of a user whom the owner has authorised to do so, when dealing with their request;
  • when dealing with a security incident or a failure that concerns the company;
  • where this is necessary to comply with a legal obligation.

5.2The processor records every entry: who entered, when, and which company. Changes made by support are marked as such in the company. The authorisation to enter is limited in time.

5.3On request the processor will provide the controller with a list of support’s entries into the controller’s company.

6. Security

6.1The processor has adopted and maintains the technical and organisational measures described on the page Security and data location, which is an annex to this agreement. It may change them, provided that this does not lower the level of protection.

6.2The controller is responsible for security on its own side: for the passwords and the two-step verification of its users, for the roles and permissions in the company, for API keys and for the devices from which the users sign in.

7. Sub-processors

7.1The controller gives the processor a general authorisation to engage the sub-processors named in the list of sub-processors, which is an annex to this agreement.

7.2The processor will inform the company’s owner by e-mail of an intended addition or replacement of a sub-processor at least 30 days in advance. The controller may object until then. If the parties do not reach agreement, the controller may terminate the contract concluded under the Terms of Service by notice with effect from the day of the change; the price paid is not refunded, unless this is required by provisions of law that cannot be derogated from by agreement.

7.3By contract the processor will impose on every sub-processor the same data protection obligations as it has itself under this agreement, and it is liable to the controller for the sub-processor’s performance of them.

8. Reading of documents by a language model

8.1On a user’s instruction, the processor passes the document on for processing by a language model in the Amazon Bedrock service. The document and the result of the reading are processed by Amazon Web Services as a sub-processor, in the regions of the European Union named in the list of sub-processors. Under its terms the content is not stored, is not passed to the model provider and is not used to train models.

8.2Before changing the model the processor will verify that with the new model, too, the content is not stored, is not passed to its provider and is not used for training. If that is not the case, the processor will proceed as for a change of sub-processor.

8.3Documents in a structured electronic format (ISDOC, Factur-X, ZUGFeRD, UBL, FA) are processed by the service without the use of a language model.

8.4The processor does not use the controller’s documents to test or to improve models.

9. Transfers outside the European Union

9.1The processor stores and processes the controller’s personal data in the European Union. It will transfer the data to a third country only on the controller’s instruction, or if the law of the European Union or of a Member State requires it to.

9.2The sub-processors belong to groups based in the United States. In the event that a transfer to a third country should occur on their side, they are bound by the European Commission’s standard contractual clauses or are covered by an adequacy decision.

9.3If the controller is established outside the European Economic Area in a country for which the European Commission has not issued an adequacy decision, making the controller’s own data available to the controller itself is a transfer to a third country. For such a transfer the standard contractual clauses under Commission Implementing Decision (EU) 2021/914, Module Four (processor to controller), become part of this agreement: the data exporter is the processor, the data importer is the controller, the description of the transfer is article 2, the governing law is the law of the Czech Republic and the Czech courts have jurisdiction.

10. Assistance

10.1The service enables the controller to locate, rectify, export and delete personal data, and thereby to deal with the requests of data subjects. The file of an attachment a user deleted stays for another 90 days in the main storage and for no longer than two years in the backup storage, and a restore of a backup taken before its deletion brings it back within the first 90 days. The controller takes this into account when dealing with a request for erasure. If a data subject addresses a request to the processor, the processor will pass it on to the controller without undue delay and will not itself reply to it.

10.2The processor will give the controller reasonable assistance with the security of processing, with the notification of personal data breaches, with a data protection impact assessment and with prior consultation with the supervisory authority. For assistance that goes beyond ordinary support it may require reimbursement of the costs reasonably incurred.

11. Personal data breaches

11.1If the processor becomes aware of a personal data breach that concerns the controller, it will notify the controller of it without undue delay by e-mail to the address of the company’s owner.

11.2In the notification it will state what is known to it: the nature of the breach, the categories and the approximate number of the persons and records concerned, the likely consequences, the measures it has taken or proposes, and a contact point where further information can be obtained. It will supply without undue delay any information that it does not have available immediately.

12. Information and audits

12.1The processor will provide the controller with the information needed to demonstrate that it complies with the obligations under Article 28 of the Regulation: this agreement, the description of security, the list of sub-processors, a list of support’s entries into the controller’s company, and answers to reasonable questions.

12.2The controller may carry out an audit no more than once a year, and at any time after a personal data breach that concerns it. As a rule, the audit is carried out in writing, by means of a questionnaire and the submission of documents; the processor demonstrates the security of the infrastructure by the reports and certifications of the infrastructure’s provider.

12.3An on-site audit at the processor may be carried out by arrangement made at least 30 days in advance, during working hours, without access to the data of other customers and at the controller’s expense.

13. Termination, return and erasure

13.1After the plan or the contract concluded under the Terms of Service has ended, the data-retrieval period laid down in them runs, during which the controller may export the data. If the controller orders a plan within this period, the period is extended until the order is due. After that period has expired, the processor will erase all of the controller’s personal data. Copies in the backup storage cease to exist no later than 90 days after the erasure; until then the processor uses them for nothing other than a restore after a loss of data. On request the processor will confirm the erasure.

13.2After the erasure the processor will retain only the data that the law of the European Union or of a Member State requires it to keep, and the operational records under article 3, which cease to exist no later than five years after they were created.

14. Liability and precedence

14.1The liability of the parties towards each other is governed by the Terms of Service. This does not affect liability towards data subjects under Article 82 of the Regulation.

14.2In matters of personal data protection this agreement prevails over the Terms of Service. The standard contractual clauses under article 9 prevail over both.

This is a translation of the Czech text. For a customer who is a business, the Czech text prevails if this translation departs from it; for a consumer, the text in which the consumer concluded the contract prevails.

The page can be printed or saved as a PDF from the browser’s menu.