Solice UI Privacy Notice

Solice UI processes the UI descriptions you submit and UI Profile data you explicitly approve to return Pattern candidates and implementation packages. Queries, UI Profiles, candidates, selections, parameter choices, PatternPackage requests, and derived packages are not saved as user history.

Search returns a signed short-lived technical context containing hashes and candidate identifiers so a later package request can be validated without storing the search. Browsing and previews remain anonymous. Complete component code and Prompt packages require a verified Clerk account. Free accounts receive five distinct successful packages per UTC day; equivalent retries do not consume another grant. The quota ledger stores only the verified Clerk subject, UTC day, opaque keyed fingerprint, and timestamps. It does not store the query, component ID, source, Prompt, UI Profile, parameters, or package payload.

Solice UI does not copy the login email into its product database. Web sessions, Codex-hosted MCP OAuth, and Helper OAuth use separate credentials and converge only on the same Clerk subject. Signed-in favorites store only the verified Clerk subject-to-component relation. Stripe customer references, Checkout state, signed-webhook deduplication, and paid-through entitlement records are stored only to operate Pro access. Card Pro renews automatically; Alipay Pro is a non-renewing 30-day or 365-day pass. Accounts with billing history use support-assisted deletion; eligible never-billed deletion removes favorites and quota grants before Clerk deletes the user and invalidates its OAuth grants. The product stores no uploads, arbitrary saved materials, or search/package history.

When the local Codex Helper user selects a component, it creates a readable Markdown reference on that Mac under ~/.codex/solice-ui/component-references/<patternId>/COMPONENT.md. This explicit local file contains the Solice UI component name, Pattern ID, owned preview address, and package-retrieval instructions so Codex can display and attach it. It contains no query, composer text, component source, credential, selection timestamp, or account identifier. The Helper refresh token is stored in macOS Keychain and access tokens stay in Helper Service memory; neither token enters the Codex renderer, Shadow DOM, CDP messages, logs, process arguments, or ordinary files. The user can delete local references by removing the component-references directory; selecting the Pattern again recreates its file.

The public soliceui.com website uses Google Analytics 4 for aggregate page and interaction measurement. Google consent mode defaults analytics storage, advertising storage, advertising user data, and ad personalization to denied, so Solice UI does not write Google Analytics cookies or enable advertising signals in the current configuration. The workspace at app.soliceui.com is not measured by this tag. UI descriptions, Clerk identity, account data, favorites, and PatternPackage contents are not sent to Google Analytics.

Do not submit passwords, access tokens, private keys, session cookies, or unrelated confidential source code. Solice UI rejects recognizable credential material. Infrastructure providers process transient request data only to operate the service; redacted operational logs do not contain raw queries or UI Profiles.

Contact: privacy@soliceapp.ai
Last updated: 2026-08-21