Table of Contents
RTI Wiki Mobile App Privacy Policy
Quick Reply: Privacy Policy for the RTI Wiki Android app, covering local data, accounts, courses, community, optional AI and voice transcription, notifications, security and deletion.
In one line. You can use RTI Wiki's core reading, search, study and local tools without an account. Account, sync, course, community, notification, AI and AwaazRTI features use the specific data described below only when you choose those features. The app has no AdMob advertising SDK and no app analytics SDK, and we do not sell personal data.
Effective and last updated: 18 July 2026. This notice applies to the RTI Wiki Android app, package in.righttoinformation.wiki, including release 1.0.2 (build 10). The website has a separate Website Privacy Policy. The app and website use the same optional RTI Wiki account.
1. Who is responsible
The app is published by BigHelpers Software & Solutions Pvt. Ltd. (“BigHelpers”, “RTI Wiki”, “we”, “us”). We decide how data handled by the app and our RTI Wiki services is used.
For a privacy question, correction or grievance, email [email protected]. To request account and associated-data deletion without signing in, use righttoinformation.wiki/delete-account.
2. Data handled by each feature
| Feature | Data involved | What happens and why |
|---|---|---|
| Core reading, search and public content | Requested page or public-content path; standard request information such as IP address, time, user agent and security/rate-limit identifiers | Public material is delivered from righttoinformation.wiki over HTTPS. Technical request data is used for delivery, abuse prevention, rate limiting and security. Search and recently opened history stay on the device unless another feature expressly sends the text. |
| On-device study and organisation | Role and focus choices, bookmarks, collections, learning progress, recent history, offline state, Case Desk records, evidence-readiness ticks and locally generated drafts | Stored in the app's private storage so these features work locally. The Android release disables app backup and expressly excludes app data from cloud backup and device-to-device transfer. |
| Optional account | Username, email address, display name, password during registration/sign-in, authentication cookie and a cached account marker | Sent over HTTPS to the RTI Wiki account server. The server stores the password as a hash; the app does not save the password text in Capacitor Preferences. The account marker supports offline account status and the cookie keeps the session signed in. |
| Optional account synchronisation | Bookmarked page paths and titles; saved drafts; Case Desk titles, status, notes, timelines, transcripts and generated results | When signed in, supported items are synchronised to the RTI Wiki server so they can be recovered and used with the account. Some Case Desk saves use background, best-effort synchronisation after the item is stored on the device. |
| Optional courses | Enrolment, quiz attempts and answers, scores, progress, certificate serial, issue date and account identity | Stored with the account to run courses, show progress and issue a certificate where offered. |
| Optional community | Post and reply text, topics, votes, follows, notification choice, username and anonymous-post choice | Stored on the RTI Wiki server to operate and moderate the community. Non-anonymous content displays the community name. Choosing “anonymous” hides the displayed name, but the service may retain account linkage for moderation, safety and deletion handling. Public posts and replies are visible to other users. |
| AI Mentor | Selected role and the title of the public article | Sent to the RTI Wiki AI proxy and Anthropic to return a short contextual tip. It does not need your account email or the article's full private notes. |
| Optional AI tools | Text, question, draft, reply or other content you submit, plus the generated result | Sent to the RTI Wiki server over HTTPS and processed using Groq or a publisher-hosted local model, depending on availability. Forum AI may also use the selected public thread. Some generated drafts and their inputs are saved in Case Desk and may synchronise when you are signed in. |
| Optional AwaazRTI | Microphone recording, selected language, transcript and generated draft | The app asks for microphone permission only after you accept the on-screen disclosure and tap Start. It records only while the recording indicator is visible, stopping when you tap Stop or after two minutes. The audio is uploaded over HTTPS to RTI Wiki and forwarded to Groq for transcription. RTI Wiki does not write the raw recording to permanent application storage. The transcript is then used for AI drafting and is saved with the result in Case Desk; signed-in Case Desk data may synchronise to your account. |
| Optional notifications | Firebase Cloud Messaging token, platform and standard technical request information | After you opt in, Google Firebase Cloud Messaging supplies a token and the app sends a registration request to RTI Wiki so requested notifications can be delivered. The on/off preference itself stays on the device. You can disable notifications in Profile and Android Settings. |
| Book purchase or support | The app itself does not receive card, UPI or bank credentials | Tapping these options opens the secure RTI Wiki website in a browser/custom tab. Any order or payment data is provided directly on the website and to its payment provider under the website notice and the provider's terms. |
3. Microphone and sensitive information
The app requests Android's microphone permission only for AwaazRTI. It does not use the microphone in the background. A visible recording control lets you stop capture, and the screen explains the transfer before Android's system permission prompt appears.
RTI descriptions and replies can contain Aadhaar numbers, financial details, health information, caste or religion, allegations, addresses or other sensitive facts. Remove information that is not needed before using AwaazRTI, an AI tool, community posting or account synchronisation. Do not speak or paste passwords, OTPs, full payment details or complete identity numbers.
4. What the app does not collect
The Android app binary:
- contains no Google AdMob advertising SDK, shows no in-app advertising and does not access the Android Advertising ID;
- contains no app analytics SDK and does not create advertising or cross-app tracking profiles;
- does not request precise GPS location, contacts, photos, videos, SMS, call logs, calendar or biometric data;
- does not receive card, UPI PIN or bank-login credentials used on the separate payment website; and
- does not sell or rent personal data.
The public website may have different analytics, advertising or payment integrations. Opening the general website or another external site in a browser/custom tab is governed by that site's notice. Public wiki article bodies fetched by the app are not an AdMob or app-analytics integration.
5. Service providers and recipients
We disclose only what is needed for the selected function to:
- our hosting and infrastructure providers, which operate
righttoinformation.wikion our behalf; - Groq, which processes optional AI text and AwaazRTI audio/transcripts for transcription or generation on our behalf;
- Anthropic, which processes the selected role and public article title for the optional AI Mentor tip;
- Google Firebase Cloud Messaging, which supplies and operates notification delivery when notifications are enabled;
- website payment and order providers when you deliberately continue to the separate purchase/support website; and
- authorities or advisers where disclosure is reasonably necessary to comply with law, protect users, investigate abuse or establish legal claims.
Community material is deliberately disclosed to other users when you publish it. Use the anonymous option where offered, but do not treat it as a way to send secret or legally privileged information.
We use processors to provide these functions; we do not permit app data to be used by us for advertising. Provider handling is also governed by the applicable provider terms and privacy commitments.
6. Storage, backup and retention
- Device-only data: remains until you remove the item, clear the app's storage or uninstall the app. The Android manifest sets
allowBackup=false, and both cloud-backup and device-transfer rules exclude all app storage domains. This is separate from account synchronisation. - Raw AwaazRTI audio: RTI Wiki uses the web server's request-temporary upload and does not copy it into permanent application storage. It is forwarded to Groq to answer that transcription request. The returned transcript may be saved as described above.
- Accounts, courses and synchronised Case Desk data: retained while needed to operate the account and until deletion, correction or removal is requested, subject to security, fraud-prevention, legal and backup requirements.
- Community content: retained to operate the discussion until you delete it, moderation removes it or an account-deletion choice requires deletion or anonymisation. Moderation and deletion audit entries may be retained where needed for safety and compliance.
- Notification tokens: used while the subscription remains active or until the token expires, is replaced or is removed through unsubscribe/deletion handling.
- Technical logs and rate-limit records: retained for the operational period needed for delivery, troubleshooting, fraud prevention and security. AwaazRTI's application-level rate limiter stores a truncated one-way IP hash with recent request times, not the raw recording.
Deletion from an active service does not necessarily erase a disaster-recovery copy immediately. Such copies are isolated from normal use and expire through the applicable backup cycle.
7. Security
App-to-server transfers use HTTPS. Account passwords are handled by the RTI Wiki account service and stored server-side as password hashes. Access to production data is restricted to operational personnel and providers who need it for their function. No system can guarantee absolute security, so avoid submitting data that a feature does not need.
8. Your choices and rights
You can:
- use the core app without registering;
- deny or revoke microphone and notification permissions in Android Settings;
- stop an AwaazRTI recording before upload;
- clear local app data through Android Settings or uninstall the app;
- remove supported saved items, bookmarks and community content in the relevant feature;
- ask us to provide, correct or erase personal data and withdraw consent for optional processing; and
- raise a grievance at [email protected].
For account and associated-data deletion, use the public deletion form or email us. The form is available without login. We may verify account ownership before acting to protect users from fraudulent deletion requests.
Applicable rights and remedies depend on the law in force and the circumstances. This policy does not claim a right or deadline that the law does not provide.
9. Children
The account, community and AI submission features are not designed for a child to provide personal data without appropriate parent or guardian involvement. If you believe a child submitted personal data, contact [email protected] so we can review and delete it where appropriate.
10. Changes
We will update this page and its date when the app's data handling materially changes. Where a new use requires a fresh choice, the app will present that choice before the feature processes the data.
- Publisher: BigHelpers Software & Solutions Pvt. Ltd.
- Privacy and grievance email: [email protected]
- Deletion request: righttoinformation.wiki/delete-account
- Package:
in.righttoinformation.wiki - Last reviewed: 18 July 2026