Privacy Policy

Miroven is operated personally by Choi Seung-woo (최승우) without business registration. The official service operator (the “Operator”) protects users’ personal information under the Korean Personal Information Protection Act and other privacy laws applicable to the Service. This Policy applies to the official website, journal app, and account and sync API offered to users globally. Miroven services operated separately by third parties are subject to their own operators’ policies.

1. Processing summary

• You can write on your device without an account. Records used only locally are not uploaded to the sync server.
• If you choose sync, we process email account information, encrypted records and photos, and metadata needed for sync. Encrypted data is also protected because it can be linked to an account.
• Records and photos are encrypted and decrypted on your device. PINs, recovery codes, and vault keys capable of decryption are not sent to the server.
• The API, database, and photo storage are on an Operator-managed TrueNAS system in the Republic of Korea. The website uses Cloudflare Pages; DNS and API connections use Cloudflare DNS and Tunnel; authentication email uses Resend. External services use Free plans. Domestic self-managed storage is distinct from external providers’ processing abroad.
• There are currently no payment features. We do not collect card numbers, payment account details, billing addresses, or other payment information. Resend email open and click tracking is not used.
• Send privacy inquiries and rights requests to miroven@mksdr.bid.

2. Purposes, information, and legal bases

We process the minimum information needed for each feature. Account information is collected through user input and email verification; sync data is received from the app. Connection information is generated during service requests. Inquiry information is collected when users send email.

The contractual basis below means entering into or performing a service contract and taking steps requested by a user under Article 15(1)(4) of the Korean Personal Information Protection Act. Security-related legitimate interests apply only where Article 15(1)(6) is satisfied, requiring assessment of whether the Operator’s interests clearly outweigh users’ rights. Reading this Policy or agreeing to the Terms is not treated as separate privacy consent.

Account creation, sign-in, and account management

Information: Email address, internal user identifier, registration time, verification values for email verification codes, verification request, expiry and use times, authentication attempt counts, verification values for session tokens, and session creation, expiry and revocation times. Temporary email delivery jobs contain the email address and verification code, and are managed as encrypted job data on the server.

Purpose and basis: Identity verification, account creation, maintaining sign-in, and reauthentication for account deletion / performance of a contract. Email verification is needed for account features. Without it, local features that do not require an account remain available.

Encrypted sync and storage management

Information: Encrypted entries, profiles and photos; encrypted vault key bundles and encryption parameters; account, record, photo and operation identifiers; versions, modification and deletion times; sync sequence and change history; ciphertext sizes; usage and limits; plan labels and entitlement status.

Purpose and basis: User-selected sync between devices, conflict resolution, file storage, and enforcing usage limits / performance of a contract. Displaying plans or entitlements does not mean that payments are currently processed or payment information collected.

Connections, security, and incident response

Information: Connection IP addresses, request times, addresses and methods, browser and operating system information, transmitted headers, and response and security event information. For rate limiting, the API stores verification values derived from IP addresses and email addresses and request counts by time window. Current API application logs are limited to request identifiers, methods, routes, response statuses, and error types. Cloudflare and upstream proxy connection processing is separate from these logs.

Purpose and basis: Delivering requested web pages / processing necessary to provide the requested service, including performance of a contract. Abuse prevention, access control, and incident response / security processing only where legitimate interests clearly outweigh users’ rights. We do not collect connection information for advertising or user behavior analytics. Cloudflare’s own network operations and security processing follow its policies.

Inquiries, rights requests, and deletion

Information: Inquiry email addresses, messages and attachments sent by users, handling results, and the minimum information needed to verify identity or authority to act for another person. Account deletion involves deletion job identifiers, request and processing statuses and times, and verification values for deletion confirmation tokens.

Purpose and basis: Service inquiries and deletion / performance of a contract. Statutory rights requests are handled under Articles 35–38 of the Korean Personal Information Protection Act and legal duties applicable to the request. Sending an email alone is not consent to unnecessary collection.

Do not send plaintext records, PINs, recovery codes, or encryption keys. If optional collection requiring separate consent or new processing is introduced, we will separately explain purposes, information, retention, and the consequences of refusal, and obtain necessary consent before processing.

3. Retention periods

