Baekya Privacy Policy

Effective and last updated: 22 October 2026.

Operated by 지니안 컴퍼니. Privacy and support contact: [email protected].

This policy covers the Baekya mobile app and support inquiries about it. Visits to the company website, jiniancompany.dev, are covered separately by the website’s privacy policy.

What stays in the app

Baekya uses your photos, notes and note formatting, capture dates and time zones, UTC timestamps for capture and reveal events, reveal and viewing status, and preferences to provide its camera and album features. It stores these in the app's private storage on your device. It also keeps local identifiers and records needed to manage deletion and the daily capture limit.

Baekya does not require an account or operate a photo-upload or cloud-recovery service. It does not send your photos or notes to the developer or record microphone audio. It does not use advertising or cross-app advertising tracking. Optional capture-location recording, Google Maps communications and Google ML Kit diagnostic and usage metrics are described below. Store purchases and data handled by your operating system or chosen external services follow their providers’ practices.

Permissions and local notifications

Camera access is used to take photos. Notifications, when permitted, are scheduled locally on your device to let you know when a photo is ready; this feature does not use a Baekya push server. Your operating system controls delivery and may show notifications on the lock screen. You can change permissions and notification visibility in system settings.

Saving a photo to the system photo library, sharing it with another app, and selecting a backup file or destination happen through actions you choose. Baekya requests or uses the system access needed for those actions. It does not upload your album automatically.

Optional capture location

If you enable location recording and grant system permission, Baekya checks a recent location while the camera screen is active in the foreground and saves it with the photo when you take it. Approximate location also works. Declining permission or turning recording off does not prevent photography. You can disable recording in the app or change permission in system settings. Turning it off keeps locations already saved. Saved location is included in password-encrypted manual backups; shared or exported photo images exclude it. Baekya does not use background location access.

Google Maps

Opening the photo map uses Google Maps over the internet. Stored capture coordinates determine the map camera and photo markers passed to the Maps SDK; the displayed region and map interactions may be transmitted to Google as the map is loaded or moved. This is separate from the optional capture-location permission. Viewing saved places does not request a new location permission, and the map's current-device-location layer is disabled. Photo thumbnails used for markers are made locally; Baekya has no photo-upload service for the map.

The Maps SDK automatically collects request and device metadata, SDK build information, IP address, a pseudonymous SDK identifier, and SDK crash information. Camera operations can also produce map-interaction information. Google receives latitude/longitude coordinates and request information for map display, and may retain and use them to provide and improve Google products and services under its own privacy policy. Requests are logged; retention depends on Google’s stated business needs and retention policies. Maps communications use encryption in transit. Use Photos/list view instead of the map if you do not want to load Google Maps. The location-recording switch does not disable Maps communications or SDK diagnostics.

On-device photo protection and ML Kit

On Android, Baekya uses bundled Google ML Kit face-detection and Latin, Korean and Japanese text-recognition models to locate areas to protect when rendering photo effects. Image analysis runs on the device. The app uses region boxes and a derived protection mask, not face identity or recognized text content. ML Kit states that the input images/text and resulting outputs are not sent to Google servers.

ML Kit separately sends diagnostic and usage metrics to Google, including device and app information, per-installation identifiers, timing/performance information, API configuration and input/output sizes, feature versions, event types and error codes. This is SDK telemetry, not an upload of your photos or notes. Google states that this data is encrypted in transit using HTTPS and is not transferred onward to third parties. The app has no separate switch for this SDK telemetry. Bundled models avoid a required first-use model download; they do not mean the SDK never communicates with Google.

For Google's handling of SDK data, see Google Maps additional terms, Google Privacy Policy, Maps SDK disclosure, ML Kit privacy, and ML Kit disclosure.

Password-encrypted manual backups

You can create a manual backup containing photos, notes, formatting, dates, saved capture locations, reveal and viewing status, and deletion information. The backup also includes photos in Trash. Device-specific daily capture-limit records and app preferences are not included. The exported backup file is encrypted with AES-256-GCM. Its encryption key is derived from your password with PBKDF2-HMAC-SHA256 using 600,000 iterations and a random salt.

Baekya uses the password temporarily during backup or restore. It does not save it for later use, log it or transmit it to the developer. Baekya cannot reset a forgotten password or recover an encrypted backup without the correct password. If the device and local data are lost and you have no usable backup and password, the developer cannot recover your album.

This encryption applies to the manual backup file. Baekya does not separately password-encrypt every photo or its entire local database. Device storage protections depend on the operating system and your device settings.

Files, sharing and operating-system backups

You choose where an exported backup goes through the system file picker. A selected location may belong to a cloud-storage provider. Photos saved to the system library, shared images and exported or imported files may be copied or synchronized by the services you choose. Their storage, access and deletion practices are governed by their policies.

On iOS, app data may also be included in an operating-system iCloud or computer backup, depending on your settings. The current Android app is configured to exclude its private app data from automatic system cloud backup and device transfer; operating-system and device behavior may vary. These are distinct from Baekya's password-encrypted manual backups. Do not assume that every copy is protected by your Baekya backup password.

Retention and deletion

Photos and notes remain locally until you remove them or the app's data is removed. Moving a photo to Trash keeps it available for restoration. Permanent deletion removes its local photo and note data; cleanup is retried if a file cannot be removed immediately. Minimal deletion identifiers and times may remain to prevent deleted items from returning during a later restore. Daily capture-limit records may also remain. These records do not contain the photo or note text.

Deleting in the app does not delete exported backups, copies in Photos, shared images or copies kept by another service or an operating-system backup. Manage and delete those separately. An older backup can still contain a photo you later deleted. Restoring Trash photos from a backup onto a fresh device makes them active album photos; an existing local Trash state is preserved. Removing the app or its data without a usable backup can cause permanent loss.

Your choices and contact

You can manage permissions in system settings, create a backup, and move, restore or permanently delete photos in the app. Keep backup files and their passwords safe. For questions about the app or this policy, or to request deletion of support correspondence, contact [email protected]. We cannot access or delete your device’s album remotely.

Support correspondence and policy updates

If you email us, 지니안 컴퍼니 receives your email address and the message, attachments and other information you choose to provide. We use this information to respond to your inquiry and resolve the issue, and retain it only as needed for that purpose and any follow-up. Email is handled through the email providers involved, under their own policies. Do not send backup passwords or photos and notes that are unnecessary for your inquiry.

Changes to these practices will be reflected in this policy, with an updated date, and in applicable store disclosures.