Ghana Data Protection Act 2012 (Act 843): can you host personal data abroad?
A practical guide for Ghanaian businesses, developers and agencies deciding where to host customer data. Based on the official text of the Act. Status as of 30.09.2026. This is general information, not legal advice.
Short answer
- 1Act 843 does not contain a section that bans hosting personal data outside Ghana. The published text has no section on cross-border transfer.
- 2What it does require: register with the Data Protection Commission (s. 27), secure the data (s. 28), and bind any processor by a written contract (s. 30).
- 3The Act applies to you if the data originates partly or wholly from Ghana (s. 45(1)(c)), wherever the server is.
- 4If your processor is not domiciled in Ghana, you must ensure it complies with the relevant laws of Ghana (s. 30(4)).
- 5Responsibility stays with you as data controller. A hosting provider does not certify compliance on your behalf.
What the Act says
The Data Protection Act, 2012 (Act 843) created the Data Protection Commission, which keeps the Data Protection Register. Section 17 lists the principles a person processing data must apply, including accountability, lawfulness of processing, openness and data security safeguards.
Scope. Under section 45(1) the Act applies to a data controller established in Ghana that processes data there, to a controller that is not established in Ghana but uses equipment or a data processor carrying on business in Ghana, and to processing of information which originates partly or wholly from Ghana. A controller not incorporated in Ghana must register as an external company (s. 45(2)).
Registration. A data controller who intends to process personal data must register with the Commission (s. 27). The application must include a description of the security measures and the name or description of the country to which the applicant may transfer the data (s. 47(1)). Registration is renewed every two years (s. 50). Processing without registration is prohibited (s. 53).
Security and processors. Section 28 requires appropriate, reasonable technical and organisational measures against loss, damage, unauthorised destruction and unlawful access. A processor may act only with the controller's prior authorisation and must treat the data as confidential (s. 29). The controller must ensure its processor complies with the security measures, under a written contract (s. 30). Where a processor is not domiciled in Ghana, the controller must ensure that it complies with the relevant laws of Ghana (s. 30(4)).
Breaches. If there are reasonable grounds to believe personal data has been accessed or acquired by an unauthorised person, the controller, or a third party processing under its authority, must notify the Commission and the data subject as soon as reasonably practicable (s. 31).
Foreign data. Section 18(2) covers the opposite direction: where personal data of foreign data subjects is sent to Ghana for processing, it must be processed in compliance with the data protection legislation of the foreign jurisdiction.
We read the text published by the Commission. We did not find amendments, and we did not verify secondary legislation or Commission guidance on transfers. Confirm the current position with the Commission before you decide.
Real-world examples
Online shop with Ghanaian customers
A Kumasi shop stores names, phone numbers and delivery addresses on a VPS in Frankfurt. It registers with the Commission, lists the country to which data may be transferred in its application (s. 47(1)(g)) and signs a written processing contract with the host.
Accra software company with a SaaS product
A startup keeps its customers' records in a PostgreSQL database on a rented server in the EU. It documents the security measures it applies, tests backups and keeps a procedure ready for reporting a breach.
Overseas company handling Ghanaian data
A company with no office in Ghana uses a local payroll processor. Under s. 45(2) a data controller not incorporated in Ghana must register as an external company.
Common mistakes
- Assuming that a server outside Ghana takes the data outside the Act. Section 45(1)(c) looks at where the information originates, not where it is stored.
- Processing personal data without registration. Section 53 prohibits it, and s. 56 makes failure to register an offence.
- Having no written contract with the host or processor, although s. 30(2) requires one.
- Treating security as a one-time setup. Section 28(2) asks you to verify regularly that safeguards work and to keep them updated.
- Having no plan for a breach. Section 31 requires notifying the Commission and the data subject as soon as reasonably practicable.
How 4hosting helps
Our datacenter is in the EU, in Frankfurt, not in Ghana. We say this plainly so that you can list the destination country accurately when you register. We offer a data processing agreement (DPA) under GDPR Article 28 and standard contractual clauses for transfers, which gives you the written processor contract that section 30(2) asks for.
Every plan includes monthly DevOps, CyberSecurity and Programming hours (from cPanel Advanced upwards; VPS plans include 1 to 8 hours). You can use them for server hardening, backups and WAF rules. 4hosting is not a compliance certifier and does not sign legal compliance for you. Migration is free. See the plans for what is included.
Frequently asked questions
Is it illegal to host Ghanaian personal data outside Ghana?
The published text of Act 843 contains no section prohibiting it. You must still register (s. 27), secure the data (s. 28) and control your processors by written contract (s. 30). Ask a Ghanaian lawyer or the Data Protection Commission about your specific case.
Where are 4hosting servers?
In the EU: Frankfurt, with points of presence in Frankfurt, London and New York. There are no 4hosting datacenters in Ghana.
Does 4hosting make me compliant with Act 843?
No. 4hosting does not certify legal compliance and holds no ISO, SOC 2 or similar certification; we describe our security practice as aligned with ISO 27001. We offer a data processing agreement (DPA) and can help with technical hardening through the included DevOps hours. Compliance of your processing remains your responsibility as controller.