Effective 22 September 2026

Privacy Policy

This policy explains how Wridian handles information when visitors read the site, contact the editorial desk, or request an accessibility adjustment. It applies to Wridian pages, forms, cookies, and ordinary correspondence connected with the address in Seoul, Republic of Korea. Wridian is an editorial information resource and does not ask readers to create investment profiles. We aim to collect the smallest amount of information needed for a clear and secure service.

1. Scope and controller

Wridian operates from 15, Gangnam-daero 98-gil, Gangnam-gu, Seoul, 06231, Republic of Korea. For privacy questions, contact +82 2-3486-7129 and identify the page or interaction involved. This policy covers information received directly and limited technical information generated when the site is requested. It does not govern third-party sites linked from our pages.

2. Information collected

When a visitor sends a contact form, we receive the name, email address, and message supplied by that visitor. Server logs may record an IP address, browser family, requested URL, response status, and timestamp for security and reliability. We do not intentionally collect recovery phrases, payment credentials, sensitive account keys, or precise location data. Please do not place such information in a message.

3. Purpose and legal basis

We use correspondence to answer questions, review corrections, and handle accessibility requests. We use security logs on the basis of legitimate operational interests in protecting the service and diagnosing failures. Optional analytics are used only after a visitor makes a cookie choice. Where consent is required, the cookie banner provides the relevant choice.

4. Retention

Routine contact messages are normally retained for 24 months after the last meaningful exchange. Records supporting an editorial correction may be kept for up to 5 years because they explain why a published page changed. Security logs are generally rotated after 90 days unless a documented incident requires preservation. Cookie choices remain for up to 12 months or until the browser data is cleared.

5. Cookies

The cookieChoice item records accept or reject so the banner does not repeatedly interrupt the same browser. It is a functional browser storage item rather than a profile of reading interests. If analytics are introduced, their name, provider, purpose, and lifespan will be listed in the cookies policy before activation. Visitors can clear storage through browser controls.

6. Processors and disclosure

Hosting, email delivery, security monitoring, and analytics providers may process limited information on Wridian’s instructions. They receive only the fields needed for their service and are expected to protect them contractually. Wridian does not sell contact details or exchange them for advertising lists. Disclosure may occur when required by lawful process or to protect people and the service.

7. International transfers

Some infrastructure providers may process technical data outside the Republic of Korea. Where this occurs, Wridian evaluates contractual safeguards, access controls, and the provider’s security commitments. A transfer does not give a provider permission to reuse editorial correspondence for its own marketing. Questions about a provider can be raised through the contact channel.

8. Your rights

Subject to applicable law, a person may request access to personal information, correction of inaccurate information, deletion, restriction, or an explanation of processing. A request should include enough detail to locate the relevant message without sending unnecessary identity documents. We may ask for proportionate verification to avoid disclosing information to the wrong person. We respond within a reasonable period and explain any lawful limitation.

9. Children and safety

Wridian is not directed at collecting information from children. We do not knowingly request sensitive credentials from any age group. If a parent or guardian believes a child sent personal information, contact the desk so the message can be reviewed and removed where appropriate. Readers should never disclose private keys or recovery phrases to Wridian.

10. Complaints

Start by contacting Wridian at the address or phone number listed above with the subject “Privacy request.” Include the date, page, and outcome you are seeking. We will review the matter, preserve relevant records, and reply with the result or a reason for limitation. A person may also contact an appropriate Korean privacy authority where local law provides that route.

11. Security

Access to contact information is limited to people who need it for editorial or operational work. We use ordinary safeguards such as account controls, software updates, transport encryption, and retention limits. No internet transmission is risk-free, so the policy does not promise absolute security. If a material incident affects personal information, Wridian will assess notification duties and communicate as required.

12. Changes

Version 1.0 was published on 22 September 2026. We may revise this policy when services, providers, or legal requirements change, while keeping the effective date visible. A substantive revision will include a short change note on this page. The current version governs information handled after its effective date, subject to applicable law.

For practical administration, correspondence is categorized by subject, such as correction request, accessibility request, general question, or suspected security issue. We use that category only to route the message and do not build behavioral profiles from ordinary correspondence. A message may be shared with a small number of staff or service providers who need it to respond, subject to confidentiality duties. If a request contains information about another person, we may ask for evidence that the sender is authorized to provide it.

