Privacy Policy
Passport Photo & ID Maker is an Android photo utility for portrait capture, local quality checks, permitted photo editing, image export and printable PDF or JPEG sheets. This policy explains how Ashmawi handles information when you use the app.
Your photos are processed on your device. There is no app account, developer-operated photo-upload service, advertising or in-app purchase in the current release. History, usage analytics and crash reporting are optional and off by default. You choose what to save and share.
1. Photos, face analysis and local processing
The app reads portraits you capture or explicitly select to check face visibility, lighting, sharpness and resolution, and to provide permitted cropping, adjustments, background separation and export. Face observations and segmentation masks are used for the current task on your device. The app does not identify people, create face embeddings or operate a face-recognition database.
We do not operate a server that receives your portraits, facial observations, masks or quality reports. Passport guidance is bundled with the app. Visiting an official source opens a website only when you choose its link.
2. Camera, photo access and saved files
Camera permission is requested for taking a photo. You may decline it and import an image instead. The Android photo or document picker grants access to the files you select; the app does not request broad access to your photo library or all device storage.
Saving an image, a PDF sheet or a JPEG sheet is an explicit action. You choose the destination through Android or save to the device's media storage where offered. A selected destination may be a cloud-backed provider. Those files and transfers are handled under that provider's policies.
3. Temporary files and image metadata
The app makes a private working copy of an imported original or camera capture and creates temporary previews and export files. It preserves the working original rather than overwriting it with edits. Abandoned session folders are removed when a new app process starts. In Settings, you can clear the working session and temporary sharing copies.
Temporary sharing copies become eligible for cleanup after 24 hours; cleanup runs on app process startup, so removal is not guaranteed at exactly 24 hours. Temporary files may remain until that cleanup, manual clearing, clearing app storage or uninstalling.
Supported original-file workflows preserve the original bytes, including any existing image metadata. Studio derivatives do not copy GPS metadata. Review an original file's metadata before choosing to share it.
4. Optional history and settings
History is off by default. If you enable it, the app keeps local references and export details for up to the most recent 100 saved items. Records can include file names and locations, format, dimensions, file size, page count, time, and the selected mode or rule. History does not keep extra photo copies or face measurements.
Removing history entries or switching history off removes the local records and associated retained access; it does not delete the saved image or PDF. Language, theme, export preferences and history choices are stored on your device.
5. Analytics, crash reporting and Google libraries
The current release has no ads, paid upgrades, advertising SDK or in-app purchases. It includes Google Analytics for Firebase and Firebase Crashlytics. Each is optional, off by default and controlled separately in Settings. Photo processing remains on your device; network access supports technical services and does not turn photo processing into a cloud service.
If you enable usage analytics, Google receives app screen views and events indicating that a photo, PDF sheet or JPEG sheet was saved. Custom events use fixed names without file contents or file-specific parameters. Analytics may also process app-instance identifiers, device and app information, usage information and approximate location inferred from network information. Advertising-ID collection, advertising storage, advertising user data and ad-personalization consent are disabled.
If you enable crash reporting, cached technical reports can be sent at a subsequent app launch with your saved choice enabled. Automatic report upload remains disabled. Reports can contain installation identifiers, app and device details, stack traces, exception messages and technical context. Reports may remain locally until a later launch; pending reports are deleted on launch when reporting is off. The app does not deliberately attach portraits, face measurements, file names or original image metadata. Automatic crash context can nevertheless incidentally include file-related details.
Turning analytics off stops its collection and resets local Analytics data. Turning either option off does not erase information already transmitted. Google service data follows the applicable service retention settings and policies; contact us with privacy requests. See Privacy and Security in Firebase and Google's Privacy Policy.
Bundled ML Kit face detection and MediaPipe segmentation process images locally. Their documented operational metrics may be handled separately when network access is available; the Firebase switches do not control these libraries. Google's ML Kit disclosure describes app and device information, installation identifiers, performance metrics, API configuration and error codes. MediaPipe's included third-party privacy notice describes performance and usage metrics. These technical disclosures do not mean that portraits are uploaded for processing.
7. Retention, deletion and backup
You can clear temporary files and history from Settings, revoke camera or file permissions through Android, clear the app's storage, or uninstall the app. Clearing app storage or uninstalling removes app-private working files, settings and history. Exported files and copies held by other apps remain in their chosen destinations and must be managed separately. Deletion uses normal operating-system deletion, not a guaranteed secure-erasure procedure.
The app disables Android app backup and excludes its app-data domains from the configured cloud-backup and device-transfer rules. Files you explicitly save to a backed-up or cloud-managed folder are subject to that destination's behavior.
8. Security and children
The app uses Android app-private storage and system permission controls. No device or storage system can guarantee absolute security. You are responsible for access to your device and for choosing recipients and save destinations carefully.
This is a general-purpose photo utility and is not specifically directed at children. We do not knowingly request children's personal information through an app account or upload service. If you believe a child has sent personal information to support, contact us.
9. These legal pages
These pages do not embed advertising, analytics scripts or third-party fonts. Opening the pages or linked services in a browser involves the website host and any destination you visit, whose own policies and normal connection handling may apply. The app's on-device processing description does not describe those independent services.
10. Changes and contact
We may update this policy when the app or its data practices change. The effective date identifies this version. For privacy questions or requests concerning information you have sent us, contact Ashmawi at ashmawi.co@gmail.com.