Overholdelse af GDPR-lovgivning

Det er vigtigt for os hos Continia Software, at vi beskytter vores kunders og brugeres personoplysninger og overholder reglerne i EU's persondataforordning.

EU's persondataforordning

Som et led i dette har vi derfor sikret, at alle vores softwareløsninger overholder kravene i overensstemmelse med GDPR lovgivningen. Derfor følger vi ISEA 3402 standardrammen specifikt med GDPR i tankerne, der blandt andet består af følgende komponenter:

  • Uddannelse af vores medarbejdere.
  • Beskyttelse af personlige oplysninger og databeskyttelse er indbygget i udvikling og produktion.
  • Udnævnelse af dedikeret Data Protection Officer.
  • Kontinuerlig kontrol og målinger.
  • Alle data behandles og opbevares i EU.
  • Alle data behandles i overensstemmelse med vores databehandleraftale.

Via vores Trust Center kan du anmode om at få tilsendt vores databehanderaftale.

Nedenfor finder du den specifikke beskrivelse af hvordan Continia Collection Management kommunikerer med Continia Bank Communication Components (CBCC).

Har du spørgsmål til ovenstående er du altid velkommen til at skrive til vores Solution Manager eller kontakte os på telefon +45 8230 5000.

Bemærk

Beskrivelsen er en del af vores databehandleraftale og findes kun på engelsk.

GDPR-compliance for Continia Collection Management

Vigtigt

Continia Software is providing this GDPR-compliance document as a matter of convenience only. It's your responsibility to classify the data appropriately and comply with any laws and regulations that are applicable to you. Continia Software disclaims all responsibility towards any claims related to your classification of the data.

When using Collection Management, you can create and send invoices as a request for payments.

This can either be accomplished with the use of the following external components installed on Continia Online, which are not part of the Microsoft Dynamics 365 Business Central software package but delivered by Continia Software.

  • The Continia MobilePay Interface Component
  • The Continia Bank Communication Components (CBCC)

Or by the included Continia Bank Communication Components (CBCC) that are in the Collection Management software package.

  1. The Continia MobilePay Interface Component is used for the following:
    • Establishing connection to the Collection Central MobilePay
    • Converting the data received from Microsoft Dynamics NAV or Dynamics 365 Business Central.
    • Converting the data received from MobilePay, and making the data available for Dynamics NAV or Business Central on demand.
  2. The Continia Bank Communication Components (CBCC) are used for communicating with the following Collection Centrals.
    • Nets
    • Danske Bank
  3. The following Collection Centrals and systems are communicated through webservices.
    • Continia Online
    • Bambora

Depending on your settings above, only Continia Online-installed components are Continia Software's responsibility and therefore, relevant for this documentation.

Vigtigt

Locally installed components, or files saved to a local file-location, is the responsibility of the user.

Flow

Creating the request for payments files:

Depending on which Collection System that is used, different files is created, but shared for the following systems is that the files is generated inside Dynamics NAV or Business Central. The files only exist in memory. From memory, the files are transferred directly to the Collection Centrals, using the Continia Bank Communication Components (CBCC). (The user can though choose to save the files in the Dynamics NAV or Business Central database, where it will be stored in a blob field.). The systems that uses this approach is listed below.

  • Danske Bank
  • Nets
  • Bambora

Bemærk

For the collection systems Danske Bank and Nets the user can choose to save the files to disk. The files are saved to disk, when the direct communication is disabled.

For the Collection system MobilePay the files are sent to Continia Online by a web request using a secure https-protocol. The information is then processed by the Continia MobilePay Interface Component and redirected to MobilePays API.

Retrieving status files, and information on completed requested payments.

Dependent on which Collection System that is used, different files and communication is performed. Shared for the listed Collection Systems are that no files are stored on any disk or media. The Continia Bank Communication Components (CBCC) all communicate to Dynamics NAV or Business Central using only memory. This all applies for the listed Collection systems below.

  • Danske Bank
  • Nets
  • Bambora

For the Collection System MobilePay, Continia Online uses the Continia MobilePay Interface Component to continuously collect payment information from MobilePays API. The retrieved data is saved on Continia Online.

When a request for status update is sent from Dynamics NAV or Business Central to Continia Online, all the collected information is then send to Dynamics NAV or Business Central. All requests is sent through a secure https-protocol.

In Dynamics NAV or Business Central data is then stored from memory, directly into a BLOB field in the Dynamics NAV or Business Central database.

Expiration

Using MobilePay:

Sign-up: When signing up, data is stored at Continia Online to enable communication with MobilePay.

Invoice data: When it comes to data stored in relation to request for payments, only the amount and invoice number will be stored at Continia Online.

Retrieving data on Requested payments: From MobilePay, Continia Online receives and stores Invoice ID and status information.

Using other Collection Systems:

No GDPR related information is sent or stored at Continia Online.

Sensitivity

All data is considered personal sensitive.