Legal Document

Privacy Policy

ACMIS Document Verification — Official Privacy Policy for the Android Application

Published by the HEMIS Consortium  |  Effective Date: 19 February 2026  |  Version 1.0

Table of Contents

  1. Who We Are
  2. Scope of This Policy
  3. Permissions We Request
  4. Information We Collect
  5. How We Use Your Information
  6. Data Storage & Security
  7. Data Sharing & Third Parties
  8. Data Retention
  9. Children's Privacy
  10. Your Rights
  11. Changes to This Policy
  12. Contact Us

1 Who We Are

The ACMIS Document Verification application ("the App", "we", "us", or "our") is developed and maintained by the HEMIS Consortium, a consortium of higher education institutions in Uganda that operates the Academic Information Management System (ACMIS) platform.

The App is used exclusively by authorised staff members of member universities and institutions connected to the HEMIS Consortium to verify student academic documents and graduation invitation cards at institutional entry points and events.

Note: This application is not intended for use by the general public. It is a professional tool issued to and operated by authorised institutional staff only.
↑ Back to top

2 Scope of This Policy

This Privacy Policy explains what information is collected when you use the App, how that information is used and protected, and the choices you have with respect to your personal data. It covers:

By installing and using the App you agree to the practices described in this policy. If you do not agree, please uninstall the App and contact your institution's IT administrator.

↑ Back to top

3 Permissions We Request

The App requests the following Android permissions. Each permission is strictly necessary for core functionality; we do not request permissions beyond what is required.

Permission Classification Why it is needed
INTERNET Normal Required to communicate with your institution's ACMIS server to authenticate staff, load the list of institutions, and retrieve student document data during verification. All network traffic is encrypted using HTTPS.
CAMERA Dangerous (runtime) Required to activate the device's rear camera for scanning QR codes printed on student academic documents (registration cards, exam permits, certificates, transcripts, virtual IDs, and graduation invitation cards). The camera is activated only when you explicitly tap "Scan QR code" and is released immediately after a successful scan or when you leave the scanner screen. No images or video are recorded, stored, or transmitted.
Camera access: The App uses the camera solely for real-time QR code decoding. No photographs, video recordings, or screenshots are ever saved to the device gallery or uploaded to any server.
↑ Back to top

4 Information We Collect

4.1 Staff Authentication Data

When you log in, you provide your institutional email address and password. Your password is never stored on the device. Before transmission it is encrypted using AES-256-CBC with PKCS7 padding and an EVP-BytesToKey-derived key, then sent over an encrypted HTTPS connection to your institution's authentication server. The plaintext password is discarded immediately after encryption.

Upon successful login, the server issues an authentication token. This token is stored locally on the device using Android's Shared Preferences storage in order to keep you logged in across app sessions. It contains no personal information beyond a reference to your staff account.

4.2 Device Identification

To prevent unauthorised access the App registers each installation as a unique device with the ACMIS platform. It collects the following device-level data on first launch:

This information is sent once to the ACMIS device-registration endpoint and is subsequently used only for device-level authentication (the App exchanges device credentials for a device token used in subsequent API calls).

4.3 Student / Document Data Retrieved During Verification

When a verification is performed (via QR scan or manual entry), the App queries your institution's ACMIS server and temporarily displays the result on screen. This may include:

This data is not stored persistently on the device. It is held in memory only for the duration of the verification session and is cleared when you navigate away from the results screen or close the App.

4.4 App Preferences

The App stores the following minimal preferences locally using Android Shared Preferences:

4.5 Data We Do NOT Collect

We do not collect or process any of the following:
↑ Back to top

5 How We Use Your Information

All information collected is used solely for the following lawful purposes:

No profiling, advertising, or sale of data. We do not build user profiles, serve advertisements, or sell, rent, or trade any personal data to third parties for commercial purposes.
↑ Back to top

6 Data Storage & Security

6.1 On-device Storage

Minimal persistent data (device token, staff session token, onboarding flag, selected institution) is stored in Android Shared Preferences, which is sandboxed to the App and is not accessible by other apps on the device (unless the device is rooted).

6.2 In-transit Security

All API communication between the App and the ACMIS servers takes place over HTTPS (TLS 1.2 or higher). Staff passwords are additionally encrypted with AES-256-CBC before transmission, providing an additional layer of protection even if a network interception were attempted.

The graduation-card verification endpoint is further protected by a request header containing an AES-encrypted API key that is validated server-side before any student data is returned.

6.3 Server-side Storage

Student records, staff accounts, and audit logs reside on servers operated by the individual member institutions (or their designated hosting providers) and are subject to each institution's own security and data-governance policies. The HEMIS Consortium does not operate a centralised copy of student data.

6.4 No Third-party Analytics or Crash Reporting SDKs

The App does not integrate any third-party analytics, advertising, or crash-reporting SDKs (e.g. Firebase, Crashlytics, Sentry, or similar). Diagnostic information about app failures is not automatically transmitted to any external service.

↑ Back to top

7 Data Sharing & Third Parties

We do not share your personal data with third parties except in the following limited circumstances:

There are no advertising networks, data brokers, social media platforms, or other commercial third parties with whom we share data.

↑ Back to top

8 Data Retention

On-device Data

Data stored locally (session tokens, device token, onboarding flag, selected institution) is retained until:

Server-side Data

Audit logs of verification events (staff account, scanned serial number / student number, timestamp) are retained by each institution's ACMIS deployment for as long as the institution's data-retention policy requires. Please contact your institution's data controller for details.

↑ Back to top

9 Children's Privacy

The App is designed exclusively for use by adult staff members of higher education institutions. It is not directed at, and we do not knowingly collect personal information from, children under the age of 18.

If you believe that a child under 18 has provided personal information through the App, please contact us immediately at the address in §12 so that we can take appropriate action.

↑ Back to top

10 Your Rights

Subject to applicable data-protection law (including, where relevant, the Uganda Data Protection and Privacy Act 2019), you may have the following rights with respect to your personal data:

Because student data retrieved during verifications is not stored on-device beyond the active session and is held server-side by your institution, requests relating to student data should be directed to the relevant institution's data-protection officer.

To exercise any of the above rights in relation to data processed by the HEMIS Consortium, please use the contact details in §12.

↑ Back to top

11 Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes we will:

Where required by law or where the changes are material, we may also provide in-app notice or notify institution administrators directly.

Your continued use of the App after changes are posted constitutes your acceptance of the updated policy. If you do not accept the revised policy, please stop using the App and contact your institution's IT administrator.

↑ Back to top

12 Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or our data-handling practices, please contact the HEMIS Consortium data controller:

HEMIS Consortium

Website: hemis.ac.ug

Email: support@acmis.ac.ug

For student data matters, please additionally contact your institution's own Data Protection Officer or Registrar's office.

↑ Back to top