Terms of Service & Privacy Policy

Effective Date: October 25, 2026 · Platform: Thema Studio Orthodox #2 Composition & Verification Workbench

Consent-First Attribution & Privacy Guarantee:

Sign in works across all providers (GitHub, Lichess, Google, and WebAuthn Passkeys) with zero email collection.
No name is required to sign in or use the workbench privately. Choosing a public name or handle (@handle) is only required when sharing, publishing, or commenting.
Never auto-filled without your consent: We never pull or auto-fill your name or email from your OAuth sign-in provider or browser autofill. You freely choose whether to credit yourself with a pseudonym (@handle) or your real name.

1. Multi-Provider Zero-Email Authentication

Thema Studio supports one-click sign-in via GitHub, Lichess, Google, and WebAuthn Passkeys. When you authenticate with any provider, Thema Studio stores only an opaque cryptographic subject identifier (provider_sub) to link your workspace and ownership permissions. We never request, auto-fill, or harvest your email address or identity profile from your sign-in provider.

2. Deferred Public Attribution (Pseudonym or Real Name — Your Choice)

You are not required to provide any name or handle to sign in, compose chess problems on the board, run the WebAssembly solver, save personal compositions or custom .thm specifications locally, disable or override built-in themes, or synchronize your private workspace.

A public author credit—either a pseudonym / handle (e.g., @chess_poet) or your real name—is only requested when you choose to share, publish (a #2 problem or a .thm theme specification/revision), or post a comment.

3. No Unconsented Auto-Fill

To protect user privacy across the platform:

No automatic profile scraping or autofill: Sign-in providers and browser form autofill are never used to populate your composer name or public handle without your explicit action.
Full control over your credit: You may change or clear your chosen public name or @handle at any time in My Page.

4. Community Hub Governance, Revisions & Anti-Spam Rules

Soundness & Verification Gate: Problems published to the Community Hub must be orthodox legal #2 positions with a unique key move (zero cooks). Published .thm specifications must compile cleanly in the Thema VM and include a non-trivial phase/predicate structure and story template.
Incremental Revision Integrity: Updates to published .thm specifications are released as numbered incremental revisions with a mandatory explanation note ("Why") so prior versions remain preserved in revision history.
Anti-Spam Policy: External URLs, promotional links, commercial solicitation, HTML/script injection, and abusive content are strictly prohibited in public handles, problem notes, theme descriptions, and comments.

5. Local-First Data Ownership

All compositions, working drafts, and custom .thm rules are stored locally in your browser (localStorage) first and can be exported or restored as standard JSON bundles at any time. Private local compositions are never uploaded or shared with external databases unless you explicitly click Share or Publish.

6. Contact

For questions regarding these Terms of Service, quota extensions, or canonical theme curation, contact Jon Schuringa at jon.schuringa@gmail.com.