Legal

Copyright and Takedown Policy

We respect copyright and act on properly made notices. This page explains what we host and what we do not, where to send a notice, how to dispute one, and what happens to accounts that repeatedly infringe. It follows the process the Digital Millennium Copyright Act sets out, as a matter of policy rather than because we have registered an agent under it.

Effective
Last updated
Version
1.1.0

1. What we host — read this first

In plain language: Almost certainly, the page you want removed is not on our servers. We are a drafting tool: articles live in private accounts, and when a customer publishes, the article goes to their own website. We cannot remove anything from a website we do not run.

To be precise about what is and is not on our systems:

  • Articles, drafts and versions are private. They are visible only to the account that created them. There are no public profiles, no share links, no comments and no public directory of customer content. Nothing a customer writes here is published by us or indexed by search engines.
  • There is no upload feature. Customers cannot upload files or images to us at all.
  • Generated images are the exception. Images produced by the Service are stored in our object storage and served from a publicly reachable URL, because publishing platforms fetch images from a URL when a post is created. This is the one place material sits on our infrastructure at an address anyone with the link can reach, and it is the material this policy can actually act on.
  • Our own marketing blog is written and published by us. If something we published infringes your copyright, tell us and we will deal with it directly.

If your complaint concerns material in one of those categories, or you believe a customer is using the Service to infringe your rights, this policy is the right route and we want to hear from you.

2. How to file a notice of claimed infringement

In plain language: Email your notice to [email protected]. It needs to contain six specific things — if any are missing we may not be able to act on it, so please include them all. They are listed plainly below.

Send notices of claimed infringement to [email protected], with "Copyright Notice" in the subject line so it is routed correctly. That mailbox is monitored and is the right route for every copyright matter on this page, including counter-notifications.

The elements below are the ones 17 U.S.C. §512(c)(3) sets out for an effective notice, and we ask for them because they are what lets us identify the material and act with confidence. A notice missing them may leave us unable to locate what you are describing, and we may have to come back to you before we can do anything.

  1. Your signature — physical or electronic — as the owner of an exclusive right that is allegedly infringed, or as a person authorised to act on the owner’s behalf.
  2. Identification of the copyrighted work you say has been infringed. If several works at one site are covered by a single notice, a representative list of them.
  3. Identification of the material you say is infringing and that you want removed or disabled, with enough detail for us to locate it — for a generated image, the full URL. A description alone is rarely enough.
  4. Your contact details: name, postal address, telephone number and email address.
  5. A statement that you have a good-faith belief that the use of the material in the manner complained of is not authorised by the copyright owner, its agent, or the law.
  6. A statement that the information in the notice is accurate, and — under penalty of perjury — that you are the copyright owner or authorised to act on the owner’s behalf.

A copy of your notice, including your contact details, may be forwarded to the account holder whose material is affected, and may be sent to a public repository of takedown notices. Redact anything you do not want disclosed, bearing in mind that the elements above must remain.

This mailbox is for copyright and other legal matters. General enquiries sent there will be redirected to [email protected] and will take longer to answer.

3. What we do when we receive a notice

In plain language: We check it is complete, remove or disable the material expeditiously, tell the account holder what happened and why, and pass on your notice so they can respond.

On receiving a notice that substantially complies with §512(c)(3):

  1. We acknowledge receipt and review the notice for completeness. If elements are missing, we will tell you what they are.
  2. We expeditiously remove or disable access to the material identified.
  3. We notify the account holder, tell them the material was removed in response to a copyright notice, provide them a copy of the notice, and explain their right to submit a counter-notification.
  4. We record the notice against the account for the purposes of our repeat-infringer policy.
  5. Where the account holder is using an affected feature, the relevant capability may be restricted while the matter is open. Restrictions of that kind limit what an account can generate or publish; they never limit its ability to read, edit or export its own content.

We act in good faith and without judging the merits of a copyright claim, which is not something we are equipped to adjudicate. Removal is not a finding that infringement occurred.

4. How to file a counter-notification

In plain language: If your material was removed and you think that was a mistake, you can say so — email [email protected]. Sending one means agreeing that a US court can hear the dispute, which is a real commitment, so read this before you do.

If material of yours was removed or disabled in response to a notice and you believe that was a mistake, or that the material is not infringing, you may send us a counter-notification. Email it to [email protected] with "Copyright Counter-Notification" in the subject line. We follow the process in 17 U.S.C. §512(g)(3), and ask for the same elements it sets out.

A counter-notification must include:

  1. Your signature, physical or electronic.
  2. Identification of the material that was removed or disabled, and the location at which it appeared before it was removed.
  3. A statement under penalty of perjury that you have a good-faith belief that the material was removed or disabled as a result of mistake or misidentification.
  4. Your name, address and telephone number.
  5. A statement that you consent to the jurisdiction of the Federal District Court for the judicial district in which your address is located — or, if your address is outside the United States, of any judicial district in which we may be found — and that you will accept service of process from the person who filed the notice, or their agent.

On receiving a compliant counter-notification, we will promptly forward it to the person who filed the original notice and tell them we will restore the material in 10 to 14 business days. We will restore it in that window unless the complainant first tells us they have filed a court action seeking to restrain the allegedly infringing activity.

5. Repeat infringer policy

In plain language: Accounts that keep infringing get closed. We count notices that stand — not ones that were withdrawn or successfully disputed — and we look at the circumstances rather than applying a fixed number mechanically.

In accordance with 17 U.S.C. §512(i), we have adopted and reasonably implement a policy of terminating, in appropriate circumstances, the accounts of subscribers who are repeat infringers.

How we apply it:

  • We record every notice that substantially complies with §512(c)(3) against the account concerned.
  • A notice that is withdrawn, or successfully answered by a counter-notification, does not count towards repeat-infringer status. Counting a disputed notice would let a bad-faith complainant close a customer’s account.
  • An account that accumulates repeated valid notices will be warned, then restricted, then terminated. We do not publish a fixed threshold, because circumstances differ and a published number is an invitation to stop one short of it.
  • A single instance of serious or wilful infringement — commercial-scale copying, or circumventing a technical protection measure — may lead to immediate termination.
  • Where we terminate an account under this policy, we will tell the account holder the reason, and we will give a reasonable opportunity to export content that is not the subject of a notice.

We also reserve the right to remove material, or restrict an account, where we have a good-faith belief that doing so is required by law or by these policies, whether or not a formal notice has been received.

In plain language: AI drafts can resemble existing work, and we do not check them against published material. If you publish a draft, you are the publisher of it. This is why reviewing before publishing matters.

Content produced by a generative model can resemble material the model was trained on, and generated images in particular can resemble existing images. We do not screen output for originality: no plagiarism or duplicate-content detection runs in this product, and our Terms of Service say so.

That places a real obligation on customers. If you publish generated content, you are the publisher of it, and you are responsible for having the rights to what you publish. Reviewing a draft before it goes live is not a formality.

We do not use customer content to train models. Questions about how the underlying model providers handle training data are addressed in our Privacy Policy.

7. Trade marks and other complaints

In plain language: This page is about copyright. For trade mark, defamation, privacy or other complaints, write to the same address and tell us what the problem is.

This policy addresses copyright specifically. For a trade mark complaint, a defamation or privacy complaint, or any other allegation about material on our systems, email [email protected] with a description of the material, its location, the right you say is affected, and your contact details. We will review it and respond.

For complaints about material on a customer’s own website, please see the first section of this page — we are not able to act on those.