Your work. Your choices.

Account: email, display name, handle, profile settings and authentication records. Google or Apple shares the details you authorize; we do not receive your password for those services. Email/password accounts store a password hash.

Creative work: prompts, reference files, audio, lyrics, artwork, voice/persona material, editor and Studio projects, Spaces conversations/artifacts, video configurations, shot references and finished exports.

Activity: generation status and costs, credits, plays, likes, follows, publishing jobs, consent records, support requests and operational/security logs. Account operations may include IP address, browser details and approximate location derived from network information.

Configured services such as MusicGPT, Kie.ai, Google Gemini and OpenRouter may receive the prompts, lyrics, references or media needed for the operation you request. Catalog voice selection and voice conversion may send the selected voice identifier and supplied audio or lyrics to MusicGPT. Music generation, lyric assistance, quality checks, Spaces and AI music video workflows can use different services.

Provider credentials stay on the server. Provider retention and processing follow their policies. Do not submit sensitive material you lack permission to process. Browser lyric-video rendering happens locally; saving projects, fetching assets, optional AI assistance and uploading exports use the server.

Visibility is controlled by the publication settings of the song, Space or video. Public content and creator details can appear on public pages and discovery feeds. Unlisted videos and Spaces are accessible to anyone with the link. Share only material you intend others to access.

Uploaded references and unpublished drafts are used for your requested workflow. A reference may be supplied to a provider when needed. External publishing sends the selected media and metadata to that platform under the visibility you choose.

When you authorize an integration, we store the platform account/channel identifier, name, handle, avatar, granted scopes and encrypted access/refresh tokens. We use them to identify your destination, refresh authorization and send the media or post you approve. Publishing history includes progress, post IDs/URLs, errors and your consent record.

Solimar uses YouTube API Services. See Google’s Privacy Policy. You can disconnect YouTube in the app and revoke Solimar’s access in Google account permissions. Other connections can be removed from Connected accounts.

Disconnecting removes stored connection credentials. Minimal publication/audit records may remain for troubleshooting and accounting. Ask through Contact to delete associated platform data. Posts already published remain on the platform until you remove them there.

A referral link includes the inviter’s code. A first-party cookie keeps that code for up to 30 days, including when a visitor starts on a shared song, video or Space. The most recent invite replaces the previous code. Creating a share link does not publish private work or issue credits.

On signup, we record the inviter and new account, code, dates, reward status and ledger entries. Referral abuse checks use salted hashes of the signup IP and a user-agent/language signature, plus normalized account email. Referral records do not store the raw IP or browser signature; other operational logs can include IP information.

Inviters see masked friend handles, dates and progress, not friend emails or network hashes. Staff can review full records and disputed eligibility. Removing browser cookies prevents attribution; past credit/accounting records may still need to be retained.

Account, project and ledger metadata are stored in PostgreSQL, with Neon in configured deployments. Uploaded and generated files use Vercel Blob. Upstash Redis supports queues and caching when configured. Vercel hosts the application. Stripe processes configured payments under its own privacy policy.

We do not sell personal data. Service providers receive what is needed to operate the selected feature. Processing can occur outside your country according to provider infrastructure. We retain work while it is saved to your account and records needed for accounting, security or resolving disputes. Backups and third-party copies may outlast deletion from the interface.

• Edit profile and preferences in Settings.
• Change publication settings and delete saved work through its page or Library. Trashed songs can be restored or deleted permanently.
• Disconnect platform accounts and revoke their authorization with the platform.
• Export finished work and clear local browser data.
• Request account/data access, correction or deletion through Contact, including data the interface does not remove.

Access to work is protected by authenticated ownership checks; public/unlisted material follows the visibility you selected. A published copy on another service must be managed there.

Use Contact for privacy requests or concerns. This page describes current processing; changes are dated here. The cookie page lists authentication, integration and referral storage.