The paperwork, in plain sentences
Privacy
The entity behind this site
Glacier Workspace Journal
Sole proprietorship (獨資)
No. 204, Minsheng E. Rd., Zhongshan Dist., Taipei City
Taiwan
UBN 72307599
Responsible person (負責人): Yeh Chun-Wei
This page is written in plain sentences because a privacy notice nobody reads protects nobody. It describes the actual behaviour of this site, which is deliberately small: one form, one stored preference, no analytics, no third parties, nothing sold.
Who is responsible for your data
The entity named in the box above — the desk behind this journal — is the collecting entity and the data controller for everything this site processes. The full legal identity, including the Taiwan uniform business number and the responsible person, appears in that box, in the site footer, and in every page footer on this site, so there is never a question of who holds your data.
Framing: Taiwan’s PDPA
This site operates from Taiwan, and the collection described here is framed under Taiwan's Personal Data Protection Act (個人資料保護法, PDPA). Under the PDPA, the purposes of collection must be specific and legitimate — in this journal's case, responding to an editorial inquiry you chose to send. No other use is made of the data.
What the inquiry form collects, and why
The form collects exactly four kinds of input: your name (so a reply can address you), your email address (so a reply can reach you), an optional phone number (only if you choose to give one), and the question itself, together with the topic label you pick. The purposes are:
- answering your inquiry from the editorial desk
- keeping an honest record of what was asked and replied, so recurring questions can become public notes
- operating basic anti-abuse measures on the inquiry endpoint
That is the complete list. The journal sends no marketing, maintains no newsletter at this time, shares nothing with third parties, and uses the data for no profiling of any kind.
Where the data actually goes
When you press send, the form posts your input as JSON to this site's own handler endpoint — same domain, this site, nothing else. The data is not routed through any external form service, analytics provider or tracking pixel. This site runs no analytics of its own either: no gtag, no Google Analytics, no advertising pixels, no session recorders. Requests your browser makes when loading pages go to this domain and this domain only.
The consent preference
Separately from inquiries, your browser stores the cookie banner choice in local storage — one small record under the key gwj_consent that says whether you pressed Accept or Decline, and when. It exists so the journal does not re-show the banner on every visit. Details of every storage item this site uses (there are very few) are inventoried in the cookies and storage notice.
Retention
Inquiry correspondence is kept while it serves the purposes above and then removed; the journal's working practice is to keep form inquiries and replies for up to twelve months, which is long enough to answer follow-ups and notice recurring subjects, and short enough to respect the reader behind the words. This period is a proposed standard the desk operates until the operator confirms a final figure. The consent preference is kept until you change it — clearing your browser's storage removes it immediately, and nothing breaks when you do.
Your rights
Under the PDPA you may request access to the personal data this journal holds about you, ask for corrections, or request that it be erased or ceased from use. Because the collected set is small (an inquiry and a reply), these requests are quick to honour. Write to the inquiry channel on the contact page or the office mailbox named in the identity box, describe yourself by the name and email you used, and the desk will act within a reasonable working window, confirming what was done in writing.
Children
This journal writes about research workflows for adult readers with their own decisions to make, and the inquiry form is not intended for children. No data is knowingly collected from children, and a request identifying a child's data will result in its deletion.
Changes to this notice
If the site's actual behaviour changes, this page changes with it — the promise being that it never describes more processing than really happens, and never hides any either.