Ceytrex ProductsPublished Updated 8 min readBy the Ceytrex Labs team

Ceytrex ID Vault - Digital Identity and Document Management for Sri Lankan Organisations

A patient file split across three departments. An employee onboarding folder nobody can find during an audit. A policyholder claim with no clear record of who approved what. Ceytrex ID Vault exists to put identity, documents, and access history in one place - with governance built in from day one.

Ceytrex Labs blog banner: "Identity and documents, locked down"

A patient's lab reports sit in one department's folder and the discharge summary in another. An employee's signed contract is in someone's email. An auditor asks who opened a claim file last month, and nobody can say. Scattered identity and document records are not just slow to search; from 1 January 2027, when key parts of Sri Lanka's Personal Data Protection Act come into operation, they become a compliance problem. This guide explains why, what the Act asks of organisations, and how to start fixing it in one department.

Quick answer: Sri Lanka's Personal Data Protection Act No. 9 of 2022 requires organisations that process personal data to keep it accurate, limited to its purpose, secure through measures such as access controls, and documented in a programme they can show to the regulator. Reporting on the Gazette published on 22 July 2026 says Part I (processing rules) and Part III (controller and processor duties) take effect on 1 January 2027. Ceytrex ID Vault gives each person one profile linked to their documents, with role-based access and a log of every view and change, which supports those obligations. It does not make you compliant on its own.

Why scattered records are a governance problem

Most document-heavy organisations in Sri Lanka, from private hospitals and channelling centres to schools, HR departments and insurers, store personal records in a mix of paper files, shared drives, spreadsheets and email attachments. Each copy is a separate risk:

  • No single version of the truth. Two departments hold different copies of the same person's record, and nobody knows which one is current.
  • No access boundary. A shared folder is usually all or nothing. Staff can open files they have no reason to see.
  • No history. When a file is opened, copied or changed, there is no record of who did it or when.
  • No retention control. Records are kept forever by default because nobody knows what can safely be deleted.
  • Slow answers. When a person asks what you hold about them, or an auditor asks for evidence, someone spends days searching.

Each of these maps directly to a duty in the data protection law, which is why the topic has moved from an IT convenience to a board-level question.

What the Personal Data Protection Act asks of organisations

The Act applies when personal data is processed wholly or partly in Sri Lanka, or by an organisation established in Sri Lanka or offering goods and services to people here (section 2). The obligations below are from Part I and Part III of the Act as passed in 2022. The Personal Data Protection (Amendment) Act No. 22 of 2025 changed parts of the law, so read the amended text on the Data Protection Authority website before relying on any section.

Obligation (section of the 2022 Act)What it means in practiceHow a governed vault helps
Lawful processing (s.5)Have a lawful basis, such as consent or a contract, for each type of recordDocument categories can carry the purpose and basis they are held for
Purpose limitation (s.6) and minimisation (s.7)Collect only what you need for a stated purposeStructured profiles replace "scan everything" folders
Accuracy (s.8)Keep data accurate and up to date; correct or erase outdated dataOne profile per person, so updates happen in one place
Retention (s.9)Keep identifiable data only as long as necessaryRetention rules are mapped per document type during setup
Integrity and confidentiality (s.10)Use technical and organisational measures, the Act names encryption and access controls among themRole-based access by role, branch or department
Transparency (s.11)Tell people what you hold and whyFaster answers because records are searchable by person
Accountability (s.12)Run a Data Protection Management Programme with catalogued records, oversight and a way to identify breachesAn audit trail of every view and update supports oversight and investigations
Data Protection Officer (s.20)Required for public bodies and for some processing, such as large-scale special categories like health dataA DPO needs logs and access reports to do the job
Processors (s.21)Use processors with appropriate safeguards, bound by a written contractAgree data processing terms with any vendor, including us
Breach notification (s.23)Notify the Authority of personal data breaches as rules will specifyAccess logs help you work out what was exposed
Impact assessments (s.24)Assess high-risk processing before starting itA pilot with a defined scope is easier to assess

When the obligations start

