Bryskalon Bryskalon

Bryskalon · bryskalon.digital

Last updated: 17 November 2026

Legal · Privacy

Privacy Policy for Bryskalon

This Privacy Policy describes how Bryskalon (bryskalon.digital), an educational resource operating for readers in South Korea, handles personal data submitted through this website. It covers what is collected, why, retention, rights, and how to contact us.

What this policy covers

Six sections · read top to bottom

  1. 01
    Operator and scope

    Who runs this site, which pages the policy applies to, and what it does not cover.

  2. 02
    Data we collect

    Contact form fields, basic technical log data, and what this site deliberately does not collect.

  3. 03
    Purpose and basis for use

    Why we read a message, why we hold a log line, and what we refuse to do with either.

  4. 04
    Retention

    How long a message lives, and how log entries leave the server.

  5. 05
    Your rights

    Access, correction, deletion, and the exact way to make a request.

  6. 06
    Contact for privacy matters

    Where to write, what to include, and where cookies are covered in more detail.

Section 01

Operator and scope

The operator of this site is Bryskalon, reachable through the Contact page. Bryskalon runs an educational cloud accounting resource: comparison guides, workflow explanations and reading for founders and small teams who need to understand Korean bookkeeping, VAT and e-tax filing without a finance department. Its publishing office is at 26 Eulji-ro 5-gil, Jung-gu, Seoul 04522, South Korea, and it can be reached by phone on +82 2-6473-3408 during Monday to Friday, 9:00 AM – 6:00 PM.

This Privacy Policy applies to pages under bryskalon.digital, including the contact form and the confirmation page that follows a message. It does not cover third-party sites Bryskalon links to for further reading — platform vendor sites, national tax resources, or bank help centres. Once you follow a link off bryskalon.digital, that other operator's own privacy notice governs what happens next.

Section 02

Data we collect

The site collects data you provide directly. When you send us a message through the contact form, we receive your name, your email address, the subject line you choose, and the message content itself. Nothing else is asked. If you write about a specific guide — a comparison page you think is out of date, a workflow step that reads wrong, a term you want explained — the correction or question you type becomes part of the record we hold.

Beyond the form, the site receives basic technical data necessary to serve pages and keep them running: browser type and version, requested pages, referring URL where your browser sends one, and the approximate time of the request. That arrives in server logs. It is generated by the ordinary act of loading a page, not by anything you do specifically.

This site does not collect account passwords, because it has no accounts. It does not collect payment details, because nothing here is sold through a checkout. It does not ask for, and does not want, sensitive identifiers such as government registration numbers, bank account numbers, or authentication credentials. If you send any of those in a message, we will delete the affected portion when we answer you.

Section 03

Purpose and basis for use

Contact details are used to reply to inquiries, review corrections to existing guides, and improve the educational writing on the site. If you write in about a guide, we read the message, decide whether a correction is warranted, and reply to the address you gave us. The legal basis for that handling is the answer to your own request — you wrote to us, and we answer.

Technical log data is used for security and basic operation: telling a well-behaved visitor apart from a scraping bot, seeing which pages fail to load, and diagnosing slowdowns. That is its whole purpose. We do not sell personal data to third parties, we do not rent email lists, and we do not build advertising profiles out of form submissions or log lines. The site runs no behavioural ad targeting of its own.

Section 04

Retention

Contact messages are kept for up to 24 months from the day they arrive, then deleted or anonymized. A message may be kept a little longer only when a longer period is genuinely needed to resolve an ongoing request — a thread still being answered, a correction still being verified against a source. When that is the case, the extension lasts only as long as the open item.

Server logs are kept for a shorter operational period and are then overwritten as a matter of routine. Logs are not archived into a long-term store and are not matched against message records to build a visitor profile. If you ask for earlier deletion of personal data you have submitted, we will act within the timelines required by applicable law, and we will confirm to you when the deletion has been carried out.

Section 05

Your rights

You may request access to personal data you submitted to this site, ask us to correct anything inaccurate, and ask us to delete it. You may also ask how it is used, who sees it, and how long it is kept. There is no charge for making a request, and no need to give a reason.

To make a request, use the Contact page with the subject "Privacy Request". Include the email address you used when you first wrote, so we can find your message without asking you to prove an identity the site never checked. We will respond within a reasonable period under applicable law, and if we cannot act on some part of the request we will tell you why rather than leave it unanswered.

Section 06

Contact for privacy matters

For privacy questions or requests related to bryskalon.digital, use the Contact page and select a privacy-related subject. Include enough detail for us to locate your message — the address you wrote from, roughly when you sent it, and the subject line if you remember it. A short, specific message works better than a long one.

You can also write to [email protected], or send post to 26 Eulji-ro 5-gil, Jung-gu, Seoul 04522, South Korea. The Cookie Policy provides further detail on cookies and similar storage used by this site.

Questions

Answering the common asks

Short answers to the questions this page tends to bring up.

Do you store anything when I only read an article?

Only the ordinary server log entry described above — requested page, browser type, approximate time. No account is created, no cookie is set for advertising, and no message is held. If you never send the form, there is nothing personal of yours on this site to delete.

Can I ask about a specific guide I read?

Yes, and corrections are welcome. Mention the page and the point in question in the message. If you want a copy of what you sent us — or want it deleted once a correction has been made — say so in the message and we will handle the request alongside the answer.

Does this page apply to the vendor sites you link?

No. A cloud accounting platform, a tax office page or a bank help centre has its own privacy notice. Once you leave bryskalon.digital, read the operator's own notice — they decide what they collect and why. We link to sources for reading, not as partners in the collection.

How do I check what cookies the site uses?

The Cookie Policy describes every cookie or similar storage this site sets, what it does, and how long it lasts. If a cookie you find is not on that list, tell us through the Contact page and we will investigate.

Related pages

The rest of the legal set on bryskalon.digital

  • Cookie Policy

    What is stored in your browser, why, and for how long.

  • Terms of Service

    The rules for using the guides, comparison pages and corrections process.

  • Contact

    Send a question, a correction, or a privacy request.

In one line

Read the guides, send us a message if it helps, and ask us to delete it when it does not.

Bryskalon · bryskalon.digital · 26 Eulji-ro 5-gil, Jung-gu, Seoul 04522, South Korea

[email protected] · +82 2-6473-3408 · Mon–Fri 9:00–18:00