Privacy Policy

Last updated:

SongDrop ("we", "our", or "the app") turns a short message you write into a song. This Privacy Policy explains what we collect, why, who else receives it, and what control you have.

Two things are worth stating up front, because they shape everything below. SongDrop has no accounts — we never ask for your name, your email or a password, and there is no profile for us to look up. And we do not store the text of your message; the records we keep in order to run the service note how long a message was, never what it said.

1. Information We Collect

The message you write

• Your message — sent over an encrypted connection to our own server, and from there to the music provider that writes the song. That is the only thing it is used for. We do not keep the text.
• The style you choose — the genre and mood you pick, or the style you describe in your own words, sent with the message as the prompt for the song.

Service records

Our server writes one record per song we accept, so we can reconcile what the service costs us and stop abuse. That record deliberately has no field capable of holding your message. It contains:

• An event ID and timestamp — generated by us, to identify the record.
• Your subscription identifier, and which kind it is — the anonymous identifier described below, plus a flag recording which kind of identifier the record was metered against. In a fallback used only when subscription checking is unavailable, a one-way keyed hash of your IP address is used instead — never the address itself.
• Message length and style length — character counts. Not the text.
• Model, audio format and unit cost — which model produced the song and what it cost us.
• Outcome — whether the request succeeded, the provider's status code, and the provider's ID for the generated song.
• Analytics ID and request ID — identifiers that let one record be matched to the corresponding event in the app.

Songs

• Saved songs — stored only on your device, in the app's own storage, alongside a small index recording each song's title, when you saved it, and which file it points to. These are never uploaded to us.
• The title of a saved song — this is the message you wrote, and the audio file is named after its opening words. Both stay on your phone.

Product analytics

• A random analytics identifier — generated on your device. It is not your name or your email, because we hold neither.
• Derived event properties — things like a message's character count and a coarse length band, whether a genre, a mood, a custom style or none was chosen, how long a song took, and, on failure, a fixed label such as "moderation blocked" or "rate limited". Never the message itself.
• Your subscription identifier — carried on every event, so a purchase can be joined to the activity that led to it. The two identifiers are deliberately linked to each other, though neither is linked to you.
• Device context — supplied by the analytics library: device type, name and manufacturer, operating system and version, app version and build, language and time zone.
• App lifecycle and screen names — when the app is installed, opened and put into the background, and which of its three screens you are on. By fixed screen name, never by what is on it.

Two mechanical safeguards run before anything is sent: a list of property names that are dropped outright (including anything called message, lyrics, prompt, title, text, name or file URI), and a rule that discards any text value longer than 24 characters — with a single named exception for the subscription identifier, which is machine-generated and never anything you typed. Because the app requires a message to be at least 25 characters, no message you write can pass either check.

Automatic capture of taps and screen contents is switched off, and session recording is not used.

Subscriptions

• An anonymous subscription identifier — generated by our subscription provider on first use. It is not derived from your device, your Apple ID, or anything about you.
• Entitlement status — whether a subscription is active and when it expires. We never see or store your payment details; purchases are handled entirely by Apple or Google.
• The analytics identifier — passed to the subscription provider as an attribute, for the joining purpose described above.

Device and technical information

• IP address — received by our server in the ordinary course of routing your request, and used to apply rate limits. We do not write it into our own records; where an address is used as a usage key at all, it is stored only as a one-way keyed hash.
• Approximate location from IP — our analytics provider derives an approximate country and region from the address events arrive from. This is not device location; see Section 3.

2. How We Use Your Information

• To generate the song you asked for, and to deliver it to your device.
• To check that a subscription is active before generating a song, and to restore a subscription you have already paid for.
• To meter what each subscription costs us, apply fair-use limits, and reconcile our provider invoices.
• To prevent abuse and enforce our Terms of Service.
• To understand how the app is used, so we can improve it.
• To send the reminders you have allowed, which are scheduled entirely on your device.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising. There is no advertising in SongDrop. We do not use your messages or your songs to train machine-learning models.

3. What We Never Collect

• Your name, email address, phone number or password — the app has no sign-up.
• The text of your messages, in any record we keep.
• Copies of your songs. They are generated, delivered to you, and saved on your device.
• Your contacts, photos, calendar or device location. The app requests none of these permissions at any point. Our audio-playback library adds a microphone permission string to the iOS build, but SongDrop never records audio and never asks for microphone access.
• Payment details of any kind. Those go to Apple or Google, never to us.
• Who you send songs to. Sharing happens through your device's own share sheet, and we are not part of it.

4. How Your Songs Are Made and Stored

