Welcome to Hall Pass Pro, provided by Mr. C's Academy / 5811Code ("we," "us," or "our").
We are committed to protecting your privacy and the privacy of the student data managed through our application ("App").
This Privacy Policy explains the App's data handling practices.
This App is designed for use by teachers and school staff ("Users") to manage student hall passes digitally.
A core principle of Hall Pass Pro is that the operational data you manage (student names, pass logs, period details) is stored locally on your device and is not transmitted to or maintained by the developer (us).
1. Information Processed by the App (Locally on Your Device)
Hall Pass Pro processes information solely on your device to enable its core functionality.
This information is not sent to the developer's servers. Collection or generation of this local data occurs through:
Information You Provide Directly into the App:
- Period Information: Names of class periods, default weekly pass limits, and pass cooldown times you configure are stored locally within the App's database.
- Student Information: Student names and any optional override weekly limits you enter manually or import via file are stored locally within the App's database.
- Pass Log Details: Reasons or notes you may optionally enter when logging a pass (e.g., emergency reason, denial detail) are stored locally within the App's database.
Information Accessed via Google Classroom Sync (With Your Permission, Stored Locally):
- If you choose to use the Google Classroom sync feature, the App accesses (with your explicit permission via Google Sign-In) your class lists directly from Google.
- Classroom Data: Course names and student rosters (including student names and Google User IDs) associated with the courses you authorize are retrieved from Google and stored locally within the App's database on your device to populate and update the student list.
- This data is not sent to the developer.
Information Generated Through App Usage (Locally):
- Pass Logs: Records of pass usage, including student name, timestamp, pass status (approved, denied, emergency), associated period ID, and week start date for limit tracking, are generated and stored locally within the App's database.
- QR Codes: Student names are used locally to generate QR codes for scanning.
- QR code images may be temporarily stored locally before you choose to share them.
App Settings & Preferences (Locally Stored):
- Settings such as theme preference, week start/end days, global pass cooldown (if used), and pass timer configurations are stored locally using the device's standard preferences mechanism.
Diagnostic Data (Standard Apple Collection - Not Linked to Your Operational Data):
- We, the developers, may receive anonymized crash reports and basic aggregated usage analytics provided through standard App Store Connect services.
- This helps us identify and fix bugs and improve the App.
- This diagnostic data is collected by Apple, is typically not linked to your identity or your specific student/pass data, and is separate from the operational data stored locally by the App.
2. How Information is Used (Locally by the App)
The information processed locally by the App is used exclusively for the following purposes on your device:
- To operate and maintain the App's functions (manage periods, students, pass logs).
- To facilitate hall pass issuance and tracking via QR codes or manual entry.
- To enforce configured pass limits and cooldowns.
- To generate reports on pass usage within the App for your viewing.
- To display and manage roster data synced from Google Classroom.
- To trigger local pass timer expiration notifications if you enable the feature.
- To allow you to initiate actions to export pass logs or student QR codes.
The developer uses aggregated, anonymized diagnostic data from Apple to improve the App's stability and performance.
We, the developers, do not access, use, or sell the operational data (student names, pass logs, period details, etc.) stored locally within the App on your device.
The App does not use any data for tracking purposes as defined by Apple.
3. Google Classroom Integration
Authentication for Google Classroom integration is handled via Google Sign-In directly between your device and Google.
We request permission only for scopes necessary to read course and roster information (classroom.courses.readonly, classroom.rosters.readonly).
Data accessed from Google Classroom is stored locally on your device and is not sent to or accessed by the developer.
Our App's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. Data Storage and Security
All operational data (period information, student rosters, pass logs, settings) is stored exclusively locally on your device within the App's secure storage area using sqflite database and shared_preferences.
The developer (Mr. C's Academy/5811Code) does not have access to the data stored within the App on your device.
Data is not automatically backed up or synced to any external server by Hall Pass Pro (cloud backup may occur only if you explicitly enable device-level backups like iCloud Backup, which is governed by Apple's terms).
You are responsible for securing your device, which in turn helps protect the locally stored data.
5. Data Sharing
We, the developers, do not share the operational data stored locally in your App.
Sharing only occurs under the following circumstances:
- User-Initiated Sharing: When you use features to export data (e.g., sharing CSV logs or QR code Zip files), you control where that data is sent via the device's standard sharing mechanisms. The developer is not involved in this transfer.
- Google: When using the Google Classroom sync feature, authentication tokens and API requests are exchanged directly between your device and Google.
- Apple: Standard, anonymized diagnostic data may be collected and made available to the developer via App Store Connect, separate from your operational data.
- Legal Requirements: If required by law, subpoena, or other legal process directed at the User, the User may need to provide access to the data on their device. The developer typically holds no data to disclose.
6. Permissions
The App requests the following permissions only when needed for specific features operating on your device:
- Camera (NSCameraUsageDescription): Required locally to scan student QR codes. Images are processed on-device and not sent to the developer.
- Photo Library (NSPhotoLibraryUsageDescription): Requested locally to allow you to select roster files (like CSV or TXT images/documents) from your library for import into the App's local database. Photos are not sent to the developer.
7. Data Retention and Deletion
Data is stored locally on your device and remains there until you manually delete it using App features or until the App is deleted.
You can archive students and clear old pass logs within the App.
Deleting the App from your device will remove the locally stored data associated with it. The developer retains no copy.
8. Children's Privacy
Hall Pass Pro is intended for use by educators.
The App processes information about students (including minors) as entered or imported by the educator user for school administrative purposes (hall pass management).
This data resides locally on the User's device.
The App does not collect information directly from children under 13 (or relevant age).
Responsibility for compliance with student data privacy regulations (e.g., COPPA, FERPA) regarding data entered into the App lies with the User (teacher/school).
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in the App's functionality or legal requirements.
We will notify you of significant changes. Your continued use of the App after such changes constitutes your acceptance.
10. Contact Us
If you have any questions about this Privacy Policy or the App's data handling practices (which occur on your device), please contact us at: mrcsacademy@5811code.com