Information the product handles
The product handles different information depending on whether you browse public pages, create an account when account access is available, join a discussion, save a trend, or contact support.
- Public browsing and product analytics: the route you visit, the page URL limited to its origin and path, signup button source, authentication method and outcome, product value and error states, rage-click signals, and one bounded tracking-interest category if you choose to answer the in-product question.
- Account information when enabled: email address, password authentication material, display name, OAuth provider identity, account identifier, and session information handled through Supabase.
- Public discussion when enabled: message body, account identifier, display name, trend, timestamp, moderation provider and labels, and whether the message is visible or removed.
- Public source records: source name, public source or community label, title, bounded excerpt, source URL, engagement and audience counts where available, timestamps, and available country metadata from official or permissioned feeds.
- Support: the sender address, message, and any information you choose to include when you email the support mailbox.
Privacy-scoped analytics
The current site uses PostHog to understand whether visitors reach important product steps. Privacy-masked session replay and rage-click detection are enabled. Broad click autocapture, automatic page-leave capture, and exception capture are discarded or disabled.
Recordings mask all readable page text, all inputs, and element attributes, and do not capture request or response bodies. Analytics removes query strings and URL hashes from automatic URL fields. It does not send form values, passwords, email addresses, display names, chat message bodies, or written survey responses. If account access is enabled and you sign in, the analytics session is identified by the Supabase user ID rather than by email or display name.
How information is used
The current product uses this information to serve public pages, operate authentication and recovery when connected, maintain sessions, show an author name beside public discussion, moderate and deliver chat, generate source-linked trend explanations, diagnose failed product steps, and understand whether the product journey works.
Saved trend slugs are stored in your browser so the saved view can work without an account. The product does not currently include advertising or a mechanism for selling account or analytics data.
Services that receive information
The product relies on the following services for the functions described here. A provider receives information only when the relevant function is used or configured.
- Vercel serves the site and handles normal web requests needed to deliver it.
- Supabase handles account authentication, sessions, and the application database when the production connection is enabled.
- Google, GitHub, or Apple participates in the authentication exchange only when you choose that OAuth provider; the product receives the identity and profile information returned through Supabase.
- PostHog receives the limited product analytics events described above.
- OpenAI receives a chat message body when OpenAI moderation is configured; otherwise moderation uses a local blocklist. OpenAI also receives source and trend context when the Why Layer explanation service is configured.
- Tin Computer's managed mailbox receives the contents of support email you choose to send.
Public discussion and browser storage
Visible chat messages and their display names are readable by anyone. Do not post private or confidential information in a trend discussion.
Saved trend slugs stay in local browser storage. You can remove an individual save in the product or clear the site's browser storage. Native sharing uses your browser or device share sheet; the clipboard fallback copies the public URL on your device.
Your choices and deletion requests
You can browse the public product without creating an account. You can choose whether to use Google, GitHub, Apple, or email authentication when account access becomes available. You can also choose not to post in public discussion or contact support.
There is no self-serve account deletion control in the current product. To request access, correction, or deletion of account-associated information, email whatshappeninginai@mail.tin.computer. Include enough information to locate the account, but do not send a password or OAuth token.
Changes and contact
This page will be updated when current product practice changes. Questions and information requests can be sent to whatshappeninginai@mail.tin.computer.