Privacy Policy

The short version

• We do not sell personal data or use listening habits to target advertising.
• Clippsly does not build a personal taste profile from your listening history to choose recommendations. Discovery is based on recent or randomly selected tracks; autoplay radio can use the track you are currently listening to. If you connect Last.fm, Clippsly can send listening events to Last.fm.
• We do collect account, content, service-activity, payment, and security information needed to run Clippsly. This includes network information used to protect creators and listeners from abuse, fraud, and ban evasion.
• IP-derived security fingerprints are pseudonymous, not anonymous. They are hashed or keyed-hashed, not encrypted, and can be compared to recognize the same network address. Older SHA-256 records may remain alongside newer keyed fingerprints.
• You can ask us to access, correct, or delete your data, subject to legal, payment, content-rights, and safety requirements.

1. Who we are

Clippsly Ltd (“Clippsly”, “we”, “us”, or “our”) is the controller of personal data processed through the Clippsly service, except where another service acts as its own controller.

Clippsly Ltd
Unit A, 82 James Carter Road
Mildenhall Industrial Estate
Mildenhall, Suffolk, IP28 7DE
United Kingdom
Privacy contact: support@clippsly.com

This policy applies to Clippsly websites, accounts, applications, APIs, music-listening and creator features, support services, and related integrations.

2. Information we process

The information depends on which Clippsly features you use.

• Account and sign-in data: Username, display name, email address, password hash, account settings, verification status, passkey public-key information, two-factor authentication data, and session records.
• Profile and content: Profile image and banner, biography, uploaded audio and artwork, track and release metadata, playlists, comments, messages, and other content you submit or publish.
• Connected services: Account identifiers and authorization data for services you choose to connect, such as Roblox, YouTube, Twitch, Discord, SoundCloud, X, or Last.fm. The data available depends on the service and permissions you approve.
• Service activity: Information needed to operate features, such as last-active time, uploads, comments, playlist changes, account settings, and whether a feature or integration was used. We may also produce operational statistics from service activity.
• Network and device information: IP addresses received by our application or infrastructure providers, browser or app user-agent information, session timing, and country or region derived from network information. Security systems may store an IP-derived fingerprint rather than the raw address.
• Safety and moderation information: Reports, suspected or confirmed policy violations, moderation decisions, enforcement history, and evidence needed to investigate abuse, copyright concerns, fraud, or ban evasion. Automated safety systems may use prior violations and network fingerprints.
• Payments and agreements: Payment provider, transaction or payment identifiers, status, product, amount or quantity, delivery records, and information needed for a payment or legal agreement. Payment providers handle payment details under their own terms.
• Support and communications: Information you provide when contacting support, including your message, account details needed to help you, and any attachments.

We do not ask users to provide more information than a feature needs, but some information is necessary to create an account, make a purchase, publish content, or protect the service.

3. How we use information

We use information to:

• create and operate accounts and provide the features you request;
• authenticate users, protect accounts, and provide customer support;
• store and deliver music, profiles, playlists, comments, and other content;
• process payments, purchases, agreements, and regional pricing;
• identify spam, fraud, copyright abuse, ban evasion, and other threats to users or the service;
• review content and apply our rules, including through automated moderation and safety tools;
• maintain, troubleshoot, and secure our applications and infrastructure;
• meet legal obligations and establish, exercise, or defend legal claims.

Listening, recommendations, and analytics

Clippsly does not use a listener’s long-term listening history to build an individual taste profile for advertising or personalized recommendations. Current discovery features use recent or randomly selected tracks, and autoplay radio may use the current track’s artist or genre. This may change if we introduce new features; we will update this policy if the way we use listening data changes materially.

Clippsly does maintain service-activity information and may create operational reports, such as counts of active accounts, uploads, comments, or playlists. These help us understand and operate the platform; they are not advertising profiles or listening-history recommendation profiles.

If you connect Last.fm, Clippsly may send track and artist information, and listening or “now playing” events, to Last.fm for scrobbling. Last.fm processes that information under its own privacy policy. Disconnecting Last.fm stops future submissions from Clippsly, but does not remove information already received by Last.fm.

Security fingerprints and ban evasion

Our systems receive network information when you use Clippsly. For security and abuse prevention, we may associate an IP-derived fingerprint with an account or session to identify repeated use of the same network, investigate suspected ban evasion, limit abusive sign-ups, or detect certain kinds of fraud.

These fingerprints may use a one-way SHA-256 hash or a keyed HMAC, depending on when and where the record was created. Older SHA-256 fingerprints may remain after newer records use HMAC. A hash is not encryption: the value cannot simply be decrypted, but it is still linkable and may be personal data. We do not use these fingerprints to target ads or personalize music recommendations.

A shared IP address can belong to unrelated people—for example, people in the same household, school, workplace, mobile network, or VPN. A match may lead to a safety review or restriction, but it can be mistaken. If you believe an action was made in error, contact support and ask us to review it.

4. Legal bases

Where data-protection law requires a legal basis, we generally rely on:

