Skip to main content
The platform hosts the apps you publish. That means we are sometimes the address a third party uses to report content — copyright complaints, abuse reports, court-ordered removal requests. This page is the reference for how those reports move through the platform: who can file one, what the workspace owner sees, what timelines apply, and how the counter-notice path works. By the end you will know what to expect if a report names your workspace, and what to do if you believe a takedown was issued against your content in error.

​
Two distinct flows

Two report types reach the platform. They look similar from the outside but follow different procedures because they have different legal foundations. This page focuses on the copyright path because it is the one with a fixed procedure. Abuse reports follow the acceptable-use policy and are handled case by case. A complete notice must identify the allegedly infringing content (URL within a workspace’s published app), the work it allegedly infringes, the reporter’s contact information, and a signed statement of good-faith belief. Notices missing any required element are returned to the sender unprocessed; they do not reach the workspace owner. Once accepted, the notice moves through a short state machine: What the workspace owner sees:

​
What’s logged for every report

Every report — accepted or rejected, copyright or abuse — is recorded with the same evidence schema. The record is immutable once written; corrections are new records that supersede earlier ones. A workspace owner can read the records for reports against their workspace. The platform retains them indefinitely for legal and audit purposes — they are not subject to the workspace’s retention settings.

​
The counter-notice path

If the workspace owner believes the disabled content was disabled in error, they can file a counter-notice. The counter-notice must identify the disabled content, state under penalty of perjury that the disabling was a mistake or misidentification, and consent to the jurisdiction of the appropriate court. Once a valid counter-notice is filed:

​
Misrepresentation

A reporter or counter-noticer who knowingly submits a false statement may be liable for damages under the relevant copyright framework. The platform does not adjudicate misrepresentation claims — those are between the parties — but the evidence chain we retain is the record the parties or a court will reference. The practical consequence: file truthful reports and truthful counter-notices. The evidence bundle is preserved and your statement is part of it permanently.

​
Court orders and law enforcement requests

Court orders take a different path. They are reviewed by the trust team for facial validity (correct jurisdiction, signed by the issuing authority, names content the platform can identify). If valid, the workspace owner is notified unless the order specifically prohibits notification, and the action ordered is carried out within the order’s timeline. We do not pre-emptively remove content in response to law enforcement requests that are not orders. A request without an order goes back to the requester with an explanation of the order we would need.

​
What stays accessible during a takedown

Only the named content is affected. Specifically:

​
Where to file a report

Reporters: send to the address published in the platform’s acceptable use policy. Notices that arrive through support channels are routed to the same intake; we do not have an in-app reporting form because reporters are typically not workspace users. Workspace owners: counter-notices are filed from the takedown record in the console. There is no API for filing one — the form collects the statement under penalty of perjury that the counter-notice procedure requires.