Privacy Policy
This draft policy explains how Omni UI handles account, email verification, component build, and generated preview data while providing the service.
Last updated: May 12, 2026
Information We Process
Omni UI may process account identifiers such as email address, user id, role, account status, verification events, session metadata, and account deactivation or reactivation records.
When you use component build features, we may process submitted source code, uploaded files, dependency lists, framework versions, environment keys and values you provide, build options, logs, generated artifacts, screenshots, and preview URLs.
How We Use Information
We use account and verification data to register accounts, send activation or login verification codes, sign users in, refresh sessions, deactivate accounts, and reactivate accounts.
We use submitted component data to queue builds, run framework-specific tooling, generate web previews, provide artifacts, debug failures, improve reliability, and protect the platform from abuse.
Email and Authentication
Email is used as the primary account and verification channel. Verification codes are intended to confirm control of the mailbox before account creation, sign-in, or reactivation.
Access tokens and refresh tokens are used to maintain authenticated sessions. In the current web client, session data is stored locally in the browser so the app can call authenticated backend APIs.
Retention and Deletion
Account deactivation clears the active session and disables the account lifecycle from the user interface. Some operational records may remain for security, auditability, abuse prevention, diagnostics, billing, and service integrity.
Build inputs, logs, artifacts, and previews may be retained for a limited period to support task status, debugging, and result retrieval. Retention windows may change as the product matures.
Security Practices
Avoid submitting secrets, production credentials, private keys, personal data, or sensitive third-party assets in component source files, environment values, dependency lists, or build configuration.
We may inspect build and account activity to protect the service, investigate abuse, resolve incidents, and maintain reliable preview infrastructure.
Related Terms
Review the Terms of Service for the rules that apply to account access, component builds, and web previews.