Privacy Policy for QRAfT

Last updated: July 10, 2026

QRAfT (QR Attendance for Teachers) is an Android app that helps a teacher keep a class roster, print QR ID cards, scan students in each morning, and export a daily attendance sheet as a PDF. This page explains what information the app handles and how.

Who Uses This App

QRAfT is used by teachers and school staff to keep attendance records. Students do not install the app, log into it, or provide any information to it directly — any information about a student is entered by the teacher, at their own and their school's discretion, for the ordinary purpose of keeping a classroom attendance record.

1. Information the App Stores

When a teacher uses QRAfT, the following is entered and stored:

• Student records — Full Name, LRN (Learner Reference Number), Grade, Section, Age, and Sex
• Attendance records — derived from the student records above: date, time, and present/absent status
• School/teacher profile (optional, printed on exported sheets) — Municipality/Town, School Name, School Address, School ID, and the teacher's name

All of the above is stored only locally on the teacher's device, in a private on-device database. QRAfT has no backend server and does not transmit this information anywhere. The app's Android configuration explicitly excludes this database from Android's automatic cloud backup, so it is not copied to Google Drive or any cloud storage by the operating system either.

This data stays on the device until the teacher deletes it (editing or removing a student, clearing an attendance sheet) or uninstalls the app, which permanently deletes it.

2. Information Handled by Third-Party Services

QRAfT uses the following Google services, each governed by Google's own policies:

• Google Mobile Ads (AdMob) — displays banner ads inside the app. Google's ad SDK may collect device and advertising identifiers to serve and measure ads, per Google's Privacy Policy and AdMob's data collection disclosures. QRAfT does not receive or store the data Google's ad SDK collects.
• Google Play services (Code Scanner API) — provides the full-screen QR code scanning UI. This runs through Google Play services on the device and may communicate with Google's servers to provide the scanning feature.

QRAfT does not use any other analytics, tracking, or advertising SDKs, and does not request access to contacts, location, microphone, or photos.

3. Children's Information

QRAfT is not directed at children and is not used by children — it is a tool for teachers. Student information entered into the app is limited to what a teacher ordinarily records for attendance purposes (name, LRN, grade/section, age, sex), stays on the teacher's device as described above, and is not shared with QRAfT's developer or any third party (other than the ad SDK behavior described above, which is unrelated to and does not include student records).

4. Your Choices

Because all school data lives on the teacher's own device, the teacher is in full control of it: edit or delete any student or attendance record inside the app at any time, or uninstall the app to remove everything permanently.

5. Changes to This Policy

If this policy changes, the updated version will be posted at this same page with a new "Last updated" date.

6. Contact

Questions about this policy or QRAfT's data practices can be sent to: pepooh696@gmail.com