Information is disposed of without delay when its purpose is fulfilled or its retention period ends. The periods below describe Miroven-API retention and cleanup rules. Expiry and actual deletion of stored data may occur at different times. Cleanup runs hourly during normal operation. If outages or workload cause delays, processing resumes after recovery.

• Account information and current sync data: Retained while the account and sync service are maintained. Access is blocked as soon as an account deletion request is accepted, and background jobs delete files and account data in sequence. There is no feature guaranteeing a fixed maximum completion time. Delays or failures are handled under section 4.
• Authentication, sessions, and delivery jobs: Verification codes are valid for 10 minutes and sessions for 30 days. Authentication, session, and delivery job records more than 1 day past expiry are cleaned up hourly. Verification code contents in delivery jobs are removed upon completed delivery, final failure, or invalidation.
• Rate-limit verification values and counts: Records are created by time window and cleaned up hourly once more than 1 day has elapsed from the start of that window.
• Sync history, temporary snapshots, and old photos: Change history becomes eligible for cleanup after 90 days, and temporary sync snapshots after 1 hour. Photos become eligible when no current record, history, or snapshot references them and the file is more than 24 hours old. Cleanup runs in batches; removal of references or expiry does not immediately delete every copy.
• Deletion status records: Status checking is valid for up to 30 days after the request. Completed jobs are cleaned up hourly once more than 1 day has passed after expiry. Failed and incomplete jobs are kept until completion to support retries and deletion without leaving files behind, and are not used for other purposes.
• Operational logs: TrueNAS service container logs rotate at 10 MB per file with up to 3 files per container, removing the oldest first. There is no automatic expiry by number of days, so logs may remain longer with low traffic. API request logs are limited to request identifiers, methods, routes, response statuses, and error types. Caddy proxy access logging is disabled. Cloudflare logs follow separate rules.
• TrueNAS recovery copies: Deployment tools support pre-update ZFS snapshots and manual or scheduled backups. Copies may contain data from before deletion. The tools’ cleanup threshold is 7 days after creation and requires the cleanup task to run. Cleanup is deferred during incomplete deployments for recovery. The Operator resolves the reason for deferral and cleans up copies, and reapplies accepted deletion requests after a restore. These copies are managed on the self-managed system in the Republic of Korea.
• Inquiries: Messages, replies, and attachments are retained for 1 year after handling is complete and then deleted by the Operator. Email providers’ backups are described separately under International transfers.
• Resend and Cloudflare data: See International transfers. These periods are separate from retention on the Operator’s own server.

If a retention duty under another law actually applies, the specific information, law and provision, and period will be disclosed and the information managed separately. Retention periods for payment and supply records are not applied indiscriminately to this Service when payments have not been introduced.

4. Disposal procedures and account deletion

In the app’s account screen, select account and data deletion and complete fresh email verification and confirmation. Once the server accepts deletion, all sessions are revoked and account access is blocked. Background jobs then delete encrypted files and account-related database rows. File deletion errors are retried automatically. If repeated failures stop a job, the Operator resolves the cause and retries it. The Operator checks and takes action on deletion failures within 14 business days. This standard does not justify delaying normal deletion or extending legally required shorter deadlines. Progress is available through the deletion status feature.

Electronic data is removed from databases and file storage. Materials subject to a separate legal retention duty are managed separately. TrueNAS recovery copies follow section 3, and deletion requests are reapplied after restoration. Deleting database rows or files does not immediately overwrite every storage block. Secure erasure or physical destruction procedures are used when storage media are reused or disposed of to prevent recovery.

Account deletion also removes the local vault linked to that account and API on the current device. Local copies on other devices and exported backups must be erased separately. Resetting a local vault alone does not delete the server account. Because of encryption, the Operator cannot restore plaintext records on your behalf. Prepare any needed backups before deletion.

5. Service providers and self-managed storage

• Plus Five Five, Inc. (Resend Free): Sends sign-in and deletion reauthentication emails and processes delivery status. Processes recipient email addresses, email bodies containing verification codes, and delivery metadata. Entries, photos, PINs, and recovery codes are not sent.
• Cloudflare, Inc. (Free): DNS, website deployment and content delivery, API connections, and security and traffic handling through Cloudflare DNS, Pages, and Tunnel. Processes connection IPs, request information, and technical information. Tunnel is used for miroven-api.mksdr.bid. Optional security cookies and additional analytics, including Web Analytics, are disabled. Network and security processing accompanying service delivery may still occur.
• Proton AG (SimpleLogin and Proton Mail): Forwards, receives, replies to, and stores support email, including privacy inquiries. Processes sender email addresses, messages, attachments, and delivery information.

