Privacy Policy
Privacy Policy for Devly
Last updated: July 22, 2026
Devly ("Devly", "we", "us", or "our") is a mobile application that helps people learn to code in Python, JavaScript, and HTML/CSS. This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices and rights you have. It applies to the Devly Android app and any related services (together, the "Service").
By using Devly, you agree to the collection and use of information as described in this policy. If you do not agree, please do not use the app.
1. Information we collect
Information you provide
- Account information: if you sign in, we (via Firebase Authentication) collect the identifiers your sign-in method provides — for Google Sign-In, this is your name, email address, and profile photo URL; for anonymous sign-in, a random device-scoped identifier only.
- Learning progress: which track you're on, lessons completed, XP, streaks, and certificate/project completions.
- Code you write: the code you type into lessons and the in-app code editor (IDE), so it can be checked or executed and so your progress can be saved.
- Purchase information: if you subscribe to Devly Pro, our payment processor (Google Play Billing, via RevenueCat) handles your payment details directly — we do not receive or store your card number. We receive confirmation of your subscription status only.
Information collected automatically
- Diagnostics and crash reports: via Firebase Crashlytics — device model, OS version, app version, and crash stack traces.
- Usage analytics: screens viewed, lessons started/completed, feature usage, and session length, used to understand what's working and to improve the app.
- Device/app integrity signals: via Firebase App Check and Google Play Integrity, used to confirm requests come from a genuine, unmodified install of the app — this does not identify you personally.
- Push notification tokens: via Firebase Cloud Messaging, if you allow notifications, so we can send streak reminders and re-engagement messages.
2. How we use your information
- To provide, operate, and maintain the Service (saving your progress, syncing across devices, running your code).
- To personalize your learning path and track completion/certificates.
- To communicate with you — streak reminders, product updates, and support responses.
- To monitor and improve the app's stability and performance (crash reporting, analytics).
- To detect, prevent, and address fraud, abuse, or security issues (e.g. abuse of the code execution sandbox).
- To process payments and manage subscriptions, if you purchase Devly Pro.
- To comply with legal obligations.
We do not sell your personal information.
3. Third-party services we use
We use the following service providers ("processors") to operate Devly. Each only receives the data necessary to perform its function, under its own privacy/security terms.
| Provider | Purpose | Data involved |
|---|---|---|
| Google Firebase (Authentication, Firestore, Crashlytics, Cloud Messaging, App Check) | Sign-in, cloud data storage/sync, crash reporting, push notifications, integrity checks | Account identifiers, progress data, device/crash diagnostics, notification tokens |
| Google Play Billing / RevenueCat | Subscription purchases and entitlement management | Purchase/subscription status (not full payment card details) |
| Code execution service (self-hosted, Piston-compatible) | Running the code you write in lessons/IDE and returning output | The code you submit to run, and its output |
| AI provider (e.g. Anthropic) | Powering the "Ask AI" tutor feature, when enabled | Your question and the relevant code/lesson context |
| Product analytics (e.g. Amplitude / PostHog) | Understanding feature usage and retention to improve the app | Usage events (not the content of the code you write) |
Some rows above describe planned/optional features. We keep this table in sync with what the current released version of the app actually does — see §12 for how we handle updates to this policy.
4. Code you write and run
When you tap "Run" in the IDE or complete a code-based lesson, the code you wrote is sent to a code-execution service so it can actually be run and the output shown back to you. This code is processed only to produce that output — it is executed in an isolated, rate-limited environment and is not used to identify you, sold, or used for any purpose other than returning your program's output. Avoid entering personal or sensitive information inside code you run, since it is transmitted to this service to execute.
5. AI tutor features
If and when the in-app AI tutor ("Ask AI") is live, questions you ask and the surrounding lesson/code context are sent to our AI provider to generate a response. We do not use this data to train third-party foundation models beyond what our provider's own terms permit, and we recommend not including personal information in your questions.
6. Data retention
We retain your account and progress data for as long as your account is active. Diagnostic/crash data and analytics events are retained for a limited period (typically up to 12 months) before being deleted or aggregated. Code submitted for execution is processed transiently and is not retained after your run completes.
7. Account and data deletion
You can request deletion of your account and associated data at any time:
- In-app: Profile → Account → Delete Account (once this control is live in your installed version).
- By email: contact us at imdadul.hrm@gmail.com with the subject "Account Deletion Request" from the email address associated with your account.
We will delete your account data, including data held by our third-party processors (§3), within 30 days of a verified request, except where we are required to retain limited records for legal, security, or fraud-prevention purposes.
8. Children's privacy
Devly is not directed at children under the age of 13 (or the minimum age required in your country). We do not knowingly collect personal information from children under this age. If you believe a child has provided us with personal information, please contact us and we will take steps to delete it.
9. Your rights (GDPR / CCPA / others)
Depending on where you live, you may have rights under laws such as the EU/UK General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA/CPRA), including the right to:
- Access the personal data we hold about you.
- Correct inaccurate data.
- Request deletion of your data (see §7).
- Export your data in a portable format.
- Object to or restrict certain processing.
- Withdraw consent at any time, where processing is based on consent.
To exercise any of these rights, contact us at imdadul.hrm@gmail.com. We will respond within the timeframe required by applicable law.
10. Security
We use industry-standard measures to protect your information, including encryption in transit (HTTPS/TLS), access controls on our backend (Firestore security rules), and isolated, rate-limited execution for user-submitted code. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.
11. International data transfers
Our service providers (§3) may process and store data outside your country of residence, including in the United States. Where required, we rely on appropriate safeguards (such as Standard Contractual Clauses) for these transfers.
12. Changes to this policy
We may update this Privacy Policy from time to time, for example as new features (like the AI tutor or subscriptions) become active. We will update the "Last updated" date above and, for material changes, notify you via the app or another reasonable method.
13. Contact us
If you have questions about this Privacy Policy or how we handle your data, contact us at:
📧 imdadul.hrm@gmail.com
App: Devly
Developer: [Your developer/company name as registered in Play Console]
This document is a template drafted for the Devly app and is not legal advice. Review it (and fill in the highlighted placeholders) with a qualified professional before publishing, especially the sections on children's privacy, GDPR/CCPA, and the developer name, to make sure it matches your actual business details and current app behavior.
Comments
Post a Comment