Privacy Policy

Last updated: September 4, 2026

1. Information We Collect

We collect information you submit in the software questionnaire, account profile, checkout, Second Opinion reviewer, or integrator matching forms. This can include contact details, business needs, and text you choose to review.

2. How We Use Your Information

We use this information to provide recommendations and reports, authenticate accounts, process payments, prevent abuse, respond to matching requests, and operate the service.

3. Information Sharing

We do not sell personal information. Clerk receives authentication data, Stripe receives checkout and payment data, and Cloudflare processes application traffic, submitted Second Opinion text, email delivery, newsletter consent records, and integrator matching requests.

4. Integrator introductions

We only share a matching request with a prospective customer or integrator after the submitter consents. The parties contract directly; do not submit secrets, regulated records, or confidential customer data in the intake form.

5. Retention and requests

Unpaid questionnaire input is not stored in our D1 database. Integrator requests are kept for up to 180 days, aggregate funnel events for 395 days, fulfillment idempotency records for 730 days, and aggregate AI telemetry for 90 days. Newsletter signups are confirmed by email before any issue is sent; unconfirmed requests are removed after 7 days, active consent is kept until unsubscribe, and the unsubscribe record is removed after 30 days. Paid report inputs remain in Stripe Checkout metadata so the private report can be regenerated. Contact privacy@softwaresausage.com to request access, correction, or deletion. Stripe may retain payment records for disputes, accounting, and legal obligations.

6. AI reviewer

Second Opinion and MCP Overwatch text is sent to Cloudflare Workers AI to generate a critique and is not stored in our D1 database. We reject common credential formats before the model call. Aggregate telemetry contains the feature, model ID, status, token counts, latency, estimated list-price cost, timestamp, optional usefulness category, and whether the user would use the reviewer again—not the submitted text, email, or Clerk user ID. MCP Overwatch also stores your monthly review count so we can enforce the plan allowance. Detection is not perfect, so do not submit secrets, sensitive personal data, or material you lack permission to process.

7. Browser-only tools

The lifecycle cost estimator and the exit test scorer run entirely in your browser. Nothing you type into them is sent to us, logged, or stored — there is no request to send it in. Their “Copy link to this result” buttons put your inputs after the # in the URL, the fragment, which browsers never transmit to a server. That link reproduces your result for anyone you send it to, so treat it as you would the worksheet itself: the exit test link contains the product name you typed.

8. MCP membership

For paid MCP access, we store your Clerk user ID, Stripe customer and subscription IDs, subscription status, and a one-way hash plus short prefix of your access token. We do not store the plaintext token.