Trust & responsibility
Security & GDPR
Security and data protection depend on how an application is configured, operated, and used. This overview explains the roles of BloomERP and its customers across our website, managed hosting, and self-hosted applications.
Last updated:
About BloomERP
BloomERP BV is a Belgian private limited company, enterprise number 1044.529.553, with its registered office at Elsbroeken 11, 2320 Hoogstraten, Belgium.
Security in practice
BloomERP includes configurable permissions for application access. The available controls and their effectiveness depend on the application, version, configuration, and operator; a product capability is not a guarantee for every deployment.
When planning a deployment, review who can access data, how hosting is secured, how updates are applied, and how backups and recovery are handled. Agree these responsibilities with the people operating your application.
Website, managed hosting, and self-hosting
Public website
Website enquiries and records held in customer applications involve different processing activities. For questions about this website or information you have sent to BloomERP, contact us using the details below.
BloomERP-managed hosting
Where BloomERP operates hosting for a customer, the division of operational and data protection responsibilities depends on the services provided and the applicable agreement. Confirm the arrangements for your deployment before using it for personal data.
Customer self-hosting
When you host BloomERP yourself, you or your chosen hosting provider operate the infrastructure and application configuration, including access, updates, backups, and recovery. Using BloomERP software does not by itself make BloomERP the operator of that environment.
Data protection roles
Under the GDPR, a controller decides why and how personal data is processed. A processor handles personal data on the controller’s instructions. These roles depend on the actual processing activity.
Customers generally decide how personal data in their business records is used and act as controllers for that processing. Where BloomERP processes that data on a customer’s behalf, the controller–processor relationship must be covered by an appropriate agreement. BloomERP may act as a controller for its own activities, such as handling enquiries.
This page is a general overview. It does not replace a privacy notice, a data processing agreement, or an assessment of your organisation’s obligations.
Read more in the EDPB guide to controllers and processors and the GDPR.
Integrations and AI services
Connecting external services, including AI providers, may send information to those providers. Review what data is shared, the provider’s terms, and the applicable processing arrangements before enabling a connection or submitting personal data.
Privacy and security contact
For privacy questions, requests concerning information held by BloomERP, or security concerns, email contact@bloomerp.io. You can also use our contact page.
If your request concerns records held by an organisation using BloomERP, contact that organisation first: it generally decides how those records are used.
Please avoid including passwords, access tokens, or unnecessary personal data in your message.