The API, database, and photo storage are managed directly by the Operator on a TrueNAS system in the Republic of Korea. Nobody else has been granted administrative access. Using TrueNAS software does not itself entrust records to or transmit them to its developer. If separate access or transfers such as remote support or external replication or backup are introduced, the actual processors will be disclosed.

The Operator reviews and manages providers’ scope of work, safeguards, and subprocessing conditions. Resend states that its standard Data Processing Addendum (DPA) applies on signup, including Free plans. See the Resend subprocessor list, Cloudflare DPA and subprocessors, SimpleLogin Privacy Policy, and Proton Mail Privacy Policy. Not every listed provider necessarily receives Miroven data.

6. International collection and transfers

When users outside Korea use accounts and sync, their data is transferred to the API and storage system in the Republic of Korea. Even with storage in Korea, processing abroad occurs through Cloudflare connections, authentication email delivery, and support email forwarding and storage.

Resend — overseas processing and storage for email delivery

• Recipient and contact: Plus Five Five, Inc. (Resend), privacy@resend.com.
• Country: United States. Selecting a sending region for the sending domain does not change the country of storage to that region.
• Information and purpose: Email addresses, email bodies containing verification codes, subjects, and sending and delivery metadata / sending and delivering authentication email. Open and click tracking is disabled.
• Timing and method: When users request authentication email, data is transmitted over an SMTP connection encrypted with STARTTLS.
• Retention: Resend Free’s published periods are 30 days for emails and logs and 7 days for backups. Residual customer data is deleted within 90 days after the Resend account contract ends. Deleting a Miroven user account differs from ending the Operator’s Resend contract, so it does not immediately remove all provider copies.
• Basis: For processing and storage necessary to enter into or perform the account authentication service contract, notice is provided under Article 28-8(1)(3)(a) of the Korean Personal Information Protection Act. Transfers not meeting these conditions require another applicable basis, such as separate consent, before processing.
• Refusal and consequences: You can refrain from requesting authentication email or request suspension of processing or deletion of an existing account. Without email verification, account sign-in and sync are unavailable. Local features without an account remain available. If you also do not want deletion reauthentication email, contact us to request an alternative check. The Operator assesses the minimum verifiable account information without requesting PINs, recovery codes, or plaintext records, and explains if identity cannot be verified. Support email also passes through overseas email providers, as described below.

Resend storage locations and retention · Resend DPA

Cloudflare — overseas processing for DNS, website, and API connections

• Recipient and contact: Cloudflare, Inc., privacyquestions@cloudflare.com.
• Countries: Processing uses a global network. Cloudflare identifies the United States and European Economic Area as its primary storage regions. The Free plan does not restrict processing to Korea or a particular country. Countries may vary by network route and subprocessor; see the Cloudflare Privacy Policy and DPA subprocessor and processing locations. This does not mean Miroven traffic’s actual country-by-country routes have been verified.
• Information and purpose: DNS queries, connection IPs, request URLs, times, headers, and other connection information, and response and security events / DNS, website delivery, API traffic relay, and security. Records and photos are transmitted after encryption in the app.
• Timing and method: Network requests during DNS lookups and use of the Cloudflare Pages website or API connected through Tunnel.
• Retention and basis: Processing follows service delivery and security purposes and applicable contracts. Cloudflare’s Security Events documentation describes up to 31 days of security event history on Free plans. This is not a blanket retention maximum for all DNS, Pages, and Tunnel data. Other network data retention follows the purposes and legal obligations in Cloudflare’s privacy information and is not controlled by the Operator as a fixed number of days. Notice under Article 28-8(1)(3)(a) of the Korean Personal Information Protection Act applies to overseas processing and storage necessary for contract performance. Processing outside those conditions needs a separate basis.
• Refusal and consequences: Avoiding these services prevents transfers from future use. You can exercise rights over information already processed through our contact address. Blocking cookies alone does not stop transmission of information needed for connections.

Cloudflare Privacy Policy · Cloudflare DPA · Security event retention

SimpleLogin and Proton Mail — overseas forwarding and storage of support email

