Skip to content

Data Processing Agreement

How Aarbaah Digital Solution protects personal data it processes on behalf of clients when building, hosting and supporting their software: roles, security, sub-processors, transfers and breach notification.

1.Introduction and Scope

This Data Processing Agreement ("DPA") forms part of the agreement between Aarbaah Digital Solution ("Aarbaah", "we", "us") and each client ("Client") for our services, whether that agreement is a proposal, statement of work, subscription or our Terms of Service (the "Agreement").

It applies whenever we process personal data on the Client's behalf while designing, developing, hosting, maintaining or supporting software, websites, mobile applications or other systems for the Client. If the Client and Aarbaah have signed a separate data processing agreement, the signed agreement takes priority over this page.

2.Definitions

Terms such as personal data, processing, controller, processor, sub-processor, data subject and personal data breach have the meanings given in the EU General Data Protection Regulation (GDPR) and in the other data protection laws that apply to the processing (together, "Data Protection Laws").

Client Personal Data
Personal data that the Client, or the Client's users, customers, patients or staff, provide to the systems we build or operate for the Client, and that we process on the Client's behalf.
Services
The development, hosting, maintenance, support and related services described in the Agreement.

3.Roles of the Parties

Client as controller
The Client decides why and how Client Personal Data is processed. The Client is responsible for having a lawful basis for the processing, for giving the required notices to data subjects, and for the accuracy of the data it provides.
Aarbaah as processor
Aarbaah processes Client Personal Data only on the Client's behalf and only to provide the Services. This DPA does not cover personal data we handle for our own purposes, such as contact details of the Client's staff used to manage the relationship; that is covered by our Privacy Policy.

4.Details of the Processing

Subject matter and duration
Providing the Services, for the term of the Agreement and until Client Personal Data is returned or deleted under section 12.
Nature and purpose
Building, configuring, testing, deploying, hosting, monitoring, backing up, maintaining and supporting the Client's systems, and troubleshooting problems the Client reports.
Categories of data subjects
Depending on the system: the Client's end users, customers, patients, students, employees, suppliers and other people whose data the Client enters into the system.
Categories of personal data
Depending on the system: identification and contact details, account and login data, transaction and order data, usage and log data, and any other data the Client chooses to store. Special categories of data, such as health data in hospital and clinic systems, are processed only when the Client's system requires them and the Client has instructed us to do so.
Project-specific details
The systems, data categories, hosting location and sub-processors for each project are set out in that project's proposal or statement of work.

5.Our Obligations

Documented instructions
We process Client Personal Data only on the Client's documented instructions, including the Agreement and this DPA, unless the law requires otherwise. If we believe an instruction breaks Data Protection Laws, we will tell the Client.
Confidentiality
Everyone at Aarbaah who can access Client Personal Data is bound by a duty of confidentiality and has access only to the data needed for their work.
Security
We apply the technical and organisational measures described in section 13, appropriate to the risk of the processing.
No other use
We do not sell Client Personal Data, use it for our own purposes or combine it with other data, except as needed to provide the Services.
Development and testing
We use realistic test data in development and testing. We use real Client Personal Data outside the production system only when needed to fix a problem, and only for as long as needed.

6.Sub-processors

Authorisation
The Client authorises us to use sub-processors, such as cloud hosting, database, e-mail and backup providers, to provide the Services. The sub-processors for each project are listed in its proposal or statement of work.
Changes
We will tell the Client at least 14 days before adding or replacing a sub-processor that processes Client Personal Data. The Client may object on reasonable data protection grounds, and we will work with the Client in good faith to find a solution.
Our responsibility
We bind every sub-processor to data protection terms that protect Client Personal Data at least as well as this DPA, and we remain responsible to the Client for their performance.

7.International Data Transfers

Aarbaah is based in Bangladesh, and our sub-processors may operate in other countries. Where Data Protection Laws restrict transfers of Client Personal Data out of a country or region, such as the European Economic Area, the United Kingdom or Switzerland, we will make the transfer only under a valid transfer mechanism, such as the European Commission's Standard Contractual Clauses and, for the United Kingdom, the UK International Data Transfer Addendum.

8.Personal Data Breaches

Notification
If we become aware of a personal data breach affecting Client Personal Data, we will notify the Client without undue delay and, where feasible, within 48 hours, so that the Client can meet its own notification duties.
Information we provide
As far as it is available to us: what happened, the categories and approximate number of people and records affected, the likely consequences, and the measures we have taken or propose to take. We will provide further information as it becomes available.
Containment
We will take reasonable steps to contain the breach, reduce its effects and prevent it from happening again, and we will cooperate with the Client's investigation.

9.Assistance to the Client

Data subject requests
If someone asks us directly to access, correct, delete or move their data held for the Client, we will pass the request to the Client and not answer it ourselves unless the Client instructs us to. We will help the Client respond to such requests, for example through system features or exports.
Assessments and authorities
We will provide reasonable help with the Client's data protection impact assessments and with consultations with supervisory authorities, as far as they concern our Services.

10.Audits and Information

On request, we will provide the information reasonably needed to show that we comply with this DPA. If that information is not enough, the Client, or an independent auditor bound by confidentiality, may audit our compliance once a year, with at least 30 days' written notice, during business hours and at the Client's cost, unless a supervisory authority requires otherwise or a personal data breach has occurred.

11.Liability

Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement, except where Data Protection Laws do not allow liability to be limited.

12.Return and Deletion of Data

When the Services end, we will, at the Client's choice, return Client Personal Data in a commonly used format or delete it, within 30 days of the Client's request, unless the law requires us to keep it. Copies in backups are deleted as the backups expire in their normal cycle and are protected by this DPA until then.

13.Security Measures

We apply the following technical and organisational measures to the systems we build and operate for the Client. Additional measures agreed for a specific project are set out in its proposal or statement of work.

Encryption
Data is encrypted in transit with HTTPS (TLS). Data is encrypted at rest wherever the hosting or database provider supports it.
Access control
Access to production systems and data is limited to the people who need it, uses individual accounts and, where the provider supports it, multi-factor authentication. Access is removed promptly when it is no longer needed.
Secrets management
Passwords, API keys and other credentials are kept in the hosting provider's encrypted configuration or a secrets manager, never in source code, and are rotated when there is any sign they have been exposed.
Secure development
Code is reviewed before release. We validate input, protect against common web attacks (such as injection, cross-site scripting and request forgery), check third-party dependencies for known vulnerabilities and apply security updates.
Availability and recovery
Systems we host are backed up and can be restored according to the backup arrangements agreed for each project.
Monitoring and incident response
We monitor the systems we operate for errors and suspicious activity, and we follow a defined process for investigating and responding to security incidents.
People and suppliers
Our staff are trained in secure handling of data and bound by confidentiality. We choose sub-processors with appropriate security commitments.

14.Contact Information

To request a signed copy of this DPA, the list of sub-processors for your project, or for any other question about how we process your data, please contact us at:

Phone
+8801715137675