Privacy

Threadgrid is designed around explicit knowledgebase files and clear ownership boundaries: threadpoint stays free and project-scoped, while threadgrid owns paid personal, private, cross-project, archive, curation, recall, and license-aware workflows. The first paid release uses Polar as the Merchant of Record/reseller and source of truth for orders and licenses.

Local private materials

Local archives, prompts, memory content, private paths, curation drafts, diagnostics, and license material can contain customer-private information. The marketing and support surfaces should describe symptoms and safe next steps without requiring raw local content by default.

Checkout and license data

Polar handles hosted checkout, order, receipt, refund, withdrawal, and license records for v0. Public threadgrid pages should refer to customer-visible order, receipt, checkout, and activation context instead of publishing private access internals or billing implementation details.

Marketing analytics

The public marketing and docs sites can use Google Analytics 4 after you grant analytics consent. Analytics are limited to page views and high-level funnel clicks such as pricing, docs, checkout, install, license, portal, and support handoffs. Declining analytics keeps Google Analytics disabled for that browser unless you later change analytics settings.

Threadgrid does not use advertising pixels, ads personalization, session replay, or Google Analytics on the hosted buy Worker. Analytics events must not include local archives, prompts, license keys, customer IDs, order IDs, private paths, command output, local memory content, support bundle data, or arbitrary customer-entered text.

Support-safe information

For v0 support questions, email support@threadgrid.dev or use the public support route rather than sending private archives, prompts, license keys, or local memory content by default. Launch support is best-effort and has no support SLA or guaranteed response time.

Prefer product area, command name, version output, operating system, architecture, status category, request ID, hashes, and the smallest useful metadata-only redacted output. Remove secrets, account identifiers, order identifiers, private paths, license material, prompts, local memory content, archive content, and unpublished work before sharing support examples.

Privacy requests and deletion

For legal, privacy, data-subject access (DSAR), or deletion requests, email support@threadgrid.dev and start with a metadata-only request. Support will ask for the minimum customer-visible order, license, or contact context needed to locate records. Threadgrid cannot delete local archives, prompts, or memory files that stay on customer machines and are never sent to threadgrid.

Review status

This page is a v0 privacy stub for early adopter lifetime. It does not replace final public-launch legal review, and any telemetry, diagnostics, or support-bundle behavior must be documented before it asks users to transmit private local content.