Privacy at UniSee
This page explains the main categories of information UniSee processes when users create, publish, remix, and manage work inside the product.
What we collect
UniSee may collect account information, billing information, usage history, prompt inputs, uploaded assets, generated outputs, project metadata, and public profile or publishing data that users choose to make visible.
We may also collect device, browser, request, and operational telemetry needed to secure the product, prevent abuse, diagnose failures, and improve service reliability.
How we use information
UniSee uses information to provide generation, project management, publishing, remix, billing, support, moderation, security, and product improvement functions.
Public projects, remix lineage, creator profiles, and related discovery surfaces may display information that users explicitly publish into the public product experience.
Public vs private content
Private work should remain visible only to the owning user and authorized product systems. Public work, remix-enabled work, creator profile information, and discovery surfaces may be visible to other users and search engines once published.
Users should review project visibility and remix settings before publishing any work.
Billing and service providers
UniSee may use third-party providers for authentication, payments, infrastructure, storage, analytics, and generation services. Payment information is typically handled by the payment provider rather than stored directly by UniSee.
Data retention and deletion
UniSee may retain account, billing, project, and operational records for security, fraud prevention, legal compliance, dispute resolution, and product continuity.
If you need account or content deletion support, use the contact details on the support page.
Contact
Privacy questions, deletion requests, and support requests can be submitted through the contact and support page.