Privacy Policy

Version 2. Last updated August 10, 2026. Replaces the policy dated June 19, 2026.

This Privacy Policy explains what information Caddie ("Caddie," "we," "us," or "our"), operated by Curious Frog, collects, how we use it, and the choices you have. It applies to getcaddie.now, app.getcaddie.now, and the Caddie Watch companion tools including the Caddie Watch Chrome extension, and should be read alongside our Terms of Service.

1. Information We Collect

The Caddie Watch Chrome extension, specifically

The Caddie Watch Chrome extension reads Whatnot live stream chat messages in real time while you are actively streaming. Specifically, it collects:

The extension does not collect browsing history, data from non-Whatnot pages, or any information from streams you are not actively monitoring. Data collected by the extension is sent exclusively to your own Caddie account, and is used to detect buyer requests in chat, match them against your inventory, display a live intent feed in your dashboard, and generate post-show analytics about viewer demand. It is associated with your Caddie account only and is not shared with other sellers.

2. How We Use Information

We do not sell your personal information, and we do not use your inventory content or buyer and viewer data to train models on behalf of, or for the benefit of, anyone outside of providing you the Service.

3. AI-Assisted Features

Caddie uses Anthropic's Claude models to power several features:

The specific content each feature needs (a photo, a search query, a chat message, your stream's activity data) is sent to Anthropic's API to generate that feature's output, and is handled under Anthropic's own API data-use terms. We don't otherwise share your account, inventory, or buyer data with Anthropic beyond what each feature requires.

4. How We Share Information

We share information with the service providers that help us run Caddie, each acting on our behalf and only for the purpose listed:

  • Railway hosts the Caddie application and its database.
  • Stripe processes payments and subscription billing.
  • Backblaze B2 stores the item photos you upload, and our nightly database backups.
  • Resend delivers transactional email.
  • Sentry provides error monitoring.
  • Anthropic powers the AI features described in Section 3.
  • Crisp provides in-app customer support chat, if you use it.
  • GitHub runs our scheduled maintenance jobs. Our nightly database backup passes through a GitHub-hosted machine on its way to Backblaze.
  • UptimeRobot checks from outside our infrastructure whether Caddie is reachable, and publishes our status page.
  • Hedera, a public network, receives fingerprints of support-access records as described in Section 8.

We do not sell, rent, or share your data with advertisers or data brokers. We may disclose information if required by law, to protect the rights, safety, or property of Caddie or others, or in connection with a merger, acquisition, or sale of assets, in which case we'd give notice as described in our Terms.

5. Buyer and Viewer Data, and Your Responsibility as a Seller

When you use Caddie Watch, you are the one collecting your viewers' chat activity from the livestream you're running. Caddie processes that data on your behalf to provide the matching feature. Your viewers have not agreed to Caddie's Terms or this Policy; they've agreed to the livestreaming platform's own terms. You're responsible for using this feature in a way that complies with applicable law and with that platform's rules regarding your viewers' data.

6. Data Retention

We keep your account and inventory content for as long as your account is active. If you cancel or your account is terminated, we delete Your Content within 30 days, consistent with our Terms.

Buyer and viewer chat data collected through Caddie Watch (usernames, messages, match outcomes) is retained for as long as your account is active, since it powers your ongoing analytics and buyer history. It is deleted on the same 30-day schedule as the rest of your account data if you cancel.

Backups. We take a nightly backup of the production database and keep it for 30 days. Data you delete disappears from the live Service immediately, but can persist in a backup for up to 30 days after that, including after account deletion. Backups are used for disaster recovery only.

Support access records are an exception, and deliberately so. Entries in your support-access record are not deleted on request while your account exists. A record whose entries can be removed on request is not a record, and the whole point of it is that it holds up in a dispute about what happened. Those entries are deleted along with the rest of your account data if you close your account. The fingerprints already published to Hedera cannot be deleted by anyone, including us, and this is explained in Section 8 and Section 12.

7. Data Security

We use industry-standard measures to protect your information, and we would rather describe them precisely than in general terms.

  • Passwords and API keys. Your password is stored as a bcrypt hash and cannot be read by anyone, including us. Caddie Watch API keys are stored hashed as well. Both can be rotated by you at any time.
  • Data in transit is encrypted with TLS. All traffic between the Caddie Watch extension and the Caddie API uses HTTPS.
  • The extension's copy of your API key is stored using chrome.storage.sync, Chrome's built-in encrypted storage. It is transmitted only to Caddie's own API at app.getcaddie.now and to no other server, and it is never exposed in plain text to the page.
  • Administrative access requires a password and a second authentication factor. Our scheduled automated jobs use a separate, narrowly scoped credential that cannot read your data, change your account, or open a support session.
  • Error monitoring is tagged by account identifier, not by identity. Sentry receives error reports with an account id attached so we can trace a bug to an account. Personally identifying request data is switched off, and the local variables inside a program's stack frames are not transmitted, so credentials and keys held in memory when an error occurs are never sent.
  • Backups are stored in the same Backblaze account as your photos, with the 30-day retention described in Section 6.

Item photos, described accurately

Your item photos are stored in a Backblaze B2 bucket and delivered to your browser and to your streaming overlay as direct storage addresses, rather than being passed through Caddie. This is a real architectural fact with consequences, and we would rather state them than let you assume otherwise:

  • The bucket cannot be listed or browsed. An unauthenticated attempt to list its contents is refused. Every part of an image's address is a randomly generated identifier, so nobody can discover, enumerate, or index your photos, or find one by guessing.
  • An image address is not secret once it has been shared. Anyone holding the address can fetch that one image without signing in to Caddie. Addresses are delivered to whatever browser loads your dashboard or your overlay page. Your viewers see your overlay as video composited by your streaming software, not as a web page, so ordinary viewers never receive these addresses. Anyone you give your overlay link to does.
  • Marking an item sold hides it inside Caddie. It does not stop its image address from working. Anyone who already had that address can still fetch the image.
  • Deleting an item does delete its underlying image files, and any address pointing at them stops working.

The practical consequence, stated plainly: don't upload a photo containing something you would not want fetchable by anyone who was given its address. Photos of collectible items, which is what Caddie is built for, are not a concern. A photo that happens to include a shipping label, a document, or personal paperwork would be.

No method of transmission or storage is perfectly secure, and we can't guarantee absolute security.

8. Support Access and Your Audit Record

Section 9 of our Terms of Service describes how support access works: only you can turn it on, you choose how long it lasts, it expires on its own, and certain things (your password, your email, your billing, your API keys and capture tokens) are blocked in code even while it is active. This section covers the privacy side of the record it produces.

Every action taken inside your account during a support session is written to a record you can read in your own Settings panel and download as a machine-readable file. Refused attempts are recorded too. The actor is recorded as "Caddie Support," never an individual's name.

Each entry carries a SHA-256 fingerprint of its own contents, taken when the entry was written. Those fingerprints, and only those fingerprints, are published to a public Hedera Consensus Service topic on the Hedera mainnet, topic 0.0.10802877. What is published is a 64-character hexadecimal digest. It is one-way and cannot be reversed into the entry it came from. No inventory data, no photos, no email addresses, no chat, no buyer information, and no personal information of any kind is sent to that topic.

Two things about the topic are worth knowing before you grant access. It was created with no administrative key, which on Hedera is permanent and publicly checkable: nobody can modify or delete it, including us, and including if we were ordered to. And it is a public network, so a published fingerprint is readable by anyone, anywhere, permanently. That permanence is the entire point of publishing it, and it is also the reason nothing but a one-way digest goes there.

The record is tamper-evident. It is not tamper-proof, and we will not describe it that way. Publishing a fingerprint proves the fingerprinted content existed at a consensus time and has not been altered since, including by us. It does not prove the content was true when it was written. What it defends against is a record being rewritten after a dispute begins.

How to check a record yourself, without our help and without a Caddie account, is published at app.getcaddie.now/verify.

9. Your Choices and Rights

You can access and update most of your account and inventory information directly in the Caddie dashboard, and export your inventory as a CSV or spreadsheet file at any time. To request a copy of your data, ask us to correct it, or ask us to delete your account and associated data, email support@getcaddie.now. We'll respond within a reasonable time.

Three limits on a deletion request, stated up front rather than discovered later: deleted data can persist in a backup for up to 30 days (Section 6); entries in a support-access record are not removed piecemeal on request while your account exists, though they go when the account does (Section 6); and fingerprints already published to Hedera cannot be deleted by anyone, though they contain no personal information (Section 8).

10. Cookies and Tracking

Caddie uses the minimum necessary to keep you signed in and the Service working, such as your session and authentication token. We don't use third-party advertising trackers and we don't sell data to ad networks. Sentry, listed in Section 4, is used only for error monitoring, not behavioral tracking. If you use the in-app support chat, Crisp sets its own cookie so a conversation can continue across visits.

11. Children's Privacy

Caddie is not directed at, and is not intended for use by, anyone under 18, consistent with the eligibility requirement in our Terms. We don't knowingly collect personal information from children.

12. Data Location

Caddie's infrastructure and service providers are based in the United States, and information is processed and stored there.

The one exception is the fingerprint publication described in Section 8. Hedera is a public, globally distributed network, so those fingerprints are stored and readable worldwide and permanently. They are one-way digests and contain no personal information.

13. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we'll provide reasonable notice, such as an email or an in-app notice, before they take effect. Changes are posted on this page with an updated version and date.

14. Contact

Questions about this Policy, or a request about your data? Reach us at support@getcaddie.now.