Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Personal Data Protection in System Design: A Guide for Jordan - Kemlat Insights
Kemlat2026-10-21T16:53:21+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Personal Data Protection in System Design: A Guide for Jordan

Jordan's Personal Data Protection Law changes how organisations should think about the systems they build. Many of the most useful protections are design decisions made long before go-live.

8 November 20266 min read
Share
Personal Data Protection in System Design: A Guide for Jordan - Kemlat Insights

Most organisations think about personal data protection after a system is built, when someone asks whether it is compliant. By then, the important decisions have already been made: what data is collected, who can see it, where it is stored and whether it can ever be deleted. Changing those decisions later is slow and expensive. Making them well at design time is far easier.

What the law means for system design, in general terms

Jordan’s Personal Data Protection Law No. 24 of 2023 came into force in 2024. At a general level, it sets conditions for collecting and processing personal data, with consent as a central basis and some defined exceptions. It gives individuals rights over their data, such as being informed and being able to access and correct it. It places obligations on organisations that hold and process personal data, including protecting it properly and dealing with breaches. It gives sensitive categories of data, such as health information, stronger protection, and it places conditions on transferring personal data outside Jordan. It also sets up a council to oversee how it is applied, and further regulations and instructions under the law add detail over time.

This article is not legal advice. The detail of how the law applies to your organisation depends on your sector, the data you hold and how you use it, so you should take advice from a qualified legal adviser. What follows are the practical design choices that make compliance much easier, whatever the precise legal position turns out to be.

Important: Treat legal advice and system design as two halves of the same task. Your adviser tells you what the obligations are; your system design decides whether you can actually meet them.

Start with a map of the personal data you hold

You cannot protect data you have not identified. Before designing or changing a system, build a simple inventory of personal data. For each type, record what it is, why you collect it, where it is stored, who can access it, who it is shared with, and how long you keep it.

Imagine a network of private schools in Amman building a new parent portal and student information system. The first inventory session finds personal data in far more places than expected: student records and grades, medical notes for students with allergies or conditions, parents’ identity numbers and contact details, fee payment records, bus route information with home locations, photographs from school events, and staff files. Some of it sits in the old system, some in spreadsheets held by individual administrators and some in a messaging group used by bus supervisors.

That inventory becomes the foundation for every design decision that follows. It also tends to expose data that nobody needs any more.

Design choices that protect personal data

Most good data protection in systems comes down to a handful of principles applied consistently. They are good practice in their own right, and they map closely to what data protection laws generally expect.

  • Collect only what you need. Every field on a form should have a reason. If the school does not need a parent’s place of work, the portal should not ask for it. Data you never collect cannot leak.
  • Be clear about purpose. Record why each type of data is collected and design the system so it is used for that purpose. Contact details collected for school communications should not quietly become a marketing list.
  • Record consent where you rely on it. If consent is the basis for processing, the system should store what the person agreed to, when and how, and let them withdraw it as easily as they gave it.
  • Restrict access by role. A bus supervisor needs a pickup location and a phone number, not grades or medical notes. A teacher needs their own classes, not the whole school. Role-based access is one of the most effective technical protections.
  • Handle sensitive data separately. Health information and similar categories deserve extra restrictions, tighter access and, where possible, separation from general records.
  • Log access to important records. Being able to see who viewed or changed a record helps detect misuse and investigate incidents.
  • Build in retention and deletion. Decide how long each type of data is kept and make sure the system can actually delete or anonymise it. Many older systems cannot delete anything, which becomes a real problem.

Designing for individuals’ rights

When individuals have rights over their data, your systems need to support them in practice. If a parent asks what data the school holds about their child, can staff produce it without searching six places? If they ask for an error to be corrected, does the correction reach every system that holds a copy?

Designing for this means keeping personal data in as few places as possible, with clear links between them, and having a documented process for handling requests: who receives them, who checks the requester’s identity, who gathers the data and how quickly a response is given. A simple request log helps show that requests are handled properly.

Hosting, vendors and the things people forget

Several design areas are commonly overlooked:

  1. Where data is hosted. If a system or cloud service stores data outside Jordan, the law’s conditions on cross-border transfer may apply. Ask vendors where data is stored and processed, including backups, and check the position with your adviser.
  2. Vendor contracts. Software providers and IT partners who handle your data should have clear contractual obligations about how they protect it, what they may use it for and what happens at the end of the contract.
  3. Test and training environments. Copying live personal data into a test system is common and risky. Use anonymised or invented data for testing wherever possible.
  4. Exports and spreadsheets. A well-protected system loses much of its value if staff can export everything to Excel and email it. Control who can export, and what.
  5. Breach response. Decide in advance how a suspected breach is reported internally, who assesses it and how the organisation meets any notification obligations. Systems should keep the logs needed to understand what happened.

Making protection part of how the organisation works

Systems only do half the job. The other half is people and process: clear ownership of personal data in each department, short training for staff on what they can and cannot do, and regular reviews of access and retention. A system that restricts access perfectly can still be undermined by a shared password or a screenshot sent in a chat group.

In the school network example, the new portal is designed with role-based access, separate handling of medical notes, a retention schedule per record type and an export restriction. The messaging group for bus supervisors is replaced by a simple view in the portal showing only what they need. Each school appoints a person responsible for handling parents’ data requests.

Designing systems people can trust with their data

Personal data protection is far easier to achieve when it is designed into systems from the start than when it is added afterwards. Mapping the data, collecting less, restricting access, planning for deletion and choosing vendors carefully all make compliance more achievable and reduce the risk of harm.

Our Enterprise Systems service includes requirements analysis, system design and data architecture with these principles built in, working alongside your legal advisers rather than replacing them. Where ownership of data is unclear across departments, our Operations Transformation work helps define who is responsible for what.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Operations Transformation

Explore our services

Related insights

Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights
Enterprise Systems

Budgeting for an ERP Project: The Costs People Forget

ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add…

14 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.