Privacy Policy
This policy explains how Strategitect Limited ("we") collects, uses, keeps and protects your personal data when you use Trigpoint (trigpoint.pub, "the site"). We handle personal data under the Personal Data (Privacy) Ordinance of Hong Kong.
0. What this policy covers
0.1 The site currently offers: (a) reading without an account; (b) submitting a correction, counter-example or applicability note privately on a node page; (c) a free account, for following the notes you have submitted; (d) Trigpoint Pass, a paid membership; (e) support payments, which may carry a public message; (f) email notices: shelf notices and promotional emails (sign-up for each is optional and separate).
0.2 The terms for paid services and accounts are set out in the Terms of Use.
1. Principles
1.1 Reading the site requires no sign-up and no personal data.
1.2 Submitting a note privately requires no sign-up, and we do not collect your email. Opening an account requires an email; the account email is used to send sign-in links and is shown to you on your page. Subscribing to Pass or making a support payment requires your email. Signing up for shelf notices or promotional emails requires your email; we send each kind only if you have agreed to it. We collect only what is needed to run the site.
2. What we collect
| Situation | What we collect | Notes |
|---|---|---|
| Reading | Technical data needed for the connection (such as IP address and browser type) | Handled by our hosting provider to deliver pages and for security |
| Visit statistics | Pages viewed, referring address, device and browser type, country or region, page load performance | Processed in aggregate by Cloudflare Web Analytics. Cloudflare states that the service uses no cookies or local storage and does not use this data to identify individuals |
| Submitting a note | Type of note, the node it refers to, the quoted location (optional), what you write, a nickname (optional), interface language, time of submission | You choose the text and nickname, so they may contain information that identifies you (see 2.1) |
| Private notes while signed in | As for "Submitting a note", linked to your account | Used to show the note's status on your page |
| Human check on submission or sign-in | Your IP address and the technical data needed to complete the check | Handled by Cloudflare Turnstile |
| Abuse limit on submission or sign-in | A count keyed to a hash of your IP address; on sign-in, also a count keyed to a hash of your email | The counts do not keep your IP address or email itself |
| Subscribing to Pass | Email, payment details | Payments are processed by Stripe. We do not see or keep your card details |
| Sign-in (accounts and members) | Email, membership status and expiry | We keep your email in your account record, to send sign-in links and to show it to you on your page |
| Public name | The public name you choose, and its change history | The public name is shown publicly; the change history is seen only by the editor |
| Reading member content | A count of reads | Used for abuse limits, keyed to a hash that identifies your membership, and kept short-term |
| Support payments | Email, payment details, a public message and a name (both optional) | Processed and kept by Stripe; the message and name are published only after review (see section 4) |
| Email notices (shelf notices, promotional emails) | Email, interface language, which kinds you agreed to, and for each the time of consent and version of the consent text, time of confirmation | You agree to each kind separately. If you have an account with the same email, you can see and change both settings on your page |
2.1 Names, text and public messages: please do not put personal information you do not want published in your public name, your nickname, your note or a support message. Support messages and names become public once published.
3. Why we use it
3.1 Submitted notes: so the editor can review them, correct or extend node content, and publish an editor-written summary and response on the discussion and response record (see section 4).
3.2 Technical data and hashed counts: to deliver pages, for security, and to prevent abuse and spam. Visit statistics: to see in aggregate which content is read, and to improve how the site performs.
3.3 Pass: to activate and verify membership, send sign-in links, handle payment, renewal, cancellation and refunds, and add an account-bound trace mark to member content (used to identify the source of a leaked copy).
3.4 Support payments: to handle payments and refunds, and to review, publish or take down a public message you chose to add.
3.5 We do not sell your personal data or give it to others for direct marketing. The site carries no third-party advertising. We do not build profiles from your behaviour.
3.6 Accounts: to let you sign in; to show you on your page the status of notes you submitted and the email you sign in with; and to let you manage your email notice settings.
3.7 Email notices: we send two kinds of email, using your email and interface language, and only if you agree. You agree to each kind separately, and one does not depend on the other: (a) shelf notices: we email you when a new shelf opens or when the reading rules change; (b) promotional emails: we intend to use your email for direct marketing of Trigpoint Pass (the site's paid membership) and offers on it. We will not use your email for direct marketing unless you agree. You can agree by ticking the box when you sign up for shelf notices, or on your page once you are signed in; agreeing costs nothing. You can stop either kind at any time (see 9.8). The list is used for nothing else.
4. What we publish
4.1 The text and nickname of a note you submit privately are never published.
4.2 Once the editor has handled a note, the discussion and response record shows its status, type, the node it refers to, a summary and response written by the editor, and the reference number you were given on submission. The summary is the editor's paraphrase of your note.
4.3 Reference numbers are random and cannot be used to identify you.
4.4 Advertising, personal attacks and submissions with no substantive content are not listed.
4.5 Support messages: a public message and name you choose to add are published, after editorial review, in the "From supporters" section of the node or shelf page where you paid, with the date of publication. The amount and your email are never published.
4.6 Private notes while signed in: as in 4.1, the text is never published. If a note is adopted, the credit reads "an anonymous reader" by default; it uses your public name only if you tick the box.
5. Sharing and processors
5.1 We share only what is necessary, and only with:
- Service providers: Cloudflare (hosting, database, human check, visit statistics); Stripe (payments, subscription management, support messages); Resend (sending the site's emails). They may process data only to provide their service to us.
- Legal requirements: where the law requires it, or where necessary to protect rights and safety or to prevent unlawful activity.
6. Processing outside Hong Kong
6.1 These providers may store or process data outside Hong Kong. We take reasonable steps to keep it protected in line with this policy.
7. Security
7.1 We take reasonable technical and organisational measures to protect personal data. IP addresses are counted only in hashed form; the sign-in credential cookie is sent only over encrypted connections and cannot be read by page scripts; the text you submit is not stored in our version history, and the copy in the editor's internal working files is deleted within 30 days after the note has been handled.
7.2 No transmission over the internet or electronic storage is completely secure. If a serious security incident affects your personal data, we will handle it and notify as applicable law requires.
8. How long we keep it
| Data | Retention |
|---|---|
| Submitted text and nickname | Kept in our cloud provider's database with no automatic deletion; you can ask us to delete it at any time (section 9). The copy of the text in the editor's internal working files is deleted within 30 days after the note has been handled |
| Editor-written summary and response | Published until taken down |
| Hashed abuse-limit counts | Short-term, then cleared automatically |
| Membership records | Kept after membership ends, until you ask us to delete them |
| Transaction records (including the original text of support messages) | Kept by Stripe; we keep them as Hong Kong law requires for business records |
| Published support messages | Published until you ask us to take them down or we take them down |
| Account (including its email), public name and change history | Until you delete the account |
| Public name of a deleted account | The name alone, linked to no one, for 90 days, so no one else can pose as its owner |
| Record of editor actions on your account (for example, rechecking your membership against Stripe's records, or deleting your account at your request) | One year; no longer linked to you once you delete your account |
| Email notice list | Until you unsubscribe, turn off both kinds, or delete your account; it is deleted then. Sign-ups through the form not confirmed within 7 days are deleted automatically |
9. Your rights
9.1 Access and correction: you have the right to access and correct personal data we hold about you.
9.2 Withdrawing a submission: we do not collect email, so we cannot verify you through an account. To withdraw a note, email hello@trigpoint.pub with the reference number and a short description of what you wrote; we will check it against the original. Once verified, we delete the text and nickname of that note and take its public entry down. The email you send is used only to handle that request. If you were signed in when you submitted, you can withdraw the note directly on your page, with no email needed.
9.3 What withdrawal covers: if we have already revised a node because of your note, that revision is our editorial content and is not reversed.
9.4 Members and supporters: you can email hello@trigpoint.pub to access, correct or delete your membership data, or to have your support message taken down. Deleting membership data ends the membership. Transaction records are handled as set out in section 8.
9.5 We will reply to a data access request within 40 days of receiving it, as the Personal Data (Privacy) Ordinance requires, and to other requests within a reasonable time.
9.6 Complaints: if you believe we handle personal data unlawfully, you have the right to complain to the Office of the Privacy Commissioner for Personal Data, Hong Kong. You are welcome to contact us first.
9.7 Deleting your account: you can delete your account at any time on your page. After deletion, sign-in stops working at once and the account cannot be restored. Your public name and its change history are deleted at once, and the name is not open to anyone else for 90 days. Notes you submitted privately are unlinked from the account, and their text is handled as set out in section 8. If you hold an active Pass, the membership ends (see the Terms of Use). Your entry on the email notice list is deleted too, whether you signed up through the form or on your page, so you receive no more shelf notices or promotional emails. Transaction records are kept by Stripe as the law requires; we delete the link between them and your account in our systems. Signing in later with the same email opens a new account, unrelated to the deleted one.
9.8 Unsubscribing: every shelf notice and promotional email includes an unsubscribe link. One click takes effect at once: both kinds of email stop and your email is deleted from the list. If you have an account, you can instead turn off just one kind on your page. You can also email hello@trigpoint.pub at any time to ask us to stop promotional emails, free of charge.
10. Cookies and local storage
10.1 Reading the site sets no cookie that identifies you. Sign-in (accounts and members) uses two cookies. Both last 30 days and are sent only over encrypted connections. One is the sign-in credential and cannot be read by page scripts. The other is used only so that pages can show whether you are signed in and whether you are a member; it contains no identifying data. Your browser also keeps interface settings, unsent drafts and the claim codes for anonymous notes in local storage on your device. These stay on your device; a claim code is sent to us only when you choose to link an anonymous note to your account.
10.2 The human check on submission and sign-in is handled by Cloudflare Turnstile, and the payment page is provided by Stripe, each under its own privacy policy. Cloudflare states that the visit statistics service we use sets no cookies (see section 2).
11. Minors
11.1 The site is not designed for children.
12. Changes
12.1 We may update this policy from time to time. Significant changes will be announced on the site, with an updated effective date.
13. Contact
Data user: Strategitect Limited. For privacy questions and requests, email hello@trigpoint.pub.
14. Language
14.1 This policy is available in Chinese and English. If the two versions differ, the Chinese version prevails.