• Recipient and contact: Proton AG (SimpleLogin and Proton Mail). Use the contact details in Proton’s privacy information.
• Countries: SimpleLogin lists server locations in Germany, Switzerland, the Netherlands, and France; Proton Mail lists Switzerland, Germany, and Norway. Support email is forwarded through SimpleLogin to Proton Mail for delivery and storage.
• Information, purpose, and timing: When sending privacy or support inquiries and exchanging replies, sender email addresses, messages, attachments, and delivery information are transmitted and stored through email networks.
• Retention: The Operator deletes inquiries 1 year after handling is complete. SimpleLogin deletes delivered emails after forwarding and retains undelivered email for 7 days. Its published periods are 7 days for mail and web server IP logs, up to 14 days for database backups, and up to 30 days for system logs after account deletion, with abuse-response exceptions. Proton Mail backups of deleted data may remain for up to 30 days. Operator deletion of an email does not simultaneously remove provider logs and backups.
• Basis and refusal: Notice under Article 28-8(1)(3)(a) of the Korean Personal Information Protection Act applies to overseas processing and storage necessary for contractual inquiries and rights requests. Processing needing another basis must separately meet its requirements. Not sending email avoids that inquiry transfer. You can view, edit, and export records or request account deletion directly in the app. There is currently no separate Korea-only support channel.

SimpleLogin Privacy Policy · Proton Mail Privacy Policy

Adequacy decisions or standard contractual clauses and necessary supplementary safeguards for EEA, UK, and Swiss transfers are assessed for the actual transfer routes. A provider offering standard terms does not mean Miroven’s contract execution or transfer legality assessment is complete. Contact us for information about applicable safeguards or copies.

7. Third-party disclosure, sale, and other uses

The Operator does not sell personal information or share it for targeted advertising. Processing entrusted to service providers is described in sections 5 and 6. Requests from law enforcement or others do not alone result in disclosure; the applicable legal basis and necessary scope are checked. Disclosures relying on separate consent will first identify the recipient, purpose, information, retention, and consequences of refusal.

There is currently no separate use of pseudonymized information for statistics or research, or provision of records for AI training. If ongoing additional use or disclosure within a reasonably related scope is introduced, criteria concerning purpose relevance, foreseeability, effects on rights, and safeguards will be published first and legal requirements checked.

8. Cookies, device storage, and tracking

Cookies are small pieces of information stored by a browser and sent with requests to the relevant server. Device storage keeps settings or app data within the browser.

• Website: The display theme is stored in localStorage under miroven-website-theme until changed or deleted. Current website code contains no visitor analytics, advertising scripts, or inquiry submission form. Cloudflare hosting connection and security processing is separate.
• App and API: The miroven_session HttpOnly cookie maintains sign-in and is valid for 30 days. Signing out removes it and revokes the server session. Vaults use IndexedDB; display settings use device storage.
• Deletion status: API-specific deletion checking information is stored in the current tab’s sessionStorage. Closing the tab or clearing storage may make status checking difficult but does not cancel server deletion.
• Email: Resend open and click tracking is disabled. Sending, delivery, and failure logs are processed separately from open and click tracking.

Browser privacy, security, or site data settings let you block or delete cookies and storage. Blocking cookies may prevent sign-in; deleting site data may remove the local vault. Prepare an encrypted backup and recovery code safely before deletion. Cloudflare’s optional security cookies and additional analytics are disabled. This does not stop Cloudflare’s network processing itself. If nonessential tracking is introduced, necessary prior consent and refusal options will be provided.

9. Security measures

The app and API use on-device encryption of records and photos, separation of authentication and vault unlocking, per-account access controls, session, request origin and CSRF checks, authentication attempt and request rate limits, and restricted log fields. Decrypted memory caches are cleared on lock and sign-out. Only a vault key bundle protected by the recovery code is sent to the server.

The Operator manages self-hosted storage on TrueNAS, separating the API, database, and file storage and restricting access to administrator secret configuration files. Public website and API connections use HTTPS, and authentication email uses STARTTLS. Internal service connections are distinct from public connections. The Operator manages administrative permissions, updates, and recovery, and restricts unauthorized access to storage locations and media. Encryption does not hide metadata such as email, access times, or ciphertext sizes, or prevent access to an unlocked device. We do not claim independent security audit or certification.

