Skip to content
whisk
FeaturesGuidesDocsPricingStatus
Sign in
whisk
FeaturesDocsGuidesComparisonsLearnSkillStatusSecurityContact
TermsAcceptable usePrivacyData processingTakedown
  • Terms of service
  • Acceptable use policy
  • Privacy policy
  • Data processing agreement
  • Takedown process
  • Security disclosure policy

Takedown process

Last updated 3 October 2026.

This is how Whisk ("we") handles a complaint that something served from whisk.page, or from a custom domain that points at Whisk, infringes your rights or breaks the law. Whisk hosts apps that other businesses build and run; we do not write them, read their data or review their content in advance. The fastest route is often the app's own operator, whose contact details are usually on the app itself.

1. What you can report

  • Content that infringes your copyright, trademark or other intellectual property.
  • Content that is unlawful where you are: defamation, private information published without consent, and the like.
  • Content that breaks the Acceptable use policy: phishing, malware, material that exploits children, incitement to violence.
  • Personal data about you held in an app, where you cannot reach the app's operator. We pass such requests to the organisation that runs the app, which is the controller of that data, as the Data processing agreement requires.

Security weaknesses in the platform itself are not takedowns; use the Security disclosure policy.

2. How to send a notice

Email support@whisk.run with the subject "Takedown". Give us all of this:

  1. The exact URL or URLs, and what is at them.
  2. What right or rule is broken, and why you believe so. For copyright, identify the work and where the original is; for trademark, the mark and its registration; for personal data, what the data is and why it should not be there.
  3. Your name, organisation if any, postal address and email, and whether you are the rights holder or act for them.
  4. A statement that you believe in good faith that the use is not authorised and that the information in the notice is accurate, and, where the law where you are requires it, that you make it under penalty of perjury.
  5. Your signature, physical or electronic.

A notice that lacks these is answered with a request for what is missing, and the clock in section 4 starts when it is complete. We may publish the notice, with your personal details removed, in the transparency report described in section 9.

3. Copyright notices under the United States DMCA

A notice under the Digital Millennium Copyright Act needs the five items above, which are the elements section 512(c)(3) asks for. Send it to our designated agent:

FieldValue
Designated agentNot yet registered
AddressAuckland, New Zealand
Emailsupport@whisk.run
Copyright Office registrationNone today

Whisk has not registered a designated agent with the United States Copyright Office, so the section 512 safe harbour is not available to us in the United States. We publish the agent's name and registration here when we register one. Send the notice to support@whisk.run in the meantime; we handle it on the timeline in section 4 whether or not the safe harbour applies. In New Zealand we rely on the safe harbour for internet service providers in sections 92B to 92C of the Copyright Act 1994, and the process on this page is how we meet it.

4. Our timeline

StepWhen
Acknowledge the noticeWithin 2 business days
Assess it: is it complete, does it describe a breach we can act on, is the content actually served by WhiskWithin 5 business days
Forward it to the organisation that runs the app, with the material removed from the notice that would identify you where the law allows, and ask them to remove the content or answerOn assessment
Disable the content if the organisation does not act5 business days after forwarding, or at once where the content is clearly unlawful, is a danger to people, or is a repeat

"Disable" means the least we can do that stops the harm. Usually that is asking the organisation to remove the content, then, if they do not, freezing the app so it shows a maintenance page. We do not read into an app's database to remove one record, because we cannot see it; the organisation does that.

Clearly unlawful material of the worst kind (child sexual abuse material, terrorist content) is removed on sight, preserved as the law requires, and reported to the authorities.

5. What we tell the organisation

When we act against an app we tell its owners, in writing and at the time:

  • what we did, and to which URLs, app or organisation;
  • why: which law or which rule of the Acceptable use policy, and the facts we relied on;
  • whether the decision came from a notice, our own detection, or an order from an authority;
  • that they may appeal under section 6, and how;
  • whether the measure is temporary or permanent.

Where an authority has ordered us not to tell them, we do not, and we tell them as soon as we may.

6. Counter-notice and appeal

The organisation that runs the app may answer a notice with a counter-notice. It must give their name and contact details, the URLs, a statement under penalty of perjury where the law requires it that they believe in good faith the content was removed by mistake or misidentification, and their consent to the jurisdiction of the courts where they are. We forward it to you. Unless you tell us within 10 business days that you have started proceedings, we restore the content. We are not a court; where you and the organisation disagree, the courts decide and we follow what they order.

Separately from a counter-notice, either the reporter or the organisation may appeal a decision we made, including a decision not to act, by replying to us within 30 days of being told. A person who did not make the original decision reviews it and answers within 10 business days, with reasons. We restore content, or act on a notice we wrongly refused, where the appeal shows we got it wrong.

7. Repeat infringers

An organisation that receives three upheld notices in twelve months is warned that the next ends its account. An organisation whose apps are used mainly to infringe is terminated at once. Termination follows the Terms of service; the organisation's export works throughout, except that content we are required to withhold is withheld.

8. Abuse of this process

A notice that is knowingly false, or is used to silence lawful content, is refused, and the sender may be liable to the organisation whose content was affected and, in the United States, under section 512(f) of the DMCA. Where someone repeatedly sends notices that are unfounded, we may stop handling their notices for a period, after warning them. We keep every notice and counter-notice for six years.

9. Transparency

Once a year we publish a report on the trust page: how many notices we received, of what kind, how many we acted on, how many we refused, how many were appealed and with what result, and how many orders we received from authorities and courts. We publish no names.

Whisk does not offer the Service in the European Union in a way that brings it within the EU Digital Services Act, so we do not treat that Act as applying to us today. If that changes we say so here. Either way, support@whisk.run is the single point of contact for authorities, for the Commission and for anyone using this page, and it takes messages in English.

10. Court orders and lawful requests

We comply with orders from a court with jurisdiction over us, and with lawful requests from authorities, in the narrowest way the order allows. We check that the request is valid and properly served before we act. Where we may, we tell the organisation concerned before we act, so they can respond; where we are forbidden to tell them, we tell them as soon as the prohibition lifts. Requests go to support@whisk.run or Auckland, New Zealand, and we do not accept service of legal process by any other route.

Contact: Whisk, Auckland, New Zealand, support@whisk.run.

See also: Terms of service · Acceptable use policy · Privacy policy · Data processing agreement · Security disclosure policy