🏛️ University Edition

University Privacy Policy

Your guide to how AttendQuick protects university professor, class representative, and student attendance data with end-to-end security and offline autonomy.

← Back to Legal Portal

1. Overview & Commitment

Effective Date: September 7, 2026

Welcome to AttendQuick University Edition (developed by Arshad Ali Kalhoro). AttendQuick is an advanced attendance and academic record platform built for university professors, instructors, and Class Representatives (CRs). Our fundamental engineering philosophy is privacy-first and offline-first.

We do NOT sell, rent, monetize, or harvest personal data. Student lists, roll numbers, and attendance records belong exclusively to you and your educational institution.

2. User Roles & Data Isolation

AttendQuick University implements strict role-based separation between Teacher accounts and Class Representative (CR) accounts:

👨‍🏫 University Teachers / Professors

Teachers create their university workspace, define subjects/classes, enroll student rosters, assign CRs with specific access permissions (e.g. today-only attendance, past date restrictions, report views), review attendance correction requests, and broadcast official announcements.

🎓 Class Representatives (CRs)

CRs can take attendance for classes assigned to them by their teachers under strict teacher-defined permission rules. In addition, CRs can create Private Classes for their own student groups, study circles, or clubs.

🔒 Strict CR Private Class Data Isolation:
Classes marked as Private by a Class Representative remain 100% on the CR's local device and their private Google Drive backup. Private classes never write to Firebase Cloud Firestore and are completely invisible to teachers or other users.

3. Information We Collect

We collect only the minimum information necessary to provide attendance tracking and cloud synchronization services:

  • Account Credentials: Full name, university email address, user-selected password (hashed via Firebase Authentication), and university / department name.
  • Academic Records: Course titles, class sections, student full roll numbers, student names (optional), and daily attendance statuses (Present, Absent, Late, Excused).
  • CR Connection Data: Unique 6-character CR Codes used to safely link a student CR to a teacher's course without exposing personal contact details.
  • Device Diagnostics & Tokens: Anonymous FCM (Firebase Cloud Messaging) device tokens used solely for delivering push notifications (such as teacher announcements, attendance correction requests, and assignment alerts).

4. Google Drive API & Backup Disclosures

📁 Google Drive File Scope (drive.file)

AttendQuick integrates with the Google Drive API using the restricted https://www.googleapis.com/auth/drive.file OAuth scope.

Strict Scope Limitations:

  • AttendQuick ONLY reads and writes backup database files (attendquick_backup_*.db) that were directly created by AttendQuick inside your own Google Drive.
  • AttendQuick has ZERO access to your personal documents, photos, spreadsheets, emails, or any other files stored in your Google Drive.
  • All backup archives are locally encrypted before being uploaded to your Drive.

5. Third-Party Service Providers

We work with trusted industry standard cloud providers to operate the application:

  • Google Firebase (Auth, Firestore, Cloud Messaging, Storage): Provides secure user authentication, encrypted database storage, and push notification delivery under Google Cloud Enterprise security standards.
  • Google Play Services: Manages seamless Google Sign-In and secure OAuth authorization.
  • Google AdMob: May display non-intrusive advertisements in designated areas. AdMob collects standard Advertising IDs (AD_ID) in compliance with Google Play Developer Policy. Users can reset their Advertising ID in Android OS settings at any time.

6. Data Security Architecture

We enforce enterprise-grade security mechanisms across every layer of AttendQuick:

  • Local Database Encryption: The local SQLite/Room database is encrypted using SQLCipher with 16 KB page alignment, protecting records even if physical device storage is accessed.
  • In-Transit Encryption: All network communication between the app, Firebase, and Google Drive uses TLS 1.3 / HTTPS encryption.
  • Firestore Security Rules: Every database read and write is validated by strict server-side Firestore security rules requiring active authentication and workspace ownership checks.

7. Data Retention & Permanent Account Deletion

You retain 100% ownership of your data at all times. You have the permanent right to delete your account and all associated records:

  • In-App Immediate Deletion: Go to Settings → Delete Account. Confirming with the keyword DELETE permanently erases your Firebase Authentication credentials, all Firestore classes and attendance records, all local Room databases, and all Google Drive backups.
  • Web-Based Deletion Request: If you have uninstalled the app or do not have access to your device, you can submit a deletion request via our public portal at attendquick.web.app/delete_account or by emailing attendquickapp@gmail.com. Requests are processed within 48 hours.

8. Educational Privacy (FERPA & GDPR Compliance)

AttendQuick is structured to respect student privacy laws including the Family Educational Rights and Privacy Act (FERPA) and the General Data Protection Regulation (GDPR):

  • We do not collect sensitive student demographic, financial, or behavioral information.
  • Student records are visible only to the authorized professor and designated class representative assigned by that professor.
  • No student data is ever used for advertising profiling or shared with data brokers.

9. Contact & Support

If you have any questions, concerns, or requests regarding this University Privacy Policy, please contact our lead developer and data controller:

Developer: Arshad Ali Kalhoro
Application: AttendQuick (University Edition)
Email: attendquickapp@gmail.com
Web Hub: https://attendquick.web.app