Report content

What this channel covers

Content generated through spicyapi that breaches the content policy: material involving a minor, intimate or sexualised depictions of a real person made without their consent, impersonation of a real individual, and anything unlawful where you or we are located.

It also covers misuse of the API against a third party — for example, an application built on it that is targeting someone.

What to include

A report is easier to act on when it carries three things:

1. The task identifier or the artefact object key. This is the fastest route to the record. If the content reached you through someone else's product you may not have it, and that does not stop the report.
2. Where you encountered it. A public post, a message, an application — anything that lets us understand the distribution path.
3. A description of what is wrong. In your own words. It does not need to cite a clause.

What not to send

Do not attach, paste, forward or link the material itself. Describe it and give us the identifier.

For content involving a minor this is not merely a preference: retransmitting the material is a criminal offence in most jurisdictions, including by the person reporting it in good faith. It also does not help — the record on our side is reachable from the identifier, and we do not need a copy from you.

Reporting without identifying yourself

You can leave the contact field blank. An anonymous report is read and assessed the same way as any other.

The trade-off is that we cannot acknowledge it, cannot ask a follow-up question, and cannot tell you the outcome. Where you are willing to be contacted, an address makes a real difference to how quickly a report can be resolved — and the privacy policy explains what happens to it.

If you are the account holder

The same channel handles appeals. If a key lost a capability or an account was restricted and you believe the decision was wrong, reply on the thread and ask for a second review. It is carried out by someone other than the person who made the first decision.

Reports about your own data

The console provides a self-service data export and a safe account-closure request after a fresh security check. Closure is blocked, with reasons shown, while tasks, balances, top-ups or team ownership remain unresolved. Other access, correction, restriction, objection or deletion requests go to the same address as reports and are handled manually. The privacy policy explains the export scope and which billing, audit, security and reconciliation records remain after closure.

Intellectual property notices

A copyright or trade mark claim goes to the same address but follows a different form, because a valid notice has formal contents a free-text report does not capture. Section 11 of the content policy lists what to include and how to mark the subject line.

Please do not file these through the form above. Keeping them separate is what stops an infringement claim and a report about a minor from sharing a queue.

Misusing this channel

Reports made in bad faith — to harass an account, to remove lawful content, or to test the process — waste the time that the serious ones need. Repeated bad-faith reports from an account are treated as a breach of the terms of service.

That is not a reason to hesitate over a genuine one. A report that turns out to be mistaken is not a report made in bad faith, and it is not held against you.

Where this is going

The form on this page assembles a report and hands it to your email client or your clipboard; nothing is transmitted from the page itself. That is a deliberate interim design while the receiving endpoint is built — a form that appears to submit and silently goes nowhere would be worse than none, because the person reporting would believe they had reported.

The email address is monitored and is the channel of record. When the endpoint exists, this page will submit directly and the address will keep working alongside it.