This policy describes the Pregnancy Journey Android application maintained by Medicab360. The app is not yet available through an official store listing. This policy reflects the Flutter project code and release notes reviewed on 25 October 2026; a published release can differ if its SDKs or configuration change.
1. Who is responsible
Pregnancy Journey is developed under the Medicab360 independent developer brand. This website does not represent Medicab360 as a legally incorporated company. For questions about this policy or app privacy, email contact@medicab360.com.
2. Accounts and online services
The reviewed application has no sign-up, user account, login, health-data server, or cloud-sync service. We do not receive the app’s personal pregnancy records on a Medicab360 server. There is no remote account-deletion process because the app does not create a remote user account.
The Android app uses internet access for consent checks and, if production advertising is later enabled, ad delivery. The reviewed code does not include a general analytics service or a Medicab360 health-data API. Notifications and reminders are scheduled on the device rather than sent as remote push messages.
3. Information you choose to keep in the app
The app can store information that you enter or create, including a selected journey and dates, planning preferences, appointment and reminder details, journal notes, checklist items, pregnancy or cycle tracking entries, symptoms, measurements, medications, supplements, and photos or keepsakes saved in app storage. App settings such as language, theme, dashboard choices and advertising consent preferences may also be stored on the device.
These records are held in the app’s local database and private device storage. They remain on the device unless you choose to make and move a backup file. The app code does not send these pregnancy records, dates, symptoms, measurements, notes or journey selection to an advertising provider for ad targeting.
4. Advertising and third-party SDKs
Pregnancy Journey is free to use. Advertising is the planned revenue source, but production ad requests are disabled by default in the reviewed project. Advertising is not active merely because an SDK is present in the code. The owner must separately approve and configure a release, and ad requests also depend on the app’s consent and provider settings.
When a store release is configured to request ads, it uses a provider selected by the explicit distribution build:
- Google Play and Samsung Galaxy Store: Google Mobile Ads SDK with Google’s User Messaging Platform for consent and privacy choices. Google says its Android SDK may automatically collect and share an IP address, app interactions, diagnostics, and device or account identifiers for advertising, analytics and fraud prevention. An IP address may be used to estimate general location. Applicable consent choices and Android advertising-ID controls affect processing; they do not mean the SDK collects no data. See Google’s SDK data disclosure and UMP privacy information.
- Huawei AppGallery: Huawei Ads / Petal Ads. The app’s Huawei request options are non-personalized and do not request location, and the app waits for the user to explicitly enable Huawei ads before allowing requests. Huawei’s advertising documentation describes the Open Advertising Identifier (OAID) and processing of device, network, app and ad-interaction information. Non-personalized ads can still involve technical data needed to deliver and measure ads. See Huawei Ads Kit and Huawei Ads’ privacy statement.
Provider SDK behavior and the data fields involved can change with SDK versions, store builds, location and consent settings. Each provider has its own privacy terms and retention practices. We do not set a provider retention period in the app. Before any store release, the owner must confirm the actual SDK versions, ad IDs, consent screens, final store build, provider disclosures and store data declarations.
5. Device permissions
Android notification permission is used for reminders that you choose to create. The app can request permission to schedule exact alarms on Android versions that require it and uses a boot-completed permission to restore locally scheduled reminders after a restart. Denying notifications does not prevent ordinary app use. The app does not request location permission for ads. Internet access is used by advertising and consent SDKs when those services are active.
6. Local controls, deletion and backups
Open More → Privacy & Security → Local Data Management in the app to review and delete supported local record categories or reset the local app data. You can also use Android’s app settings to clear app storage or uninstall the app. The developer cannot remotely erase data that has stayed on your device.
Android automatic cloud backup and device-transfer backup are disabled for the app in the reviewed manifest rules. The app also has a manual backup and restore feature. A manual backup may contain database records, preferences and photos, and the backup file is not encrypted. You choose where it is saved and whether to move or share it. Keep it somewhere private, do not send it with a support request, and delete it separately when you no longer need it. Removing information from the app does not delete copies of a backup file that you saved elsewhere.
Data kept locally remains until you remove it, reset app data or uninstall the app, subject to device behavior. Data in a manual backup remains until you delete that file. Ad providers determine retention for information their SDKs process under their own policies.
7. Children
Pregnancy Journey is an informational and organization app, not a service designed for children. The owner must review age targeting and each store’s audience rules before publication. Do not enter another person’s information in the app without an appropriate basis to do so.
8. Privacy questions
For questions about data processing by the app or this policy, contact contact@medicab360.com. Include the app version and store build, if available, but do not email pregnancy records, account credentials or backup files. For a local record, use the controls in the app; a message to Medicab360 cannot remove data from your device or from a backup file you hold. See the data and privacy requests page for the available options.
9. Changes and review
This policy may be updated when app behavior, SDKs or store configuration changes. The “Last updated” date at the top identifies the current version. Before publication and after significant SDK updates, the owner should review the policy against the released build and the providers’ current privacy documentation.