Information you provide

• Text, prompts, CV content, captions, translations, reply drafts, and brainstorming requests you choose to submit.
• Message or email content you paste into the reply-writing features.
• PDF files you choose to open locally for summarization. The app extracts text from the PDF on-device before sending summary prompts.
• Images or screenshots you choose for OCR-style workflows. In the current code path, the image is selected locally and camera access is only requested when you choose to take a photo.

How the app uses data

• To generate AI responses for the feature you selected.
• To store task history, favorites, onboarding state, theme preference, and notification preference locally on your device.
• To support app reliability, crash diagnostics, and advertising when those services are enabled in the app build.

Permissions and access

• Camera permission is requested only when you choose to capture a photo for OCR.
• Notification permission is requested only if you enable notifications in Settings.
• Photos and PDF selection use system pickers where possible instead of broad storage access.
• The app does not request contacts, call logs, SMS, microphone, precise location, or broad file-system access for the current feature set.

Third-party services

• AI requests may be sent to the configured OpenAI-compatible provider to generate results.
• Google Mobile Ads may be used for free-tier advertising.
• Firebase Crashlytics is initialized for crash reporting. Firebase packages for analytics, remote config, and messaging are present in the project, but any production disclosure should be based on the exact release build you ship.

Retention and control

• Task history is stored locally on-device unless you delete it.
• You can remove history entries, clear local history, revoke permissions, or uninstall the app at any time.
• Use device settings to disable runtime permissions or notification access.

Security and transport

• The app is configured to use HTTPS for the default AI base URL.
• Public policy URLs and production service endpoints should always use HTTPS.
• You should not submit highly sensitive information unless you are comfortable sending it through the configured AI provider and any enabled third-party SDKs used in production.

Contact

For privacy or support requests about Obama AI, use the official developer contact details published on the Google Play listing for Mubarak Babangida / Moubs Corps.
Support channel: Google Play developer contact email and support page