Terms of use

Last updated: 20 October 2026

1. Who we are

The dataflows.ro website is run by Sly Data Intelligence SRL (DataFlows brand), tax code 47884809, registered office at Șos. Colentina 16, Bl. A5, Ap. B44, Bucharest, 021177, Romania. Contact: contact@dataflows.ro, +40 712 344 092.

2. Acceptance of the terms

By using this website you accept the terms below. If you do not agree with them, please do not use the website.

3. What the website offers

The website presents information about DataFlows, our solutions and services, articles and a glossary of terms. The information is general and is not a commercial offer. The features, prices and conditions of a specific project are set out in a separate offer and contract.

4. DataFlows applications: common provisions

DataFlows applications are intended for companies and institutions. The provisions below apply to all applications; the contract signed with each client may supplement or change them, and in case of any difference the contract prevails.

• Accounts and access. User accounts are created and managed by the organisation that uses the application, through its administrators. The organisation sets the roles and permissions of each user and is responsible for removing access for those who no longer need it.
• Sign-in credentials. Each user keeps their password, the sign-in codes received by SMS or e-mail and access to their Google account (where Sign-in with Google is used) confidential. Accounts are personal and must not be shared. Any suspected unauthorised access must be reported immediately to the administrator and to us.
• Data entered. Data entered in the applications belongs to the client, who is responsible for its correctness and for the documents issued on its basis. The applications check data against the configured rules, but they do not replace the control and responsibility of the people who enter, approve or sign it.
• Automatically generated suggestions. Some applications offer calculated or AI-generated suggestions (for example codes, budget classifications or projections). Suggestions are indicative; the decision and the responsibility lie with the user who accepts them.
• Availability and maintenance. We do everything we can to keep the applications available at all times. Planned work is announced in advance and done, as far as possible, outside working hours. The availability level and support response times are those set out in the contract.
• Hosting and backups. The applications run in the DataFlows cloud, on an instance dedicated to the client, or on the client’s servers. In the DataFlows cloud we make automatic backups. When the application runs on the client’s servers, backups and infrastructure security are the client’s responsibility, unless agreed otherwise.
• Acceptable use. It is forbidden to try to bypass access rights, to access data of other organisations, to upload malicious files or to deliberately overload the system. We may temporarily suspend an account to stop abuse or a security incident, informing the client’s administrator.
• End of contract. When the contract ends, the client may request an export of its data in a common format, within the period set in the contract. After that period, data hosted in the DataFlows cloud is deleted, except data we are required by law to keep.

5. Application-specific provisions

DataFlows Depo (warehouse management)

• The stock in the application reflects the scans and operations recorded by users. Its accuracy depends on following the workflow (receiving, transfers, picking, shipping, stock counts) and on correct labelling of goods and locations.
• Depo does not replace the client’s invoicing software or ERP. The accounting records remain in that software; the link between them works within the limits of the data the client’s software makes available.
• The mobile app runs on phones or terminals provided by the client. Operations made without a signal are synchronised when the connection returns; the client is responsible for the devices, access to them and the internet connection.

DataFlows Pharma (GMP manufacturing)

• Pharma supports compliance with EU GMP, Annex 11 and 21 CFR Part 11, but responsibility for compliance remains with the manufacturer: validation of the system in its environment (based on the validation package we deliver), internal procedures, staff training and quality decisions, including batch release.
• Electronic signatures in the application are personal and carry the meaning shown at signing (for example “reviewed” or “approved”). Users may not hand over their signing rights to others.
• The audit trail cannot be changed or deleted from the application. Configuration changes that affect the validated state are made through the manufacturer’s change control procedure.

DataFlows ALOP (budget execution and procurement)

• ALOP is intended for public institutions. Approval workflows, signatories, roles and permissions are configured by the institution according to its internal control; the institution is responsible for ensuring the configuration matches its internal decisions.
• Users sign in with a username, password and a one-time code received by SMS or e-mail or, where the institution has enabled this option, with a Google account whose e-mail matches an account already created by the administrator.
• Documents are signed electronically with each signatory’s own certificate, outside the application; ALOP checks the signatures in the uploaded files and links them to the workflow steps. The image of a handwritten signature is applied only by its owner or, when the option is ticked, by a person authorised by the owner, who takes responsibility for that authorisation.
• XML exports are generated according to the schemas published by the Romanian Ministry of Finance at the time of implementation. The institution checks the documents before sending them on and tells us when the official schemas change, if we have not already updated them.
• Suggested CPV codes, budget classifications and budget projections are indicative. Responsibility for committing, verifying, authorising and paying expenditure remains with the persons designated by the institution, as required by law.
• Each institution’s data is kept in a separate database. Unsaved drafts are deleted automatically after 30 days.

DataFlows Docu (document generation)

• Templates and the content of generated documents are set by the client; Docu fills in the templates with the data it receives, without checking its legal meaning. The client is responsible for the form and content of the documents it issues.
• API access uses personal access keys for each application that sends data. The client keeps them confidential and tells us if a key has been compromised, so that we replace it.
• Generated documents are kept for the period set in the configuration or in the contract, then deleted.

DataFlows Sales (B2B sales)

• The B2B store is accessible only to customers and sales agents invited by the seller. Sales are concluded between the seller and its customers, under the seller’s commercial terms; DataFlows is not a party to these transactions.
• Prices, stock levels and exchange rates shown come from the seller’s data and from the configured public sources and are indicative until the seller confirms the order.
• Delivery and export documents are generated from the order data; the seller is responsible for checking them before use.

Custom applications

For custom-built applications, the features, deadlines, rights of use and ownership of the developed components are set out in the project contract. The DataFlows platform they are built on remains the property of Sly Data Intelligence SRL.

6. Intellectual property

The texts, images, logos, trademarks and other materials on the website belong to Sly Data Intelligence SRL or to partners who allowed us to use them. You may quote short excerpts, citing the source and linking to the original page. Any other reproduction, modification or commercial use requires our written consent.

7. Acceptable use

You may not use the website to disrupt its operation, to attempt unauthorised access to our systems, to transmit malicious software or unlawful content, or to send unsolicited messages through the contact form.

8. Accuracy of information and liability

We make every effort to keep the information on the website correct and up to date, but we cannot guarantee that it is free of errors or that the website will always be available without interruption. To the extent permitted by law, we are not liable for damage resulting from the use of the information on the website or from being unable to access it.

9. Links to other websites

The website may contain links to websites of other organisations. We do not control their content and are not responsible for it.

10. Personal data and cookies

How we process personal data is described in the Privacy policy, and the cookies we use are described in the Cookie policy.

11. Governing law

These terms are governed by Romanian law. Any disputes will be settled amicably or, failing that, by the competent courts in Bucharest.

12. Changes

We may update these terms when the website or the law changes. The date of the last update is shown at the top.