Try That UI

Privacy

Last updated 23 October 2026

The early-access form asks for one email address so we can notify you when access is ready. We do not sell or rent your address. This page also covers the hosted review workspace.

What we collect

When you join the list, the configured waitlist service receives your email address and the fact that it came from the marketing site. We do not ask for passwords, payment details, screenshots, or source code on this page.

How we use it

We use the address to manage the early-access list and send the promised access notification. We do not use it for advertising profiles or unrelated marketing.

Measurement

We use a first-party aggregate measurement service for bounded page and funnel events and may use Google Analytics 4 for public acquisition and conversion measurement. Analytics events never include an email address, page content, a source URL, or a query string. Google Signals and advertising personalization are disabled. Both systems honor Do Not Track, Global Privacy Control, and this browser’s opt-out below.

Your choices

You can request removal from the early-access list by emailing hello@trythatui.com. A later access email will also include an unsubscribe or removal path if one is enabled by the waitlist provider.

The hosted product

The paragraphs above describe this marketing site. The hosted review workspace at app.trythatui.com is a different surface, and this page is its privacy policy too. Signed-in workspaces can send and store the screens, screenshots, repository metadata, notes, experiments, and decisions needed to provide synchronization and review. Nothing is written to a connected repository without a separate, explicit approval. A signed-out mode identified as local in the product can keep its workspace state in that browser.

Information you provide in the product

You may provide an account email, screen URLs, screenshots, source references, repository selections, notes, experiment settings, feedback, and approval decisions. When you sign in or use a hosted feature, the product may transmit and persist the relevant workspace data so it can survive reloads, synchronize across devices, and be available to authorized workspace members.

Connected services and repositories

GitHub and GitLab connections use the scopes displayed during provider consent. Read access may be used to list repositories and inspect the repository or revision you choose. Repository write, pull-request, merge, and deployment operations are separate capabilities: they remain disabled unless configured and require the approvals shown in the product. Disconnecting a provider stops future access. Deleting provider-derived workspace data is a separate action.

The optional X Bookmarks feature uses read-only OAuth scopes to retrieve the connected owner's bookmarks and related public post metadata. Tokens are kept server-side. Imported rows remain private unless an authorized user deliberately submits an item for publication. We never ask for your X password.

Screenshots, rendering, and AI-assisted features

When you upload a screenshot or request hosted capture, rendering, source analysis, or proposal generation, the relevant image, page material, source excerpt, or instruction may be processed by our hosting, storage, sandbox, or configured model provider. The product identifies when external processing or consent is required. Do not submit secrets or material you are not authorized to process.

What the product records

We keep first-party aggregate records to understand whether people can start a review, add a source, inspect Current and Proposed, make a decision, use a browser handoff, connect a provider, and recover from errors. The allowlist contains page views with a coarse route, intent for named controls and surfaces, bounded funnel steps, bounded error categories, and job-latency buckets. We may group totals by a one-way server-side tenant hash, a coarse region, device class, and a human, bot, automation, or unknown traffic class. Counts in small cells are bucketed.

Those aggregate records do not include source URLs, repository names, page bytes, DOM, text, screenshots, cookies, auth or session ids, IP addresses, precise location, full user-agent text, query strings, hashes, secrets, provider identities, or free-form notes. Optional Clarity, GA4, or Cloudflare Web Analytics scripts on the product stay disabled unless the owner explicitly configures a public provider identifier and approval flag. Do Not Track, Global Privacy Control, and an explicit tenant or user opt-out suppress them before loading.

What we do not do

Service providers

Vercel hosts the service and processes ordinary request and server-log data. Supabase may provide account, database, and private object-storage services. GitHub, GitLab, X, WorkOS, Pipedream, Stripe, model providers, and analytics providers process data only when their corresponding feature is configured or used. Their own terms and privacy notices apply. The product reports which capability is actually enabled.

Retention and your control

Local browser data can be cleared or exported from that browser. Hosted workspace records are retained while needed to operate the beta, protect the service, and satisfy legal obligations. To request access, correction, export, or deletion of hosted account data, email hello@trythatui.com. We may need to verify the request before acting on it.

Security and children

We use access controls, signed sessions, tenant boundaries, private storage, bounded provider permissions, and operational monitoring. No service can guarantee absolute security. Keep credentials out of screenshots and notes. Try That UI is a professional tool and is not directed to children under 13.

Changes

If this policy changes materially, the date above will change. Questions can be sent to hello@trythatui.com.

← Back to Try That UI · Terms · About · Built by Mike Yerke