Guth Labs stone head markLABS

Contact / support / incident path

One address. A precise subject line.

Pre-engagement communication goes to hello@getguth.com. Customer-specific support and escalation terms begin only in a signed scope.
Quote or audit

Quote request

Describe the agent or workflow and one behavior it must get right—or must never do.

Prepare email
Security concern

SECURITY REPORT

Give a safe summary, affected Guth page or supplied artifact, UTC time, observed impact, and a non-sensitive way to reproduce it.

Prepare email
Privacy request

Privacy request

Identify the inquiry or email address involved and the correction, access, or deletion request.

Prepare email
Accessibility

Accessibility

Name the page, device or assistive technology, and the barrier you encountered.

Prepare email

General questions

Ask without beginning a quote.

Use this for product, partnership, research, press, or other non-emergency questions.
This opens a pre-addressed email in your own email app. Nothing is uploaded or stored by this page. Do not include passwords, API keys, regulated data, confidential source files, or full transcripts. For an active security event, use the incident guidance below.

Active incident

Stop the affected path first.

If a system may still send, spend, publish, expose data, or change production, use the customer's own emergency controls to disable that capability, rotate exposed credentials, and contact the relevant provider. Do not email secrets or exploit payloads. Guth's public mailbox is not an emergency service and no response time is promised before a signed support agreement.