Privacy Policy

HD Camera - Pro Photo Editor · com.psnv.aibcamera
Operator: PSNV · Contact: krgencom@gmail.com
Updated: October 26, 2026

1. Camera, editing and local files

Capture, media editing, gallery, OCR, barcode and face/background processing run on the device. Core capture and editing do not automatically upload your photos or videos to PSNV servers. Explicit sharing, export or backup sends selected files, including any embedded location metadata, to your chosen destination. Vault access uses an in-app PIN and Android app storage. Device lock and security settings help protect access to the device.

2. Optional permissions and system services

Camera access enables capture. Microphone access enables recording and voice shutter. Voice shutter uses the device speech-recognition service, which may send audio to its provider depending on the service and device settings. Optional location features can add GPS tags or stamps. Address lookup uses system geocoding; photo maps request OpenStreetMap tiles. Those providers may receive coordinates or map areas and network information such as IP addresses. You can change permissions in Android settings. Imports use system file-selection tools.

3. Advertising and privacy controls

The app uses Google AdMob. Where permitted, its SDK may process and share IP-derived general location, app/ad interactions, diagnostics and identifiers such as advertising or app-set IDs for ads, measurement and fraud prevention. Google UMP determines applicable messages and manages choices. Settings shows ad privacy options when required by the SDK. Declining personalization does not necessarily remove all ads. Android also provides advertising-ID controls. See the linked AdMob and Google privacy information above.

4. Analytics and crash diagnostics

Firebase Analytics processes feature, ad and purchase events and properties such as app version, language, country and free/premium status. Turning off “Share usage analytics” in Settings stops future analytics collection and resets local analytics data; this does not promise erasure of previously uploaded data. Advertising choices and crash diagnostics are separate. Firebase Crashlytics in Android release builds processes crash traces, device/app details and installation identifiers. We do not intentionally add media or typed content to analytics events or error reports. See Firebase’s linked privacy information.

5. On-device models and purchases

ML Kit processes image/text inputs on-device, while contacting Google for models, compatibility information and performance/usage metrics. Google Play or ONE store handles payments, depending on the store version installed. The app checks and stores product/purchase identifiers and access rights; it has no feature to receive payment-card or bank details.

6. Retention, deletion and contact

Local media and settings may remain until removed using app deletion/trash controls or Android app-data management. Exported copies must be managed at their destinations. Analytics follows configured Google Analytics retention controls. Google documents that Crashlytics begins removing relevant crash information and identifiers after 90 days. Provider policies and legal obligations may require additional retention. Contact PSNV at the email above about access, correction, deletion or other privacy requests concerning data we control. Identifying relevant records may require additional information. We use email addresses and message contents received from you to respond.

7. Security, providers and changes

The app uses Android storage/security features and app access controls. Google’s ads SDK uses TLS in transit. Chosen sharing destinations and system services have their own privacy practices; external services may process data internationally. We update this page for material privacy changes. Provider references are linked in the Korean sections above.