Privacy Policy for GyanGo
This Privacy Policy describes how Gyango (“we”, “us”, “our”) handles information when you use the GyanGo Android app. You can host this page on your website; align your Google Play Data safety form and any in-app disclosures with the same facts for each release.
1) Overview
GyanGo is an offline-first AI learning assistant. We design the app so that core tutoring and model inference run on your device wherever the product is built to do so.
Some features use the internet (for example Google Play subscriptions, optional anonymous diagnostics when you turn them on, and flows you start explicitly). This policy explains what may be processed on-device, what may go over the network, and what Android permissions the app declares.
2) Information you provide or that the app processes
Depending on how you use GyanGo, we may process:
- Text you type or paste, and text shared into the app from other apps (for example via Android “Share” or “Ask GyanGo” / process-text style entry points where supported), to generate learning responses.
- Voice audio when you choose voice input, for speech-to-text and tutoring.
- Images or previews you explicitly attach using the system photo picker, share into the app as an image, or otherwise select for features such as image explanation or on-device text recognition—only in connection with that user action, not in the background.
- Calendar-related information only when you explicitly use a flow that reads or writes calendar data (for example adding a suggested event). We do not use calendar access for unrelated background profiling.
- Device and app technical data when you opt in to anonymous diagnostics (see section 5)—limited to what the app is designed to send, not your lesson text (see section 5).
3) Android permissions declared in the app manifest
The GyanGo app declares the following permissions (as shipped in our source manifest):
| Permission | Purpose |
|---|---|
android.permission.INTERNET |
Network features you use or enable (for example Play subscription checks, optional diagnostics uploads, and other online flows). |
android.permission.ACCESS_NETWORK_STATE |
Detect connectivity (for example to gate optional diagnostics and other network-aware behavior). |
android.permission.RECORD_AUDIO |
Optional voice input only when you use voice features (for example after tapping a microphone control). You can deny this and use text. |
android.permission.READ_CALENDAR |
Only when you use a feature that legitimately needs to read calendar data you choose to interact with. |
android.permission.WRITE_CALENDAR |
Only when you choose to create or update calendar entries from supported flows (for example saving a suggested date). |
You can grant, deny, or revoke these permissions in Android Settings at any time. If you deny a permission, related features may not work; other features may still be available.
Photos and camera: Our shipping app manifest does not declare android.permission.CAMERA. Image features rely on user-initiated flows such as the system photo picker, sharing an image into GyanGo, or similar. Your device may still offer a camera as part of the system UI; that is controlled by Android and your device vendor, not by GyanGo accessing the camera continuously in the background.
4) How we use this information
We use the information above to:
- provide AI-assisted learning responses and related features you request;
- run speech-to-text when you use voice input;
- run on-device analysis of images or extracted text when you choose those features;
- perform optional calendar actions when you choose them;
- maintain safety, stability, and quality of the app;
- operate subscriptions and optional diagnostics as described below.
5) Optional anonymous diagnostics (Firebase)
GyanGo can use Google Firebase Analytics and Google Firebase Crashlytics for anonymous diagnostics.
-
Default: For new installs, anonymous diagnostics are off until you turn them on in app Settings (“Share anonymous diagnostics” or equivalent). The app stores this choice locally (DataStore key
anonymous_diagnostics_enabled). - What we aim to send: Coarse event names and short, non-content parameters (for example app version, device model, success flags, durations)—not your chat text, prompts, model answers, photos, OCR text, voice recordings, or transcripts. Crash reports may include stack traces and limited device/app metadata for debugging.
- Custom analytics and Wi-Fi: Custom analytics events are sent only when diagnostics are on, the preference has been applied, and the device reports Wi-Fi or Ethernet (custom events are not sent on cellular in this design; they are dropped rather than queued with user content).
- Crashlytics: The app disables Crashlytics collection when diagnostics are off or when the device is not on Wi-Fi/Ethernet, aligned with the same product gating as Analytics. Native crash handling can still vary by Android version or SDK behavior; we do not attach user-generated lesson text as Crashlytics custom keys.
Third-party SDKs (including Google’s) may process data under their policies. Declare Firebase Analytics and Firebase Crashlytics in Google Play’s Data safety section and match declarations to what you actually ship. Merged dependencies may add other disclosures (for example identifiers); review the merged manifest for each release.
6) Subscriptions and Google Play
Paid or trial access may be offered through Google Play Billing. Google processes payments and subscription state; we receive what is needed to unlock features in the app according to your purchase. For how Google handles billing data, see Google’s privacy documentation.
7) Data sharing and selling
We do not sell your personal information.
We may share information with service providers that help us run the app or comply with law—for example Google (Play, Firebase), hosting, or support tools—under appropriate agreements and safeguards. We may also disclose information if required by law or to protect users, children, or our rights.
8) Data retention
- On your device: Conversation or app data remains until you delete it inside the app or clear app data / uninstall in Android settings.
- With service providers: Data is retained as long as needed for the purposes above, legal obligations, or security, and we aim to limit retention where practical.
9) Children and safety
GyanGo is built with children and families in mind. Parents and guardians should supervise younger users, review permissions and Settings (including diagnostics), and use device parental controls as appropriate.
If you believe a child has shared personal information inappropriately, contact us (section 12) and we will review the request.
10) Security
We use reasonable technical and organizational measures to protect information. No method of transmission or storage is completely risk-free; we work to reduce risk and improve safeguards over time.
11) Changes to this Privacy Policy
We may update this policy when the app or legal requirements change. We will adjust the Last updated date at the top when we publish a new version. Material changes may also be reflected in the app or Play Store listing where appropriate.
12) Contact
- Privacy: privacy@gyango.com
- General support: support@gyango.com
This document is intended to describe the product’s engineering and privacy posture accurately. It is not legal advice; have qualified counsel review before relying on it for compliance.