Privacy Policy

Last updated: 30 October 2026

In short

• No accounts, no ads, no ad tracking. We never ask for your name, email or phone number, and the app contains no advertising identifiers or ad networks.
• Your recordings stay on your phone — except what you choose to send:
  1. a short loop built from your sound, when you ask for an AI backing track;
  2. the microphone, streamed live to Google while Live mode is running;
  3. a track (and, only if you switch it on, the sample) that you post to the feed. A clip that opens with the original sound carries up to 2.5 seconds of your recording inside the track and its video.
• Anonymous product analytics, processed by PostHog in the EU. You can turn it off in Settings.

Who we are

Zero to Drop is published by the developer named on its App Store and Google Play pages ("we", "us"). Questions about privacy: support@zerotodrop.com.

What we process, and why

Recordings

The app records only while you hold the record button. Analysis, the choice of role and genre, and the whole local track are computed on your phone. Recordings are not uploaded, and they are deleted when you delete them or uninstall the app.

The loop you send for an AI backing track

When you tap Write an AI backing (or ask for a full-length or HQ track), the app first asks for your consent, then uploads an eight-bar loop that it has already mixed from your sound — not the raw recording — together with musical settings (tempo, key, genre, role). Our server passes it to one AI provider to generate the backing track:

• fal.ai, which runs the models we use for backing tracks (ACE-Step, Stable Audio and Google's Lyria);
• ElevenLabs, for the licensed HQ export.

The loop and the generated backing track are stored on our servers for no longer than one day and then deleted automatically. Providers receive the loop only to generate your result, under their API terms.

Live mode

Live mode streams audio from your microphone to Google (Lyria RealTime) for as long as the session runs — at most ten minutes — so the music can follow your sound. The app asks for your consent before the first session. We do not store the stream; the connection goes from your phone to Google with a one-time key that expires within a minute.

Posts in the feed

If you tap Post, the app uploads the track (and the share card's video, if one was made) and we store it with the sound's name, the genre, tempo, "presence" score and whether it has an AI backing — such posts are labelled as AI-generated wherever the track is shown: in the feed, on the share page and in the video. Other users see and hear it in the app, and anyone with the link can play it on its public share page (zerotodrop.com/s/…) — the audio files themselves are served from public addresses on our server.

A clip can open with the original sound: Start with the original sound is on by default and can be switched off before you export. When it is on, up to 2.5 seconds of your recording play at the start of the posted track and its video, so they are public with the post. The recording file itself is uploaded and shared for others to remix only if you switch on Share the sound itself, which is off by default. Posts are filed under a short public tag derived from your device credential, so other people can hide everything from one creator; the tag cannot be turned back into the credential. You can delete your posts in the app at any time; deleting removes the files from our storage.

If a post or an AI result is reported, we keep the report — which post or result, the reason, the settings the AI was given for that result, any note the reporter added, and when — for as long as we need it to moderate. So that one network cannot hide a post on its own, a counted report on a post is also stored with a one-way keyed hash of the reporter's network address (see below); that hash is kept at most 30 days, and deleted when a moderator decides on the post.

Device credential

On first launch our server issues your phone a random identifier and a signature. It is how we count daily limits, know whether you have Pro, and know which posts are yours. It is not linked to your name, email, phone number or any advertising identifier.

Network address

Like any server, ours sees your IP address with each request. We use it only for short-lived counters that stop one network from abusing free limits or reports, and the counters are keyed by a one-way hash of the address, not the address itself. The only place that hash is kept next to anything of yours is a report you made on a post, for at most 30 days (see Posts in the feed). The address is not stored with your recordings, posts or analytics.

Purchases

Payments are handled by Apple or Google; we never see your card, name or address. RevenueCat receives your purchase history from the store (which products, when, renewals and cancellations) together with your device credential, so it can confirm your subscription. It also receives your analytics ID (see below), so that subscription events can be counted in our product analytics.

Product analytics

We use PostHog (EU cloud, servers in the EU) to understand how the app is used — for example how many people finish a track, which genres they switch to, and where something failed. The app sends:

• events about what happens in the app: screens opened, recordings made, tracks built, genre changes, AI requests and their outcome, exports, posts, paywall views, purchases started or completed, and error codes;
• crash reports when the app crashes or catches an error: the error type, its message with quoted text, links, file paths and identifiers cut out, and where in the code it happened (function, file, line). They are PostHog events like the rest and the same switch turns them off;
• your app version, OS and version, and your phone's language and region settings;
• a random analytics ID created on your phone. It is separate from the device credential and is not an advertising identifier.

It never sends audio, file names, text you typed (such as a sound's name), your location, contacts or advertising identifiers. PostHog discards your IP address before storing events. We use this data only to improve the app — never for advertising, and we do not sell it. Events are kept for up to 12 months.

Analytics is on by default. Turn it off in Settings → Share anonymous usage stats: the app deletes events it has not sent yet and sends nothing more.

Who receives data

Some of these providers are in the United States. Where data leaves the EEA or UK, the transfer relies on the European Commission's Standard Contractual Clauses or an equivalent safeguard.

How long we keep it

Your choices and rights

• Delete a post: in the app, on the post.
• Stop analytics: Settings → Share anonymous usage stats.
• Withdraw AI consent: Settings → Ask again before using AI.
• Hide a creator: on any of their posts; undo in Settings → Blocked creators.
• Delete everything on your phone: uninstall the app.
• Delete data on our servers, or get a copy: write to support@zerotodrop.com and include the ID shown in Settings → Diagnostics. We answer within 30 days.

If you are in the EEA or the UK: we rely on contract to produce what you ask for (tracks, AI backing, posts, Pro), and on legitimate interests to keep the service secure and to run product analytics, which you can switch off at any time. You may access, correct, delete, restrict or object to processing of your data, and complain to your data-protection authority.

Children

Zero to Drop is rated 13+ and is not directed at children under 13. We do not knowingly collect data from them. If you believe a child under 13 has sent us data, write to us and we will delete it.

Security

Everything travels over HTTPS or secure WebSockets. Provider keys stay on our server; the phone only ever gets one-time tokens.

Changes

If we change this policy in a way that matters, we will show the change in the app before it takes effect.

Contact

support@zerotodrop.com