Report Illegal or Infringing Content

This is the notice-and-action mechanism that Audexum provides under Article 16 of Regulation (EU) 2022/2065 (the Digital Services Act). It is the single route for telling us that content on or from the Service is illegal, infringes your rights, or breaks our Acceptable Use Policy.

We host content that users give us. That includes:

• Public share clips at audexum.com/s/… — audio a user chose to publish, readable by anyone with the link, with no sign-in
• Podcast feeds generated from a user's audiobook
• Files users upload to be processed — books for audiobook generation, video and audio for dubbing, recordings for voice enrollment
• Audio our models generated for a user, including cloned voices
• Images and videos generated with our image and video tools, and the images users upload to them, including those published on a share page

We do not review any of it before it is generated or published, and no law requires us to go looking. What this page creates is the duty to act once you tell us.

Email is the only channel on which we accept notices. Every address below has been tested and delivers. Mail to any other address at our domain does not exist and will bounce, so please use one of these four.

If you send it to the wrong one of these four, we will route it internally rather than make you resend it. We do not publish a telephone number and we do not take notices by phone.

Article 16(2) of the DSA sets out what makes a notice complete enough for us to act on. Please include all five:

1. Why you believe the content is illegal or infringing — a plain explanation is fine. If it is illegal under a specific law, name it if you can.
2. The exact location. The full URL, for example https://audexum.com/s/<clip id>. One notice may list several URLs. A description without a URL or a file we can identify is usually not enough for us to find the content. For an image or video, the share page URL is best; if you only have the file, send it, or the file name, which starts with audexum- and contains the media id we need.
3. Your name and email address. You may leave these out only for a report concerning child sexual abuse material or a sexual offence against a child. For everything else we need to be able to reach you, and we cannot act on an anonymous claim of rights.
4. A statement that you believe, in good faith, that the information in your notice is accurate and complete.
5. If you are claiming a right — copyright, trade mark, your own voice or image — say what the right is and how you hold it. See sections 6 and 7.

Read this before you send. If your notice leads to a counter-notice or to a dispute, we will pass your notice, including your name and email address, to the person who posted the content. That is how they get a fair chance to answer. If that is a problem for you, say so in the notice and we will tell you what we can do before we forward anything.

We will not tell you who the uploader is. Their identity is their personal data and we disclose it only to an authority or a court that has the power to require it.

We are honest about the ceiling. The abuse mailbox is read by a person, not monitored around the clock, so the true worst case for a non-urgent notice sent on a Friday night is the following week. We are not promising a 24-hour takedown, because a single operator cannot deliver one every day of the year.

Automated steps, and who decides. A person reads every notice and makes every decision on it. We do not run automated content scanning of published content. There are two automated steps. First, our image and video tools run safety checks that can refuse a generation before the user receives it; that is a refusal to produce something, not a decision on a notice. Second, when anyone reports a public share link of an AI-generated image or video, that link is switched off automatically the moment the report arrives, as an interim measure until a person reviews it. The owner keeps the file in their library, and we email them straight away to say the link was restricted, why, that the step was automated, and how to contest it. A person then decides whether the link stays off. Blocked and reported media are always reviewed by a person.

What we can do about content, in ascending order: leave it up; remove the public share link so the clip stops being reachable; delete the file; disable a cloned voice; suspend a feature; suspend or terminate the account. Which we choose is set out in /aup.

Notices from entities awarded trusted flagger status under the DSA are handled ahead of other notices. Tell us your status in the notice.

If we remove, disable, restrict or demote content, or suspend a feature or an account over it, we send the affected user a statement of reasons under Article 17 of the DSA. It says:

• What we did, and to which content or which account
• Whether it affects the content only, the feature, or the whole account
• Whether we acted on a notice from someone else, on an order from an authority, or on our own review
• The ground: which law we think it breaks, or which part of /terms or /aup it breaches, and why the content falls under it
• Whether automated means were used. A decision on a notice is always made by a person; the one automated step is the interim switch-off of a reported media share link (section 4), and the statement we send at that moment says so
• How to appeal, and by when

We send it as soon as we act, to the account's email address. We withhold it only where telling you would break the law or wreck a live investigation by an authority — and where the restriction is lifted later, we tell you then.

Audexum offers voice cloning. That means we can be the tool used to make a synthetic voice of someone who never agreed to it, and reporting that is the reason this section exists. Our rules on whose voice may be enrolled are in /aup.

Email [email protected] with VOICE in the subject line. Say that the voice is yours, or that you act for the person whose voice it is, and that you did not agree to it. Include the URL of the clip, or the file. We prioritise these and aim to decide within 5 working days.

What helps us decide faster:

• The exact URL of the clip, or the audio file itself
• A link to a genuine recording of your voice that predates the clip
• Anything showing who you are, if the voice is a public one
• If you act for someone else, what your authority to act is
• Where else the clip is circulating, if you know

We can check for our watermark. Almost every audio file our production service delivers carries an AudioSeal watermark in the signal, and it survives MP3 encoding and ordinary re-encoding. Send us the file and we can run a detector over it. Read the result carefully: a positive result says the audio carries an AudioSeal watermark, which is consistent with our output but is not a unique Audexum identifier — other services using the same open watermark would also match. A negative result does not prove the audio is not ours, because heavy re-processing can degrade any audio watermark. It is evidence, not proof, and we will tell you which it is in your case. How the watermark works is described at /ai-disclosure.