The Data Protection Authority was set up in 2023, and some administrative parts of the Act were brought into operation that year. An earlier plan to bring the main obligations into force on 18 March 2025 did not go ahead, and the 2025 amendment followed. According to the Daily FT's report of Gazette Extraordinary No. 2498/16 of 22 July 2026, sections 2 and 3, Part I and Part III take effect on 1 January 2027, and the Authority has advised organisations to use the months before then to review governance, policies, contracts and safeguards. Not every part of the Act starts on that date; check the DPA site for the current status of data subject rights and penalties.

This article explains the law in general terms to help you plan. It is not legal advice. For decisions about your organisation, read the Act and the Authority's rules and guidance, and speak to a lawyer or your Data Protection Officer.

What Ceytrex ID Vault does

ID Vault puts four things together that are usually managed separately:

  • Digital identity: one person, one profile, with a physical card, a QR code and an online identity page.
  • Document vault: upload, tag and retrieve reports, forms, certificates and history against that profile.
  • Role-based access: admins, staff, reviewers and customer portals with clear permission boundaries, set by role, branch or department.
  • Audit trail: every view and update is tracked for internal controls and traceability.

The ID Vault page describes how this applies to hospitals and clinics (a medical e-card with allergies, prescriptions, lab results and discharge documents), education (student ID with certificates, transcripts and admissions files), HR (contracts, onboarding documents and training certificates) and insurance and finance (KYC documents and claim history). These are the use cases the platform is designed for; each deployment is scoped to the organisation.

How to start small

A full rollout across every branch is a large change for staff. In the systems we build, a pilot in one department is the lower-risk route, and it gives you real evidence before a wider decision.

  1. Pick one workflow with clear pain. For example, patient documents in one clinic, or onboarding files in HR. Avoid starting with the most sensitive or most complex records.
  2. Make a record inventory. List the document types in that workflow, why you hold each one, who needs to see it and how long you should keep it. This is useful for the Act's accountability duty whether or not you use any software.
  3. Define roles before features. Write down who can view, upload, verify and manage each category. Keep it as narrow as the work allows.
  4. Clean up as you migrate. Do not import duplicates and outdated copies; decide which version is current and record that decision.
  5. Train the people who will use it daily. Adoption decides whether the old shared folder quietly comes back.
  6. Review after the pilot. Check retrieval time, whether access rules fit real work, and what the audit log shows. Then decide whether to extend to other departments or branches.

Pricing depends on scope. The ID Vault page lists a Pilot package (one department or branch), a Growth package (multi-branch structure, lifecycle workflows, audit reporting and migration planning) and an Enterprise package (advanced permissions, custom integrations and multi-site governance), each quoted after a discovery workshop. Larger integrations fall under our custom software work.

Questions to ask any document system vendor

  • Where is the data stored, who at the vendor can access it, and is that written into a contract (the Act expects controller-processor contracts)?
  • Can access be limited by role, branch and department, and can we export the access log?
  • How do we correct or delete a record, and how do we apply retention periods?
  • How do we get all our data out if we leave?
  • What happens to the audit trail when a staff member leaves the organisation?

Frequently Asked Questions

Does the Personal Data Protection Act apply to small private businesses?

The Act applies to processing personal data in Sri Lanka and does not exempt businesses by size. Some duties, such as appointing a Data Protection Officer, depend on the type and scale of processing, and the Authority will set details by rules. Check the DPA site for guidance that applies to you.

Will using ID Vault make us compliant?

No software makes an organisation compliant by itself. ID Vault provides access control, a single record per person and an audit trail, which support several obligations. You still need lawful bases, notices, retention decisions, contracts and a management programme.

Can we pilot with one department first?

Yes, and we recommend it. A pilot for one department, branch or workflow lets you test document structure, access rules and staff adoption before a broader rollout.

Can the profile and document categories match our own forms?

Yes. The identity profile fields, card layout, document categories, branch hierarchy and permission groups are configured for each organisation during setup.

Is health data treated differently?

The Act has stricter conditions for special categories of personal data, which include health data, and large-scale processing of special categories is one of the cases where a Data Protection Officer is required. Hospitals and clinics should plan for that.

Plan an ID Vault pilot for one department

Tell us which records cause the most trouble today. We will map document types, roles and retention with you and scope a pilot.

Sources

Ceytrex Labs meeting room and conference table
Call Us
Get in Touch