Privacy

Last updated July 2026

Stet is operated by Landstrom LLC, a Delaware limited liability company (“Stet,” “we,” or “us”). This policy covers both the Stet website (stethq.com) and the Stet application. For privacy questions or requests, contact us at hello@stethq.com.

Data we collect

Account data (via Clerk)

When you sign up or sign in, our authentication provider Clerk gives us your email address, display name, and organization name and membership. We store your Clerk user ID and organization ID to associate your account with your workspace. You can also sign in with Google; if you do, Google provides Clerk with your basic profile (email and name) to authenticate you, and Google’s handling of your data is governed by Google’s own privacy policy.

Slack connection data

When you connect a Slack workspace, we store its name and ID, a bot token (only ever in encrypted form — see Security), channel metadata (name, ID, member count, public/private and archived status, and whether our bot is a member), and the Slack user ID of the person who installed Stet.

Broadcast content and delivery data

We store the broadcasts you compose (text, blocks, images, and audience configuration), the per-channel delivery results (status, timestamps, the Slack message identifier, and any Slack error messages), and your sending-profile settings (display name, avatar, footer).

Replies to your broadcasts

If you use reply notifications, our Slack app receives messages from the public channels it is a member of in order to detect replies posted in the thread under a message you broadcast. When such a reply is posted, we store the reply’s text, the Slack user ID of the person who replied, a link to the message, and timestamps, and we notify the Stet user who created that broadcast. We use this only to surface replies to the broadcast’s author, and you can delete stored replies by deleting the associated broadcast.

Telemetry and analytics

We collect aggregate operational telemetry (event counts, error rates, latency) that does not include message content. We also use PostHog for product analytics: cookieless visit and signup counts on the website, and an aggregate “broadcast completed” event from the send pipeline that includes your organization’s ID and name and per-broadcast counts — but no message content.

Waitlist email (website)

If you join the beta waitlist, we collect your email address and the use-case you select, processed by our email provider Loops, solely to contact you about the Stet beta and launch. Every email includes an unsubscribe link.

What we don’t collect

How we use your data

Who we share it with

We share data with the following service providers to operate Stet. We don’t sell personal data, and we may disclose data if required by law or to protect our legal rights.

Data retention

Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights, contact us at hello@stethq.com. We do not sell or share personal information as those terms are defined by the California Consumer Privacy Act (CCPA/CPRA).

Security

Slack bot tokens are encrypted at rest using AES-GCM (256-bit, via the Web Crypto API). Only ciphertext is stored in our database; plaintext tokens are never logged or written to disk. API keys are stored only as hashes. Access to production systems is restricted to authorized personnel.

International transfers

We use service providers (including Cloudflare, Neon, Clerk, and Slack) that may process data in the United States and other countries. Where required, we rely on appropriate safeguards for international transfers.

Changes to this policy

We’ll provide at least 30 days’ notice of material changes via the email associated with your account or an in-product notice. Continued use after the effective date constitutes acceptance.

Contact

Landstrom LLC — hello@stethq.com.

← Back to stethq.com