What Brandon ThinksWhat Brandon Thinks
  • Meet Brandon
  • How it works
  • Sample report
  • Pricing
  • My reports
What Brandon ThinksWhat Brandon Thinks
What Brandon Thinks

For entertainment and reflection—not diagnosis or professional advice.

Product

  • Read my chat
  • Meet Brandon
  • Sample report
  • Pricing

Analyzers

  • WhatsApp
  • iMessage
  • Relationship

Company

  • About
  • Contact
  • Updates
© 2026 What Brandon Thinks
Raw conversations are never public content.
·PrivacyTerms
Fazier badgeVerified on DANG!AiTop10 ToolsLovable App Badge

Privacy Policy

How What Brandon Thinks handles chat data, reports, accounts, and payments

2026/07/13

The short version

What Brandon Thinks needs the conversation text to generate a report, but our application does not store the raw chat in D1, R2, application logs, or emails. We store the participant information you confirm, a keyed source fingerprint, the derived preview and full report, and evidence message IDs.

This is not a claim that the request leaves no trace anywhere. Report generation uses Kie.ai, whose currently published policy says text and metadata log records are kept for 2 months and then automatically deleted.

Chat processing

  • Pasted text and WhatsApp TXT exports are parsed in your browser.
  • After you consent, the current parsed conversation is sent over HTTPS to our server and then to Kie.ai for the generation request.
  • Kie.ai runs Claude Sonnet 4.6. We instruct the model to paraphrase patterns, avoid diagnoses, and cite only source message IDs.
  • Once processing finishes or fails, our application discards the raw request object. The database has no column for raw message bodies.
  • The deterministic local pattern engine is used only in development and E2E; production does not silently replace a failed Kie request with a local report.

Kie.ai's current data retention policy says log records containing text or metadata are retained for 2 months. That third-party policy may change, so we review it before material provider changes.

Accounts and reports

Google provides account authentication. We receive basic account details such as your name, email address, and provider account identifier. A guest report is claimed by your account when you sign in before checkout.

We keep derived reports, private share-link hashes, and entitlement state so you can reopen your history from the signed-in private report library. We do not send report-delivery emails.

Payments

Stripe processes checkout and payment details. We do not receive or store your full card number. We keep Stripe customer, Checkout, invoice, payment status, amount, currency, and report entitlement references for fulfillment, refunds, fraud prevention, and financial audit needs.

Deletion and retention

Deleting a report removes its derived preview and full report, share links, and entitlements. Deleting an account removes reports claimed by that account. Payment records may be retained where reasonably required for financial, tax, dispute, and legal obligations.

Kie.ai controls deletion of its own provider logs under its published retention policy. Deleting a report here does not accelerate that separate schedule.

Security and access

Guest ownership uses an HttpOnly SameSite cookie and a keyed HMAC. Share tokens are stored only as hashes and expire after seven days. User and administrator pages require authenticated authorization; the administrator report view shows derived data and operational status, never raw chat.

No internet service can promise absolute security. We use reasonable technical and organizational safeguards and limit stored content to what is needed for the product.

Contact

Questions or deletion requests can be sent to hello@whatbrandonthinks.net.