GDPR¶
What Is Done with Personal Data¶
This integration treats the name of the responsible coworker on each customer, as well as the names stated on invoices and orders as Our reference and Your reference. There are however differences between the different ERP systems, please see the field mappings per ERP system for more details.
It may also be used to sync contact person information.
Why Personal Data Is Needed¶
It is important to keep track of the responsible coworker on customers, and it is a very important part of invoices and orders to be able to see which persons where involved from each side. On invoices, the reference field is typically mandatory in ERP systems. If contact persons are synced, of course personal information will be included.
What Personal Data¶
| Object | Personal data |
|---|---|
| Customers | Name of responsible coworker. |
| Invoices | Our reference |
| Invoices | Your reference |
| Orders | Our reference |
| Orders | Your reference |
| Contact Persons | Name |
| Contact Persons | |
| Contact Persons | Phone number |
| Contact Persons | Cellphone number |
Transfer of Personal Data¶
Data is transferred through the Lime CRM REST API. Calls are done using HTTPS.
Logging of Personal Data¶
Data being synced is logged in Syncify's cloud service for cloud based ERP systems and locally on the server where Syncify's sync service is installed for on-premise based ERP systems.
For the on-premise sync service made by Syncify, it is possible for Syncify to request the logs. This is only done for troubleshooting reasons.
For the cloud sync service made by Syncify, the logs are kept on AWS within EU.
If any of the sync services made by Syncify encounter a temporary error in the middle of a data exchange between Lime CRM and the ERP system, after having attempted a few retries, instead of losing the state of the current data being synced, it is persisted temporarily to a server on AWS in EU. The next time the sync runs, it will start by finishing that state, which increases the robustness of the sync. This data may contain personal information depending on what was being synced currently.
Possible Avoidance of Using Personal Data¶
Through field mappings it is possible to remove the individual data points containing personal information from the integration. This will however result in a worse user experience of the integration since important data will be missing.
Warning
Turning off the below features will have a major impact on the robustness of the service.
It is possible to turn off the feature to persist the state if there was an error not solved by a few retries during a sensitive state of the data exchange in the sync service. Doing this may result in more often downtime of the integration.
For on-premise based ERP systems, it is possible to turn off the possibility for Syncify to request the logs to be sent to them for troubleshooting reasons.