Privacy Policy
What information Zenjit processes and your rights.
On this device, without signing in
The device stores practice identifiers, targets and current counts, progress status, and start, update, and completion times. Lanterns from completed bead practices and your choices of beads, sound effects, haptics, motion, background music, volume, and guide voice also stay on the device.
Your private journal
Writing a journal entry stores up to 3,000 characters, an entry identifier, and creation and update times on the device. Entries may contain personal information you write yourself. In My journal, you can read, edit, or delete entries individually. Unsaved writing may be lost if the app is forcibly closed.
Records are not sent to our servers
Zenjit currently has no feature that sends practice records, journals, or preferences to the operator’s server or syncs them to other devices. Journal entries are not sent to analytics services or included in lantern sharing. The operator cannot directly access, recover, or delete entries on your device.
Sharing lantern messages
Sharing passes a prepared public message, its category, and credits through the operating system’s sharing feature. A message link is included when a public address is configured. Journal entries and practice identifiers, counts, and times are not included. You choose the app and recipient; shared content is subject to the selected service’s policies. Opening an original-source link takes you to an external site.
Audio and device features
The app can play sound effects, 24 background tracks, and two Korean and two English guide voices, and provide haptics. It does not record through the microphone. Music and voices are included in the iPhone app; no external AI voice-generation service is called during use. On the web, connection information may be processed when loading content files. If you allow timer notifications, the device schedules a completion alert. Timer progress and remaining time may appear on the Lock Screen. Timer records are not sent to the operator’s server for these features.
Retention and deletion
Records are not automatically deleted after a set period, and there is no bulk export feature. Journal entries can be deleted individually. Deleting an app differs from offloading it. Copies retained in operating-system or cloud backups, and their restoration, depend on device and backup settings. Zenjit does not provide its own cloud backup or restoration from the operator’s server.
Purchase verification and restoration
RevenueCat checks prices and ownership. Unless purchase data processing is paused, opening or returning to the app may process customer identifiers, Apple transaction, product and ownership data, and app, device and connection information. A customer record may be created before a purchase. Apple and RevenueCat handle purchases and restoration; items added by a remaining-items purchase are confirmed on the device from Apple purchase history. Purchase history and statistics are also used to operate and analyse purchase features. We do not receive card numbers or Apple account passwords, or send journal and practice records.
Connection information and request limits
When you connect to the purchase-verification or privacy-request server, your IP address is processed to limit excessive requests and protect the service. We do not store that IP address as a separate field in the app’s purchase or privacy-request database. Connection and security information handled by Cloudflare, including retained copies, is subject to the provider’s processing and retention practices.
Requests about purchase information
You can submit a request or check its status in the app’s Privacy information screen. When you choose to use this feature, Apple-signed app transaction information is sent to identify the requester and find existing requests, whether or not purchase features are connected. The server retains a request identifier, a value linking it to the purchaser, review status, and processing times so the same request can continue. A support code can be linked once within 15 minutes of issue; expiry does not immediately delete its stored verification value. Submitting a request does not complete deletion, request an Apple refund, or delete records on this device.
Retention and deletion of purchase information
Information needed to provide and restore purchases and prevent duplicate processing is retained for as long as needed for those purposes. We review the necessary scope for each request. Information no longer needed is identified for deletion, while information that must be retained by law is kept separately under the applicable basis and period. If we retain some information, we explain the specific items, reasons, retention period or end conditions, and processing outcome. We do not provide a feature that immediately deletes all purchase information upon receiving a request or automatically deletes it all after a fixed period.
Recovery and deletion-protection records
We may keep separate minimal records to prevent duplicate processing or the re-creation of deleted information when recovering from an interrupted request or an earlier system state. These can include protective values that can be linked to a purchaser, request and operation identifiers, processing status and times, and values used to check that records are consistent. We do not treat these values as anonymous. We review their purpose, other retention requirements, and retained copies before removing them; elapsed time alone does not mean that every copy has been deleted.
Using purchases again after deletion
Before requesting erasure, pause purchase processing in the app’s Privacy information screen, then fully close and reopen the app. Verified access for the same purchaser and a pause marker may remain on this device. Support checks linked customers, other devices, copies and retention reasons, and distinguishes Zenjit-server and RevenueCat outcomes. After receiving the overall closure notice, explicitly consent to processing and resume. Checking or restoring purchases may recreate RevenueCat records; it neither cancels Apple purchases nor restores deleted journals.
Services that process information
Apple processes payments and Apple purchase history. We use RevenueCat for purchase verification, restoration and purchase analytics, Cloudflare for privacy requests, and Gmail for messages you send. RevenueCat stores customer data in AWS data centres in the United States. Customer identifiers can be linked to a person and are not treated as anonymous. Automatic advertising identifier collection and optional diagnostics are disabled, and we do not use this data for advertising tracking. Do not send passwords, verification codes or raw transaction proofs.
Contact and operator
When you contact us, we use the display name you provide, your email address, subject, message, attachments, and our replies to investigate and assist you. Where needed, we also review the iPhone model, iOS and app versions, affected screen and actions, and redacted error screenshots that you choose to provide. The app does not automatically add or send this information in a support email. Do not send journal entries, passwords, verification codes, or raw transaction proofs. Use the address below for privacy questions too.
Retention and deletion of support emails
Our policy is to delete ordinary support emails without undue delay once the reply and necessary follow-up are complete. This covers received messages, sent replies and quoted content, and attachments; the affected messages are also deleted from Trash. We do not save or back up support emails in another email app or separate storage. For complaints, disputes, or legally required retention, only the necessary information is separated and assigned a retention basis and end date. Deleting messages in Gmail does not simultaneously remove all copies within Google; the provider’s deletion processes and retention exceptions may apply.
Privacy officer
DONG KYEONG RYU · destinylink88@gmail.com
Effective date
October 5, 2026