Privacy Policy

Account information and service data

Authentication is provided through Clerk. Account identifiers, supplied profile details and preferences are used for account access and workspace features.

Depending on the tools used, Smili processes prompts, conversations, uploaded documents and media, generated outputs, characters and voice references, bookmarks, memories, workflow and project data, and credit-usage records. Technical and operational records support service operation, security, troubleshooting and abuse prevention.

Third-party processing

Requests and relevant uploaded references are sent to the selected AI provider or processing service to carry out the requested task. Providers depend on the selected tool and model. Integrations include services from OpenAI, Anthropic, Google, BytePlus, Replicate, ElevenLabs, Kling and others; availability can change.

Hosting and database services, Clerk, and Google Cloud Storage also process information for service operation. Processing may occur outside your country. Website fonts are loaded from Google Fonts and Fontshare/CDN services, which can receive technical connection information when pages are opened.

Provider retention, training use and processing terms can differ. Smili does not promise that every provider retains nothing or never uses submitted content for training. Do not upload personal information, confidential materials or voices and likenesses without authority.

Storage, sharing and retention

Account-linked records and saved content are stored in the application database. Uploaded and generated media can be stored in cloud object storage or provided through AI-provider URLs. Some stored media is served through public object URLs; possessing a media URL may permit access.

Shared chat and presentation links are intentionally viewable without signing in. Avoid sharing content links containing information you do not intend others to see.

Saved application content is stored in your account unless deleted or removed through applicable lifecycle or account-deletion processes. Turning off chat history is not a zero-retention or zero-processing mode: temporary chat records can exist during use and are subject to lifecycle cleanup and expiry.

Operational records, backups and external-provider data can have retention periods separate from saved application content. Account controls do not promise immediate deletion of all such records. Contact support with questions about retention or a particular deletion request.

Controls and deletion requests

Settings provides controls for saved history and account deletion. Account deletion uses a recoverable process across Clerk, local account data and inventoried owned storage objects. Partial cleanup can remain pending and be retried.

Deletion does not recall exported content, copies made by recipients, or independently retained external-provider data. Contact primary support for access, correction, deletion or privacy questions. Requests may require identity verification; do not email passwords or verification codes.

Applicable privacy rights remain available. This information does not limit rights you may have under applicable law.

Browser storage

Cookies and local or session storage support sign-in, security, preferences and application state. Third-party services have their own processing practices. See Cookies information and contact primary support about privacy questions.