Privacy Policy

1. Who We Are

DevDocs – Offline Developer Docs (com.devdocs.app) is an Android application that allows developers to download and browse API documentation sets completely offline. An optional paid subscription, DevDocs Pro, adds extra features including AI features that work online. The app is developed and maintained by an independent developer.

This Privacy Policy explains what data is collected when you use DevDocs, how it is used, and your rights. If you have any questions, contact us at abdulhady.aariyan@gmail.com.

2. What Data We Collect

DevDocs collects the minimum data necessary to keep the app stable, understand which features are used, and — only if you use DevDocs Pro AI features — answer your requests. We do not collect your name, email, reading history, bookmarks, or what you read.

3. When DevDocs Uses the Internet

DevDocs connects to the internet only in these situations:

• Downloading and updating documentation sets — when you install a docset (or when Pro's automatic updates run), the app fetches the documentation and its catalogue from kapeli.com and Kapeli's public feed on GitHub over HTTPS. Once downloaded, a docset is available offline.
• Sending analytics and crash reports — Firebase Analytics and Crashlytics transmit the events described in Section 2 in the background.
• Purchases — Google Play handles tips and the DevDocs Pro subscription (see Section 5).
• DevDocs Pro AI features — only when you use one of them (see Section 4).

Every free feature — reading documentation, searching, bookmarking, navigation, settings — works with zero network connectivity. The app is designed to function indefinitely in airplane mode after docsets have been downloaded.

4. DevDocs Pro and AI Features

DevDocs Pro includes AI features: Ask (questions answered from your downloaded docs), Explain (explain text you select on a page), meaning search, and Learn (flashcards and quizzes made from doc pages). Nothing is sent unless you use one of these features. If you never use them, DevDocs behaves exactly as described in Section 3.

What is sent when you use an AI feature

• Ask: your question, the earlier questions and answers in the same conversation (for follow-ups), and short passages from the documentation you downloaded that match your question.
• Explain: the text you selected, the page title and docset name, and nearby documentation passages.
• Learn: the text of the documentation page(s) you chose.
• Meaning search (if turned on): your search text or question, and the public documentation text of the docsets you prepare for AI (again after a docset update), so it can be converted into a search index (numbers) that is stored on your device.
• Every AI request also carries your Google Play Pro receipt and its signature (so the server can confirm you have Pro) and a random installation ID.

Text that looks like a password, API key or private key is blocked on your device and never sent. Even so, please don't type or select personal or confidential information (names, emails, private code, secrets) in AI features — whatever you send is processed as described here.

Who receives it

• Our server, which runs on Microsoft Azure (Southeast Asia region). It checks your receipt, deducts an AI credit and forwards the request. It does not store your questions, selected text or answers. It keeps only: a monthly credit counter keyed by a one-way hash (SHA-256) of your purchase token — never the token itself — and technical logs with counts, timings and error codes, without any request text.
• OpenAI, which generates the answer as our service provider (processor). We send requests with OpenAI's storage turned off and include only a hashed, pseudonymous identifier (derived from the purchase hash) that OpenAI uses to detect abuse. Under OpenAI's API policies, this data is not used to train OpenAI's models, and OpenAI may keep it for up to 30 days for abuse monitoring before deleting it, unless the law requires longer. OpenAI may process data in the United States. OpenAI: your data →

What stays on your device

Study decks and their review progress, and the meaning-search index, are stored only on your device. Ask conversations and Explain answers are not saved after you leave the screen. If you report an AI answer, the report (an answer ID and the reason you picked — no text) is kept on your device.

5. In-App Purchases (Tips & DevDocs Pro)

DevDocs offers optional one-time tips and an optional DevDocs Pro subscription through Google Play Billing. Every free feature stays free; nothing that was free requires payment.

All payment processing is handled by Google Play. DevDocs never receives or stores your card details, billing address, or other payment information. What we receive from Google Play is a signed purchase receipt (order ID, product, purchase time and purchase token). For tips, it is used on your device only, to confirm the purchase. For DevDocs Pro, it is kept on your device and sent to our server with each AI request so the server can verify the subscription (Section 4). When buying, the app also passes Google Play a hashed form of the random installation ID, which helps Google Play detect fraud.

For information about how Google handles payment data, refer to the Google Payments Privacy Notice. You can manage or cancel your subscription in the Google Play Store app.

6. Third-Party Services

7. Data Storage & Retention

All data you create within DevDocs — bookmarks, search history, study decks, settings, and downloaded documentation files — is stored on your device using Android's local storage. It is not uploaded to our servers. (If Android backup is turned on for your Google account, Android may include app settings in your own device backup.)

• AI request text (questions, selected text, passages): not stored by our server; held only while your request is processed. OpenAI may keep it for up to 30 days for abuse monitoring.
• AI credit counters: one record per subscription per month, containing only numbers (credits used) and keyed by a one-way hash of your purchase token. Kept so monthly limits work; we delete records on request (see Section 9).
• Server technical logs (no request text, no tokens, no IP addresses): kept for 30 days, then deleted automatically.
• Analytics events: retained by Google for up to 14 months, then automatically deleted, in line with Firebase's retention settings.

Uninstalling DevDocs from your device removes all locally stored data (docsets, bookmarks, search history, study decks, settings).

8. Children's Privacy

DevDocs is a developer tool intended for users aged 13 and above. We do not knowingly collect any data from children under 13. If you believe a child under 13 has used the app, please contact us at abdulhady.aariyan@gmail.com and we will take appropriate action.

9. Your Rights & Deleting Your Data

DevDocs requires no account, so there is no user profile to access or correct on our end. You can still control and delete your data:

• Local data — delete bookmarks, search history, study decks and docsets directly in the app. Uninstalling the app removes all local data.
• AI features — simply don't use them and nothing is sent. Ask conversations are not saved.
• Server data deletion — email abdulhady.aariyan@gmail.com with the subject "DevDocs data deletion" and your Google Play order ID (it starts with "GPA."). We will use it to find and delete the AI credit records linked to your subscription. Because we store only hashes and no request text, there is nothing else on our server to delete. Data held by OpenAI for abuse monitoring is deleted automatically within 30 days.
• Analytics — analytics and crash data are tied only to random installation IDs, not to you. Uninstalling the app (or clearing its data) starts a new ID. Contact us with any questions about this data.
• Questions or requests — contact abdulhady.aariyan@gmail.com and we will respond within 30 days.

10. Security

All network connections made by DevDocs use HTTPS (TLS). Documentation files are stored in the app's private files directory, which is not accessible to other apps on the device. Our server stores purchase tokens only as one-way hashes, keeps its secrets in Azure Key Vault, and does not log request text. We do not transmit data over unencrypted channels.

11. Changes to This Policy

If this Privacy Policy changes in a way that affects how your data is handled, we will update the "Last updated" date at the top of this page and, where appropriate, notify you via an in-app notice on the next app launch.

Continued use of DevDocs after a policy update constitutes acceptance of the updated terms. We encourage you to review this page periodically.

12. Contact