Optional voice reference
You can also choose an audio file from your device and select a 10–30 second clip on its waveform. Reading and trimming happen in your browser without microphone access. The original file is not uploaded: only the selected clip is sent when you save it or generate a song, under the same recording rules below.
When you choose Record my voice (BETA), you authorize microphone access for that recording. The accepted audio stays in your browser until you request music generation or choose to save it for future use. Either action sends it to Somora over HTTPS. The recording is used as a vocal reference by the generation equipment and is not sent to the ChatGPT composition assistant.
Saving the recording is optional. Saved voices are available in your account to preview and select for new generations until you remove them from your library. Authorized administrative staff may also access these recordings for support and platform operations. Removing a saved voice prevents its use in new requests, but does not delete earlier requests or songs already generated. Recordings linked to those requests may be retained for history recovery; you can request deletion of this data through support or our public email address.
The original recording has restricted access and does not appear on a public page. The synthesized voice in the resulting song may be heard in previews and on its individual page under the publication policy below. Temporary recordings that are neither saved in your library nor linked to a request are removed after 48 hours.
Rewarded ads on Android
In the Android app distributed through Google Play, you may choose to watch an ad to receive one extra music generation and one AI composition, subject to availability and the limit displayed in the app. Ads are optional: declining or closing them does not prevent normal use of your plan. Credits belong to your account and are granted after completion is confirmed; they are not money and cannot be transferred.
This feature uses Google AdMob and the Google Mobile Ads SDK. Google may collect and share IP addresses, from which approximate location may be inferred, device or advertising identifiers, app and ad interactions, and diagnostic information to provide and measure advertising and prevent fraud. Available options depend on your region, permissions and privacy choices. Where required, we display a consent message before requesting ads. You can review your choices through Ad privacy preferences in the app and Android advertising controls.
To grant credits without duplication, Somora records an attempt linked to your account, its status and completion dates. Ad confirmation uses random attempt identifiers and a provider transaction. We do not send passwords, email addresses, song lyrics, voice recordings or support messages through this advertising integration. Reward records are retained to reconcile balances, respond to requests and prevent abuse, under the retention rules and rights channels described in this policy.
See also Google’s Privacy Policy and Google’s advertising controls.
Android notifications
The app can notify you when a song is ready, generation fails or there are support updates. Enabling these alerts is optional. You can control permission and notification categories in Android settings; this does not prevent viewing notifications within your account.
We use Google’s Firebase Cloud Messaging to deliver alerts. Somora associates an installation identifier and a device delivery token with your account and authenticated session. Google processes this token and technical data needed for delivery. The content sent through this integration contains only notification and device binding identifiers: voice recordings, song lyrics and support messages are not sent to Firebase Cloud Messaging.
When an alert arrives, the app uses your session to retrieve authorized content from Somora’s API, such as the song title or ticket subject. Signing out revokes that session’s binding and clears local alerts. Expired sessions stop receiving new alerts, and cleanup routines remove their bindings. Notification history within the account remains separate from these delivery bindings. Delivery also depends on connectivity, device settings and a valid session.
Account and access data
We process your name, email, account identifier, plan information and authentication records. Google sign-in provides a profile identifier, name, email and email verification status. Passwords for direct registration are stored as hashes, rather than readable text.
Songs, support and payments
We process the parameters you submit, including title, tags, lyrics, language, duration, BPM, key and seed, as well as audio files, request history and progress. Tickets, messages and notification read records support customer service.
We also record purchases, payment status, amounts, plans, payment references and referral credits. Checkout sends the information needed for a transaction to Mercado Pago. Full card numbers and security codes are handled by the payment integration; in the Mercado Pago integration, card tokens and identity documents passed to the API are not persisted in our payment records.
For subscriptions purchased in the Google Play app, Google processes the payment. Somora retains purchase identifiers, product, status, access period and verification token to validate, restore and track the subscription; it does not receive the card number or security code used in Google Play. The Android app uses the same account, music and support features as the website.
What is public
Completed songs are automatically published on individual pages with permanent addresses and full-track playback. These pages display the creator’s public name, title, lyrics, tags, duration, BPM, key, language, seed and creation and completion dates, according to the available song data. The platform’s homepage may display title, tags, duration and a preview of up to 30 seconds among recent songs. By generating a song, you authorize this automatic publication; avoid confidential information in this content.
Your account contact details, payment information, support tickets and messages are restricted to your account and authorized administrative access. Downloading the original file from the library requires account or administrator authentication and authorization.
Somora Feed data and posts
Somora Feed, at feed.somora.media and in the Android app, uses your existing Somora account. For authentication and access control, it receives the account identifier and name, plan and necessary permissions. It uses its own session and cookies, linked to the original session through server-to-server authorization; your password is not transferred to Feed. Your browser also stores the language preference.
Your artist profile is created when you sign in to Feed and can be edited. Feed stores the profile data you configure, including @handle, public name, biography, links, styles, photo and cover; posts, selected music, comments, replies, quotes, likes, reposts, votes, playlists, challenge entries and collaboration credits. Profiles, posts and interactions displayed in the community may be seen by others, including visitors. Playlists marked private, your bookmark list, blocks, mutes and reports have restricted access. Aggregate interaction counts may be displayed without exposing your private bookmark list.
Posting a song to Feed is your choice. A library item imported to prepare a post remains restricted within Feed until you publish; a published track can be heard in full. Lyrics, tags, preset and seed appear in a Feed post’s creation details only when you choose to share them. This does not change the automatic publication of a generated song’s individual Somora page, described above. Removing a Feed post does not automatically delete the song from your library or its original page.
Your chosen permissions control downloads and new remixes. Sharing a Kassio project sends a copy of the project and the audio needed to view it; allowing editable copies makes it possible to create a copy in another account. Promotional clips include the selected excerpt, title, public name and Somora branding. Copies and files already obtained with your authorization, including material posted outside Somora, are not automatically recalled when you change a permission or delete a post.
To operate the community and provide private artist analytics, we record plays, playback positions and listening time, as well as interactions. The technical feed_visitor cookie may last for up to 30 days. Listen counting uses a daily pseudonymized identifier derived from the account or browser identifier, together with the track and playback data; this is not a promise of anonymity. The artist dashboard presents aggregate metrics, without a named list of listeners.
This data supports profiles and timelines, playback, collaboration, abuse moderation and support. You can edit your profile, delete your own posts and adjust permissions. Requests about other data or account deletion can be made through support or the contact in this policy. Deleting the original account invalidates authenticated Feed access; synchronization also disables the profile and removes its posts from public view. The retention, protection, backup and rights procedures described in this policy apply.
Purposes and legal grounds
We use data to create and protect accounts, fulfil generation requests, deliver files, process payments and credits, provide support and meet legal obligations. Depending on the purpose, processing may rely on contract performance, legal obligations, assessed legitimate security interests or consent where required.
Cookies and navigation data
A session cookie keeps you signed in. Your browser may also store preferences such as language. The website, including when accessed through the Android app, uses Google Analytics to understand navigation; the tool may use cookies and process technical information about devices and visits.
Our integration does not send password fields, ticket messages, lyrics or private identifiers as analytics events. Public support, privacy and terms pages do not load Analytics. Browser settings allow you to manage cookies and storage; blocking the session cookie prevents persistent sign-in.
Providers and sharing
Necessary data is processed by hosting and storage providers such as DigitalOcean, Google for sign-in and analytics, Mercado Pago for payments, and the email service configured for account messages. When you use Fill with AI in Advanced mode, we send the song name, theme, language, style and duration to OpenAI to prepare lyrics and the musical description. You can review this result before submitting a music generation request. In Easy generation, we send your free-text description, default language and plan limits to prepare the composition. When you click Generate music in Advanced mode, if the assistant is enabled and configured, we send the title, musical description, lyrics, language, duration, BPM and key to OpenAI to correct the description and section structure before generating audio. This also applies to fields written manually or prepared with Fill with AI. This review asks for minimal changes, may correct sung lines and does not send your voice recording. If the service is unavailable or returns an unusable response, generation continues with your original text. Sharing is limited to each function and applicable legal requirements.
These providers may process information in other countries. Where applicable, international transfer mechanisms and safeguards required by data protection laws must be observed. Please also consult these providers’ policies.
Retention and protection
We keep data needed for account operations, music history and support, as well as legally required records. Deletion requests are assessed in light of those purposes, legal retention and backups; we do not promise immediate removal of every record.
The service uses access controls, permission checks, password hashes and HTTPS in production. Contact us if you identify account misuse or exposure of personal data.
Your rights and contact
You may request confirmation of processing and access, correction, sharing information, portability where applicable, eligible deletion or anonymization, objection and withdrawal of consent. Use our public email or a ticket; appropriate identity verification may be requested to protect your account.
JK Desenvolvimento Web receives requests at [email protected]. You may also contact Brazil’s National Data Protection Authority (ANPD) or other competent authorities as provided by applicable law. This policy may be updated; the date on this page identifies the published version.
Hotmart payments and affiliation
When you choose Hotmart checkout, your verified Somora account email may be sent to prefill the checkout, together with an opaque reference used to associate the purchase with your account. Hotmart directly collects the data required by its checkout and processes payment under its own privacy policy. This integration does not send songs, voice recordings, lyrics, prompts or workflows to Hotmart and does not receive full card numbers or security codes.
To recognize the first sales channel before registration, the API may use the technical somora_billing_visit cookie for up to 365 days. It holds a random identifier, is inaccessible to JavaScript, and recognizes the same browser across both sites through the shared API. This visit record stores only a hash of that identifier, the channel, creation time and expiry, without an IP address, name or email. At registration, the channel is associated with the account to determine future payment methods and remains while the account exists. After registration, the association no longer depends on the cookie. Before registration, blocking or deleting cookies or changing browsers may prevent first-visit recognition. This record does not change existing accounts or subscriptions.
To deliver and track access, Somora records the account association, checkout reference, product, plan, transaction and subscription identifiers, amount, currency, status and paid access period. Payment notifications are verified and technical records retain only fields needed to operate the service; this integration does not persist buyer names, emails, phone numbers or identity documents received in those notifications, or detailed affiliate financial payloads.
If you apply for a partnership, we process the ticket containing your channels and the Hotmart email you provide to review your request and identify your application. Hotmart handles data necessary for affiliation and commission payments within its program. Tickets are restricted to your account and authorized staff. The purposes, safeguards, retention rules and rights channels described in this policy apply.
Music uploaded for Remix
Selecting a song in the Remix tab requests its upload to Somora and OpenAI for audio analysis, lyric transcription, and musical description and language suggestions. This is separate from the optional voice reference recording, which remains restricted to Somora generation processing. Only send files you have the right to upload and avoid confidential content.
The original song is stored with restricted access and provided to the generation equipment to produce the remix. Somora may convert a copy for analysis while preserving the original bytes. Uploads not linked to a generation request are removed after 48 hours by cleanup routines; those linked to your history remain available for request recovery. Request deletion of your data through Support or the public contact channel.
Identified lyrics and musical characteristics are editable suggestions and may contain errors. The analysis and original upload are not automatically published. When you generate a remix, the resulting music, title, lyrics and other parameters follow the music publication rules described in this policy.
Somora operator
JK Desenvolvimento Web
CNPJ: 49.553.853/0001-40
Public contact: [email protected]