set.net 隱私權政策
生效日: 2026 年 11 月 16 日
版本: 1.0
中文與英文文本均為作準文本。若有衝突,以繁體中文(zh-TW)文本為準。
1. 蒐集者身分(個資法第 8 條)
本隱私權政策說明,在 set.net 以及相關收件網域(包括 qrm8.com)所提供的只收不發信箱服務(下稱「本服務」)中,我們如何蒐集、處理與利用個人資料。
蒐集並處理個人資料的非公務機關/控管者為:
本政策中的「我們」、「set.net」,即指上述以個人名義經營的營運方。本告知旨在符合臺灣《個人資料保護法》(下稱「個資法」)第 8 條;對於台灣以外、可能適用 GDPR 或類似法律的使用者,另於第 11 條提供說明。
服務本身的規則見《服務條款》與《使用者協議》。本政策不能取代那些文件。
2. 適用範圍
本政策適用於你瀏覽網站、註冊或使用信箱、購買短名稱、與我們聯絡、啟用通知,或以其他方式使用本服務時,我們所處理的個人資料。也適用於他人寄到本服務信箱、而其內容本身可能含有個人資料的郵件。
3. 公開地址——誰可以寄信,誰可以讀信
這一點很重要:並不是任何人只要知道地址,就可以讀取收件匣。
3.1 set.net 或 qrm8.com 地址就「收信」而言是公開的。任何人只要知道或猜到該地址,就可以寄信過去。
3.2 網頁收件匣並不公開。以一般方式讀取已保存的信件,必須使用該信箱的密碼或一次性登入碼(OTP)登入。已登入的近用,是透過工作階段 Cookie 進行。
3.3 部分已啟用的信箱,仍可使用舊版的機密收件匣網址(/inbox/ 加上一組秘密權杖),不必再輸入密碼。任何人取得該網址,即可在信件過期前讀取該信箱已保存的郵件。僅知道電子郵件地址並不夠。這類權杖路徑視為敏感資訊;因此網站伺服器對 /inbox/ 網址關閉了存取紀錄。請勿分享舊版收件匣網址。
3.4 若你啟用 LINE、Telegram 或瀏覽器 Web Push,信件內容(通常包括寄件人、主旨與正文,其中可能含有驗證碼)可能被送到那些裝置或帳號。能看到那些管道的人,就可能看到該內容。
3.5 寄到「尚未啟用的信箱」(亦非我們的系統信箱)的郵件,系統會默默丟棄、不予保存。
4. 蒐集目的(個資法第 8 條)
我們基於下列目的蒐集與利用個人資料:
- 提供並營運只收不發信箱服務,包括建立與維護你的信箱。
- 驗證聯絡電子郵件、辦理登入(密碼或登入碼)、復原近用,以及維護帳戶安全。
- 透過 ez.wiki 與 Stripe,處理短名稱購買、優惠碼、付款確認、退款及相關爭議。
- 經由郵件服務商,向你的聯絡電子郵件寄送交易信件(例如確認與重設密碼連結)。
- 在你綁定 LINE、Telegram 或 Web Push 時,發送選用的新信或登入通知。
- 防止濫用、詐欺、冒用與過載(包括頻率限制、工作量證明、鎖定與稽核紀錄)。
- 營運 abuse@set.net、postmaster 等系統信箱,並處理你的請求或依法配合的程序。
- 遵守法律、執行《服務條款》與《使用者協議》,以及確立、行使或防禦法律上的請求。
我們目前不會把個人資料用於行銷。若日後有變更,我們會更新本政策,並取得法律所要求的同意。
就個資法的特定目的而言,上述目的相當於履行契約或類似契約關係、顧客管理與服務、電子商務與金流、資通安全管理、申訴或爭議處理,以及法令遵循等通常目的。
5. 個人資料類別(個資法第 8 條)
依你使用本服務的方式,我們可能處理:
- 帳戶與註冊資料: 自選信箱名稱與網域;聯絡電子郵件(經正規化,例如去除空白並改為小寫);密碼的雜湊值(不是明文密碼);註冊時選填的 Telegram 使用者名稱;註冊 IP;時間戳記(建立、啟用、最近登入);信箱狀態;以及你在已登入狀態下購買名稱時,信箱之間的關聯。
- 登入與安全資料: 工作階段識別(以雜湊保存);CSRF 權杖;登入碼(以雜湊保存,且很快過期);失敗次數與鎖定資料;工作量證明紀錄;以及與這些事件相關的 IP。
- 信件內容: 信封與信件標頭中的寄件人、主旨、純文字與 HTML 正文、大小,以及原始郵件資料(可能包括依原樣收到的標頭與附件),保存至第 6 條的期間為止。其中可能含有驗證碼,以及寄件人寫在信裡的任何個人資料。
- 通知資料: 若你綁定,則包括 LINE 使用者識別與綁定時間;Telegram 對話識別與使用者名稱;Web Push 訂閱端點與金鑰;以及最近推播時間。完成綁定所用的連結碼為短期資料。
- 購買與付款中繼資料: 訂單識別、所選名稱與網域、標價與實收金額、幣別(美元)、語文、優惠碼、付款狀態、保留到期時間,以及 ez.wiki 回傳的識別碼(例如該側的付款或使用者編號)。set.net 不會接收或保存你的完整卡號。 卡片與帳單資料由 ez.wiki 與 Stripe 處理。
- 服務信件紀錄: 記錄我們曾寄出確認、重設等信件,包括信箱、種類、時間、IP 與成敗——不是那封外寄信的完整正文。
- 語文與結帳的 Cookie/本機儲存, 見第 8 條。
- 伺服器與營運紀錄: IP、時間、請求路徑,以及網站、系統或郵件紀錄中的類似技術資料;但部分帶有權杖的網址路徑已關閉存取紀錄。
- 稽核紀錄: 由營運或系統寫入的安全與帳戶事件(行為者、動作、對象、IP、時間)。
- 你寄到 RoyFang@M-Commerce.com、Roy@Set.Net、abuse@set.net 或其他已公布聯絡方式的來信。
我們不會故意蒐集特種個人資料(例如健康或政治意見)。此類資料可能出現在他人寄入信箱的郵件中;僅在信件保存期間,以及你已啟用的通知範圍內保存。
6. 利用期間、地區、對象與方式(個資法第 8 條)
6.1 期間(目前已實作的保存)
以下為本服務目前的行為。標示「未發現自動清除」者,會保存到我們另行刪除,或法律另有要求為止。
| 資料 | 目前保存期間 |
| 已啟用使用者信箱中的信件 | 收到後 24 小時起無法再讀取,隨後由每小時執行的清除作業永久刪除。此外,每個信箱最多 200 封;超過上限時會刪除較舊信件。 |
| 我們營運的系統信箱(例如 postmaster、abuse)中的信件 | 7 天 |
| 尚未確認的免費註冊(以及該筆待確認資料相關的工作階段、權杖與訂閱) | 48 小時後刪除;名稱重新可供註冊 |
登入工作階段(__Host-u) | 12 小時;若選擇「記住我」,則為 30 天 |
預先工作階段 Cookie(__Host-upre) | 2 小時 |
| 語文 Cookie/本機儲存 | 最長 1 年(或直到你清除) |
結帳 Cookie(__Host-buyord、__Host-buyret)與名稱保留 | 15 分鐘 |
| 重設密碼連結 | 1 小時,一次性 |
| 確認連結(免費註冊) | 48 小時 |
| 管理員核發的設定密碼連結 | 24 小時,一次性;到期後再留 7 天即刪除殘留紀錄 |
| 登入碼及相關寄送/失敗紀錄 | 登入碼本身為短期(目前 5 分鐘);殘留的登入碼與寄送/失敗列約 24 小時後清除 |
| 註冊 IP 頻率紀錄、登入失敗 IP 紀錄、LINE/Telegram 綁定失敗紀錄 | 24 小時 |
我們寄出確認或重設信的紀錄(mail_sends) | 30 天 |
| 工作量證明已使用權杖 | 至挑戰到期為止(目前約 10 分鐘) |
| 已啟用信箱的 LINE/Telegram/Web Push 綁定 | 直到你解除綁定,或信箱被刪除(僅待確認註冊)或停用後另行清除 |
| 已啟用或已停用的信箱紀錄(包括聯絡電子郵件、密碼雜湊、註冊 IP 與已綁定的聊天識別) | 未發現自動清除。 依目前營運,已啟用或已停用的名稱不會回收,因此除非你成功請求刪除或我們另行清除,這些紀錄可能無限期保存。見第 9 條。 |
| 購買/訂單紀錄 | 未發現自動清除(可能為會計、退款與爭議而無限期保存) |
| 應用程式稽核紀錄 | 未發現自動清除(可能無限期保存) |
| Nginx 網站紀錄 | 每日輪替,保留 14 天。/inbox/、/confirm/、/reset/、/set-password/ 及其他部分帶權杖路徑的存取紀錄為關閉。 |
| 系統/郵件/認證紀錄(rsyslog) | 每週輪替,保留 4 代(約 四週) |
| systemd 日誌 | 未設定明確的時間上限;日誌也會轉送到 syslog |
6.2 利用地區
個人資料在臺灣(營運方為中華民國(台灣)公民,並在此管理本服務)以及新加坡使用——本服務目前託管於 DigitalOcean 的 sgp1 機房。資料也可能在第 7 條所述處理者所在的其他國家處理,可能包括美國、歐盟或英國、日本,以及那些服務商使用的其他地點。
6.3 利用對象
利用對象包括營運方、第 7 條的處理者與平台、法律要求或允許時的專業顧問或主管機關,以及你授權的人(例如因你分享密碼、舊版收件匣網址,或已綁定的 LINE/Telegram/推播裝置)。寄信到公開地址的寄件人,並不因此取得讀取收件匣的權利。
6.4 利用方式
我們以電子方式在託管伺服器上蒐集、儲存與處理個人資料;以交易電子郵件寄送通知;在結帳時把你導向 ez.wiki/Stripe;在你選用時發送推播或即時通訊通知;並在支援、濫用處理、退款或法律事務需要時進行人工檢視。
7. 處理者與其他利用對象
我們使用下列類型的處理者或平台(你使用其服務時,亦適用其隱私權政策):
- DigitalOcean — set.net 的主機與基礎建設,目前位於 sgp1(新加坡)。
- ez.wiki,由 ez.wiki 經營 — 負責託管結帳、優惠碼驗證與每一客戶使用次數上限,並把付款狀態通知我們。我們會傳送含有結帳所需訂單與聯絡資料的交接權杖;我們只收回付款中繼資料,不會收到完整卡號。
- Stripe — 在託管 Checkout 頁處理卡片等付款。
- LINE(LY Corporation 及其集團)— 若你綁定官方帳號以接收通知或登入碼。
- Telegram(目前為機器人 @b2b2cbot)— 若你綁定 Telegram 以接收通知或登入碼。
- 瀏覽器或裝置的推播服務 — 若你啟用 Web Push,則為你瀏覽器廠商的推播服務(依瀏覽器與裝置而異,例如 Google、Mozilla、Apple 或其他業者所營運的服務)。
- Brevo(交易郵件;SMTP 主機為
smtp-relay.brevo.com)— 把確認、重設密碼等信件寄到你的聯絡電子郵件,寄件者顯示為 set.net <no-reply@set.net>。這些信不是從你的 set.net 或 qrm8.com 信箱寄出。
我們不會出售你的個人資料。
8. Cookie 與本機儲存
我們使用下列 Cookie 及類似儲存,目前不使用第三方廣告 Cookie。
| 名稱 | 類型 | 目的 | 目前有效期間 |
__Host-u | 必要、HTTP-only、Secure、SameSite=Lax | 已登入的工作階段 | 12 小時;若選擇「記住我」,則為 30 天 |
__Host-upre | 必要、HTTP-only、Secure、SameSite=Lax | 預先工作階段/註冊完整性 | 2 小時 |
u_lang | 偏好設定(頁面腳本可讀取;非 HttpOnly) | 介面語文(zh 或 en) | 1 年 |
__Host-buyord | 必要、HTTP-only、Secure、SameSite=Lax | 識別短名稱結帳訂單 | 15 分鐘 |
__Host-buyret | 必要、HTTP-only、Secure、SameSite=Lax | 結帳返回輔助 | 15 分鐘 |
瀏覽器 localStorage 中的 setnet-lang | 偏好設定,存在你的瀏覽器 | 在首頁記住語文 | 直到你清除網站資料 |
語文 Cookie 可能由伺服器(/lang/zh 或 /lang/en)或首頁腳本設定。ez.wiki 或 Stripe 的結帳頁可能依其政策另設 Cookie。
你可以在瀏覽器中封鎖 Cookie,但必要 Cookie 是登入、完成購買與保護工作階段安全所需。
9. 個資法第 3 條權利,以及如何行使
依個資法第 3 條,除該法所定例外外,你得:
- 向我們查詢或請求閱覽你的個人資料;
- 請求製給複製本;
- 請求補充或更正;
- 請求我們停止蒐集、處理或利用;以及
- 請求刪除。
行使上述權利,請從我們能合理對應到該信箱的聯絡電子郵件,寫信到 RoyFang@M-Commerce.com(主要聯絡,我們會從此信箱回覆)或 Roy@Set.Net(僅收信/Inbound Only),說明是哪一個信箱、以及要行使哪一項權利。我們可能需要先確認你的身分。我們會在法定期間內回覆,回信會由 RoyFang@M-Commerce.com 寄出。若你只寄到 Roy@Set.Net,請注意該地址是本服務上的只收不發信箱,該處的來信會依第 6 條的信件保存期間處理,除非另行複製保存。聯絡方式僅為電子郵件。
請注意以下實務限制,我們僅在法律允許的範圍內適用:
- 使用者收件匣中的信件在 24 小時後即會刪除(若達到 200 封上限,可能更早)。已清除的信件無法還原。
- 目前沒有自助「刪除帳戶」按鈕。若你要求刪除帳戶資料,我們可能停用該信箱(不再保存來信)。依目前營運,該名稱會繼續保留、不會釋放給他人。在我們有法律或安全上的需要時(包括避免該名稱被他人重新註冊),我們可能保留有限紀錄(例如訂單紀錄、稽核列,或僅保留名稱的占位資料)。
- 若有法定例外(例如履行契約、防禦法律請求,或刪除將妨害我們的法定義務所必要的資料),我們會說明理由。
上述權利不減少你在其他適用法律下不得拋棄的權利。
10. 不提供資料的後果(個資法第 8 條)
你沒有義務提供個人資料。若不提供聯絡電子郵件與密碼,我們無法完成免費註冊,也無法協助復原信箱。若未在付款處理方完成結帳,我們無法建立付費短名稱。若不啟用 LINE、Telegram 或 Web Push,你只是不會收到那些選用通知。若拒絕必要 Cookie,你可能無法登入或完成購買。你仍可在不建立帳戶的情形下,寄信到屬於他人的公開地址,但這不會讓你自己擁有收件匣。
11. 給境外使用者的 GDPR 式說明
若你位於歐洲經濟區、英國,或其他有類似規範的地區,請閱讀本條。那些法律是否適用,取決於具體事實(包括本服務是否向你行銷或提供)。本政策並不表示在所有情形下都當然適用某一外國法律。
11.1 控管者: Roy Fang,聯絡方式見第 1 條。並非公司,也未另行指定資料保護長,亦未指定歐盟或英國代表人。
11.2 在 GDPR(或類似法律)適用時,我們擬主張的合法基礎包括:
- 契約(第 6 條第 1 項 b 款):建立與營運你的信箱、登入與復原,以及完成你請求的購買。
- 正當利益(第 6 條第 1 項 f 款):維護本服務安全、防止濫用與詐欺、在停用後避免名稱被回收、保存訂單與安全事件紀錄,以及防禦法律請求——並與你的利益與權利平衡。
- 同意(第 6 條第 1 項 a 款):選用的 LINE、Telegram 或 Web Push 通知,你可以解除綁定。撤回同意不影響撤回前已進行的處理。
- 法律義務(第 6 條第 1 項 c 款):法律要求我們保存或提供資料時。
11.3 跨境傳輸。 本服務託管於新加坡,並由台灣管理。第 7 條的處理者可能在其他國家處理資料。個人資料在本服務託管地新加坡,以及各處理者所在的其他國家處理。就該等傳輸,我們依賴各處理者所提供的保護措施。
11.4 在 GDPR 或類似法律下可能另外享有的權利:近用、更正、刪除、限制處理、對於基於正當利益的處理提出異議、資料可攜、撤回同意,以及不受某些自動化決策拘束的權利。我們不會以單純自動化決策,對你作出產生法律效果或類似重大影響的決定(ez.wiki 上的優惠碼上限屬於付款規則,並非此類剖析)。
11.5 申訴。 請先與我們聯絡(第 15 條)。你也可以向所在地主管機關,以及下述臺灣個人資料保護委員會提出申訴。
12. 兒童
本服務並非以兒童為對象。你必須具有條款所述的契約能力。未成年人應經法定代理人同意,方可使用本服務。若你認為我們誤收了兒童的資料,請聯絡 RoyFang@M-Commerce.com(主要聯絡,我們會從此信箱回覆)或 Roy@Set.Net(僅收信/Inbound Only)。
13. 安全
我們採取與小型只收不發服務相稱的措施,包括 HTTPS、密碼雜湊、在使用 __Host- 前綴時採用 HttpOnly 且 Secure 的工作階段 Cookie、一次性權杖雜湊、頻率限制,以及對部分帶權杖路徑關閉存取紀錄。任何傳輸或儲存方式都不是絕對安全。你也必須自行保護密碼、登入碼、聯絡電子郵件、已綁定的聊天帳號,以及任何舊版收件匣網址。
14. 變更
我們可以更新本政策。我們會公布更新後的文本並修改生效日,也可能透過網站或你的聯絡電子郵件通知你。在可行時我們會提前 15 日通知,方式與《服務條款》所述相同。
15. 聯絡與申訴
你也可以向臺灣主管機關個人資料保護委員會,或對你的申訴有管轄權的其他監督機關提出申訴。
本服務的準據法為中華民國(台灣)法律,見《服務條款》。第一審管轄法院為臺灣臺北地方法院。
set.net Privacy Policy
Effective date: 16 November 2026
Version: 1.0
The Traditional Chinese and English versions are equally authentic. If they ever conflict, the Traditional Chinese (zh-TW) version prevails.
1. Who we are (identity of the collector)
This Privacy Policy describes how personal data is collected, processed, and used in connection with the receive-only mailbox service at set.net and related mailbox domains including qrm8.com (the “Service”).
The controller / non-government agency that collects and processes personal data is:
- Name: Roy Fang, a citizen of the Republic of China (Taiwan), acting as an individual / sole operator (not a company or other legal entity)
- Email (primary; we reply from this address): RoyFang@M-Commerce.com
- Email (Inbound Only): Roy@Set.Net
In this policy, “we,” “us,” “our,” and “set.net” mean that individual operator. This notice is intended to satisfy Article 8 of Taiwan’s Personal Data Protection Act (個人資料保護法, “PDPA”), and also to give GDPR-style information to users outside Taiwan where those laws may apply.
The Terms of Service and User Agreement describe the Service itself. This policy is not a substitute for those documents.
2. Scope
This policy covers personal data we process when you visit the site, register or use a mailbox, buy a short name, contact us, enable notifications, or otherwise use the Service. It also covers mail content that others send to a mailbox on the Service, which may itself contain personal data.
3. Public addresses — who can send, and who can read
This is an important point, and it is not the case that anyone who knows an address can read the inbox.
3.1 A set.net or qrm8.com address is public for receiving. Anyone who knows or guesses the address can send mail to it.
3.2 The web inbox is not public. To read stored mail by the ordinary method you must sign in with the mailbox password or a one-time sign-in code (OTP). Signed-in access uses a session cookie.
3.3 For some already-active mailboxes, a legacy secret inbox URL (/inbox/ plus a secret token) still works without a password. Anyone who obtains that URL can read that mailbox’s stored mail until the messages expire. Knowing the email address alone is not enough. Those token paths are treated as sensitive; the web server turns access logging off for /inbox/ URLs for that reason. You should not share a legacy inbox URL.
3.4 If you enable LINE, Telegram, or browser Web Push, message content (typically sender, subject, and body, which may include a verification code) may be delivered to those devices or accounts. Anyone who can see those channels may see that content.
3.5 Mail sent to a name that is not an active mailbox (and is not one of our system mailboxes) is silently discarded and is not stored.
4. Purposes of collection (PDPA Art. 8)
We collect and use personal data for the following purposes:
- Providing and operating the receive-only mailbox service, including creating and maintaining your mailbox.
- Verifying your contact email, authenticating sign-in (password or OTP), recovering access, and keeping the account secure.
- Processing paid short-name purchases, promo codes, payment confirmation, refunds, and related dispute handling, through ez.wiki and Stripe.
- Sending transactional messages to your contact email (for example confirmation and password-reset links), via our mail provider.
- Sending optional new-mail or sign-in notices if you link LINE, Telegram, or Web Push.
- Preventing abuse, fraud, impersonation, and overload (including rate limits, proof-of-work, lockouts, and audit records).
- Operating system mailboxes such as abuse@set.net and postmaster, and responding to your requests or legal process.
- Complying with law, enforcing the Terms of Service and User Agreement, and establishing, exercising, or defending legal claims.
We do not currently use personal data to send marketing. If that changes, we will update this policy and obtain any consent the law requires.
These purposes correspond, in PDPA terms, to customary specific purposes such as performing a contract or similar relationship, customer administration and service, electronic commerce and payment, information and communications security, handling complaints or disputes, and legal compliance.
5. Categories of personal data (PDPA Art. 8)
Depending on how you use the Service, we may process:
- Account and registration data: chosen mailbox name and domain; contact email (normalized, for example trimmed and lowercased); password hash (not the password in clear text); optional Telegram username at sign-up; sign-up IP address; timestamps (created, activated, last sign-in); mailbox status; and a link between mailboxes if you buy a name while signed in.
- Sign-in and security data: session identifiers (stored as hashes); CSRF tokens; OTP codes (stored as hashes, short-lived); failed-attempt and lockout data; proof-of-work challenge records; and IP addresses associated with these events.
- Mail content: envelope and header sender, subject, text and HTML bodies, size, and raw message data (which may include headers and attachments as received), for the retention window in Section 6. This may include verification codes and any personal data a sender puts in the message.
- Notification data: if you link them, LINE user identifiers and link time; Telegram chat identifiers and username; Web Push subscription endpoint and keys; and timestamps of last push. Link codes used to complete a binding are short-lived.
- Purchase and payment metadata: order identifiers, chosen name and domain, list price and amount charged, currency (USD), language, promo code, payment status, hold expiry, and identifiers returned by ez.wiki (for example a payment or user id on that side). We do not receive or store your full card number on set.net. Card and billing details are processed by ez.wiki and Stripe.
- Service-message logs: records that a confirmation, reset, or similar mail was sent, with mailbox reference, kind, time, IP, and success/failure — not the full email body of that outbound message.
- Language and checkout cookies / local storage, as in Section 8.
- Server and operations logs: IP addresses, timestamps, requested paths, and similar technical data in web, system, or mail logs, except that access logging is turned off for some token-bearing URL paths.
- Audit records: operator- or system-written records of security and account events (actor, action, target, IP, time).
- Correspondence you send to RoyFang@M-Commerce.com, Roy@Set.Net, abuse@set.net, or other published contacts.
We do not intentionally collect special categories of data (for example health or political data). Such data might appear inside mail that someone sends to a mailbox; it is stored only for the mail retention window and for any notification you have enabled.
6. Period, area, recipients, and means of use (PDPA Art. 8)
6.1 Period (current implemented retention)
The following reflects the Service’s current behavior. Items marked “no automatic purge found” are kept until we delete them manually or a legal rule requires otherwise.
| Data | Current retention |
| Mail in an active user mailbox | Inaccessible 24 hours after receipt, then permanently deleted by an hourly purge. Also, at most 200 messages per mailbox; older messages are deleted when the cap is exceeded. |
| Mail in system mailboxes we operate (for example postmaster, abuse) | 7 days |
| Unconfirmed pending free sign-up (and related sessions, tokens, and subscriptions for that pending row) | 48 hours, then deleted; the name becomes available again |
Sign-in session (__Host-u) | 12 hours, or 30 days if you choose “remember me” |
Pre-session cookie (__Host-upre) | 2 hours |
| Language cookie / localStorage | Up to 1 year (or until you clear it) |
Checkout cookies (__Host-buyord, __Host-buyret) and name hold | 15 minutes |
| Password-reset link | 1 hour, one-time |
| Confirmation link (free sign-up) | 48 hours |
| Admin-issued set-password link | 24 hours, one-time; leftover records are deleted 7 days after expiry |
| Login OTP and related send/failure records | OTP itself is short-lived (currently 5 minutes); leftover OTP and send/failure rows are purged after about 24 hours |
| Sign-up IP rate-limit log; login-failure IP log; LINE/Telegram link-failure logs | 24 hours |
Record that we sent a confirmation or reset mail (mail_sends) | 30 days |
| Proof-of-work used-token records | Until the challenge expires (currently about 10 minutes) |
| LINE / Telegram / Web Push bindings for an active mailbox | Until you unlink them, or the mailbox is deleted (pending sign-ups only) or disabled and later erased |
| Active or disabled mailbox records (including contact email, password hash, sign-up IP, and linked chat ids) | No automatic purge found. Under current operations, activated or disabled names are not recycled, so these records may be kept indefinitely unless you successfully request deletion or we erase them. See Section 9. |
| Purchase / order records | No automatic purge found (may be kept indefinitely for accounting, refunds, and disputes) |
| Application audit log | No automatic purge found (may be kept indefinitely) |
| Nginx web logs | Rotated daily, 14 days kept. Access logging is off for /inbox/, /confirm/, /reset/, /set-password/, and some other token-bearing paths. |
| System / mail / auth logs (rsyslog) | Rotated weekly, 4 generations kept (about four weeks) |
| systemd journal | No explicit time cap is configured; journals are also forwarded to syslog |
6.2 Area of use
Data is used in Taiwan (where the operator is a citizen and administers the Service) and in Singapore, where the Service is hosted on a DigitalOcean droplet in region sgp1. Data is also processed in other countries where our processors are located (see Section 7), which may include the United States, the European Union or United Kingdom, Japan, and other locations used by those providers.
6.3 Recipients
Recipients are the operator; the processors and platforms in Section 7; professional advisers or authorities where the law requires or allows; and, for mail content, anyone you authorize (for example by sharing a password, a legacy inbox URL, or a linked LINE/Telegram/push device). Senders who mail a public address do not thereby gain the right to read the inbox.
6.4 Means of use
We use personal data by electronic collection, storage, and processing on the hosted servers; by sending transactional email; by redirecting you to ez.wiki / Stripe for checkout; by sending optional push or chat notices; and by manual review when needed for support, abuse, refunds, or legal matters.
7. Processors and other recipients
We use the following categories of processors or platforms (their own privacy policies also apply when you use their services):
- DigitalOcean — hosting and infrastructure for set.net, currently in region sgp1 (Singapore).
- ez.wiki, operated by ez.wiki — hosted checkout, promo-code validation and per-customer use limits, and payment-status notices back to us. We send a handoff token with order and contact data needed to check out; we receive back payment metadata, not your full card number.
- Stripe — card and similar payments on the hosted Checkout page.
- LINE (LY Corporation and its group) — if you link the official account for notices or OTP.
- Telegram (currently the bot @b2b2cbot) — if you link Telegram for notices or OTP.
- Browser or device push services — if you enable Web Push, your browser vendor’s push service (for example services operated by Google, Mozilla, Apple, or others, depending on the browser and device).
- Brevo (transactional email; SMTP host
smtp-relay.brevo.com) — confirmation, password-reset, and similar messages to your contact email, sent with a From header of set.net <no-reply@set.net>. These are not sent from your set.net or qrm8.com mailbox.
We do not sell your personal data.
8. Cookies and local storage
We use the following cookies and similar storage. We do not currently use third-party advertising cookies.
| Name | Type | Purpose | Lifetime (current) |
__Host-u | Essential, HTTP-only, Secure, SameSite=Lax | Signed-in session | 12 hours, or 30 days if you choose “remember me” |
__Host-upre | Essential, HTTP-only, Secure, SameSite=Lax | Pre-session / sign-up integrity | 2 hours |
u_lang | Preference (readable by the page script; not HttpOnly) | Interface language (zh or en) | 1 year |
__Host-buyord | Essential, HTTP-only, Secure, SameSite=Lax | Identifies a short-name checkout order | 15 minutes |
__Host-buyret | Essential, HTTP-only, Secure, SameSite=Lax | Return-from-checkout helper | 15 minutes |
setnet-lang in localStorage | Preference, stored in your browser | Remembers language on the homepage | Until you clear site data |
The language cookie may be set by the server (/lang/zh or /lang/en) or by the homepage script. Checkout on ez.wiki or Stripe may set additional cookies under those sites’ policies.
You can block cookies in your browser, but essential cookies are needed to sign in, complete a purchase, and keep a session secure.
9. Your rights under PDPA Article 3, and how to exercise them
Under Article 3 of the PDPA, subject to the exceptions in the Act, you may:
- make an inquiry or request to review your personal data;
- request a copy;
- request supplementation or correction;
- request that we stop collecting, processing, or using the data; and
- request deletion.
To exercise these rights, write to RoyFang@M-Commerce.com (primary contact; we reply from this address) or Roy@Set.Net (Inbound Only) from a contact email we can reasonably associate with the mailbox, and tell us which mailbox and which right you are exercising. We may need to verify your identity. We will respond within the time the law requires, and any reply will come from RoyFang@M-Commerce.com. If you write only to Roy@Set.Net, please note that it is a receive-only mailbox on the Service, so messages there follow the mail retention period in Section 6 unless they are copied elsewhere. Contact is by email only.
Please note the following practical limits, which we will apply only as the law allows:
- Mail in a user inbox is already deleted after 24 hours (and sooner if the 200-message cap is hit). We cannot restore purged mail.
- There is currently no self-service “delete my account” button. If you ask us to delete account data, we may disable the mailbox (it will stop receiving stored mail). Under current operations the name stays reserved and is not released to others. We may retain limited records (for example order records, audit rows, or a reserved-name stub) where we have a legal or security need, including to prevent the name from being re-registered by someone else.
- If a legal exception applies (for example data necessary for performance of a contract, for our legal claims, or where deletion would impair our statutory duties), we will explain that.
These rights do not reduce any non-waivable rights you have under other applicable law.
10. Consequences of not providing data (PDPA Art. 8)
You do not have to give us personal data. If you do not provide a contact email and password, we cannot complete a free sign-up or recover a mailbox. If you do not complete checkout with the payment processors, we cannot create a paid short name. If you do not enable LINE, Telegram, or Web Push, you will simply not receive those optional notices. If you refuse essential cookies, you may be unable to sign in or complete a purchase. You can still send mail to a public address that belongs to someone else without creating an account, but that does not give you an inbox.
11. GDPR-style information for international users
If you are in the European Economic Area, the United Kingdom, or another place with similar rules, this section is for you. Whether those laws apply depends on the facts (including whether the Service is offered to you). This policy does not concede that any particular foreign law applies in every case.
11.1 Controller: Roy Fang, contact details in Section 1. No company is involved, no separate data-protection officer is appointed, and no EU or UK representative has been appointed.
11.2 Legal bases we would rely on if the GDPR (or a similar statute) applies:
- Contract (Art. 6(1)(b)): creating and operating your mailbox, sign-in and recovery, and completing a purchase you request.
- Legitimate interests (Art. 6(1)(f)): keeping the Service secure, preventing abuse and fraud, keeping reserved names from being recycled after disablement, keeping records of orders and security events, and defending legal claims — balanced against your interests and rights.
- Consent (Art. 6(1)(a)): optional LINE, Telegram, or Web Push notifications, which you can unlink. You may withdraw consent without affecting processing that took place before withdrawal.
- Legal obligation (Art. 6(1)(c)): where a law requires us to keep or disclose data.
11.3 International transfers. The Service is hosted in Singapore and administered from Taiwan. Processors in Section 7 may process data in other countries. Personal data is processed in Singapore, where the Service is hosted, and in other countries where our processors are located. We rely on the safeguards provided by each processor for those transfers.
11.4 Additional rights that may apply under the GDPR or similar law: access, rectification, erasure, restriction of processing, objection to processing based on legitimate interests, data portability, withdrawal of consent, and the right not to be subject to certain automated decisions. We do not use solely automated decision-making that produces legal or similarly significant effects about you (promo-code limits on ez.wiki are payment rules, not profiling of that kind).
11.5 Complaints. You may contact us first (Section 13). You may also lodge a complaint with your local supervisory authority, and with Taiwan’s Personal Data Protection Commission (個人資料保護委員會) as described below.
12. Children
The Service is not directed at children. You must have legal capacity to contract, as described in the Terms. If you are a minor, you may use the Service only with the consent of your legal guardian (未成年人應經法定代理人同意). If you believe we have collected data about a child in error, contact RoyFang@M-Commerce.com (primary contact; we reply from this address) or Roy@Set.Net (Inbound Only).
13. Security
We use measures appropriate to a small receive-only service, including HTTPS, hashed passwords, HttpOnly Secure session cookies on the __Host- prefix where used, hashed one-time tokens, rate limits, and turning off access logs on some token-bearing paths. No method of transmission or storage is completely secure. You must also protect your password, OTP codes, contact email, linked chat accounts, and any legacy inbox URL.
14. Changes
We may update this policy. We will post the updated text and revise the effective date, and we may also notify you via the site or your contact email. Where practicable we will give 15 days’ notice, as described in the Terms of Service.
15. Contact and complaints
You may also complain to the competent authority in Taiwan, the Personal Data Protection Commission (個人資料保護委員會), or to another supervisory authority that has jurisdiction over your complaint.
Governing law of the Service is the law of the Republic of China (Taiwan), as stated in the Terms of Service. The court of first instance is the Taiwan Taipei District Court (臺灣臺北地方法院).