# Privacy Policy — LMS Learner App (Android) **Last updated:** 13 May 2026 **App name (store listing):** dataknowledge **Package name:** `com.dataknowledge.org.lms` --- This Privacy Policy describes how **Dataknowlage** (“we”, “us”, “our”) collects, uses, stores, and shares information when you use our **Android learner application** (the “App”) connected to our learning management service (the “Service”). By using the App, you agree to this Privacy Policy. If you do not agree, do not use the App. **This document is provided for convenience and to support Google Play disclosures. It is not a substitute for legal advice.** Replace all bracketed placeholders before publishing. --- ## 1. Who this policy applies to This policy applies to **end users (learners)** who install and use the App. Administrators may use a separate application; their processing may be described in a separate policy if applicable. --- ## 2. Information we collect We collect and process data needed to operate accounts, deliver courses, process payments where applicable, secure access, and communicate with you. ### 2.1 Account and profile information - **Email address** (for sign-in, verification, and communication where enabled). - **Password** (stored and processed by our authentication provider; we do not store your raw password in plain text in our own databases). - **Display name** and related profile fields as configured in the Service. - **Phone number** when provided or required for account or payment flows. - **Email verification status** and related timestamps as stored in the Service. ### 2.2 Learning activity and content - **Course enrollments**, progress, completion, and related metadata. - **Exam or assessment results** and scores where the Service records them. - **Reviews, ratings, feedback, and application or registration forms** you submit through the App. - **Certificates or certificate-related metadata** issued through the Service. - **Files or media** you upload or that the App accesses as part of learning (for example course PDFs, previews, or assets served by the Service). ### 2.3 Device access, security, and fraud prevention To help prevent account sharing and manage institutional device policies, the App may associate your account with a **device identifier or device label** derived on the device (for example a persisted app-specific device id combined with platform information). This may be used to: - determine whether sign-in or sign-out requires **administrator approval**; - enforce **logout limits** or similar policy rules configured in the Service. ### 2.4 Payments When you pay for paid content, payment details are handled by our **payment processor** (see Section 5). We may receive and store **transaction identifiers**, **amounts**, **course identifiers**, **timestamps**, and **payment status** as required to confirm enrollment and for records. ### 2.5 Notifications - **Firebase Cloud Messaging (FCM)** tokens or equivalent identifiers used to deliver push notifications. - **Notification preferences** and read/delivery state as implemented in the Service. - On Android 13 and above, the App may request **POST_NOTIFICATIONS** permission to show notifications. ### 2.6 Technical and diagnostic data - **IP address**, **device model**, **OS version**, **app version**, and similar technical data may be collected automatically by our infrastructure providers (for example Google Firebase) as part of normal service operation, security, and reliability. - We do not intend the App to sell your personal information. If we use additional analytics in the future, we will update this policy and Play listings accordingly. ### 2.7 Media and storage (optional features) If you use features that **save images** (for example saving a certificate preview to your gallery), the App may request access consistent with Android rules for that action. We process such data only to complete the action you initiate. ### 2.8 Web content and third-party embeds The App may display **embedded web content** (for example video players or links opened in an in-app browser). Those providers may collect data under their own policies when you interact with their content. --- ## 3. How we use information We use the information above to: - create and authenticate your account; - provide courses, materials, exams, certificates, and support; - process payments and confirm entitlements; - send service-related notifications (and, where permitted, educational or promotional notices consistent with your settings and law); - enforce access rules (including device approval workflows); - maintain security, prevent abuse, and comply with law; - improve reliability and troubleshoot issues. --- ## 4. Legal bases (if you have users in the EEA, UK, or similar jurisdictions) Depending on jurisdiction, we rely on one or more of: **performance of a contract**, **legitimate interests** (security, fraud prevention, product improvement where balanced), **consent** (where required, for example marketing notifications or certain permissions), and **legal obligation**. --- ## 5. Third-party services and processors The App relies on service providers. They process data on our behalf or as independent controllers per their terms. | Provider | Purpose | Policy reference | |----------|---------|-------------------| | **Google Firebase / Google Cloud** | Authentication, database (Firestore), cloud messaging, file storage, and related infrastructure | [Google Privacy Policy](https://policies.google.com/privacy), [Firebase](https://firebase.google.com/support/privacy) | | **Razorpay** | Payment processing for paid courses | [Razorpay Privacy Policy](https://razorpay.com/privacy/) | | **YouTube / Google** (if embedded) | Video playback in-app | [YouTube Terms](https://www.youtube.com/t/terms), [Google Privacy Policy](https://policies.google.com/privacy) | Links are provided for convenience; providers may update their documents. --- ## 6. Data retention We retain information for as long as your account is active and as needed to provide the Service, comply with law, resolve disputes, and enforce agreements. Retention of specific records (for example payments or certificates) may follow **legal, tax, or accounting** requirements. When data is no longer needed, we delete or anonymize it in line with our internal practices and provider capabilities. --- ## 7. Security We use industry-standard measures appropriate to the risk, including **encryption in transit** (HTTPS/TLS) for network communications and access controls on backend systems. No method of transmission or storage is 100% secure; we cannot guarantee absolute security. --- ## 8. Children The Service is not directed to children under **13** (or the minimum age required in your region). We do not knowingly collect personal information from children. If you believe we have collected such information, contact us at **[YOUR_PRIVACY_EMAIL]** and we will take appropriate steps. --- ## 9. Your rights and choices Depending on your location, you may have rights to **access**, **correct**, **delete**, **export**, **restrict**, or **object** to certain processing, and to **withdraw consent** where processing is consent-based. You may also have the right to **lodge a complaint** with a supervisory authority. To exercise rights, contact **[YOUR_PRIVACY_EMAIL]**. We may need to verify your identity before fulfilling requests. You can stop collection of certain data by discontinuing use of the App or by adjusting **device permissions** (for example notifications), though some features may not work without them. --- ## 10. International transfers Your information may be processed in **India** and other countries where we or our providers operate. Where required, we use appropriate safeguards (such as contractual clauses) for cross-border transfers. --- ## 11. Changes to this policy We may update this Privacy Policy from time to time. We will post the updated version at **[YOUR_PRIVACY_POLICY_URL]** and update the “Last updated” date. Continued use of the App after changes constitutes acceptance unless applicable law requires additional steps. --- ## 12. Contact **Rushikesh Deshpande** Email: **rushikeshgdeshpande@gmail.com** Address (optional): **Pune, Maharashtra** --- ## Google Play — suggested Data safety alignment (checklist) Use this checklist when completing **App content → Privacy policy** and **Data safety** in Play Console. Map each item to your actual console answers. | Data type / practice | Typical disclosure | |----------------------|--------------------| | Email, name, phone | **Personal info** — account management, app functionality | | User IDs | **Personal info** — authentication | | Payment info | **Financial info** — processed by Razorpay; you may declare only order metadata if that matches your implementation | | Purchase history | **Financial info** or **App activity** — enrollments / payments | | Device or other IDs | **Device or other IDs** — fraud prevention, app functionality (device binding) | | App interactions, course progress | **App activity** — app functionality | | Crash or performance data | **Diagnostics** — only if you enable such collection | | Cloud message token | **Device or other IDs** or **App activity** — messaging | | Photos / media (save to gallery) | **Photos and videos** — optional user-initiated save | Declare **data shared** with **Google (Firebase)** and **Razorpay** as required. Declare whether data is **encrypted in transit** (typically yes). Declare whether users can **request deletion** if you offer that process. ---