Our legal basis depends on the interaction. A request for information is handled because it is necessary to respond to the visitor's request, while security logging is based on a legitimate interest in maintaining availability and investigating abuse. Consent is used for optional analytics and can be withdrawn through the cookie controls. Withdrawal does not affect processing that occurred before the withdrawal, and it does not remove records that must be retained to resolve a documented complaint.

Contact messages are normally retained for 24 months after the last meaningful exchange, then deleted or anonymized. Security logs are normally retained for 90 days, except where a longer period is reasonably necessary to investigate an incident, preserve evidence, or comply with a lawful request. Accessibility reports may be retained for 36 months so recurring barriers can be tracked and corrected. Aggregated, non-identifying statistics may be retained longer because they no longer identify a visitor.

Wridian may use ordinary service providers for hosting, form delivery, email routing, security monitoring, analytics, and domain services. Providers receive only the information needed for their documented function and are expected to apply appropriate safeguards. Depending on the visitor's location and the provider's infrastructure, information may be processed in the Republic of Korea or another country with suitable contractual or legal safeguards. We do not sell personal information or use contact messages for unrelated advertising.

Visitors may request access, correction, deletion, restriction, or an explanation of processing by calling +82 2-3486-7129 or by using the contact page. Please include enough detail to identify the relevant interaction, but do not send passwords, private keys, or identity documents unless we specifically explain a secure method. We generally acknowledge a request within five business days and aim to provide a substantive response within 30 days, subject to lawful extensions for complex requests. A requester may also contact the Personal Information Protection Commission of Korea if they believe a concern has not been resolved.

We review this policy when our forms, hosting arrangements, cookie configuration, or legal obligations change. The current version is dated 22 September 2026; material revisions will be shown with a new effective date and a short description of the change. The prior version may be retained internally for accountability, but it will not be used to justify new processing after the revised policy takes effect.

For clarity, the policy applies whether a visitor reads one article, follows several internal links, submits a correction, or contacts the accessibility desk. It also covers technical records created when a browser requests a page, including records used to identify failed requests or unusual automated traffic. It does not create a user account system, and Wridian does not intentionally combine reading history with the identity supplied in a contact message. A visitor may browse the editorial material without providing a name or email address.

Information supplied voluntarily is handled according to the purpose for which it was sent. For example, an email address may be used to answer a question, but it is not added to a newsletter unless the visitor separately requests that service. A message may contain a URL, browser details, or a preferred format if those details help us investigate the issue. Visitors should redact private keys, passwords, payment details, government identifiers, and information about another person before sending a message.

Where applicable, processing is based on responding to a request, maintaining site security, complying with a legal obligation, or a consent choice for optional analytics. Legitimate-interest processing is limited to proportionate operational purposes, such as detecting repeated failed requests or preserving a record of a correction decision. Consent can be withdrawn using the available controls, but withdrawal does not invalidate processing that occurred before it. If the legal basis for a particular request is unclear, Wridian may ask for a short clarification before taking action.

Contact correspondence is normally retained for 24 months after the last meaningful exchange. Security logs are generally retained for 90 days, while an incident record may be retained for up to 24 months when necessary to investigate or demonstrate the response. Accessibility reports may be kept for 36 months to identify recurring barriers, and anonymized aggregate measurements may be retained without a fixed deletion date because they no longer identify an individual. A lawful hold, complaint, or request from an authority may require a longer period.

Wridian may rely on hosting, form delivery, email routing, domain, security, and analytics providers, including infrastructure providers that process data in the Republic of Korea or another jurisdiction. A provider receives only the information needed for its documented service and is expected to protect it through access controls, confidentiality terms, and appropriate technical measures. International transfers are assessed under the applicable Korean privacy framework and the provider's contractual safeguards. Wridian does not sell personal information or use private correspondence to build advertising audiences.

Visitors may request access, correction, deletion, restriction, or information about processing by writing through the contact page or calling +82 2-3486-7129. We normally acknowledge a request within five business days and aim to provide a substantive response within 30 days, although complex requests may require a lawful extension. We may ask for proportionate information to verify that a request concerns the requester, and we do not require a visitor to send a password or private key. A concern may also be raised with the Personal Information Protection Commission of Korea.

The policy was reviewed on 22 September 2026. A material change to forms, analytics, hosting, retention, or visitor rights will receive a new effective date and a brief change description. Earlier versions may be retained internally for accountability but are not used as the basis for new processing after a revised version takes effect.