Acceptable Use Policy

What you may and may not do on Simuze, and what happens when someone breaks the rules.

Effective date: 10 June 2026 Last updated: 10 June 2026

Simuze is a platform for musicians, fans, labels, and venues. This Acceptable Use Policy explains what's okay to do on Simuze, what's not, how we moderate, and how you can flag a problem.

It forms part of our Terms of Service at /legal/terms.

1. The short version

  • Don't break the law.
  • Don't harm or harass other people.
  • Don't pretend to be someone else.
  • Don't post content you don't have the rights to.
  • Don't spam, scam, or game the system.

If you do these things, we'll act. The rest of this page explains the details and how.

2. What you may not post or do

This list isn't exhaustive — common sense applies to anything not listed — but it covers the main categories.

2.1 Illegal content

You may not post or transmit content that:

  • Is unlawful under Dutch law or the law of your country.
  • Depicts or facilitates child sexual abuse. This is an absolute prohibition. We report all such material to the appropriate authorities.
  • Incites or facilitates terrorism, mass violence, or other serious crime.
  • Constitutes hate speech or discrimination on the basis of race, ethnicity, religion, national origin, disability, gender, gender identity, or sexual orientation, beyond what is protected expression under Dutch law.
  • Infringes copyright, trademark, or other intellectual property rights. (See Copyright Policy at /legal/copyright.)
  • Defames a real person.
  • Violates someone's privacy (e.g. posting their personal details without consent — "doxxing").
  • Is non-consensual intimate imagery, or sexually explicit imagery of any person without their clear consent (and not at all if they are a minor).
  • Promotes or facilitates fraud.

2.2 Harm to other users

You may not:

  • Threaten, intimidate, stalk, or harass other users.
  • Use Simuze to coordinate harassment campaigns against anyone, on or off platform.
  • Send unwanted sexual content or unwanted explicit communication.
  • Encourage self-harm or suicide. If you're worried about yourself or someone else, please reach out to a professional — for example, 113 Zelfmoordpreventie (Netherlands, https://www.113.nl, 0800-0113) or a local equivalent in your country.

2.3 Misrepresentation

You may not:

  • Impersonate another person, artist, band, label, or venue.
  • Misrepresent your affiliation with a person, brand, or organisation.
  • Use someone else's name or likeness to create a misleading account.
  • Use AI-generated voices or images to impersonate a specific real person without clear permission and context.

Tribute bands, cover acts, and clearly-labelled parody are fine — as long as your page and content make the distinction clear.

2.4 Content you don't own

You may not upload music, artwork, photos, video, or text that you don't have the rights to upload. Simuze relies on you holding the rights you say you have.

This includes:

  • Recordings of other artists' work without their permission.
  • Bootleg recordings of live performances.
  • Master recordings owned by labels you have no agreement with.
  • Photos or artwork you didn't take or didn't licence.

If you legitimately cover or sample another work, you're still responsible for any songwriter, publisher, or mechanical royalties. Simuze does not handle this on your behalf.

2.5 Spam, scams, and manipulation

You may not:

  • Send unsolicited promotional messages to other users.
  • Create fake accounts.
  • Buy, sell, or trade plays, downloads, follows, likes, or favourites.
  • Use bots, scrapers, or automated tools to interact with Simuze beyond what our API or features allow.
  • Move transactions off-platform specifically to avoid Simuze's fees (see Seller Terms section 11).
  • Manipulate prices through fake transactions.
  • Create misleading event listings or sell tickets for events you can't deliver.

2.6 Technical abuse

You may not:

  • Disrupt or attack Simuze's infrastructure (DoS, intrusion attempts, exploiting vulnerabilities).
  • Bypass rate limits, paywalls, or access controls.
  • Reverse-engineer Simuze in a way that breaches Dutch software-protection law.
  • Extract data from Simuze in bulk without our permission.

Responsible security research is welcome. If you find a vulnerability, please disclose it to admin@simuze.com with details. We won't take legal action against good-faith security research that follows reasonable disclosure norms.

3. How we moderate

3.1 What we look at

We act on:

  • User reports. Anyone can report content or accounts that violate this policy.
  • Trusted-flagger notices (where we have such arrangements under the DSA).
  • Legal orders from competent authorities.
  • Our own observations when staff become aware of an issue.

We don't proactively scan all uploaded content beyond automated technical checks (file format, malware, etc.). We're a hosting platform; we rely on users and rights-holders to flag problems.

3.2 What we do

Depending on the seriousness and context, we may:

  • Leave it alone — not every report is valid.
  • Reach out for context — sometimes a quick conversation resolves things.
  • Remove or hide the content.
  • Restrict the account (e.g. limit who can see it, or suspend selling).
  • Suspend or close the account.
  • Report to authorities where the law requires it (e.g. child sexual abuse material).

3.3 Notice to the affected user

When we act on content, we tell the user whose content it is, except where:

  • The law prohibits us from notifying them.
  • Notifying would put someone at risk.
  • The action is fully automatic (e.g. detection of malware in an upload).

The notice will explain what we did, why, and how to appeal.

3.4 Appeals

If we've acted against your content or account and you disagree, you can appeal:

  1. Reply to our notice, or email admin@simuze.com with your appeal.
  2. Explain why you think our decision was wrong.
  3. A different person from the one who made the original decision will review.
  4. We'll respond within 14 days, usually faster.

If you're still not satisfied, the DSA gives you the right to use a certified out-of-court dispute settlement body for content moderation disputes. We'll point you to one in our response when applicable.

You can also go to court. Your statutory rights are not affected by these procedures.

3.5 Repeated breaches

We give people the benefit of the doubt for one-off, minor issues. For repeated breaches, or single serious ones, we'll escalate quickly — including permanent account closure where warranted.

3.6 Frivolous or abusive reports

We may, in line with the DSA, restrict the ability to file notices and complaints from accounts that frequently submit reports that are clearly unfounded or filed in bad faith.

4. How to report something

4.1 Report a piece of content

Use the Report button on the content (track, comment, group post, profile, event). Pick the closest category and add detail.

4.2 Report a copyright issue

Use the takedown procedure at /legal/copyright. Don't file a copyright report unless you actually hold the rights — false copyright claims are a violation of this policy themselves.

4.3 Report something serious or off-platform

For anything urgent, sensitive, or involving real-world harm: admin@simuze.com.

Please include:

  • A link to the content or account you're reporting.
  • A description of what's wrong, with specifics.
  • Your contact information (we may need to follow up; we'll keep your identity confidential where possible).
  • Any evidence you can share.

4.4 Report by post

For legal notices that must be in writing: Atypisch.nl, attn. Trust & Safety, Europalaan 2b, 3525KS Utrecht

5. Transparency

We publish a DSA Transparency Statement at /legal/dsa-transparency covering, where applicable: number of orders received from authorities, number of notices received from users and trusted flaggers, our moderation actions, and other statistics required by the DSA.

6. Changes

We may update this policy. Material changes are notified to registered users with at least 30 days' notice. The "Last updated" date at the top is always current.