Privacy
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Kolwen has not launched. This page describes what kolwen.com does today, and says plainly which parts change on the day the assistant itself ships.
What this site is
Static pages, served by a Cloudflare Worker. The Worker runs one small script of ours (worker/index.mjs). It hands every request for a path with no static file to the pages, so a missing page gets the 404 page, except that it answers /status.json and /subscribe itself, and every 15 minutes it requests six of our own pages to check that they answer. It does not log, keep or store a visitor's request, and there is no database and no storage of visitor data on our side. The status record, once its store is bound (it is not yet), holds only the time, each page check's result, and which result the owner was last told of. A subscriber store is built and switched off: while it is switched off, no address can be stored, and no mail goes to a subscriber in this build. Once an alert address is set, the Worker tries to mail the owner when the result of its checks changes: from all passing to a failure, with each failed check's path, HTTP status or error (a timeout or a network error), timing and content-type result, the number of failed checks and the UTC time; and from failing back to all passing, with a recovery note. Once the status record is bound and can be read, a failure that goes on is not mailed again once the owner has been told, and a send that fails is tried again by the next run that still finds the failure (until then, and whenever the record cannot be read, every failing check run is mailed), and no visitor data is in either mail (a send that fails is logged by its error class only). Until an address is set, nothing is sent.
Measured: grep -nE '^[[:space:]]*"main"' wrangler.jsonc returns one line, "main": "worker/index.mjs",; the config declares a name, a compatibility date, the assets block, a cron trigger (*/15 * * * *), the observability block with invocation logs off, the send_email binding, one variable (ALERT_FROM) and an empty previews block. The alert recipient is a secret set outside the file, so the file holds no recipient address; its one address is the sender, the published info@kolwen.com in ALERT_FROM.
Cookies
[pending legal review] This part is waiting for legal review and is not shown yet.
Measured: curl -sI https://kolwen.com/ and the same on an asset—no Set-Cookie header on either (re-measured 2026-10-08, after the zone's JavaScript Detections were switched off).
A note on what could change that: per Cloudflare's own cookie and clearance pages (read 2026-10-08), Bot Fight Mode sets the __cf_bm cookie, and Turnstile sets cf_clearance only when its pre-clearance option is enabled. If either is ever switched on for this site, the sentence above, "no cookies at all", would be reworded the same day. Both are off today.
Your language choice (English or Thai) is stored in your browser's localStorage, which is not a cookie, is never sent to a server, and never leaves your device. Clearing your browser data removes it.
Measured: web/index.html uses localStorage.setItem / getItem for one key, and nothing else.
When the assistant ships, this changes, and here is exactly how
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Worker logs. Today the Worker logs the result of each of its own page checks (the path, status, timing and error class) and, when the result of the checks changes, one line saying whether an alert was sent, not sent because no alert address is set, or failed (with the error's class only); never a visitor's request (see "What this site is"). Invocation logs are switched off in wrangler.jsonc. When the Worker first answers visitors' requests with code of ours (an API, a payment-provider webhook or a chat endpoint) with invocation logs switched on, Cloudflare Workers Logs will record each such request. Switching it on is Cloudflare's setting, and the page says "All newly created Workers will come with the observability setting enabled by default". Cloudflare's documentation (https://developers.cloudflare.com/workers/observability/logs/workers-logs/, page last updated Oct 12, 2026, read 2026-10-17) says an invocation log contains details such as the request, the response and related metadata, that a fetch request's message shows the request method and the request URL, and that anything the Worker prints with console.log is stored too. The same page gives a retention of 3 days on the Workers plan without a monthly charge and 7 days on the paid Workers plan, in its table "until then" (until 30 November 2026), and says "Beginning December 1, 2026, Workers Logs will use Cloudflare Observability pricing". For the period after that date it names no retention for either plan; its limits table gives only a "Maximum log retention period" of 7 days.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Who else sees your request
Cloudflare serves this site, so it necessarily handles your request: your IP address, the URL you asked for, and your browser's user-agent reach their edge before any bytes reach you. That is how any hosted site works, and it is not something we can turn off while remaining online. Cloudflare no longer injects its bot-detection script into the served HTML: the zone's JavaScript Detections setting was switched off on 2026-10-07, and Bot Fight Mode is off.
Measured 2026-10-08: curl -s https://kolwen.com/ | grep -c challenge-platform prints 0.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Age
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Contact
privacy@kolwen.com reaches the maintainer. Anything you send there is read by a person.
[pending legal review] This part is waiting for legal review and is not shown yet.
What we do not do
- [pending legal review] This part is waiting for legal review and is not shown yet.
- No account, no sign-up, and nothing to log in to.
- Kolwen's own systems—the site and its Worker—collect and store nothing about a visitor, so there is nothing there to sell or share. Two parties outside those systems do handle data, as this notice already says: Cloudflare handles every request; and the mailbox behind the contact address holds what you send to it. What each retains cannot be measured from this repository.
When the assistant ships
[pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
- [pending legal review] This part is waiting for legal review and is not shown yet.
[pending legal review] This part is waiting for legal review and is not shown yet.
Changes
This notice is versioned with the site in git; its history is the change log. There is no separate "last updated" line to fall out of date.
[pending legal review] Full Thai versions of the Terms, the Refunds and the Privacy pages, equal in substance to the English, are still to come.
This page: your language choice is stored locally in your browser
ความเป็นส่วนตัว
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Kolwen has not launched. This page describes what kolwen.com does today, and says plainly which parts change on the day the assistant itself ships.
What this site is
Static pages, served by a Cloudflare Worker. The Worker runs one small script of ours (worker/index.mjs). It hands every request for a path with no static file to the pages, so a missing page gets the 404 page, except that it answers /status.json and /subscribe itself, and every 15 minutes it requests six of our own pages to check that they answer. It does not log, keep or store a visitor's request, and there is no database and no storage of visitor data on our side. The status record, once its store is bound (it is not yet), holds only the time, each page check's result, and which result the owner was last told of. A subscriber store is built and switched off: while it is switched off, no address can be stored, and no mail goes to a subscriber in this build. Once an alert address is set, the Worker tries to mail the owner when the result of its checks changes: from all passing to a failure, with each failed check's path, HTTP status or error (a timeout or a network error), timing and content-type result, the number of failed checks and the UTC time; and from failing back to all passing, with a recovery note. Once the status record is bound and can be read, a failure that goes on is not mailed again once the owner has been told, and a send that fails is tried again by the next run that still finds the failure (until then, and whenever the record cannot be read, every failing check run is mailed), and no visitor data is in either mail (a send that fails is logged by its error class only). Until an address is set, nothing is sent.
Measured: grep -nE '^[[:space:]]*"main"' wrangler.jsonc returns one line, "main": "worker/index.mjs",; the config declares a name, a compatibility date, the assets block, a cron trigger (*/15 * * * *), the observability block with invocation logs off, the send_email binding, one variable (ALERT_FROM) and an empty previews block. The alert recipient is a secret set outside the file, so the file holds no recipient address; its one address is the sender, the published info@kolwen.com in ALERT_FROM.
Cookies
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Measured: curl -sI https://kolwen.com/ and the same on an asset—no Set-Cookie header on either (re-measured 2026-10-08, after the zone's JavaScript Detections were switched off).
A note on what could change that: per Cloudflare's own cookie and clearance pages (read 2026-10-08), Bot Fight Mode sets the __cf_bm cookie, and Turnstile sets cf_clearance only when its pre-clearance option is enabled. If either is ever switched on for this site, the sentence above, "no cookies at all", would be reworded the same day. Both are off today.
Your language choice (English or Thai) is stored in your browser's localStorage, which is not a cookie, is never sent to a server, and never leaves your device. Clearing your browser data removes it.
Measured: web/index.html uses localStorage.setItem / getItem for one key, and nothing else.
When the assistant ships, this changes, and here is exactly how
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Worker logs. Today the Worker logs the result of each of its own page checks (the path, status, timing and error class) and, when the result of the checks changes, one line saying whether an alert was sent, not sent because no alert address is set, or failed (with the error's class only); never a visitor's request (see "What this site is"). Invocation logs are switched off in wrangler.jsonc. When the Worker first answers visitors' requests with code of ours (an API, a payment-provider webhook or a chat endpoint) with invocation logs switched on, Cloudflare Workers Logs will record each such request. Switching it on is Cloudflare's setting, and the page says "All newly created Workers will come with the observability setting enabled by default". Cloudflare's documentation (https://developers.cloudflare.com/workers/observability/logs/workers-logs/, page last updated Oct 12, 2026, read 2026-10-17) says an invocation log contains details such as the request, the response and related metadata, that a fetch request's message shows the request method and the request URL, and that anything the Worker prints with console.log is stored too. The same page gives a retention of 3 days on the Workers plan without a monthly charge and 7 days on the paid Workers plan, in its table "until then" (until 30 November 2026), and says "Beginning December 1, 2026, Workers Logs will use Cloudflare Observability pricing". For the period after that date it names no retention for either plan; its limits table gives only a "Maximum log retention period" of 7 days.
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Who else sees your request
Cloudflare serves this site, so it necessarily handles your request: your IP address, the URL you asked for, and your browser's user-agent reach their edge before any bytes reach you. That is how any hosted site works, and it is not something we can turn off while remaining online. Cloudflare no longer injects its bot-detection script into the served HTML: the zone's JavaScript Detections setting was switched off on 2026-10-07, and Bot Fight Mode is off.
Measured 2026-10-08: curl -s https://kolwen.com/ | grep -c challenge-platform prints 0.
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Age
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Contact
privacy@kolwen.com reaches the maintainer. Anything you send there is read by a person.
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
What we do not do
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- No account, no sign-up, and nothing to log in to.
- Kolwen's own systems—the site and its Worker—collect and store nothing about a visitor, so there is nothing there to sell or share. Two parties outside those systems do handle data, as this notice already says: Cloudflare handles every request; and the mailbox behind the contact address holds what you send to it. What each retains cannot be measured from this repository.
When the assistant ships
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
- [รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
[รอที่ปรึกษากฎหมาย] ส่วนนี้รอที่ปรึกษากฎหมายตรวจสอบ จึงยังไม่แสดง
Changes
This notice is versioned with the site in git; its history is the change log. There is no separate "last updated" line to fall out of date.
[รอที่ปรึกษากฎหมาย] ฉบับภาษาไทยเต็มของข้อกำหนด การคืนเงิน และความเป็นส่วนตัว ที่เนื้อหาเท่ากับฉบับภาษาอังกฤษ ยังจะตามมา
หน้านี้: ภาษาที่เลือกถูกเก็บไว้ในเบราว์เซอร์ของคุณ