When you press Create Song, your message and style are sent to our own server, which validates the request, checks your subscription, and forwards it to our music provider. Our server holds the credentials for that provider so they never ship inside the app.

The finished song is delivered to your device. Until you save it, the app plays it directly from the provider's link; saving downloads it into the app's storage on your phone.

Deleting the app deletes your saved songs. We keep no cloud copy and have no way to restore them — though your device's own backup may include them, which is a matter between you and Apple or Google. Keep your own copies of anything that matters.

5. Notifications and Tracking Permission

The app asks once, on first open, whether it may send notifications, and records only whether you agreed. Reminders are scheduled entirely on your device: no push tokens are created and no server sends them, which also means we cannot see whether a notification was ever delivered or shown. If you tap one, we record an anonymous event noting which of our fixed reminder messages it was, so we can tell which are worth keeping.

On iOS you will also see Apple's App Tracking Transparency prompt. We record only whether you allowed or denied it. SongDrop does not currently use the advertising identifier that prompt governs, runs no advertising, and shares no data with advertising networks. Declining limits nothing in the app.

You can turn either permission off at any time in your device settings.

6. Who Else Receives Your Data

We share data with the following providers, only so far as needed to run the app:

• WaveSpeedAI — generates the music. Receives your message and style as the prompt for the song, and processes them under its own terms and retention practices.
• RevenueCat — manages subscriptions. Receives your anonymous subscription identifier, the analytics identifier, store receipts and entitlement status.
• Apple and Google — process purchases and distribute the app. They receive your payment and account details directly; we never see them.
• PostHog — product analytics. Receives the anonymous events described in Section 1, including the subscription identifier, device context, and the IP address events arrive from. It does not record your screen, your taps, or the content you create.
• Cloudflare — runs our server and holds our service records. Receives request metadata including your IP address.

Each of these providers operates under its own privacy policy. Data may be processed in the United States.

7. Legal Bases

Where the UK or EU GDPR applies, we are the data controller, and our lawful bases are:

• Performance of a contract — generating the song you asked for, and checking your subscription before doing so. Without this we cannot provide the service at all.
• Legitimate interests — keeping the service working and affordable: rate limiting, abuse prevention, metering cost, and diagnosing failures. We have weighed these against your interests and kept the data minimal and pseudonymous, which is why our records hold lengths rather than text.
• Consent — notifications and the tracking permission in Section 5. You can withdraw either at any time in your device settings.
• Legal obligation — retaining transaction records where tax or accounting law requires it.

8. Retention and Deletion

• Your message — not retained by us. Passed to the music provider and discarded.
• Saved songs — on your device, until you delete them or remove the app.
• Service records — kept for [ choose a retention period — see site/README.md ], after which they are deleted or aggregated.
• Analytics events — according to our analytics provider's retention settings.
• Subscription records — for the life of the subscription, and as long as tax and accounting rules require.

You can stop most collection yourself at any time: turn off notifications or tracking in your device settings for SongDrop, and delete the app to remove everything stored on your device.

9. Your Rights

Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, restrict or object to how we use it, receive it in a portable form, and complain to your data protection regulator. In the UK that is the Information Commissioner's Office; in the EU it is your national authority. California residents have equivalent rights to know, delete, correct and opt out, and we will not discriminate against you for exercising them.

Because there is no account, we cannot identify you from our records. What our records link to each other is one install's activity, joined by the two anonymous identifiers in Section 1 and nothing else. To make a request about those records, email our contact address and include your subscription identifier, which you can copy from the app under Settings → Subscription.

We will respond within one month. If we cannot identify your records from what you send us, we will say so rather than guess — matching the wrong records to a person would be its own privacy failure.

10. Security

All traffic between the app and our systems is encrypted in transit. Our credentials for the music provider are held server-side and never shipped inside the app. Access to our service records is limited to people who need it to operate the service.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. The strongest protection here is structural rather than procedural: the service is designed so that the sensitive thing — what you wrote — is never stored in the first place.

11. International Transfers

Our providers operate globally, so your data may be processed outside your country, including in the United States. Where data leaves the UK or the EEA, we rely on the safeguards those providers offer, such as Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework.

12. Children

SongDrop is not intended for anyone under 13, and you must be at least 13 to use it. We do not knowingly collect personal data from children under 13. If we learn that we have, we will delete it promptly. If you believe a child under 13 is using SongDrop, contact us.

13. Changes to This Policy

We may update this policy. We will change the "Last updated" date above, and where changes are significant we will tell you in the app. Continuing to use SongDrop after a change means you accept the updated policy.

14. Contact Us

If you have any questions about this Privacy Policy, please contact us at:

our contact address

, .