Introduction
Welcome to AttendQuick. We respect your privacy and are committed to protecting the personal data of our users, specifically those using the School Portion of our application. This Privacy Policy explains how we collect, use, store, and safeguard your information when you log in or register using Sign in with Google, and when you use our attendance and school management services.
Effective Date: July 26, 2026
Developer / Entity: Attend Quick Development Team
Contact Email: attendquickapp@gmail.com
Governing Laws: Islamic Republic of Pakistan
1. Information We Collect
When you use the School Portion of AttendQuick, we collect and process different categories of information depending on your user role (Principal, Teacher, Admin, or Owner).
Google User Data (Retrieved via Google Sign-In)
When authenticating with Google, we retrieve basic profile details via OAuth 2.0 protocols to facilitate onboarding:
Email Address
Primary login verification, record sync and lookup.
Full Name
To personalize your workspace & school directory.
Profile Photo
Displayed within settings and headers inside the app.
Google ID
Secure token validator for Firebase Authentication.
School-Related Data (Created by Users)
- School & Role Identity: School names, registration details, school contact info, and role mappings (Owner, Principal, Teacher, Admin).
- Class & Student Directory: Classes, rosters, subjects, grades, and student listings. Note: Student information is entered manually by school staff. Students do not sign in using Google OAuth.
- Attendance Sheets: Attendance status logs (Present, Absent, Late, Sick/Approved Leave, Activity) including timestamps and log editors.
- Correction History: Logs of edits requested by teachers and approved/denied by school principals.
Technical & Hardware Data
- FCM Push Tokens: Device identifier tokens stored on Firebase Cloud Messaging to send real-time reports, announcements, or request notifications.
- Offline Cache: Temporary SQLite database logs saved locally to support offline access, which automatically sync with cloud databases upon restoration of internet connection.
2. How We Use Your Information
We process your data only for legitimate core service functionalities, including:
- Authentication: Granting secure access, verifying identity, and mapping roles correctly.
- Service Operation: Managing class records, saving attendance logs, providing correction workflows, and generating visual reports.
- Real-time Notifications: Alerting teachers and principals about status shifts, approvals, or emergency announcements.
- Account Synchronization: Matching cloud databases with offline edits to avoid duplicate or lost attendance records.
- Diagnostics: Resolving app stability errors, crash logs, and security vulnerabilities.
3. How We Share and Disclose Data
We do not sell, rent, trade, or share your Google user data or school logs with third-party advertising services.
Data sharing is strictly limited to the following essential partners:
| Partner / Platform | Purpose | Data Shared |
|---|---|---|
| Firebase / Google Cloud | Database hosting, Authentication system, Cloud messaging (push notifications). | User profiles, School logs, FCM Tokens, Auth sessions. |
| Render | Backend cloud server processing account transactions (e.g. secure deletions). | Request payloads, auth headers, account IDs. |
We may also share data if required under the statutory laws of the Islamic Republic of Pakistan, or to protect the safety and security of our users.
4. Data Security and Retention
Data Security
We utilize robust measures to keep your data safe:
- HTTPS/TLS: All client-to-server data transmission is encrypted via secure network sockets.
- Firestore Rules: Server-side verification rules ensure users only access records belonging to their designated `schoolId`.
- Identity Verification: Google ID tokens are verified cryptographically before granting access to our backend API endpoints.
Data Retention
We retain school attendance logs and profile data for as long as the school workspace is active or until a user explicitly requests account deletion.
5. User Rights: Account & Data Deletion
We believe in absolute data ownership. You can request the deletion of your account and all associated data directly from the settings panel in the app, which communicates with our secure `/delete-account` endpoint:
- Teachers: Deletion removes personal login credentials, profile pictures, and workspace mappings immediately.
- Principals (Cascade Deletion): Since a school's configuration belongs under the Principal's workspace, requesting deletion triggers a **cascade deletion** that permanently deletes all student data, class structures, registered teacher logs, historical attendance reports, and sync files from the database.
Warning: Deletion is irreversible. The Attend Quick Development Team cannot recover or restore data once deletion is completed.
If you encounter issues during deletion, you can request manual removal by emailing us at attendquickapp@gmail.com. We will process your deletion request within 14 business days.
6. Compliance with Google API Policies
Our integration with Google OAuth adheres strictly to the Google API Services User Data Policy, including the Limited Use requirements:
- We do not use Google profile data to build advertising dossiers or target promotional messages.
- We do not transfer Google account information to external data brokers or affiliate systems.
- No human operators read your raw Google authentication token, except for specific troubleshooting requests initiated by the user.
7. Contact Information
If you have any questions or feedback regarding this Privacy Policy, please contact our support team:
Attend Quick Development Team
Email: attendquickapp@gmail.com
Jurisdiction: Islamic Republic of Pakistan