Where your dataactually lives.
Understand the infrastructure behind LoginHR — from hosted production environments in Frankfurt to deployment inside your own data center.
Real infrastructure. Clear responsibilities. Transparent data protection.
Conceptual diagram of three layers: the LoginHR application, a hosting environment, and a data center facility in Frankfurt. It is not the operator’s network topology.
- Frankfurt, GermanyNamed hosting region
- EU hosting regionEuropean Union
- N+1 powerFacility redundancy
- N+1 coolingFacility redundancy
- Cloud / on-premisesTwo deployment choices
Infrastructure location
Built on infrastructure you can locate.
LoginHR production workloads for hosted clients run inside a carrier-neutral colocation facility in Frankfurt, Germany, operated by a global data-center provider.
Frankfurt
Germany
EU region
- 01FrankfurtEuropean hosting regionThe hosting region. No street address is published.
- 02N+1Power redundancyA facility standard. It is not a LoginHR application specification.
- 03N+1Cooling redundancyA facility standard. It is not a LoginHR application specification.
- 04ColocationCarrier-neutral facilityPhysical environment around the servers. The operator is not named on this page.
The colocation facility is the building and its power, cooling and physical security. It is not, by itself, a description of LoginHR’s application architecture.
The operator’s name is disclosed to customers under NDA during technical due diligence. It is not published here.
Facility resilience
Resilience starts before the software.
N+1 power, N+1 cooling, and a carrier-neutral colocation. The drawing explains the idea. It is not an as-built plan.
N+1 power
Redundant power capacity intended to tolerate the loss of one relevant component under the facility’s design. Component counts and electrical paths are not published.
Facility standards
Independent standards. Clearly attributed.
The hosting facility operates under twelve certifications, attestations, standards and sustainability schemes. They are not all the same kind of credential.
These are facility or operator credentials, not LoginHR certifications. They cover the data center environment in the scope defined by the issuing organization, including power, cooling, physical infrastructure and physical security. A facility standard does not automatically cover every part of the LoginHR service.
Facility credential
ISO 27001
Information-security management system
Management systems
ISO management-system standards. Confirm site, scope and current validity for the Frankfurt facility.
Site, scope, validity and the issuing body are confirmed during technical due diligence. The grouping on this page is a reading aid.
The data center operator is disclosed to clients under NDA during technical due diligence. Certificate files are not published on this page.
Deployment choice
Your infrastructure. Your choice.
Two paths are described. They do not share the same operator, the same residency, or the same responsibilities.
Conceptual diagram of a hosted deployment: the application inside a hosting environment, inside a facility boundary marked Frankfurt.
- Location
- Frankfurt, Germany.
- Environment
- A European colocation facility operated by a third-party infrastructure provider.
- Data residency
- Hosted data is physically located in the European Union.
- Consideration
- Cross-border transfer requirements must be assessed for personal data moving from Egypt.
Conceptual diagram of an on-premises deployment: the application inside a customer-controlled boundary. No network devices are specified.
- Location
- The customer’s own data center.
- Environment
- Customer-controlled hosting infrastructure.
- Data residency
- An Egyptian on-premises deployment can support organizations that require their data to remain in Egypt, subject to the actual system architecture, integrations, backups and data flows.
- Consideration
- Physical hosting does not automatically establish compliance with every privacy or security requirement.
Due diligence
The questions enterprise buyers should ask.
Why the facility matters
Ask these of the facility before relying on a hosting claim.
- 01Where is data physically stored?
- 02Who controls physical access?
- 03How are power failures handled?
- 04How is cooling resilience addressed?
- 05What evidence supports the facility’s claims?
A certified colocation environment is one way those questions are answered in writing. The documents are shared in due diligence and are not reproduced here.
Cross-border transfer, stated openly
Hosted deployments place data in a European region. That fact should be visible before a contract, not after.
- 01Employee information may include personal data originating in Egypt.
- 02Egyptian Personal Data Protection Law 151/2020 creates obligations concerning relevant cross-border transfers.
- 03Authorisation, where required, runs through the Personal Data Protection Centre.
- 04On-premises deployment in Egypt is offered as an alternative.
Not every transfer requires the same authorisation. Licensing, permits, exemptions, implementing regulations and current procedure are checked with qualified counsel. No transfer authorisation is presented as already granted.
Data protection
Data protection. Explained obligation by obligation.
Two statutes. Open either one for the article and the support LoginHR provides.
These are the controls and support mechanisms LoginHR provides. They do not, by themselves, make the customer or LoginHR legally compliant.
European Union
GDPR. From requirement to operational response.
Six obligations, the article each one rests on, and the support LoginHR provides.
Lawful basis
Article 6
Each employee-data category is associated with a declared lawful basis, such as contract, legal obligation or consent, and that basis is kept with the underlying record.
LoginHR records the basis the customer declares. It does not choose the lawful basis for the customer.
Egypt
Egyptian data protection. Made understandable.
Law 151/2020 includes a data-protection contact, cross-border transfer, and retention. These are not the GDPR articles above.
151 / 2020
Lawful basis and consent
Law 151/2020
Data categories are declared with processing purposes, and configurable consent capture is associated with relevant categories where applicable.
Product support for the basis the customer declares. It does not decide when consent is the right basis.
Responsibility
From regulation to responsibility.
An obligation and the support LoginHR provides are different things. Choose a mechanism to see which entries use it.
GDPR
- Lawful basisArticle 6In the product
- Data subject rightsArticles 15–22In the product
- Records of processingArticle 30Document
- Breach notificationArticles 33–34Process
- International transfersChapter VStated openly
- Security of processingArticle 32In the product
Egyptian PDPL
- Lawful basis and consentLaw 151/2020In the product
- Data subject rightsLaw 151/2020In the product
- Data protection officerLaw 151/2020Contractual
- Breach notificationLaw 151/2020Process
- Records of processingLaw 151/2020Document
- Cross-border transferLaw 151/2020Stated openly
- Security measuresLaw 151/2020In the product
- Retention and deletionLaw 151/2020In the product
This map shows where each control lives: in the product, in a document, in a process, in the contract, or as a disclosure. It is not an independent assessor’s finding.
Technical due diligence
Your data deserves clear answers.
Talk with LoginHR about the hosting record and the protection duties on this page.
Additional facility information and technical documentation are available under NDA during due diligence.