Privacy Policy

DNAC CMS uses a Role-Based Access Control (RBAC) system. Each user is assigned exactly one role. Below is a complete, accurate breakdown of what data each role can read or modify:

• Account credentials: Staff ID / username, email address, hashed password, assigned role, and class/subject assignments.
• Student records: Name, admission number, class, section, attendance history, examination marks, CCE grades, viva results, fee balance, point history, leave history, medical entries, out-pass records, mentoring logs.
• Financial data: Store credit/debit transactions, DISA coupon issuances, PTA fee records, class deposit records — all linked to student IDs.
• Session data: A signed JWT token, device user-agent string, and login timestamp, used to enforce concurrent-session limits.
• AI conversation data: Prompts and AI responses stored per user session to maintain chat history.
• Usage activity: Page visit counts and feature-usage tallies stored server-side for the Staff Engagement leaderboard (attendance marked, out-passes processed, transactions created, mentoring recorded, etc.).

We do not collect payment card numbers, government ID numbers (Aadhaar, PAN), or biometric images on our servers.

The Android app offers optional Fingerprint / Face ID login:

• All biometric matching is performed entirely on the device by Android's secure hardware (TEE / Strongbox). We never receive or store fingerprint images or face geometry.
• When enabled, only an obfuscated session token is stored in device localStorage — not your password.
• The biometric prompt re-appears every time the app is brought to foreground (session lock). This is a security feature, not a bug.
• You can disable biometric login at any time; doing so immediately removes the stored token from your device.

• Session token: Stored in localStorage to persist login across app restarts. Cleared on logout.
• Page data cache (dnac_page_*): API responses for attendance, marks, and dashboard are cached locally for instant display (stale-while-revalidate). TTL: 5 minutes.
• Preferences: Theme (dark/light), lite mode, and sidebar state stored in localStorage.

Cached data never leaves your device to third parties. It is automatically evicted when your device storage is near capacity.

• Authenticate users and enforce role-based access control.
• Display and record student academic, financial, and disciplinary data as entered by authorised staff.
• Generate institutional reports and exports (PDF, print) for authorised roles.
• Calculate the Staff Engagement leaderboard score (based on attendance marked, out-passes processed, transactions created, mentoring sessions, and other activity counts).
• Send push notifications for leave approvals and system alerts (only with granted permission).

We do not use your data for advertising, user profiling, or any purpose unrelated to school management.

• Vercel — hosting and serverless compute. Data processed under Vercel Privacy Policy.
• Groq API — AI assistant responses. Groq does not use prompts to train models. See Groq Privacy Policy.
• Firebase Cloud Messaging — push notification delivery. See Google Firebase Privacy.

No student or staff personal data is sold or shared with advertising networks, data brokers, or analytics services.

• All data in transit is encrypted via TLS 1.2+ (HTTPS only).
• Passwords are hashed server-side and never stored in plain text.
• Session tokens are signed JWTs, validated server-side on every request.
• Concurrent login sessions are limited; each new device login can trigger forced logout of old sessions.
• MAIN role actions require a time-based 6-digit rotation code in addition to credentials.
• Android app enforces biometric re-lock every time the app returns from background.

• Access: View data associated with your account via the dashboard.
• Correction: Request corrections through your institution's admin.
• Deletion: Request account/data deletion by emailing us. Institutional records (attendance, results) may be retained per school policy.
• Portability: Download your data via PDF/print report export.
• Withdraw biometric: Disable biometric login at any time to remove the stored token from your device.

DNAC CMS is operated by school staff, not directly by students. Student data is entered by authorised staff on behalf of the institution. We do not knowingly collect personal data directly from minors. Student records are governed by the policies of the operating institution, which is responsible for obtaining necessary consents from parents/guardians.

We may update this policy periodically. The "Last Updated" date at the top reflects the most recent revision. Significant changes will be communicated through the app or by email. Continued use after changes constitutes acceptance.