Campus Shield AI — Privacy Policy
Effective date: 17 July 2026 · Last updated: 1 November 2026
This Privacy Policy explains how the Campus Shield AI mobile application and website (together, the "Service") collect, use, share, and protect information. Campus Shield AI is a school administration tool used by educational institutions to manage attendance, staff and student rosters, parent notifications, and optional school-bus tracking.
The Service is operated by CAMPUS SHIELD AI ("we", "us"), the data controller for account and platform data. Each participating school or institution is an independent controller of the student, staff, and parent records it enters ("Institution"). For questions about a specific student or roster record, contact your Institution first.
1. Who this applies to
The Service is used by institution administrators, teachers, parents/guardians, bus drivers, and students. Accounts for students, staff, and drivers are created and managed by the Institution's administrator; individuals do not self-register. Login credentials are issued as one-time temporary passwords that must be changed on first sign-in.
2. Information we collect
We collect only what the Service needs to function. We do not use advertising IDs, third-party advertising networks, or third-party analytics SDKs, and we do not sell personal data.
| Category | Examples | Required / Optional | Purpose |
|---|---|---|---|
| Identity | Name; roll number, staff/driver ID, login ID; Firebase user ID | Required | Account creation, attendance, roster management, authentication |
| Contact | Parent phone number; staff/driver phone; email and recovery email; institution address | Required (some optional, e.g. recovery email) | Login, account recovery, and parent notifications |
| Credentials | Temporary one-time passwords | Required | Provisioning sign-in. Stored in Firebase Authentication (hashed); the plaintext temporary value is transient and removed after the account is created |
| Location (precise) | Bus driver's live GPS while a driver-started sharing session is active; student pick-up/drop-off coordinates at the moment of boarding; admin-entered bus-stop coordinates | Optional (bus feature only; requires the driver to grant location permission) | Live bus tracking and boarding logs. Sharing continues visibly in the background until the driver stops it or the four-hour safety limit expires |
| Photos | Institution logo; user profile avatar; bus photo | Optional (user-initiated upload) | Profile and branding |
| Academic and financial records | Marks, results, schedules, fee amounts, balances, school-recorded payment details and receipts | When the institution uses these features | Academic administration, fee accounting and receipt access; card details are not collected in the school-office payment flow |
| Additional institution-entered information | Student or guardian address, date of birth, identification numbers (including Aadhaar where entered), blood group or other health information, caste and religion | Only where the institution has an applicable lawful basis and required notices/consent | Authorized institutional administration. Institutions must minimize collection and must not enter unnecessary sensitive information |
| Support and content safety | Help messages, content references and reasons in reports, moderation decisions, and private deletion receipts | When used | Respond to requests, remove harmful content, suspend abusive accounts and confirm deletion. Sender-block preferences stay on the device, scoped to account and institution |
| App activity | Attendance records; staff remarks; safety/incident reports; boarding logs; WhatsApp notification preferences | Required for the relevant feature | Core school-management functionality |
| Device & technical | Push notification (FCM) token; crash logs, stack traces, device model/OS and a crash-reporter installation identifier | Required (push) / automatic (crash reports) | Delivering notifications and diagnosing crashes |
3. Location — how it is used
Location (ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION):
is optional. Drivers start live bus sharing by tapping Send location. The active session can continue in the background with a
visible system notification or location indicator. It stops when the driver taps Stop sharing or after four
hours. A separate one-time location may be captured when a driver marks a student picked up/dropped. Live
location is deleted when the session ends; route history and boarding logs are retained by the Institution.
Students and guardians can separately choose My location on a map to show their current position or use it for directions after granting permission. This does not start live bus sharing or share a family member's position with the school. Map and route requests may send relevant coordinates to Google Maps as described below.
4. How we use information
- To authenticate users and secure accounts.
- To provide attendance, roster, remarks, incident reporting, notices, and bus tracking.
- To send notifications to parents/guardians (push and, with consent, WhatsApp).
- To diagnose crashes and improve stability.
- To comply with legal obligations and maintain security and audit records.
5. How information is shared
We share personal data only as described here. We do not sell personal data and do not share it for advertising.
Service providers (processors)
- Google Firebase (Authentication, Cloud Firestore, Cloud Storage, Cloud Functions,
Cloud Messaging, and Crashlytics) hosts and processes Service data on our behalf. See Google's
Firebase privacy
information. Data is processed in the United States (region
us-central1).
Notifications via WhatsApp (Meta)
If a parent/guardian has opted in, we send attendance alerts only (a student marked absent or late) through the WhatsApp Business Platform operated by Meta Platforms, Inc. These messages include the recipient's phone number and message content such as the student's name, class, and attendance status and date. Bus tracking, pick-up/drop-off, and any other events are delivered as in-app push notifications, not over WhatsApp. Messages are only sent to parents who have granted consent and have not opted out. WhatsApp/Meta processes this data under its own privacy policy. Parents can opt out at any time through the Institution.
Maps and route services (Google Maps Platform)
When transport maps, location search, or road routing are used, Google Maps Platform receives the map area, route endpoints, search text, and ordinary network information. Driver and student names are not included in those Google requests. See the Google privacy policy.
Legal
We may disclose information where required by law, to protect safety, or to enforce our terms.
6. Data security
All data in transit is protected with HTTPS/TLS encryption. Authentication is handled by Firebase Authentication; passwords are never stored in plaintext at rest. Sensitive identifiers used in audit records (for example, user IDs and IP addresses) are stored as one-way hashes. Access to Institution data is restricted by server-side security rules based on role and institution membership.
7. Data retention
Account and roster data is retained while the account is active. When an account is deleted (see below), personal identifiers are removed. Certain institutional records that must be preserved — such as attendance — are de-identified (the student reference is replaced with a salted, non-reversible hash) and retained for up to seven (7) years for recordkeeping, legal-claims, and security-audit purposes, or a shorter period where applicable law requires. A minimal deletion-audit record containing only hashed identifiers and counts (no name, code, email or user id) is retained for the same period.
8. Your rights and choices — account deletion
You can request access to, correction of, or deletion of your personal data. Depending on your jurisdiction you may also have rights to restrict or object to processing and to data portability. To exercise these rights, contact us or your Institution.
8.1 Institution administrators
An Institution administrator can permanently delete the Institution account at any time from Settings → Account → Delete Institution Account in the app, after re-entering their password and typing the Institution code to confirm. They can also request deletion without the app — including without reinstalling it — using our account-deletion page: https://campusshieldai.in/account-deletion. This public page is available without signing into the app.
Deleting the Institution account removes the Institution record, every teacher, student, parent and driver account the Institution manages, and all of its data — Firebase sign-ins, profiles, contact details, memberships, device (push) tokens, attendance and other records, and stored files. Only the non-identifying deletion audit described in Section 7 is kept. A person who also belongs to another Institution keeps that other membership and their sign-in. Requests are verified and completed within 30 days.
8.2 Teachers, students, parents and drivers
Open Settings → Account → Delete Account to confirm permanent deletion of your account for the current institution. No administrator approval is required. Processing starts automatically after a 24-hour cancellation window and completes within 30 days. You can withdraw in the app before processing starts. Save the private status link supplied by the app; it provides completion confirmation without signing in and expires 30 days after completion or cancellation.
Deletion removes your access, profile and contact details, linked relationships, notification tokens and personal uploads for that account. Memberships in other institutions remain. Records may be retained only where retention is legally required; a school's general wish to keep records is not a reason to refuse account deletion. The institution must explain any retained records and their legal basis. If you cannot sign in, use the public deletion request page; ownership verification may be needed.
8.3 Content safety and support
Use the content safety menu on a notice or remark to report bullying, threats, inappropriate material or unauthorized disclosure of personal information. You can block an identified sender's notices and remarks on this device and unblock them from the blocked-content row. School administrators review reports and can remove content or suspend abusive accounts. A basic automated text filter catches some threats and abuse; reports and human review cover context and attachments. For escalation, contact campus.shield29@gmail.com.
9. Permissions used (Android)
| Permission | Why it is used |
|---|---|
| Internet | Communicate securely with Firebase and notification services |
| Location (fine & coarse) | Optional bus feature; driver-started active sharing, including visible background sharing |
| Notifications (post notifications) | Deliver bus, attendance, and announcement notifications |
10. International transfers
Data is processed and stored on Google Cloud/Firebase infrastructure in the United States. Where you are located elsewhere, your data is transferred and processed under the safeguards Google provides for its Firebase services.
11. Changes to this policy
We may update this policy from time to time. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, by notice within the Service.
12. Contact us
For privacy questions or to exercise your rights:
- Data controller: CAMPUS SHIELD AI
- Email: campus.shield29@gmail.com
- Postal address: Kethepally, Street, Nalgonda, Telangana 508211, India
- Support: campus.shield29@gmail.com