Legal
Privacy Policy
Last updated: 18 October 2026
Engage Digital Projects Ltd, trading as RudeTune (“RudeTune”, “we”, “us”, or “our”), operates the RudeTune iOS application and the website at rudetune.app. This Privacy Policy explains what personal data we collect, why we collect it, how we use it, and your rights under applicable data protection law including the UK GDPR, the EU GDPR, and the Data Protection Act 2018.
18+ and mature content
RudeTune is an adult comedy product. You must be 18 or older to create an account or use the Service. Generated songs may contain strong language and crude humour. See Section 11 (Age Requirement) below.
Data Controller
Engage Digital Projects Ltd, trading as RudeTune, is the data controller for the personal data described in this policy. You can reach our privacy contact through our support page for any data-protection query, subject-access request, or complaint.
1. Data We Collect
Account information
When you create a RudeTune account we collect your email address, display name, and authentication identifiers. If you sign in with Apple or Google we receive only the identifiers those providers share with us - we do not receive your Apple or Google password. If you use the app as a guest without signing up, we create an anonymous account with an internal identifier so your songs and purchases are linked to it; if you later sign up, that guest account’s songs and purchases move to your new account.
Age check
Before you use the app we check that you are 18 or older, either with Apple’s Declared Age Range check (which shares only an age range with us, never your date of birth) or by asking for your date of birth. A date of birth is used once on your device to work out whether you are an adult and is then discarded: it is never sent to us or stored. We store only the outcome (adult or under 18), which method was used, and when, on your device and against your account on our servers, so that we can apply the heat-level rules in our Terms of Service. On the website, a shared song link asks you to confirm you are 18 or over before it plays and remembers that confirmation in your browser (see Section 5).
Song creation data
To generate your personalised song we collect what you enter in the creation wizard: the occasion, the heat level, the names (the person the song is for, your name, and any pet names), the stories, traits, and phrases you add about them, anything you mark as off limits, and your music preferences (genre, mood, and voice). This is the content used by our AI providers to produce your lyrics and audio. Generated lyrics and audio files are stored securely and linked to your account.
Payment information
All purchases are processed through Apple’s App Store via StoreKit 2. We receive transaction identifiers and purchase receipts from Apple to verify entitlements. We never see or store your card number or billing address - Apple handles all payment data.
Usage and device data
We collect pseudonymous usage events (such as which steps of the wizard you complete) through PostHog analytics. These events are keyed to your account’s internal identifier; they do not include your email address or name. We also collect standard device information - device model, operating system version, and app version - to diagnose crashes via Sentry error tracking. On our public website, Sentry also runs in your browser for error and performance monitoring: when a page errors, or a sampled page load is timed, Sentry receives the error or timing together with your IP address, your browser and device type (user agent) and the address of the page you were on. Errors are all reported; performance traces are sampled at 10% of page loads. We configure it not to attach account details, cookies or request bodies, and we do not use it to identify or track you across sites. If you allow notifications, we store your device’s Apple push-notification token so we can tell you when your song is ready. We also use Apple’s DeviceCheck service, which stores a small per-device flag with Apple (not your identity), to limit how many free songs one device can generate. IP addresses are processed transiently for rate limiting. Our security and audit logs retain IP data (in raw form in our internal admin audit log, and in hashed form in security event records) for abuse detection; this processing is based on our legitimate interests.
Shared content
When you share a song via a unique link or QR code, the landing page is publicly accessible to anyone with the link. No account is required to listen. We record only an aggregate view count per share link; we do not keep timestamps, locations, or a log of individual accesses.
Support requests
When you contact support in the app, we store your message together with your account so our reply appears in My Tickets, and you can reply there to continue the conversation. Every message in that conversation (yours and ours) is stored with the ticket. Adding an email address is optional in the app - add one if you would also like the reply by email. You can also add a name so we know what to call you; it is optional and used only to address our reply. The web contact form on our website has no signed-in session, so it requires an email address so we can reply to you. Support tickets are retained while open, and personal content (your message, every reply in the conversation, name, and email) is permanently stripped from a ticket 90 days after it is resolved, keeping only the reference number, category, and status - see Section 7 (Data Retention).
2. How We Use Your Data
- Service delivery - to generate your personalised song, store it, and deliver it to you and your recipient.
- Account management - to authenticate you, manage your purchase history, and maintain your entitlements.
- Push notifications - to notify you when your song is ready. You can opt out in iOS Settings at any time.
- Service improvement - aggregated usage data helps us understand how to make RudeTune better. We do not sell personal data.
- Legal compliance and fraud prevention - to meet our legal obligations, detect abuse, and protect our users.
Lawful basis for processing
Under Article 6 of the UK/EU GDPR, we rely on the following lawful bases:
- Contract (Art. 6(1)(b)) - to create your account, generate and deliver your song, process your purchase, and provide customer support.
- Legitimate interests (Art. 6(1)(f)) - for pseudonymous analytics, fraud prevention, abuse detection, and maintaining service security. You may object to processing carried out on this basis at any time.
- Legal obligation (Art. 6(1)(c)) - to retain financial records for tax and accounting purposes.
- Consent (Art. 6(1)(a)) - for optional marketing communications and non-essential cookies. You may withdraw consent at any time without affecting the lawfulness of prior processing.
- Consent (Art. 6(1)(a)) - Community Feed - if you choose to opt a purchased song into the Community Feed, we rely on your consent to publicly stream that song’s audio, its lyrics text with per-line timings, its name-scrubbed display title, and its genre and occasion within the app. This consent is given per song, is never pre-selected, and is entirely optional. You can withdraw it at any time by opting the song out. See Section 6 (Community Feed) for full detail.
AI training and model improvement
We do not use your personal data, stories, lyrics, voice inputs, or generated songs to train, fine-tune, or improve any machine-learning or AI model - neither our own nor any third party’s. Our third-party AI providers process your inputs solely to generate the song you requested and do not use them to train their models; limited transient retention may apply under each provider’s terms.
3. Automated Decision-Making and AI
RudeTune uses automated systems, including large language models and music-generation models, to produce your lyrics and audio. Under Article 22 of the UK/EU GDPR you have the right to information about automated processing that significantly affects you.
- What is automated - lyric drafting, audio composition, quality scoring (profanity detection for information only, slur filter, sentiment check), and content-moderation decisions that block hateful, graphic sexual, threatening or abusive inputs.
- Human oversight - our support team may listen to, review, and read the lyrics of songs you generate (including preview and full audio) for moderation, trust-and-safety, abuse investigation, and customer-support purposes. Reviewer access is restricted to authorised staff and logged in an internal audit trail. We handle any appeal you raise by email. We do not use automated decision-making for anything that produces legal or similarly significant effects on you.
- Your rights - you may request a regeneration, contest an outcome, or ask a human to review a moderation decision via our support page.
- AI limitations - generative AI can produce unexpected, inaccurate, or stylised output even when inputs are correct. You are responsible for the accuracy of the information you submit - see our Terms of Service for details.
4. Third-Party Services
We use the following third-party processors to deliver the service. Each is bound by a data processing agreement and subject to appropriate safeguards.
| Provider | Purpose | Data shared |
|---|---|---|
| Supabase | Authentication, storage & community audio delivery | Account info, song files, opted-in community audio |
| Third-party AI provider | AI lyric generation (and a short scene description for the cover art) | Your wizard inputs: story details, traits, off-limits topics, occasion, heat level, names, music preferences |
| Third-party AI provider | AI music (audio) generation and lyric timing | Generated lyrics, style; the generated audio, transcribed to time the on-screen lyrics |
| Third-party AI provider | AI cover-art generation | Song title, recipient first name (in personalised covers), and a short scene description and imagery keywords drawn from your story and lyrics (never names) |
| Apple | Payments, distribution, Sign in with Apple, push notifications, DeviceCheck, age-range check | Transaction receipts, sign-in identifiers, push-notification token, per-device DeviceCheck flag |
| Sign in with Google (only if you choose it) | Sign-in identifiers, email address | |
| Email delivery provider | Account emails (sign-up confirmation, password reset) and support emails | Email address; for support, your message, name, and our reply |
| Team messaging provider | Internal alerts to our team | Support ticket reference and subject line, the title of a reported song, and internal identifiers in operational alerts |
| Vercel | API hosting | Request metadata |
| PostHog | Analytics | Pseudonymous usage events |
| Sentry | Error monitoring | Crash and error reports, performance timings, device and browser info, IP address, page address |
The AI and other providers above are described by their category and function. A current list of our named sub-processors is available on request via our support page.
We do not sell, rent, or trade your personal data to third parties for their own marketing purposes.
6. Community Feed
The Community Feed described in this section is currently disabled and is not available to any user. It is described here so this policy is ready if we switch it back on; nothing in this section applies while it remains off.
The Community Feed is an optional, play-only area inside the RudeTune app. If you choose to share one of your purchased songs, other people using the app can listen to it (see below for what guests and registered users can hear). Taking part is voluntary and is based entirely on your consent. If you never opt a song in, none of this section applies to you.
What is published when you opt in
What is made public is limited to:
- a 30-second preview of the song audio;
- a name-scrubbed display title;
- the song’s cover artwork (a version without names);
- the genre and occasion;
- the song lyrics as text, with per-line timings used to display a synced lyric line during playback in the app; and
- your chosen profile display name, shown as the author of the song.
Because the lyrics are published, please review your song’s lyrics before opting it in: they are generated from the story and names you provided and may mention names or personal details.
Your profile display name is published with each song you share. It is frozen at the time an admin approves the song for the feed, so a later change to your display name does not alter the byline on a song that is already public. The published name stays as it was approved unless we are asked to update it. You can change your display name at any time in Manage Account.
What is never published:
- your email address; and
- the name or email of the person the song is for or about (the recipient).
Anyone using the RudeTune app, including guests who have not yet created an account, can hear a 30-second preview of a community song. Hearing the full song, and liking or sharing a song, requires a registered (non-guest) RudeTune account. Community songs are play-only: listeners cannot download, save, or re-share the audio.
Legal basis and versioned consent
We publish a song to the Community Feed only on the basis of your explicit, opt-in consent (Article 6(1)(a) UK/EU GDPR). Consent is given per song through a dedicated, never pre-selected confirmation, and you can withdraw it at any time by opting the song out. Withdrawing consent does not affect the lawfulness of any streaming that took place before you withdrew.
Each time you opt a song in, we record the version of the consent notice you agreed to, the time, and your confirmation, in a durable consent log. If we materially change what the Community Feed publishes or how it works, we will ask for your consent again under the new version rather than relying on your earlier agreement.
Songs that mention other people
A song shared to the Community Feed may describe or refer to a real person who is not the person who shared it. When a user opts a song in, they confirm to us that they have that person’s permission to share it publicly. This confirmation is the sharing user’s responsibility and is how we reduce the risk of someone’s song being shared without their knowledge. It does not, by itself, give RudeTune a separate legal basis to process that person’s information, so we give the people featured in shared songs a direct and reliable way to have a song removed.
If a song features you and you did not agree to it being public
You do not need a RudeTune account, and you do not need to know who shared the song. Contact us through our support page with enough detail to identify the song (for example, a description of it, the display title, or a link). We will remove the song from the Community Feed and delete the public audio copy promptly, normally within 72 hours of verifying your request, and ahead of any wider investigation. We treat this as a request you are entitled to make, and we will not require you to prove that you own the song before acting on a credible objection.
If a shared song contains your personal data, you have the same rights over it as any other personal data we hold, including the right to object to the processing and the right to erasure. To exercise these rights, contact us through our support page. We will respond within one month, as required by the UK/EU GDPR, and we may extend this by up to two further months for complex requests, in which case we will tell you within the first month.
How to withdraw consent and remove a song
If you shared the song, you can opt it out at any time from My Songs in the RudeTune app, which removes it from the Community Feed. If you are featured in a song someone else shared, use the removal route above by contacting us through our support page.
Retention and removal of community audio
While a song is opted in, a copy of its audio is held in our content delivery storage (a dedicated Supabase Storage bucket) so it can be streamed to listeners. When you opt a song out, or when the song or your account is deleted:
- we stop the song appearing in the Community Feed and stop issuing new playback links for it straight away;
- we delete the public copy of the audio promptly; and
- we purge it from our content delivery cache.
Because of how streaming and content delivery networks work, we cannot guarantee that every copy disappears from every device or cache at exactly the same instant. The 30-second preview copy is held in a private storage bucket and is reachable only through short-lived signed playback links that we issue; a preview link already issued stops working within about five minutes, and a full-song playback link within about four minutes. Any cached copy at a delivery network’s edge is removed within its cache lifetime (up to 24 hours). After that, the song is no longer available through the Community Feed. We keep a minimal, durable record that the song was opted in and later opted out, so we can demonstrate that consent was given and withdrawn.
7. Data Retention
- Active accounts - data is retained for as long as your account is active.
- Deleted accounts - deletion is immediate and irreversible: your access to the service and your ability to sign in end at once, and there is no recovery window. Residual personal data, including song audio files, is permanently purged from our systems within one month.
- Guest accounts - guest accounts with no completed purchase (including a SongPass subscription) are deleted after 12 months of inactivity, and their residual data is purged within the following month. Guest accounts with a completed purchase are retained in the same way as full accounts.
- Order records - purchase records are retained for 7 years to comply with UK financial and tax regulations. These records contain only transaction identifiers and amounts, not payment card details.
- Analytics data - pseudonymous analytics events are retained to help us understand long-term service trends. You can ask us to delete the analytics events linked to your account at any time via our support page.
- Support tickets - support requests are retained while open. 90 days after a ticket is resolved we strip the message, every reply in the conversation, and the name and email, keeping only the reference number, category, and status. Replying to a resolved ticket within one month reopens it; the 90-day clock then restarts when the ticket is next resolved.
8. Your Rights
Under UK and EU GDPR you have the following rights regarding your personal data:
- Access - request a copy of the personal data we hold about you.
- Rectification - ask us to correct inaccurate data.
- Erasure - request deletion of your account and personal data (“right to be forgotten”).
- Portability - receive your data in a structured, machine-readable format.
- Restriction - ask us to restrict processing while a dispute is resolved.
- Objection - object to processing based on legitimate interests.
- Withdraw consent - where processing is based on consent, you may withdraw it at any time without affecting the lawfulness of prior processing.
To exercise any of these rights, contact us via our support page. We will respond within one month. You also have the right to lodge a complaint with the UK Information Commissioner’s Office (ICO) at ico.org.uk.
9. Data Security
All data is encrypted in transit using TLS 1.2 or higher. Data stored in Supabase is encrypted at rest. Audio files are served via time-limited signed URLs - direct public access to storage is disabled. We follow industry-standard security practices and conduct regular reviews of our access controls.
10. International Transfers
RudeTune is operated from the United Kingdom. Some of our third-party providers process data in the United States. Where data is transferred outside the UK/EEA, we ensure appropriate safeguards are in place - including Standard Contractual Clauses or the UK International Data Transfer Agreement - in line with ICO guidance.
11. Age Requirement and Children's Privacy
RudeTune is an 18+ product. It generates comedy songs that, at the Saucy and Rude heat levels, contain strong language and crude humour, and it is not directed at, or intended for use by, anyone under 18. You must be 18 or older to create an account or use the Service.
We do not knowingly collect personal data from anyone under 18. If we become aware that we have inadvertently collected such data, we will delete it promptly. If you believe a minor has provided us with personal data, or that a minor is using the Service, please contact us via our support page.
We never allow sexual or humiliating content involving a minor in any form; see Section 6 (Content Moderation) of our Terms of Service for the content rules that apply to everything you submit.
12. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page and, for material changes, notify you via the app or email. Continued use of the service after changes take effect constitutes acceptance of the updated policy.
13. Contact Us
If you have any questions or concerns about this Privacy Policy or how we handle your data, please get in touch:
RudeTune (Engage Digital Projects Ltd)
Privacy enquiries: our support page
General support: rudetune.app/support
Website: rudetune.app
You also have the right to lodge a complaint with the UK Information Commissioner’s Office at ico.org.uk or with your local EU data-protection authority.
© 2026 RudeTune. All rights reserved.