10. Your rights and how to exercise them

Users and authorized legal representatives or agents may request access, correction, deletion, suspension or restriction, withdrawal of consent, portability or transmission, and object to processing under applicable law. Withdrawal does not retroactively invalidate lawful processing before withdrawal.

1. View, edit, and delete records in the app, and export encrypted backup files. An encrypted backup is not equivalent to a standard personal data portability format directly readable by another provider.
2. Request deletion of account and server data from the app’s account screen. See Account deletion.
3. For other access, correction, or portability requests, or if you cannot use the app, email miroven@mksdr.bid with the request type and relevant account email. Recovery codes, PINs, and plaintext records are not required.

The Operator verifies identity or authority only as necessary and responds within applicable legal deadlines. Access requests under the Korean Personal Information Protection Act are generally acted on within 10 days. Justified deferral or refusal will include reasons and remedies. If law restricts deletion, the basis and period will be explained. Users will not be unfairly discriminated against for exercising rights.

The Operator cannot decrypt record contents, so viewing and editing plaintext takes place on users’ devices. This technical limit does not categorically exclude legal rights over email, account information, or ciphertext.

11. Personal information of users under 18

Account and sync services are intended for users aged 18 or older. No separate date-of-birth collection or age verification process is operated. If the Operator learns that a user is under 18, processing of that user’s personal information stops and the account and related personal information are deleted.

12. Automated processing and sensitive information

There is currently no feature analyzing records to make automated evaluations or decisions with legal or similarly significant effects. Supported email domain checks, authentication and request rate limits, and usage limit checks are automated. Requests may be refused or delayed based on the entered email domain, failed authentication or request counts, and storage usage. Contact us to ask for reasons or a review of objections.

Records are not intended for public posting; public profiles and journal publishing are not provided. Sensitive content such as health or beliefs entered by users is encrypted in the app. The Operator has no feature collecting plaintext to classify or analyze it. Unique identifying information such as Korean resident registration numbers is not required for signup. Writing and encryption on users’ own devices are distinct from storage of ciphertext on the server.

13. Additional information for global users

Global availability does not mean identical legal requirements apply in every country. Additional rights and protections may apply depending on residence, location of use, and service delivery. This Policy does not limit those rights.

• EEA, UK, and Switzerland: Applicable laws provide rights of access, correction, erasure, restriction, portability, objection, and complaints to supervisory authorities. The basis appropriate to the actual processing is used: contract performance, legitimate interests in lawful security purposes, legal obligations, or separate consent. Where GDPR applies, rights requests are generally handled within 1 month; legally permitted extensions will be explained with reasons and duration within the initial deadline. Required regional representatives, supervisory authorities, and transfer safeguards will be disclosed after applicability is assessed.
• US states: Where relevant state laws and business applicability thresholds are met, rights may include access and copies, correction, deletion, portability, opting out of sale, targeted advertising and certain profiling, and appeals. The Operator does not currently sell personal information or share it for targeted advertising. Applicable opt-out signal and appeal duties are assessed alongside actual settings.
• Other regions: Requests under applicable privacy law are accepted through the same contact address. Additional local notices, consent, representatives, or localization requirements are assessed with the scope of service provision.

This Policy is available in Korean and English. The English version is a translation of the Korean original, which is authoritative, subject to mandatory applicable law. Contact us if you need help understanding the Policy or exercising your rights. Translations identify the applicable period and changes together with the policy information.

14. Responsible person, contact, and remedies

• Personal information controller: Choi Seung-woo (최승우), individual operator
• Person responsible for personal information protection: Choi Seung-woo (최승우)
• Privacy inquiries, access requests, and complaints: miroven@mksdr.bid

Send privacy inquiries, rights requests, and transfer safeguard inquiries to the email above. In Korea, contact the Personal Information Infringement Report Center for privacy infringement consultation or the Personal Information Dispute Mediation Committee for mediation. Users abroad may also complain to their competent privacy supervisory authority. Contacting the Operator first is not a condition for approaching an authority.

15. Effective date and changes

This Policy takes effect on October 25, 2026. Changes will display an effective date and summary, and previous policies and their periods of application will remain available. Changes significantly affecting rights, including information categories, purposes, or international transfers, will be separately explained for easy comparison; consent will be obtained before application where necessary.

Related information: Terms of Service · Security · Help