Privacy & transparency

Privacy Policy

This Privacy Policy explains what Probeshika stores on your device, what limited technical information may be processed by online services, and why that information is needed.

Last updated: September 23, 2026
✦

Overview

Probeshika is an educational information utility for students tracking admission deadlines, exam schedules, and university information in Bangladesh.

This Privacy Policy explains the difference between information stored locally on your device and limited technical information processed by online services used by the app.

01

Information We Collect

Probeshika follows a data-minimization approach. We do not require traditional account registration and do not intentionally collect personal identity information such as your real name, email address, phone number, or physical location.

Local-only data

Stored on your device

  • Language preference, theme selection, and notification toggle
  • Custom display name and avatar image stored in app internal storage
  • Favorite institutions and saved admission units
  • Custom reminders, alarm settings, and alert offset settings
  • Cost Planner entries
  • Routine Maker plans, schedules, and daily study activities
  • Local notification history and in-app alert status
  • Cached admission content and other locally cached app content
Remote / synchronized data

Transmitted over secure connections

  • Anonymous Backend User ID: created automatically by Supabase to support secure backend communication.
  • App-Generated Installation ID: a randomly generated UUID stored in app preferences and not derived from hardware.
  • FCM Registration Token: provided by Firebase Cloud Messaging to route push notifications.
  • Device Platform & timestamps: sent alongside notification-related data to support delivery compatibility and synchronization.
02

Information We Do Not Collect

  • Personal identity information such as real name, email address, phone number, or password
  • Hardware identifiers such as IMEI, MAC address, Android ID, or serial number
  • Precise location data, including GPS location
  • Device contacts, photos, media files, or private calendar contents
  • Behavioral tracking, browsing history, or cross-app advertising identifiers
03

How We Use Information

We use the limited technical data processed by the app solely to provide and maintain core functionality.

Admission content & updates Fetches university deadlines, exam schedules, admission information, and home banners from Supabase over secure connections, with real-time updates while active.
Push notification delivery Synchronizes the FCM registration token, app-generated installation ID, anonymous session ID, and platform information to our Supabase backend through a secure RPC so targeted admission alerts can be delivered to your installation.
Local reminders & alarms Uses Android's local scheduling mechanisms to trigger reminders and alarms that you configure in the app. Alarm scheduling can use Android's exact-alarm capability where required for reliable timing.
Calendar integration When you choose to add an event to your calendar, Probeshika uses an Android system calendar intent. The app does not request permission to read or modify your existing private calendar data.
Network connections When Probeshika connects to online services, those services may automatically process standard technical information, such as IP address and connection or request metadata, when necessary to provide and secure their services.
Third-party SDK diagnostics Third-party SDKs used by Probeshika may automatically process limited technical, diagnostic, installation, performance, configuration, or service-related information required for their operation, security, reliability, and maintenance.
No advertising or behavioral profiling

Probeshika does not use third-party SDKs for personalized advertising, cross-app behavioral profiling, or advertising-based tracking.

04

Permissions

Notifications POST_NOTIFICATIONS is used so you can receive admission alerts and reminders.
Internet & network state INTERNET and ACCESS_NETWORK_STATE are used to retrieve online content and maintain network-aware behavior.
Boot completed RECEIVE_BOOT_COMPLETED is used to restore scheduled local reminders and alarms after device restart.
Exact alarms SCHEDULE_EXACT_ALARM is used where the app needs Android's exact alarm scheduling capability for user-configured reminders or alarms that must trigger at the selected time.

Probeshika does not request Location, Camera, Microphone, Contacts, SMS, Phone State, or Calendar read/write permissions. Calendar-related features use Android system intent popups without reading or writing your private calendar contents.

05

Security

We use safeguards appropriate to the app's architecture, including encrypted network transport such as HTTPS/TLS and secure realtime connections where applicable, restricted backend RPC access, and Android's application storage sandbox.

Access to backend operations is restricted according to the function being performed. Sensitive server-side credentials used for backend notification delivery are not embedded in the Android application.

Android backup and device-transfer mechanisms may preserve selected app data according to Android's backup configuration and your device/account settings. This may include locally stored preferences, database data, or other app data selected by the operating system's backup rules.

No system connected to the internet can be guaranteed to be completely immune from every security risk.

06

Third-Party Services

Probeshika does not include advertising SDKs and does not use analytics for advertising or behavioral tracking. However, third-party services used to provide core functionality may process limited technical, diagnostic, installation, or service-related information.

Third-Party SDK Data Processing

Some third-party services used by Probeshika may automatically process limited technical or diagnostic information necessary to operate, secure, maintain, and improve their services.

Depending on the service, this may include device or installation identifiers, application information, SDK or feature versions, configuration information, performance or diagnostic metrics, error information, and information about how a specific SDK feature is configured or used.

Probeshika does not use this information for personalized advertising, cross-app behavioral profiling, or advertising-based tracking.

01

Supabase

Supabase provides backend database, authentication, and realtime infrastructure used by Probeshika.

Probeshika sends limited technical information required for backend functionality, including an anonymous backend user ID, an app-generated installation/device ID, and notification-related information.

View Supabase Privacy Policy ↗
02

Firebase Cloud Messaging & Firebase Installations

Firebase services are used to support push-notification delivery and installation-related identification needed for messaging.

Firebase may process device and installation information, including an FCM registration token and related technical information, to route notifications and operate the messaging service.

View Google's Privacy Policy ↗
07

Data Retention

Local device data

Local data remains on your device while needed until you delete it, clear Probeshika's app storage through Android settings, or uninstall Probeshika.

Cached admission content and other local cache data may be updated, replaced, or removed during normal app operation.

Backend device & token data

App installation IDs and FCM registration tokens are retained in our secure notification database as long as needed to deliver active push alerts.

FCM registration tokens and app installation information may be updated when the token changes or when the app synchronizes with the backend.

Backend records may be removed or updated as part of normal notification-service maintenance.

08

Your Choices & Control

  • You can control many of your app preferences and locally stored data using the controls provided in Probeshika and Android.
  • You can turn notifications on or off through the app's notification settings and Android notification controls.
  • You can remove local app data by clearing Probeshika's app storage or uninstalling the app.
  • You can manage your language, theme, reminders, alarm settings, saved institutions, Cost Planner entries, Routine Maker plans, nickname/avatar, and other local preferences directly within the app.
  • No traditional account management: Probeshika does not provide traditional user account registration or login. The app may use an automatically created anonymous backend session for technical functionality, but it does not provide a personal account profile containing your name, email address, or password.
09

Changes to This Privacy Policy

We may update this Privacy Policy when the app's data practices, third-party services, or relevant requirements change.

When we make changes, we will update the "Last updated" date and publish the revised policy on this page and within the app where applicable.

10

Contact

If you have any questions, concerns, or inquiries regarding this Privacy Policy or Probeshika's data practices, please contact us at:

We welcome questions about privacy, data handling, security, and the services used by Probeshika.