Data Processing Agreement
Version 1.0 · Effective [EFFECTIVE DATE]
Draft — details pending legal review. Items in [square brackets] are still to be confirmed by the operator.
In short
- Public summary / template — not the signed contract. The binding version is the agreement signed between the parties; where they differ, the signed agreement prevails.
- EPS Exam decides why and how learner data is used; Lacspace only processes it on EPS Exam's documented instructions.
- Lacspace must keep data confidential and secure, use only listed subprocessors, help with user rights requests and report incidents promptly.
- At the end of the engagement, data is returned or deleted as instructed.
This summary is for convenience — the numbered sections below are the full text.
1. Parties
2. Background and relationship to other agreements
3. Definitions
"Personal data" means information that identifies or can identify an individual. "Processing" means any operation on personal data. "Data subjects" are the individuals whose data is processed. "Subprocessor" means a third party engaged by the Processor to process personal data. "Incident" means a breach of security leading to accidental or unlawful destruction, loss, alteration, disclosure of, or access to, personal data.
4. Roles
The Controller determines the purposes and means of processing. The Processor processes personal data only on the Controller's behalf and does not use it for its own purposes.
5. Controller's responsibilities
The Controller is responsible for having a lawful basis and giving notices to data subjects (including the Privacy Policy), for the accuracy of instructions, and for the content it publishes.
6. Documented instructions
The Processor processes personal data only on the Controller's documented instructions — this DPA, the engagement, and written instructions given through agreed channels (including admin-portal configuration). The Processor will tell the Controller if it believes an instruction breaks the law.
7. Scope of processing
The subject matter, duration, nature, purposes, data categories and data subjects are described in Schedule 1.
8. Confidentiality
The Processor ensures that personnel authorised to process personal data are bound by confidentiality obligations and access it only as needed for their role.
9. Security
The Processor implements appropriate technical and organisational measures, including those in Schedule 2, and reviews them as risks and technology change.
10. Subprocessors
The Controller authorises the subprocessors listed in Schedule 3. The Processor imposes data-protection obligations on each subprocessor that are no less protective than this DPA, and remains responsible for their performance.
11. Changes to subprocessors
The Processor will give the Controller at least [NOTICE PERIOD — e.g. 15] days' written notice of a new or replacement subprocessor. The Controller may object on reasonable data-protection grounds, and the Parties will discuss in good faith.
12. International transfers
Personal data may be stored or processed outside Nepal at the locations in Schedule 3 (including India). The Processor will transfer data only to those locations or others approved in writing, using providers with recognised security standards.
13. Data subject requests
The Processor will promptly forward to the Controller any request it receives from a data subject, and will provide reasonable technical help (for example export, correction and deletion tools) so the Controller can respond.
14. Assistance to the Controller
The Processor will reasonably help the Controller meet its obligations on security, incident handling, risk assessments and responding to authorities, taking into account the information available to the Processor.
15. Incident notification
The Processor will notify the Controller without undue delay, and in any case within [INCIDENT NOTICE HOURS — e.g. 48] hours, after becoming aware of an incident, with the information then available, and will take reasonable steps to contain and remediate it.
16. Records
The Processor keeps records of the processing it performs for the Controller, including subprocessors, locations and security measures, and makes them available on request.
17. Audits
On reasonable notice, the Processor will make available information needed to show compliance with this DPA, and allow reasonable audits by the Controller or an auditor it appoints, no more than once a year unless an incident has occurred.
19. Return and deletion
At the end of the engagement, the Processor will, at the Controller's choice, return the personal data in a commonly used format and/or delete it within [DELETION PERIOD — e.g. 30] days, except where the law requires retention, in which case it remains protected under this DPA.
20. Backups
Data in backups is deleted in the normal backup cycle ([BACKUP RETENTION — e.g. 30 days]) and is not restored except for recovery purposes.
21. Liability
Each Party's liability under this DPA is as set out in the engagement, without limiting liability that cannot be limited by law.
22. Duration
This DPA lasts as long as the Processor processes personal data for the Controller, and its confidentiality and deletion obligations survive termination.
23. Changes
This DPA may be changed only in writing signed by both Parties. The public summary on this page will be updated to reflect material changes.
24. Governing law and disputes
This DPA is governed by the laws of Nepal. Disputes will be resolved first by negotiation and then as set out in the engagement or, failing that, by the courts of Kathmandu.
25. Contacts
Schedule 1 — Processing details
| Item | Details |
|---|---|
| Subject matter | Operation of the EPS Exam website, admin and institute portals, mobile app and API |
| Duration | For the term of the engagement, plus the return/deletion period |
| Nature | Hosting, storage, retrieval, structuring, transmission, backup, deletion, technical support and maintenance |
| Purposes | Accounts, exam delivery and scoring, results and leaderboards, orders and payment verification, order tracking, support and complaints, newsletters (on consent), institute accounts, security |
| Data subjects | Learners (including minors with guardian involvement), parents/guardians, institute staff and students, teachers, customers, newsletter subscribers, enquirers |
| Data categories | Name, email, phone, password hash, display name, exam attempts/results/rank, orders and payment references, payment screenshots, device identifier, support messages and complaints, institute/batch membership, technical logs |
| Special categories | None intended. Identity documents are not requested unless a feature expressly requires them |
Schedule 2 — Security measures
- Encryption in transit (HTTPS/TLS) for all web, app and API traffic.
- Passwords stored only as salted one-way hashes; one-time codes are short-lived.
- Role-based access for admin and institute portals; least-privilege access for staff.
- Authentication tokens with expiry; rate limiting and CAPTCHA on sensitive endpoints.
- Server-side verification of eSewa and Khalti payments; no storage of wallet PINs or card data.
- Audit logging of administrative actions.
- Credentials and secrets kept out of source code and rotated when exposure is suspected.
- Regular backups of the database; encryption at rest as provided by the hosting providers — [CONFIRM encryption at rest on database and storage].
- Dependency updates and security fixes applied as part of maintenance.
- Incident response process with notification to the Controller.
Questions about this policy? Contact EPS Exam Customer Support at epsexam2008@gmail.com or +977-9815393939. To make a formal complaint, use our Complaints & Grievance page.
Related policies
- Terms of Use
- Privacy Policy
- Cookie & Storage Notice
- Payments & Billing
- Refund Policy
- Exam & Results Policy
- Learner Content Licence
- Code of Conduct
- Account & Data Deletion
- Complaints & Grievance
- Copyright & Takedown
- Disclaimer
- Security & Responsible Disclosure
- Accessibility Statement
- Software Licence (Lacspace)
- All legal documents
EPS EXAM DOT COM