• Contract: to create your account and provide features, content storage, purchases, and support you request.
• Legitimate interests: to secure Clippsly, prevent abuse and fraud, enforce platform rules, protect users and creators, and maintain reliable services. We balance these interests against your rights and use safeguards such as limiting access to security information.
• Consent: for optional integrations or other features where consent is the appropriate basis. You can disconnect an integration or withdraw consent for future processing where available.
• Legal obligation: to meet applicable financial, regulatory, or legal requirements.

5. When we share information

We do not sell personal data. We share information only when needed for the purposes described here, including with:

• Hosting, storage, and delivery providers that operate Clippsly applications, databases, audio storage, and content delivery;
• Email and support providers that deliver account, security, legal, and support communications;
• Payment providers, including Stripe or NOWPayments where used, to create and process transactions. Crypto transactions may be recorded on public blockchains and are not anonymous by default;
• Services you connect, such as Last.fm or OAuth providers. They receive information required for the feature and permissions you authorize;
• Moderation, copyright, and safety providers, including audio-recognition or account-safety services, when needed to review content or investigate abuse. This may involve submitting relevant content, metadata, or connected platform identifiers;
• Distribution platforms, including Roblox or other destinations you choose, when you use music distribution or publishing features. Required artist, release, track, and content information may be sent to deliver the release;
• Authorities or other parties when required by law, or when reasonably necessary to protect users, investigate suspected abuse, enforce our terms, or defend legal claims.

Our service providers are expected to process information only for the services they provide to us and under appropriate contractual safeguards. When you use another company’s service directly or connect an account, that company may also act as an independent controller under its own privacy policy.

Examples of providers used by particular features include Bunny.net for storage or delivery, Amazon SES for email, Stripe and NOWPayments for payments, ACRCloud for audio recognition, and Rayward (formerly Rotector) for configured Roblox or Discord safety checks. This is not an exhaustive list and may change. For a Rayward safety check, we may send the relevant connected platform identifier; the integration is designed not to retain the provider’s response for more than 24 hours. A resulting Clippsly moderation or enforcement record may be retained under the rules in Section 8.

6. Public content and connected accounts

Content you choose to publish—such as a public profile, public release, comment, or public playlist—may be visible to other users or the public. People who can view public content may copy or share it, and copies may remain outside Clippsly after you remove the original.

When you connect a third-party account, Clippsly receives the identifiers and permissions necessary for the integration. You can disconnect available integrations in your settings. Disconnecting stops future access or submissions by Clippsly where technically supported; it does not delete information already held by the third party.

7. Cookies and similar storage

Clippsly uses cookies or similar browser storage that are necessary to keep you signed in, secure your session, and provide requested features. We do not use Clippsly cookies to follow you across unrelated websites for targeted advertising. Connected third-party services may use their own technologies under their own policies.

8. Retention and account closure

We retain information for as long as reasonably needed for the purposes in this policy, subject to legal requirements and safety needs. There is not one retention period that applies to every type of information.

• Account and profile information is generally kept while your account is active.
• Session credentials expire for sign-in purposes. Session and security records may remain after expiry where needed for security, abuse prevention, or ban-evasion investigations.
• Moderation, safety, and ban records may be retained after account closure when necessary to protect users, enforce restrictions, or establish, exercise, or defend legal claims.
• Payment, transaction, and agreement records may be retained for applicable accounting, tax, and legal requirements.
• Content delivered to an external platform may remain subject to that platform’s retention and removal processes.

When information is no longer needed, we aim to delete it or remove identifiers. Closing an account does not necessarily erase every safety, payment, legal, or externally distributed record. Where we retain information after closure, we limit it to the purpose that requires retention.

9. Your choices and rights

Depending on where you live, you may have the right to access, correct, delete, restrict, or object to certain processing, receive a copy of your information, withdraw consent, or complain to a data-protection authority.

You can change some profile details, account settings, and connected services through Clippsly. To make another privacy request, contact support@clippsly.com. We may ask for information reasonably needed to verify that the request is yours. We aim to respond within 14 days and will follow applicable legal deadlines.

Some requests may be limited where we must retain information for legal obligations, payment records, safety, abuse prevention, or legal claims. If we cannot fully comply, we will explain why where the law allows.

If you are in the UK, you can complain to the Information Commissioner’s Office (ICO). If you are in the EEA, you can contact your local data-protection authority.

10. Security

We use technical and organizational safeguards intended to protect information, including access controls, password hashing, and encryption for certain data. Security fingerprints are pseudonymous, not anonymous, and no online service can guarantee perfect security. Please use a unique password, protect your sign-in credentials, and contact us if you suspect unauthorized access.

11. Children and age requirements

Clippsly is intended for people aged 13 or older. Users under 18 must have parental or guardian consent as required by Clippsly’s rules. We do not knowingly seek to collect personal information from children under 13. If you believe a child under 13 has provided personal information, contact us so we can investigate and take appropriate action.

12. International processing

Clippsly’s main application data is primarily hosted in Germany, but information may be processed in other countries by our infrastructure, payment, email, moderation, distribution, or connected-service providers. Where required, we use appropriate safeguards for international transfers. The relevant provider’s location may depend on the feature you use.

13. Changes to this policy

We may update this policy when our services, data practices, or legal requirements change. We will update the date above and provide notice of material changes by email or through Clippsly where appropriate.

14. Contact

For privacy questions or requests, contact support@clippsly.com.