Privacy policy
What Dissy collects when you make and share tracks, why, who else handles it and how to get it deleted.
The short version
- Drafts and takes you have not published stay on your phone.
- To write lyrics and covers, your topic goes to the AI providers named below. The app asks before the first time.
- We don't sell your data, show ads or track you across other apps and sites.
- We never store your IP address, other people's songs or screenshots of your chats.
- Usage statistics are sent only if you say yes.
- You can delete your account in the app at any time: how it works.
Who is responsible
Dissy is made by Siarhei Sheleh, the developer of the Dissy app on the App Store and of dissy.fm ("Dissy", "we", "us"). We decide how your personal data is used, so we are its controller under the GDPR and the UK GDPR.
Contact for anything about your data: privacy@dissy.fm. Postal address: on request at legal@dissy.fm.
What we collect and why
| Data | What exactly | Why | Legal basis |
|---|---|---|---|
| Device | a random device token, an App Attest key that proves a real copy of the app on a real iPhone, two DeviceCheck bits that Apple stores for us | keep your guest account, protect the free track and rewards from abuse | contract; legitimate interest in preventing fraud |
| Account | the identifier and email address Sign in with Apple shares (often a private relay address), your artist name; Google sign-in or an email code when we offer them | sign you in and keep your tracks with you on a new phone | contract |
| Age group | only the group: under 13, 13 to 15, 16 to 17 or 18+, and where it came from; your birth year stays on your phone | apply the age rules below | legal obligation; contract |
| What you make | tracks, voice recordings and videos you publish or send by link, lyrics, titles, covers, avatar, bio | store, play and show what you share | contract |
| Requests to AI | the topic of a track, lyric lines, requests to the assistant, a photo you attach for a cover | generate lyrics, beats, covers and edits | contract; your consent to send them to AI providers |
| Purchases and coins | Apple's signed records of your purchases and subscriptions (product, transaction number, price, currency, dates, refunds) and your coin history | give you what you paid for, handle refunds | contract; legal obligation (accounting) |
| Social activity | follows, blocks, Fire you send and receive, replies, collab invites, notification settings, the push token of your phone | run these features | contract |
| Listening | plays of each track, and for counted plays a pseudonymous listener key | play counts, charts, artist milestones | legitimate interest in fair charts |
| Safety | reports you send (reason, text, a reply email if you give one), appeals, moderation decisions on your content, a log of which moderator opened it | keep Dissy safe and meet our legal duties | legal obligation; legitimate interest |
| Anti-fraud signals | a code made from your network prefix with a key that changes every day, the network type (home, mobile, data center), the country, how many accounts used one device | stop fake plays, fake accounts and abuse of rewards | legitimate interest |
| Server logs | request number, route, result, timing, the model and its cost; no request text and no IP address | run Dissy and fix errors | legitimate interest |
| Usage statistics | events such as "track ready" with a random install number, screen, app version and language | see what works and what to fix | consent |
| Messages to us | what you write to our addresses | answer you | contract; legitimate interest |
Anti-fraud signals are described here by kind on purpose: publishing exact thresholds would help people get around them.
What stays on your phone
- Drafts and takes you have not published. We don't copy them to our servers.
- Your birth year, if you typed it in.
- Topics you dictate: speech recognition runs on the phone.
- The camera and microphone work only while you record.
What we never collect or keep
- Your IP address. Cloudflare, which delivers every request, sees it; our code uses it only in memory to limit requests and to make the daily anti-fraud code, and never writes it down.
- Other people's songs. A reference track is turned into a few style numbers and deleted right after.
- Screenshots of your chats. Only the facts you choose to keep are stored.
- Voiceprints or face templates. Your voice is used to make and moderate your tracks, never to identify you.
- Your contacts, precise location or advertising identifier.
AI providers
Lyrics, covers, beats and the assistant are made by AI models. When you make a track, your topic and lines go to the model that writes for you. Before the first generation the app asks for your OK and names the providers.
| Provider | What it gets | What for |
|---|---|---|
| OpenRouter | your request, passed on to the model | routes requests to the model vendors below |
| Anthropic | topic and lines | writes lyrics by default |
| Moonshot AI, Z.ai, DeepSeek, Alibaba (Qwen), Xiaomi | topic, lines, assistant requests, text and images for safety checks | backup lyric writers, the assistant, beat and cover prompts, safety checks |
| the cover description made from your topic | covers | |
| fal.ai | style numbers or a picture description | model-made beats and covers, when switched on |
| ElevenLabs | your recording | studio clean-up of your voice, when switched on |
| Cloudflare Workers AI | the recording of a track you publish | a transcript for safety checks |
Test builds let you pick other models in Settings; the vendor of each model is named next to it.
We don't use your recordings, lyrics or topics to train AI models. Providers get them only to answer your request.
Who else handles your data
We use service providers that process data for us under contract:
| Provider | Role |
|---|---|
| Cloudflare | hosting, databases, file storage, delivery of the app's requests and of this site, email sending, bot checks, detection of known child sexual abuse material |
| Apple | Sign in with Apple, App Attest, DeviceCheck, purchases and subscriptions, push notifications |
| the AI providers above | generation and safety checks |
| DigitalOcean | the server of our usage statistics (Aptabase, run by us) |
Other recipients:
- Other people see what you publish: everyone for public tracks (18+ only), anyone with the link for link tracks.
- Authorities and child-safety bodies such as NCMEC, when the law requires it or a child is in danger.
- A buyer or successor, if Dissy is sold or reorganised, under this policy.
We don't sell your personal information and don't share it for cross-context behavioural advertising. There are no ads and no advertising or tracking tools in Dissy.
Transfers outside your country
Our providers work in many countries, including the United States and China. When data leaves the European Economic Area or the United Kingdom, we rely on the European Commission's standard contractual clauses, the UK addendum to them, or the EU-US Data Privacy Framework where the provider is certified. Write to us for a copy of the safeguards.
How long we keep it
| Data | How long |
|---|---|
| your account | until you delete it; deletion is done within 30 days, most of it within a day |
| published tracks and files | until you delete the track or your account; files of a withdrawn track are removed within 7 days |
| topic and inputs of a generation | 7 days after the job ends; results 30 days |
| raw plays | 35 days; the network code inside them 7 days; the daily key 48 hours |
| listener device key | up to 90 days |
| unpicked collab takes | 30 days |
| reports, moderation cases and appeals | 1 year, then names and texts are removed |
| moderation decisions | 400 days, for transparency reporting |
| evidence of child sexual abuse material | 1 year, as the law requires |
| anti-fraud cases | 180 days |
| device signals without personal data | 365 days after the last change |
| invite codes | 30 days, then 90 days for anti-fraud |
| server request log | 90 days |
| sign-in sessions | up to 180 days |
| purchase and coin records | as long as tax and accounting law requires; after you delete your account they keep no name, email or device |
| backups | up to 400 days; used only to recover from failures |
| usage statistics | as long as we need them to compare app versions; they carry no name and no account |
Your rights
Depending on where you live, you can:
- get a copy of your data and receive it in a portable format;
- correct it or have it deleted;
- object to uses based on legitimate interest, or ask us to limit them;
- withdraw consent at any time: statistics in Settings, AI providers by not generating;
- complain to the data protection authority where you live or work.
In the app you can delete your account and turn statistics off. For everything else, email privacy@dissy.fm. We answer within one month (45 days under US state laws) and may ask you to confirm the account is yours.
US state privacy laws, including California (CCPA as amended by the CPRA). In the last 12 months we collected the categories in the table above: identifiers, commercial information (purchases), audio and visual information (what you publish), internet activity in Dissy, approximate location (country) and inferences limited to anti-fraud. We don't sell or share personal information and don't use sensitive personal information to infer things about you. You can use your rights without being treated differently, and an authorised agent can act for you.
Children and teens
Dissy is rated 13+.
- Under 13. You can make tracks on your phone as a guest. We don't create an account, profile or public page for you. Making a track still sends the topic to the AI providers above, without any name or account attached. If we learn that we hold other personal data of a child under 13, we delete it. Parents can write to privacy@dissy.fm.
- 13 to 17. You can have an account and publish by link. There is no public profile, no public tracks, no Fire, and a feed filtered for teens. Notifications stay quiet at night.
- 18+. Public tracks, profile, charts and Fire.
Security
Connections are encrypted. Your files sit in private storage and are served by short-lived signed links. Tokens are stored only as hashes; sign-in tokens, push tokens and reply emails are encrypted. Every time a moderator opens your content, it is logged. Provider keys live only on our servers. If a breach puts your data at risk, we will tell you and the authorities as the law requires.
This website and cookies
dissy.fm sets no cookies of its own and loads nothing from other sites. Cloudflare, which delivers the site, may set a strictly necessary security cookie to tell people from bots. Track and artist pages are closed to crawlers that collect data for AI training.
Changes
When we change this policy, we update the date below. If a change matters for how we use your data, we tell you in the app before it applies.
Effective from 16 November 2026.