Privacy Policy
Last updated: November 2026
1. Who we are
EduMarks is a cloud-based, multi-tenant school management and Education Operations / Enterprise Resource Planning platform, operated by EnigmaSoft (referred to here as "EduMarks", "we", "us", or "our"). This policy explains how we handle personal data across the Service — whether you're a school administrator, a teacher or other staff member, a parent or guardian using the Parent Portal, or a learner.
2. Scope of this policy
This policy covers personal data processed through the Service itself (the school-facing platform, the Parent Portal, and this marketing website) — it does not cover any third-party site you reach by following a link from ours. Where a School (a school, trust, or organisation using the Service) is the Controller for personal data it enters into the Service — meaning it decides why and how that data is used — this policy explains our role as the School's data Processor for that data, per Section 4. Where we act as Controller in our own right (for example, for this marketing website's own visitor data, or a School's own billing relationship with us), this policy explains that processing directly.
3. Categories of personal data we collect
Depending on which modules a School's Package enables, the Service may hold:
- Learner data: name, class/grade, attendance records, marks and report cards, conduct/disciplinary records, and — where enabled — timetable and lesson-plan assignments;
- Parent/guardian data: names and contact details, and any messages exchanged through the Parent Portal;
- Staff data: names, roles, timetables, payroll-related identifiers, and — where the HR module is enabled — performance records;
- Account data: login credentials (stored as a one-way hash, never in plain text) and related session metadata for anyone with a Service account;
- Uploaded documents: staff and student signature images, and payment-proof images submitted through the fees module;
- Payment/billing data: fee and invoicing records, where a School processes fees or subscription billing through the Service;
- Support communications: anything you send us directly for support purposes.
We do not design the Service to collect special categories of personal data (such as health, religious, or biometric data). If a School enters such information into a free-text field of its own accord, it does so as the Controller responsible for that decision — see Section 8's note on legal bases.
4. Sources of data
Almost all personal data in the Service is entered directly by a School's own Administrators, staff, or (through the Parent Portal) parents/guardians — we do not buy, scrape, or independently source personal data about learners, staff, or parents from anywhere else. As explained in Section 2, Schools act as the Controller for the data they enter: they decide what to collect and are responsible for having a lawful basis to collect it (including obtaining any notice or consent from parents/guardians that applicable law requires — see Section 12).
5. Purposes of processing
We process personal data to: provide the Service's core functionality (record-keeping, report cards, fee receipting, payroll, the Parent Portal); maintain the security and integrity of the Service, including tenant isolation between Schools; respond to support requests, including the account-recovery tools described in Section 6; comply with legal obligations; and administer a School's own account and billing relationship with us. We do not use personal data entered into the Service for advertising, and we do not sell personal data.
6. Legal bases for processing, where applicable
Where applicable law requires a lawful basis for processing, we rely on: performance of our contract with the School (the Terms of Service and Data Processing Agreement) for ordinary Service delivery; our legitimate interest in keeping the Service secure and functioning, for security-related processing; and compliance with a legal obligation, where one applies. For personal data a School itself enters about its own learners, staff, and parents/guardians, the lawful basis is a matter for the School as Controller — see Section 12.
7. Sharing and disclosure
We share personal data with:
- the small number of Sub-processors described in our Data Processing Agreement (provided to schools during registration), engaged solely to help us deliver the Service (for example, our transactional email provider);
- a School's own Authorised Users, within that School's own Account — never across Schools, per the tenant isolation described in our Terms of Service;
- law enforcement or regulators, where required by law;
- a successor entity in the event of a merger, acquisition, or sale of assets, subject to that entity being bound by materially equivalent privacy commitments.
We do not sell personal data, and we do not share it with third parties for their own independent marketing purposes.
8. Retention periods
- Active account data is retained for as long as a School's subscription remains active, so the Service's core function — an ongoing academic and administrative record — keeps working.
- Security and activity logs (audit trails of account activity) are retained for 24 months, after which older entries are automatically pruned.
- Backups follow the same retention as the data they contain, and age out of our backup rotation accordingly rather than being kept indefinitely.
9. Security measures
We use technical and organisational measures appropriate to the sensitivity of the data involved, including encrypted transport, hashed credential storage, tenant-isolated data access, CSRF and session protections on account-modifying actions, and audit logging of both ordinary account activity and our own support-team access tools. Full detail on these measures, including the specific support tools our team can use and how their use is logged, is in our Data Processing Agreement (provided to schools during registration).
10. Cookies and tracking
The Service uses one cookie that is strictly necessary: a session cookie that keeps you signed in as you move between pages, and carries your progress through registration. It expires automatically after a period of inactivity and is cleared when you sign out. Your browser may also keep a few small preferences locally, for example that you dismissed a banner; these are never sent to us.
We do not use advertising cookies, third-party tracking scripts, or analytics services that track individual visitors across sites.
10A. Website contact form
The contact page (/contact) has a message form. If you use it we collect your name, email address, optional school name and message, and email them to our support mailbox. We use them only to reply to you and keep them in that mailbox until they are no longer needed; you can ask us to delete yours at any time (section 14). To limit abuse we use a one-way hash of your IP address for rate limiting; the address itself is not stored.
10B. Developer portfolio: contact form and visitor counts
The public developer page (/developer) has a contact form. If you use it we collect your name, email address, message and, if you choose, a budget range. We use them only to reply to you. They are emailed to the site owner and kept until the owner deletes them; you can ask us to delete yours at any time (section 14). To limit abuse we store a one-way hash of your IP address with the message and use it for rate limiting; the address itself is not stored and the hash cannot be reversed.
The page also keeps anonymous daily counters (page views, clicks on outbound links, CV downloads). They contain no IP address, no cookie, no browser details and no visitor identifier, and nothing is counted when your browser sends Do Not Track or Global Privacy Control. The page loads no third-party fonts, scripts or trackers.
11. Data subject rights
If a School entered your personal data into the Service (for example, as a learner, parent/guardian, or staff member), that School is the Controller responsible for your request — please contact your School's Administrator first, since we are required to act on the Controller's instructions per our Data Processing Agreement. If you're unable to reach a resolution with your School, or your request relates to data we hold as Controller in our own right (Section 2), contact us using the details in Section 14 and we will assist, consistent with applicable law — which may include rights to access, correct, delete, or object to processing of your personal data, depending on your jurisdiction.
12. Children's data
Because the Service is built for schools, it necessarily processes personal data about learners who are minors. Schools using the Service act as Controller for that data, and are responsible for obtaining any parental/guardian notice or consent applicable law requires before entering a learner's data into the Service — this policy, and the Service itself, do not substitute for that responsibility. We do not knowingly collect personal data about children other than through a School's own use of the Service as Controller, and we do not use learner data for advertising or profiling unrelated to the Service's educational and administrative purpose.
13. Automated decision-making
The Service does not make automated decisions producing legal or similarly significant effects about a Data Subject without human involvement. Features such as computed grade averages, attendance summaries, or fee-balance calculations are administrative aids for the School's own staff to review and act on — they are not automated decisions applied to a Data Subject without a human School representative in the loop.
14. Contact for privacy requests
For privacy questions or requests relating to data we hold as Controller in our own right, contact admin@edumarks.co.ls. For data a School entered as Controller, please contact that School's Administrator directly in the first instance, per Section 11.
15. Policy updates
We may update this policy from time to time, most often to reflect new features, legal or regulatory requirements, or operational changes. Material changes will be posted here with an updated "Last updated" date, and — where the change is significant — communicated to School Administrators directly.