Privacy Policy

🔒 Privacy Policy for Vidya Learning ERP Application

Last Updated: October 22, 2026

Vidya Learning ERP ("we", "our", or "us") operates the Vidya Learning ERP mobile application (the "App") and associated educational enterprise services. We are fully committed to protecting the privacy of our students, teachers, parents, and institutional administrators.

This Privacy Policy describes how we access, collect, use, store, handle, and share user and device data when you interact with our platform. It also outlines your rights regarding strict data control, user consent, and permanent account deletion.

📂 1. Types of Data We Access and Collect

We only collect and process personal and sensitive user data that is strictly necessary to perform the core functionalities of our educational ERP platform.

A. Personally Identifiable & Authentication Information

• Account Records: Full name, email address, password hashes, mobile number, role designation (Student, Teacher, Admin, Parent), and unique custom alphanumeric System IDs.

• Third-Party Identity Sync (Google OAuth): When you choose to utilize the "Login using Google" feature, we securely extract your verified Google profile information (first name, last name, and email address) to pre-fill, synchronize, or authenticate your localized account profile session.

• Institutional Mapping Profiles: Alphanumeric school codes (institute_code) utilized during independent signup tracks to map user records directly to their authorized school database partition.

B. Educational Activity & Submission Records

• Student Submissions: Academic worksheets, quiz answers, duel logs, leaderboard scoring metrics, and live arena battle responses.

• Media Captures (Subjective Homework Evaluations): Image attachments (photos of worked notebook drawings/handwriting) and video recordings (oral proofs or mechanical deflection demonstrations) submitted by students for teacher assessment.

• Audio Recordings (Read Along Engine): Live voice input parsed via microphone hardware to calculate oral pronunciation accuracy scores against target curriculum phrases.

C. Device Data & App Analytics

• App Set ID: A resetable device token utilized exclusively for non-advertising, policy-compliant use cases, such as platform usage analytics, fraud prevention, and session tracking.

• System Metrics: Device model, operating system runtime version, local timezone configurations, and crash/ANR tracking data routed via the Firebase Crashlytics plugin wrapper.

⚙️ 2. How We Use Your Data

We restrict the processing, handling, and analysis of your data to policy-conforming educational and functional administrative capabilities reasonably expected by the end user:

• Core Functionality: Operating classroom pipelines, managing student/teacher mappings, delivering automated exams, and maintaining sibling-ordered quest curriculum tree workflows.

• Speech Evaluation: Processing oral audio inputs via the dynamic Read Along engine to automatically score speech attempts using the formula: Earned Marks = Math.round((correct_words / total_words) * max_marks).

• Visual Grading: Delivering file uploads and video streams safely to the teacher’s pending grading queue interface.

• Stability Monitoring: Logging anonymous crash and operational trace metrics via Crashlytics to prevent hardware device hangs or memory leaks.

🤝 3. Data Sharing & Third-Party Disclosure Policy

🚫 We Do Not Sell Your Data

We do not sell, rent, or trade your personal or sensitive user data to any third parties for monetary or commercial consideration. All data remains isolated inside our secure enterprise partitions.

🔍 Permitted Disclosures

We share user data only with the types of parties listed below, strictly under secure conditions:

1. Your Primary Educational Institution: All student submissions, grades, profiles, and attendance data are shared directly with the specific school administrators and mapped teachers linked via your institute_id or institute_code.

2. Infrastructure Service Providers: Data is handled securely by our trusted database hosting systems and core processing engines (such as your localized Ollama inference controllers or native speech synthesis modules).

3. Legal Compliance & Security: We may disclose data if required by applicable national privacy laws, or to protect the safety and rights of our users.

🔒 4. Secure Data Handling & Cryptography

All personal and sensitive data handled by the App is protected with industry-standard technical and organizational security measures:

• Data in Transit: All communications between the mobile client layout wrapper and the backend Node.js server are encrypted over secure channels using modern cryptography (HTTPS/TLS protocols).

• No Persistent ID Violations: We strictly prohibit the linking of persistent device hardware identifiers (such as MAC addresses, IMEI numbers, or SIM serial numbers) to any resettable identifiers or personal accounts.

• Token Security: Third-party authorization tokens (like Google Sign-In credentials) are validated strictly via backend Web Client handshake validations to prevent client-side security manipulation.

🔄 5. Data Retention, Control, and Account Deletion

We respect your right to control your digital footprint. We maintain a strict data retention and permanent deletion policy:

• Retention Period: We retain user data only for as long as your profile remains an active, valid student or employee account within your school's structural curriculum map, or as needed for institutional record-keeping compliance.

• Permanent Account Deletion Mandate: If you choose to close your account, you can request permanent deletion at any time. This option is accessible within the App settings and externally through our support portal.

• Complete Erasure: Upon receiving a valid account deletion request, we permanently delete all associated user profiles, media submissions, grades, and linked tokens from our active database rows within 30 days. Account freezing or deactivation is never used as a substitute for true data erasure.

👶 6. Children's Privacy Compliance

Our application is widely utilized within early childhood development blocks (Class 1 to Class 5).

• No Ad Tracking: We do not include any advertising SDKs, tracking pixels, or monetized behavioral profiling tools.

• School Supervision: Accounts for minor students are created under the direct structural oversight of their respective school administrations or legal parent guardians using secure institutional code authorizations.

• Strict SDK Vetting: Every dependency integrated into our build variants (such as Capacitor native plugins or Firebase components) is strictly vetted and compliant with Google Play Families Policies.

📣 7. Prominent Runtime Disclosures (Hardware Permissions)

To provide total visibility, our platform uses explicit Runtime Permission Prompts preceded immediately by an in-app clear disclosure screen before opening hardware channels:

• Camera Access: Utilized exclusively when the user interacts with subjective question formats to take a photo of handwritten notebook work, or capture homework video proofs.

• Microphone Access: Utilized strictly within the Read Along interactive view panel to capture voice transcripts and evaluate pronunciation accuracy in real time. Audio data is translated to text instantly on-device and is never recorded or stored on our servers.

📧 8. Privacy Point of Contact & Enquiries

If you have any questions, compliance concerns, or data erasure requests regarding this Privacy Policy, please contact our designated privacy operations team:

• Data Protection Officer (DPO): Agrawal International Developer Operations

• Primary Contact Email: privacy-support@agrawalinternational.com (or your chosen system email)

• Administrative Escalations: Reach out via your specific build flavor’s integrated "Contact Administrator" WhatsApp link layout.