If we conclude a cloned voice was enrolled without the speaker's agreement, we disable the voice, remove the clips made from it that you identified, and act against the account under /aup.

Send rights claims to [email protected]. Include everything in section 3, plus:

1. The work. Identify what is being infringed — the book, the recording, the track, the film, the mark. A link to the original helps.
2. The infringing material. The URL on our service, or enough to let us find the file.
3. Your standing. Say whether you are the rightholder or authorised to act, and how.
4. A good-faith statement that the use is not authorised by you, your agent or the law — note that quotation, parody, criticism, review and other exceptions under Directive 2001/29/EC can make a use lawful without your permission.
5. A statement that the information is accurate, and that you accept you are responsible for it.

Designated contact. Rights claims are received and decided by the operator named at /imprint, at [email protected]. We have not appointed an outside agent, and any notice sent to that address reaches the person who decides it.

Counter-notice. If we take your content down over a rights claim and you believe the claim is wrong, reply to the statement of reasons, or write to [email protected], with: the content and where it was, why you are entitled to use it, your name and email, and a statement that you believe in good faith the content was removed in error. We pass a counter-notice to the person who complained. If the two of you disagree on facts we cannot resolve, we may leave the content down and tell you both to settle it between yourselves or in court — we are not a tribunal and we will not pretend to be one.

If we agree with your counter-notice, we restore the content, tell the complainant, and the strike against your account is removed.

Report it to [email protected] with URGENT in the subject. You do not have to give your name. Do not attach the material itself — send the URL.

We remove it, terminate the account, preserve what an investigation would need, and report it to the competent authorities in Bulgaria. This takes precedence over everything else on this page. There is no appeal that restores such an account.

If you believe someone is in immediate danger, contact the police first — 112 anywhere in the EU. We are not an emergency service and we cannot act at that speed.

Report vulnerabilities to [email protected], not through the abuse route. Tell us what you found, how to reproduce it, and what an attacker could reach. Give us a reasonable time to fix it before you publish.

The rules for testing — what is in scope, what is not, and the undertaking we give researchers who stay within them — are in /aup. We do not run a paid bug bounty and we do not promise a reward.

Both sides can appeal, on the same route: [email protected], within six months of our decision.

• If your content was removed or your account restricted — quote the account email and the statement of reasons, and say why you think we got it wrong.
• If you reported something and we did not act — quote our reply and tell us what we missed.

A person reviews the appeal. We aim to answer within 14 days and we will tell you the outcome and the reason for it. If we were wrong we reverse it, restore the content and the account, and put back any credits affected.

You are never limited to us. You can take the dispute to a court, and if you are a consumer in the EU you can bring proceedings in the courts of the country where you live. You can also contact the consumer authority where you live, or the Bulgarian Commission for Consumer Protection (Комисия за защита на потребителите). We are not signed up to any out-of-court dispute settlement body and we do not claim to be.

We keep a record of the notices we upheld against an account. If, after being told at least twice that specific content or conduct infringes someone's rights or breaks /aup, the same account does it again, we treat the holder as a repeat infringer and terminate the account.

We do not count notices we assessed and rejected, notices the sender withdrew, or notices overturned on appeal. A single serious infringement can be enough on its own. Before we terminate on this ground we give notice and a chance to answer, unless the content is child sexual abuse material or someone is at immediate risk. Opening a new account to get around a termination is itself a material breach of /terms.

We may reject, and stop processing, notices that are manifestly unfounded, that are sent in bulk without anyone checking them, or that are sent to silence lawful speech or to damage a competitor. Where someone does this repeatedly we warn them first and then suspend their use of this reporting route, as Article 23(2) of the DSA allows.

A notice we disagree with is not a bad-faith notice. Getting it wrong in good faith costs you nothing here. Knowingly making a false statement in a notice can carry consequences under the law that we do not control.

This is the single point of contact required by Articles 11 and 12 of the DSA. It serves Member State authorities, the Commission and the European Board for Digital Services, and it serves users — there is no separate address for either.

• Orders to act against illegal content (Article 9) and orders to provide information (Article 10): [email protected]
• All other communications from an authority: [email protected]
• Communications from users about content: [email protected]
• Languages: English and Bulgarian. Send it in either. We can read a notice in another EU language but we will answer in English or Bulgarian, and a translation may slow us down.

We are established in Bulgaria, so the Bulgarian Digital Services Coordinator is our supervising authority. Full operator details, including the status of the company registration, are at /imprint. We give effect to a valid order and tell the affected user what we did and on whose order, unless the order or the law says otherwise.

We have not designated an electronic point of contact separate from these addresses, and we do not currently publish DSA transparency reports: we understand the Article 15(2) exemption for micro and small enterprises to apply to us at our present size. We will publish one when it stops applying.

• Your own personal data. Access, correction, erasure and objection go to [email protected] and are described at /privacy.
• Billing disputes and refunds. See /refunds.
• Content on other websites. If audio made with Audexum has been published somewhere else, we can act on the copy we host, not on the copy they host. Tell us anyway — the account behind it is still ours to deal with.
• Third-party software notices. See /attributions.

We may update this page as the product and the law change. The current version is always the one at /report, with its version number and date at the top. It sits alongside /terms and /aup; where this page and the Acceptable Use Policy describe the same step, they are meant to say the same thing, and if they do not, tell us at [email protected] and we will fix it.