Effective date: September 28, 2026
The current public version of this policy is available at https://novellessa.com/pregnancy-test-scanner/privacy.
This Privacy Policy explains how Pregnancy Test Scanner handles information when you use its educational features, Scan feature, local records, reminders, and advertising.
Overview
Pregnancy Test Scanner provides pregnancy-test education, optional Scan interpretation, and tools for keeping local records and reminders. The app has no user accounts or cloud-sync feature. When advertising is enabled, the app uses Google Mobile Ads (AdMob). The app does not currently use a separate analytics service such as Firebase Analytics.
Information stored on your device
Depending on the features you use, the app stores information in Android app-private storage, including:
- My Tests records that you explicitly save: selected result, date and time, and an optional note. The image is not included.
- My Signs entries: date, selected signs, custom sign text, and optional notes.
- Reminder date and time and its state, active Test Timer state, preferences such as language and App Lock settings, favorites, recently viewed articles, and Scan entitlement state.
These records are not synchronized to an app account or our server. The app’s backup configuration excludes its persistent app data from Android cloud backup and device transfer. The app does not claim app-level encryption of its local database. Android app-private storage provides the storage boundary used by the app.
Pregnancy Test Scan images
When you start Scan, CameraX captures an image. The app prepares the image on your device and crops the test result area. The original full camera image is not intentionally sent. When you submit the Scan, the prepared crop is sent over HTTPS to our Scan server at pregnancy-api.novellessa.com. Our server forwards the crop to OpenAI for AI processing. This transfer is necessary to provide the Scan feature.
The Scan image is not saved in My Tests. If you separately choose to save a result, My Tests stores the selected result, date and time, and any note you add, but not the image. The app and proxy are designed to process the image in memory without intentionally persisting an image file. The proxy does not intentionally log image bodies, prompts, Scan interpretations, raw OpenAI responses, or API keys. Its application logs may include operational metadata such as a generated request ID, method, fixed route label, status, generic outcome, latency, and request payload byte count. Nginx access logging is disabled for the Scan API host. Hosting infrastructure may handle its own operational records; its retention period has not been verified, so no fixed infrastructure retention period is promised here.
The app does not send Scan images, Scan interpretations, My Tests records, or My Signs data to AdMob for ad targeting.
AI processing by OpenAI
Our server sends the prepared Scan image and Scan instructions to the OpenAI Responses API so OpenAI can return an interpretation. Each request sets store:false. In the production OpenAI organization, API call logging is set to “Enabled per call”; store:false means Responses application-state storage is not enabled for these Scan calls. It does not mean zero retention.
The production organization’s model-feedback sharing, evaluation/fine-tuning sharing, and API inputs/outputs sharing for model improvement are disabled. OpenAI’s API data controls state that API content is not used to train models by default unless the API customer opts in. These sharing settings do not prevent OpenAI from processing the image to provide the requested Scan service.
Under standard OpenAI API abuse-monitoring controls, content may still be retained in abuse-monitoring logs for up to 30 days. We do not claim that Modified Abuse Monitoring or Zero Data Retention applies to the production organization. OpenAI’s provider-side processing and retention follow the terms and controls that apply to that organization.
Advertising and consent
When advertising is enabled, the app uses Google Mobile Ads (AdMob). Google’s SDK may process device and app information needed for advertising, measurement, fraud prevention, diagnostics, and related functionality. Google’s SDK disclosures identify categories including IP address, app interactions, diagnostics and performance information, and device or account identifiers. Google UMP is used for advertising consent and privacy choices where applicable.
The app does not add pregnancy-test images or results, Scan interpretations, My Tests records, My Signs, expected-period dates, notes, or reminder health context to ad requests or use them for ad targeting. AdMob can process its own SDK data as described by Google.
Other services and analytics
The app uses OpenAI through our Scan proxy for Scan interpretation, Google Mobile Ads for ads when enabled, and Google UMP for applicable advertising consent and privacy choices. It does not currently use a separate analytics service such as Firebase Analytics or Firebase Crashlytics. This does not mean AdMob performs no measurement or diagnostics processing.
The Scan proxy endpoint is pregnancy-api.novellessa.com. This policy does not state a geographic processing location for the hosting infrastructure or providers. See each provider’s applicable terms and privacy information for details about its processing.
Retention and deletion
Locally saved records remain until you delete them, clear the app’s storage in Android settings, or uninstall the app. You can delete individual My Tests records and My Signs entries, remove favorites, clear recently viewed history, and cancel a reminder. There are no user accounts, so account deletion is not applicable. The app does not provide a request to delete OpenAI or hosting-provider logs. The proxy is designed not to persist Scan image files; provider and production-host retention follow their own applicable settings and practices.
Google and OpenAI handle data they receive under their applicable retention and deletion practices. See the AI section above for the standard OpenAI abuse-monitoring retention caveat. The production host’s infrastructure log-retention period has not been verified.
Security
The app stores local records in Android app-private storage. Scan requests to the production proxy and the proxy’s requests to the OpenAI API use HTTPS. Google states that Google Mobile Ads data is encrypted in transit. These protections do not guarantee absolute security. The app does not claim end-to-end encryption, app-level database encryption, or storage of biometric data.
If you enable App Lock, Android system authentication handles biometrics or your device credential. The app does not store biometric data, PINs, passwords, or device credentials.
Children
The app is intended for adults age 18 and older and is not directed to children.
Changes
This Privacy Policy may be updated when the app’s features, data practices, providers, or applicable requirements change. The effective date will be updated with the policy.
Contact
For questions or requests about this Privacy Policy, contact apptechno64@gmail.com.