Help
Support
Launch support contact
Email support@threadgrid.dev for v0 launch support. This inbox is monitored for checkout, activation, license, install, and customer-safe troubleshooting questions.
v0 support is best-effort and has no support SLA, uptime SLA, or guaranteed response time. Do not send private archives, prompts, local memory content, license keys, entitlement tokens, order identifiers, or raw diagnostics by default.
Use the same inbox for legal, privacy, data-subject access (DSAR), or deletion requests. Start with a metadata-only request; support will ask for the minimum customer-visible order, license, or contact context needed to locate records.
Where to start
Start with the surface that owns the behavior: free project-scoped threadpoint, paid threadgrid workflows, hosted checkout, license, docs, or install. Public support content should describe customer-visible symptoms and safe next steps without exposing private product, account, license, or local memory details.
threadpoint
Use the public repository for the free project-scoped tool, including install, validate, doctor, adopt, promote, prune, restore, and scan behavior.
threadpoint repothreadgrid
Use these docs for paid personal, private, cross-project, archive, curation, recall, license, customer-safe troubleshooting, and planned workflow labels.
threadgrid guideWorkflows
Use the workflow guide for shipped commands, planning-only surfaces, and planned or unavailable paid workflow labels.
workflow guideCheckout
Use the hosted buy surface for limited-time early-adopter lifetime purchase handoff. Do not paste order details, license material, or private account data into public issues.
checkoutLicense status
Use the license page for local status guidance and current activation behavior. Keep license material out of source files and support examples.
license guideCustomer portal
Use the hosted portal to recover Polar order and license details after validating the license key. Do not send raw license keys, customer IDs, or order IDs to support.
customer portalDocumentation
Use the troubleshooting guide when a route, command example, or availability statement is unclear.
troubleshootingWhat to include
- Product area: threadpoint, threadgrid, checkout, license, docs, or install.
- Command name and version output when available.
- Operating system and architecture, written generically when paths are private.
- Metadata-only redacted command output with secrets, license keys, tokens, account identifiers, order identifiers, private paths, prompts, and local content removed.
- Whether license status is unconfigured, active, inactive, or unavailable without including the key.
- Whether the workflow is documented as shipped, preview-only, planned, or unavailable.
Service incidents
If checkout or hosted license validation appears unavailable, email support@threadgrid.dev with the request ID if visible, approximate UTC time, public URL or command name, and redacted status category. Do not send your license key, payment details, order identifiers, customer identifiers, provider screenshots, or private local content.
Analytics
Public marketing and docs pages can use Google Analytics 4 after analytics consent for page views and high-level funnel clicks. Analytics are separate from local threadgrid workflows and must not include license keys, command output, private paths, order IDs, customer IDs, prompts, archives, or local memory content. See the privacy page for the current disclosure.
Diagnostics
For v0, support bundles are planned, not shipped. Until a reviewable bundle command is documented, copy only the smallest useful metadata-only redacted output into support conversations. Prefer status categories, hashes, command names, versions, operating system, and architecture over raw local content.