Regulation · Bahrain
Bahrain PDPL
At a glance
- Jurisdiction
- Bahrain
- Supervisory authority
- Personal Data Protection Authority
- In force
- In force since 1 August 2019
- Official name
- Law No. (30) of 2018 with respect to Personal Data Protection
What Bahrain’s PDPL asks of you, article by article
How GovernID fits: Bahrain’s PDPL starts from written, explicit consent, asks you to tell people about processing and, in many cases, to notify the Authority before you start. GovernID builds that into collection. Your RoPA holds the items a notification asks for, privacy notices are generated from it in Arabic and English, and each record collected through GovernID carries the notice, consent and retention period that applied on the day it arrived.
Good to know: Response times are short: 15 working days for access and 10 working days for correction, erasure and objections. Some processing, such as biometric identification or surveillance recording, needs the Authority’s approval first.
| Requirement | Article | What GovernID does | What stays with you |
|---|---|---|---|
| Scope. The law covers automated processing and manual processing in a filing system, by people and companies resident or established in Bahrain, and by foreign controllers that use means in Bahrain. Those foreign controllers appoint a representative. | Art. 2 | GovernID hosts each company’s data in the country where it is registered, and each company in a group works in its own portal. | Deciding whether the law applies to you and appointing the representative. |
| Data quality. Process fairly and lawfully, for a specific and legitimate purpose, with only the data needed, kept accurate and no longer than necessary. | Art. 3 | Each processing activity in your RoPA records its purpose, data categories, legal basis and retention period. Every field is classified before the first record arrives, and each record keeps the terms it was collected under. | Deciding purposes and judging what is necessary. |
| Legal grounds. Consent is the starting point. Without consent, processing is allowed only for a contract, steps before a contract, a legal obligation or court order, vital interests or legitimate interests. | Art. 4 | Legal bases come ready in the Privacy Taxonomy. Each activity records its basis, and each record keeps the basis that applied on the day it arrived. | The legal assessment, including the legitimate interest test. |
| Consent. Consent must come from a person with full capacity, be written, explicit, clear and specific, freely given and informed. People can withdraw it at any time. | Art. 24 | The approved consent text is shown at collection, one purpose per box, never pre-ticked. GovernID keeps the version on the record with the dates consent was given and withdrawn. People withdraw in the Privacy Center. | Deciding when consent is the right ground, and approving the text. |
| Sensitive data. Processing sensitive data without consent is prohibited, except in the cases the law lists, such as employment duties, legal claims or health care. | Art. 5 | Sensitive fields are marked in the RoPA and at collection, and GovernID recommends a DPIA for activities that use them. | Choosing the exception and the safeguards. |
| Security and processors. Apply technical and organisational measures and document them. Processors give sufficient guarantees and work under a written contract on your instructions. | Art. 8 | Safeguards are recorded for each activity and storage location, and Corporate Privacy Memory keeps how each activity looked on any past date. Processors and other recipients are recorded in each activity and shown as processing flows. | Implementing the measures and signing processor contracts. |
| Breach notification. Notify the Authority within 72 hours of discovering a breach, unless it would not affect people’s rights; a late notice must give the reasons for the delay. Tell the people affected, unless the data is unintelligible to others (for example, encrypted), later measures have removed the high risk, or it would take disproportionate effort, in which case a public notice is made instead. Document every breach with its causes, effects and remedies. | Art. 8; Ministerial Order No. 43/2022, Art. 4 | Breach Impact Analysis shows which activities used the affected system, which data was kept there and which safeguards applied. | Assessing the breach and notifying. |
| Data Protection Guardian. Appointing a guardian is optional unless the Authority requires it for certain categories. The guardian keeps the record of processing and reports to the Authority; the appointment is notified within 3 working days. | Art. 10 | Your DPO works from one RoPA, sees which activities are confirmed and which have changed, and can export reports for management. | Appointing the guardian and notifying the Authority. |
| Notification to the Authority. Notify the Authority before automated processing, with the purpose, data and people categories, recipients, transfers and security measures, unless an exemption applies, for example a guardian is appointed. Notify changes within 30 days. | Art. 14 | Your RoPA holds every item the notification asks for, for each activity, and process owners confirm their activities with every confirmation logged. | Filing the notification with the Authority. |
| Prior authorisation. Some processing needs the Authority’s written approval first, such as biometric data for identification, genetic data, matching files held for different purposes, and visual recording for surveillance. | Art. 15 | Each processing activity records the data categories it uses, so you can see which ones fall under these cases. | Applying for authorisation. |
| Information to people. When you collect data from the person, tell them who you are, the purpose, recipients, whether answering is required, their rights and any direct marketing use. When data comes from elsewhere, tell them within 5 days. | Art. 17 | Privacy notices are generated from the RoPA with these items and served as a link at the moment of collection. Each record keeps the notice version the person saw. | Approving the notice and keeping it accurate. |
| Access, correction and erasure. People can access their data free of charge, with a reply within 15 working days, and ask for correction, blocking or erasure, with a reply within 10 working days. | Art. 18, 23 | In the Privacy Center, people see the records that contain their verified contact details, withdraw consent, object to processing and get an instant preliminary report. DSAR Automation finds every record of a person across connected collection points. | Handling access, correction, blocking and erasure requests, and requests made through other channels. |
| Objection and direct marketing. People can object to direct marketing and to processing that causes them harm; stop within 10 working days. They can also object to decisions based only on automated processing. | Art. 19–22 | Marketing consent is its own box with its own text, never pre-ticked, and people withdraw it in the Privacy Center. Objections made in the Privacy Center reach your team at once, with their date. | Stopping the processing in your own systems in time. |
| Transfers abroad. Transfer only to countries on the Authority’s list of adequate protection, with the Authority’s case-by-case approval, or under one of the exceptions such as consent or a contract. | Art. 12, 13 | Transfers are recorded in each activity, appear in the privacy notice built from it, and GovernID recommends a DPIA when data is sent abroad. | Choosing the transfer route and getting approval. |
| Complaints. People can complain to the Authority in writing, including electronically. | Art. 25, 26 | Requests made in the Privacy Center are logged with their date, so you can show when each one arrived. | Answering the Authority. |
This page summarises the law to show where GovernID supports your work. It is not legal advice; your legal counsel decides how the law applies to your company.
Right of access: what a response must include
Under Article 18 PDPL, the controller must tell the data subject, on request and with proof of identity, whether their personal data is processed.
| The response must include | Article |
|---|---|
| Whether personal data is being processed | Art. 18(1) |
| All the data being processed | Art. 18(1)(1) |
| Source of the data, unless confidentiality is required by law | Art. 18(1)(2) |
| Purpose of processing | Art. 18(1)(3) |
| Names or categories of recipients | Art. 18(1)(4) |
| How the data is used where it is the sole basis of a decision directly affecting the data subject | Art. 18(1)(5) |
Deadline: 15 working days. The controller may ask for missing details within 10 days (Art. 18(2)). Fee: free.
What GovernID does: Every record collected through GovernID is stored with its purpose, legal basis, the notice version shown, consent scope, retention end date and collection point. These are the answers an access response has to give. In the Privacy Center, the individual sees their records instantly as a preliminary report and can export it, and your team finds a person's records across every GovernID collection point with PII Search.
What stays with you: Data held in systems outside GovernID and a copy of it, the formal response letter, identity checks beyond the verified e-mail, redaction of third-party data, and tracking the deadline.
Rectification, erasure and objection are separate rights and are handled separately; this section covers access only.
Frequently asked questions
Do we need to notify the Authority?
Usually, before automated processing (Art. 14). There are exemptions, for example when you have appointed a Data Protection Guardian, and some processing needs prior authorisation instead (Art. 15).
Is a Data Protection Guardian the same as a DPO?
The role is similar. Appointing one is optional unless the Authority requires it, and an appointed guardian keeps the record of processing (Art. 10).
Does the law require breach notification?
Yes. The law sets security duties (Art. 8), and Ministerial Order No. 43/2022, issued under it, requires notifying the Authority within 72 hours of discovering a breach, unless it would not affect people’s rights. The people affected must also be told, unless an exception applies. GovernID’s Breach Impact Analysis shows the scope of an incident from your records.
Where is our data hosted?
GovernID hosts each company’s data in the country where it is registered.
Is this page legal advice?
No. It summarises the law to show where GovernID supports your work. Your legal counsel decides how it applies to your company.
The law and its regulations: official sources
Links go to the issuing authority's own website. Some government sites restrict access from outside their country.
- Law No. (30) of 2018 with respect to Personal Data Protection – pdp.gov.bh, English translation
- Ministerial Order No. 42/2022: countries and territories with adequate protection – pdp.gov.bh, English translation
- Ministerial Order No. 43/2022: technical and organisational security measures – pdp.gov.bh, English translation