Terms of Service

Last updated: 2026-05-23.

These terms apply to your use of stackquarterly.com (the “Site”) and to the editorial content Stack Quarterly publishes. Stack Quarterly is operated by Lumenwhite Media Holdings Pte Ltd, a Singapore-registered company (“we”, “us”, “our”).

Acceptance

By accessing the Site you accept these terms. If you do not accept them, do not use the Site. You can still read these terms; they may help you decide whether to come back.

What you may do

• Read every piece on the Site, free of charge, without registration.
• Quote individual pieces with attribution under fair-use and fair-dealing principles. The format we suggest is at /style-guide/.
• Subscribe to the newsletter, RSS feed, or JSON Feed.
• Use the Site’s search, bookmarking, and reading-progress features.
• Cite our pieces in academic work, journalism, conference talks, and other professional contexts.

What requires our permission

• Republishing a full piece (more than ~200 words of body text). Terms are at /press/. The short form: full piece, byline preserved, canonical link in the head, “Originally published at Stack Quarterly” line above the body, and the republication runs within 30 days of the original.
• Using the Stack Quarterly wordmark or brand mark on commercial collateral (sales decks, landing pages, ad creative, packaging). Inline citation in editorial work does not require permission.
• Training a machine learning model on the full text of Stack Quarterly pieces. Indexing for search and answer-generation is permitted under standard search-engine terms; training a model that reproduces or paraphrases the corpus at scale is not.

Permission requests go to editorial@stackquarterly.com. We are generally permissive about honest editorial use and restrictive about commercial use of the wordmark.

What you may not do

• Republish full pieces without meeting the conditions above.
• Modify pieces and continue to attribute them to the original author. Edits beyond house-style adjustments require the author’s approval.
• Misrepresent yourself as a Stack Quarterly contributor, editor, or representative.
• Scrape the Site in a way that imposes a load disproportionate to ordinary reader use. The robots.txt at /robots.txt documents which paths are crawlable.
• Use the Site to distribute malware, phish readers, or otherwise harm other users.
• Bypass technical measures (such as rate limits) we put in place to protect the Site.

Copyright

All editorial content on the Site is copyright of the named author or, in the case of Editorial Team pieces, of Lumenwhite Media Holdings Pte Ltd. The Stack Quarterly wordmark and brand mark are copyrighted by Lumenwhite Media Holdings Pte Ltd.

If you believe content on the Site infringes your copyright, send a notice to editorial@stackquarterly.com with:

• A description of the work you believe is infringed.
• The URL on Stack Quarterly that hosts the infringing material.
• A statement that you have a good-faith belief the use is unauthorized.
• Your contact information.

We respond to good-faith copyright notices.

User submissions

When you submit material to Stack Quarterly — via the contact form, the pitches inbox, the tips inbox, or otherwise — you grant us the right to read that material, to use it in our editorial work, and (if your submission becomes a piece on the Site under your byline) to publish it as agreed. Pitches that are declined are not used. Tips that are corroborated and become pieces are credited if the tipster has agreed to be credited.

You retain copyright in your submission. You warrant that the submission is yours to submit (you wrote it, or you have permission to share it) and that the submission does not infringe any third party’s rights.

Disclaimer

The pieces on Stack Quarterly are editorial opinion from working practitioners. They are not engineering advice for your specific situation. We do our best to be accurate; we do not warrant that any specific piece is suitable for any specific use case. Run code samples against your own dependencies, in a test environment, before you run them in production. Make your own decisions about which tools belong in your stack.

Limitation of liability

To the maximum extent permitted by law, Lumenwhite Media Holdings Pte Ltd is not liable for indirect, incidental, special, consequential, or punitive damages arising out of or related to your use of the Site. Our total liability to you for any claim arising out of or related to these terms is limited to the amount you paid us in the twelve months preceding the claim, which for almost everyone is zero.

Indemnity

You agree to indemnify and hold harmless Lumenwhite Media Holdings Pte Ltd, its officers, directors, and editorial contributors from any claim or demand arising out of your use of the Site in violation of these terms.

Termination

We may suspend or terminate your access to the Site (for example, by blocking your IP after a sustained abusive scraping pattern) without notice. The editorial content on the Site remains available to the general public; we are not terminating your right to read the publication, we are terminating an abusive usage pattern.

Changes to these terms

When these terms change, we update the “Last updated” date at the top and post a note in the corrections log at /corrections/. Material changes are flagged in a newsletter issue before they take effect.

Governing law

These terms are governed by the laws of the Republic of Singapore. Disputes are submitted to the exclusive jurisdiction of the courts of Singapore. If you are a consumer in a jurisdiction whose mandatory consumer-protection law gives you additional rights, those rights are not affected by this clause.

Severability

If any provision of these terms is held unenforceable, that provision is modified to the minimum extent necessary to make it enforceable, and the remainder of the terms continue in effect.

Contact

Questions about these terms go to editorial@stackquarterly.com. For Singapore-law specific correspondence, identify the request as such in the subject line.