1. About this policy
IOE Notices (Android package com.be.ioenotices) is developed and maintained by Rohit Yadav (developer account rohityadav_sas). The app uses MeroEngineering infrastructure to provide academic notices, search, attachments, and feedback services. In this policy, “we” and “us” mean the app's developer and operator.
This policy covers the Android app. The separate MeroEngineering website privacy policy covers website accounts and services. IOE Notices does not require an account or Google sign-in and does not offer payments or display advertising.
2. Information processed by the app and our services
- Notice requests: loading or searching notices can send the selected category, page number, and search terms to our API. Viewing or downloading an attachment sends a request identifying that file to its hosting service. These requests also expose ordinary connection information, such as your IP address, request time, URL, and technical headers, to the receiving service and its infrastructure providers.
- Notifications: we use Google Firebase Cloud Messaging (FCM). Firebase processes an installation identifier, a messaging token, category topic subscriptions, and technical connection and delivery information to route notifications to your app installation. These are installation identifiers, not a requirement to give us your Google account. The app stores its messaging token locally; the current app does not upload that token to our own API as a user profile.
- Feedback you submit: sending a bug report or feature request sends its type, title, description, selected notice category, a randomly generated report identifier, and any name or email address you choose to provide. Name and email are optional. App version, Android version, and device manufacturer/model are included automatically when you send feedback. Our database also records the submission time. Do not include passwords, financial details, or other sensitive information in reports.
- Local information: the app stores settings, notification preferences, cached notices and attachments, and reading/viewing state on your device. A name or email entered in a successfully submitted report is remembered locally to prefill later reports. You can edit or remove those fields before another submission.
The current app does not include advertising, Google Analytics, or Firebase Crashlytics SDKs. We do not ask for access to your contacts, microphone, camera, or precise location. This does not mean that network requests or Firebase's delivery infrastructure process no technical data.
3. How information is used
We use request information to retrieve notices and files, installation and subscription information to deliver category notifications, and local data to remember preferences and make previously loaded content available faster. Feedback and its app/device details help us reproduce bugs, evaluate feature requests, and improve the app. If you provide an email, we may contact you for clarification or updates when your bug is fixed or your feature request is considered or added. We do not use feedback email addresses for advertising.
Our infrastructure also processes request information for security, rate limiting, troubleshooting, and service operation. In particular, feedback requests are rate-limited using connection information to reduce abuse.
4. Service providers and sharing
We do not sell or rent your personal information. Information is processed by providers where needed to operate the app:
- Google/Firebase: notification delivery and installation services. See Firebase privacy informationand Google's Privacy Policy.
- Cloudflare: our API, website, database, file delivery, security, and operational logging infrastructure. Feedback is stored in our Cloudflare D1 database and is available to authorized administrators. See Cloudflare's Privacy Policy.
- External sites and apps: opening an original notice, developer profile, or email link is subject to the destination's practices. Sharing a notice or file sends it to the app or recipient you choose.
Information may also be disclosed where legally required or necessary to investigate abuse and protect rights or safety. Providers may process data outside Nepal, including in countries where they operate.
5. Permissions and your controls
- Notifications: choose categories in the app's Settings or disable notifications in Android Settings. Turning off notifications does not itself delete Firebase installation data.
- Attachment downloads: choose Wi-Fi only, Any network, or Off for background notification attachment downloads. Opening a notice or requesting a download yourself can still retrieve its attachment.
- Storage: on older Android versions, storage permission may be requested to save a file you download. Files exported to shared storage remain under your control and may remain after uninstalling the app.
- Feedback: reporting is voluntary and does not require your name or email. Technical app/device details are sent with a report, not as a separate continuous feedback upload.
6. Retention and deletion
Local settings and app-private data remain until cleared, replaced by the app, or removed by clearing app storage or uninstalling. Cached files can be replaced or removed as storage is managed. Delete exported downloads separately using your device's file manager.
Submitted feedback and contact details are retained for support and product improvement; the current feedback system has no automatic expiry. Uninstalling does not remove reports already submitted. You can request access, correction, or deletion by emailing rohityadav.se@gmail.com with the subject “IOE Notices privacy request”. Include your report's reference code and, if supplied, the email used for the report so we can locate it. We may ask for limited additional information to verify a request; do not send identity documents or passwords. Anonymous reports may be difficult to locate without a reference code.
We review deletion requests and remove personal information that is no longer needed, except where retention is necessary for legal obligations, security, or an unresolved dispute. Operational logs and provider-held data have separate retention periods governed by their service settings and policies. We do not promise immediate removal from provider backups. Firebase installation data is subject to Google's retention and deletion processes.
7. Security
Our app API uses HTTPS. We use restricted administrative access, input validation, and rate limits to help protect submitted data. No transmission or storage system can be guaranteed completely secure.
8. Children
IOE Notices is intended for engineering students and is not directed to children under 13. If you believe a child has submitted personal information, contact us so we can investigate and arrange its removal where appropriate.
9. Changes and contact
We may update this policy when the app or its data practices change. The date above identifies the latest revision. For questions about IOE Notices or your information, contact Rohit Yadav at rohityadav.se@gmail.com.