Privacy
What this site processes, which services receive it, and the choices you control. This policy covers benlive.tv, its AI tools, and Port.
Your analytics preference
For this browser
Checking your current setting…Manage optional analytics without changing access to the site.
Analytics are enabled by default. The site's “Analytics” privacy-settings link displays this preference. Opting out stops new analytics capture; it does not delete earlier events or stop processing needed to deliver the site, answer an AI request, or operate an account.
Your choice is kept in this browser's local storage. Make the choice separately on each browser or device. Clearing site data resets it to the default. If storage is unavailable, a change applies for this page visit but may not survive a reload. The analytics SDK is configured to respect Do Not Track; browser settings and blockers may prevent collection even when this preference says “On.”
Analytics & site improvement
PostHog helps Ben understand which pages and features are useful and where the experience breaks down. The shared integration records page views and selected interactions, such as navigation, project links, calls to action and outbound links. General click and input autocapture is disabled.
- Visit and device information
- Events can include timestamps, page URLs, referrers, browser and device details, screen dimensions and IP-derived location. Location estimates may be more specific than a country. URLs and referrers may include query parameters.
- Browser identifiers
- PostHog uses cookies and local storage to recognize a browser and link visits. The site does not deliberately identify analytics visitors with their name or email, but persistent identifiers make this data pseudonymous rather than fully anonymous.
- Chat engagement
- Selected events report chat use, preset question selection and resets. Chat messages, prompts and AI responses are excluded from the site's custom analytics events. Processing the conversation itself is described below.
- Presentation replay and feedback
- Context First and Prehog additionally enable session replay, exception reporting, feature flags and optional surveys. Replay records page interactions and rendered content; input values and marked sensitive areas, including chat dialogs, are masked. Survey answers, including any optional written response you submit, are sent to PostHog. Masking a field in replay does not mask a submitted survey answer. The shared integration disables replay on other pages.
Analytics requests pass through t.benlive.tv to Ben's PostHog project. Using a site subdomain does not mean the data stays on your device or avoids a third-party processor. The SDK is downloaded from jsDelivr. See PostHog's privacy policy and data-storage information.
AI questions & working content
When you use an AI feature, submitted text and relevant conversation history are sent through Firebase Functions to OpenRouter and the model provider serving the request. The site adds instructions appropriate to the tool. A fallback provider or model may serve a request if the first attempt is unavailable. This processing is separate from analytics and still occurs when analytics is off.
The main chat keeps its conversation in page memory. Some tools, including Promptpad, Agent Agenda and Problem Solver, save working state in this browser's local storage. Model preferences may also be saved. Resetting a chat or clearing browser storage does not delete records already held by a provider or infrastructure service.
Operational logs include request, model, timing and error details; upstream error responses can also enter diagnostic logs. Do not submit secrets or information you cannot share with the services processing your request. Provider retention and use of content depend on the service and account settings; this site does not promise zero retention or exclusion from model training. See OpenRouter's privacy policy and the selected model provider's terms.
Port accounts, devices & community
If you sign in to Port, Firebase Authentication and Firestore process account identifiers, email, display name, profile photo and your chosen handle. Connecting a device stores its name, capacity and status, operational snapshots, tasks and results, and connection records. Community posts, replies and reactions are stored and shared according to their audience and access controls.
Disconnecting a device removes its associated device records, snapshots and tasks and revokes its sessions. It does not erase your account, community content or audit records. Removing a handle is not account deletion. Contact Ben for account or data requests.
Storage, service providers & your choices
- Browser storage
- Theme, analytics preference, tool drafts, model choices and authentication state may be stored locally. Clear this site's data in your browser to remove local copies; that also clears preferences and may sign you out. The optional 3D scene runs in your browser. Its selected mode is saved in the tab's session storage so it can resume when you return to the landing page; switching back to 2D clears that choice. This appearance preference is not sent to a server.
- Hosting and security
- Firebase/Google Cloud and the site's network services process requests and operational metadata, including network addresses. API abuse protection uses a keyed hash of an IP address with request counters and timestamps. A hashed identifier is not the same as having no identifier. External fonts, scripts, embeds and links can connect to other services governed by their own policies. See Firebase's privacy information.
- Retention and removal
- Local data remains until the tool or browser clears it. Service-side retention varies across analytics, accounts, operational logs and AI providers; there is no single deletion period covering all of them. Analytics opt-out, device disconnection and local resets have different effects. Contact Ben to ask about access, correction or deletion, including which feature and approximate dates are involved. Do not send passwords or API keys with a request.
- Advertising and external contact
- This site does not use its analytics integration to sell data or target advertising. If you contact Ben by email or through an external service such as LinkedIn, that service also processes the information you choose to send.
Questions about your data?
Contact Ben McNulty at benmcnulty@live.com. Describe your request and the feature you used so the relevant records can be located.
Last updated: September 7, 2026. This policy may change as the site's features and services evolve.