Privacy policy

Builderlog (“this site”) publishes honest build logs at builderlog.net. This page explains what data is collected when you visit and how it is used. We kept it short and plain on purpose.

What we collect

• Analytics — We use Google Analytics 4 to understand overall traffic (page views, rough location, device type). It is aggregated anonymously and does not identify you.
• Ad measurement — We may use the Meta (Facebook, Instagram) pixel to measure ads. The pixel sends Meta the pages you visit and clicks on purchase links. It does not send directly identifying details such as your name or email. If you do not want these cookies, block them in your browser or turn off personalized ads in Meta's ad settings.
• View counts — Each post has a simple counter stored in Cloudflare KV. It records only a number, not who you are.
• Server logs — Our host (Cloudflare) keeps standard access logs (IP, browser details) for security and abuse prevention.
• What you send us — If you use email or the optional work-fit form, we receive the name or team label, reply address and work description you enter. Form contents go to a private operator notification channel.

There is no account sign-up or newsletter gate. Please do not send passwords, access tokens, customer records or identifiable work data.

How we use what you send

Contact details and work descriptions you choose to send are used only to understand your request and reply. We do not publish them or count them as sales. Please anonymize work descriptions and send only the contact details we need to reply.

Referral promotion

If you use the referral promotion, we process the referral code, the order number of the referred person’s payment, hashed values of their email and phone number (not the originals), the payment time, the referral reward status (pending, paid, cancelled), and the number and time of ebook downloads. This is for paying referral rewards, preventing self-referral and duplicate rewards, cancelling rewards on refunds, and handling disputes. The referred person’s email and phone number are not shown to the referrer, who sees only the number of referrals (pending, paid). We keep referral records for 5 years from the date of the payment, cancellation or block decision (the period for payment and supply records under Korean e-commerce law), and keep only hashes of emails and phone numbers. If a member leaves, the referral code is deleted and the referral records are kept as hashes only for that period. We do not provide them to third parties or outsource their processing, and ebook files are served from our own cloud storage.

Prompt request form

The request form on the home page collects your reply email and your request. It is sent only if you agree, and used only to review and answer prompt requests. We do not add you to ad mail or newsletter lists.

Requests are sent through Cloudflare servers and the Brevo email service to the operator's private inbox. We do not post or store your request or email on public pages or in the site database. We keep the received email only as long as needed to handle the request. To have it deleted, tell us by replying or through the contact page.

To prevent spam, we temporarily store a keyed hash of your IP address (not the address itself) and the number of requests per hour. If you do not agree to email collection, you cannot send the form, but you can still browse the free prompts.

Payments and My purchases (Kakao login)

Package payments are made in the Toss Payments checkout. Toss Payments handles card numbers and other payment details; Builderlog does not receive them. Builderlog stores the order number, product, amount, payment status and Toss Payments payment key to process orders, confirm downloads and handle refunds.

Kakao login is optional. If you log in, we receive only your Kakao member number to link your purchases; we do not receive your name, email, phone number or profile. We use a secure cookie (bl_session) valid for 30 days to keep you logged in, and we do not store Kakao access tokens.

When you link a package bought on Gumroad to My purchases, we verify you with your purchase email and order number. When Gumroad sales ended (2026-10-03), we kept a copy of the Gumroad sales records so earlier buyers can keep getting their files. We do not store the email itself, only an irreversible fingerprint (hash) plus the order number, product and refund status. Separately, to manage buyers on my.builderlog.net, we keep encrypted copies of ctee and Gumroad purchase records from the sellers' dashboards (email, name (ctee), product, amount, date) (details at my.builderlog.net/privacy). Linked sale IDs and product names are stored with your Kakao account.

Order and payment records are kept for 5 years under Korea's Act on Consumer Protection in Electronic Commerce. To delete your account, contact us and we will delete your Kakao member number and purchase links (except records we must keep by law). Processors: Toss Payments (payments), Kakao (login), Cloudflare (servers and data storage).

Builderlog member service and Latpeed purchases (my.builderlog.net)

If you buy a Builderlog product on Latpeed (Team Mavericks Inc.), Latpeed sends Builderlog your name, email, phone number, purchase survey answers and marketing consent to confirm the purchase. Builderlog uses them to confirm purchases, announce updates and provide support, and sends marketing news only to those who agreed (you can withdraw anytime with the unsubscribe link in the email).

Email, name and phone number are stored encrypted, and lookups use an irreversible fingerprint. The originals are destroyed 3 year after your last purchase or login, and payment records are kept for 5 years under Korea's e-commerce law. Processors: Cloudflare (servers and data storage, outside Korea), Brevo (email delivery, outside Korea). You log in with a 6-digit email code (or Kakao account email consent), and login details for a computer where you installed the tools stay only in a locked file on that computer.

Full privacy policy and terms for the member service: my.builderlog.net/privacy · Terms of Service

Privacy officer

Name: So Byung-wook · Title: CEO · Contact: [email protected]. Send requests to view, correct, delete, suspend processing or withdraw consent to this contact. For rights-violation counseling: the Personal Information Infringement Report Center (118, no area code) and the Personal Information Dispute Mediation Committee (1833-6972).

Cookies and ads

Builderlog shows ads through Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your visits to this and other sites.

• You can turn off personalized ads in Google Ads Settings.
• See how Google uses data at policies.google.com/technologies/partner-sites.
• You can see and opt out of third-party ad networks at aboutads.info.

Affiliate links

Some posts may include affiliate links (for example, Coupang Partners). If you buy through them, this site may earn a small commission at no extra cost to you. Affiliate links do not change our honest reviews of tools.

Your choices

You can block cookies in your browser settings and use the opt-out links above. We do not collect personal accounts on this site, so there is no profile to delete.

Contact

Send questions about this policy to [email protected] or through the contact page.