Responsible use

That right comes from owning the material, from a licence, or from the law. It never comes from us, because it was never ours to hand over. Everything below follows from that: we build the tool so that the question gets asked at the moment it matters, we keep a record that makes a complaint answerable, and we act when one arrives. What we do not do is pretend the judgement is ours. It is yours.

• A one-time acknowledgment. The first time you use the extension, it asks you to acknowledge that choosing what to copy, and having the right to copy it, is your responsibility.
• A confirmation for every new domain. The first time you copy from a given site, the extension asks you to confirm that you have the right to reuse that site’s material. It asks again for the next new domain, and the one after that.
• A separate approval for every destination. A copy is only ever delivered to an origin you have individually approved, and your browser asks you for access to that origin separately. You can withdraw an approval at any time.

Your answers to the first two are stored in your own browser. They are prompts, not paperwork, and the responsibility does not depend on them: under section 6.3 of the Terms, running a conversion is itself a warranty to us that you have the right to copy that page, whether or not the prompt was shown and whether or not the record of it still exists on your machine.

Some of these are policy. Most are architecture, which is the more useful kind of promise.

• It carries no tabs permission, so it cannot enumerate your browsing history or see pages you have not asked it to copy.
• It carries no debugger permission, so it cannot attach to the DevTools protocol, intercept network traffic, or step around browser security.
• It declares no content scripts. Until you grant site access, no wpgraft code runs on any page you visit, and broad access is requested at your first copy through the browser’s own prompt rather than silently at install.
• It never reads cookies, localStorage, sessionStorage, authorization headers or any credential. Not to send them, not to hold them, not at all.
• It never captures form-field data. Values you typed are never read, and values a site pre-rendered into the page are stripped before anything is transmitted. A password field additionally loses its name and placeholder.
• It never transmits JavaScript. Scripts, styles, meta and head nodes are discarded in your browser, and our conversion service accepts none.
• Where it re-fetches an image or a font that cross-origin rules put out of reach, the request is made with credentials explicitly omitted, and any address that does not resolve to a public internet host is refused.

The Privacy policy sets all of this out in detail, permission by permission.

We do not build anything that circumvents an access control, and we forbid using wpgraft to work around one. No paywall bypass, no login bypass, no defeat of a technical protection measure, no scraping of a members-only area you are not authorised for. That is section 6.4 of the Terms and it is not negotiable.

There is an honest caveat, and it is better said than left out. The extension reads what your browser has already rendered for you. If you are signed in to a page, nothing technically stops the extension from reading that page, because from its point of view it is simply the page on screen. We never receive your credentials and we never hold a session of yours. But the decision to copy such a page, and any duty of confidence you owe about what is on it, is yours, and the Terms prohibit doing it where the page shows other people’s personal data, financial account data, government identifiers or private messages.

wpgraft has no bulk mode, no crawler, no URL queue and no public API. One deliberate action copies one section, element or page, in the browser you are sitting in front of, on a site you have granted access to.

• Quota is counted and enforced on our servers, not in the extension.
• Calling our endpoints outside the extension and plugin, automating the Service, or running it at machine scale is prohibited by section 8 of the Terms, including on plans described as unlimited.
• “Unlimited” means unlimited for a person working, including heavy agency use. It is not a licence to point a script at a sitemap.

This matters more than it sounds. Most of the harm a copying tool can do comes from scale, and scale is the one thing this design does not offer.

We never store the pages you copy. Captured markup and styles pass through our conversion service in memory, are converted, and are returned to your browser. They are not written to disk or to any database, ever. There is no archive of copied pages to leak, subpoena or hand over, because there is no archive.

We do keep a record that a conversion happened. One row per successful conversion: your account identifier, the URL you copied from, the destination builder, a status, a duration and a timestamp. We keep it for 24 months.

We keep it for three reasons, and the third is the one this page is about: to meter your plan, to investigate conversions you report as broken, and so that a rights holder with a valid complaint gets a real answer instead of a shrug. Without it, a complaint about a copy of your site would reach a company that could truthfully say it had no idea who did it. We would rather be able to say who did it.

Your Library is outside all of this. The copies you choose to save are written to storage inside your own browser profile. We do not host it, receive it, sync it, back it up or index it, and we cannot produce it if asked. Keeping a copy there is still keeping a copy, and the rules about what you may copy apply to it exactly as they apply to what you publish.

• Copyright and trademark complaints. The procedure, what to send, and what we can do with it are on the Copyright complaints page. We acknowledge within five business days.
• Blocking a source domain. Where a rights holder asks, or where we have reasonable grounds, we may block conversions from a specific domain outright.
• Suspension and termination. Two valid, unrebutted complaints against one account normally produce a suspension and a warning; a third produces termination. We terminate repeat infringers.
• Impersonation is terminated on sight. Cloning a site to pass yourself off as a person or a business, to phish, or to deceive anyone about who is behind a page, ends the account immediately, without notice. There is no grey area in that case and we do not treat it as one.
• No refund follows a termination for breach. That is section 6 of the Refund policy, and it is deliberate: a policy that refunds people we removed for infringement is a policy that costs nothing to trigger.
• Disclosure. Where a rights holder has a valid claim, or where the law requires it, we may disclose the conversion record (account identity, source URL, timestamp) to them or to a competent authority.

A page like this is worth reading only if it is honest about its own limits, so:

• We do not review what you copy. Captures are not stored, which means they are also not inspected. There is no human and no filter looking at them.
• We cannot tell whether you have the right. No tool can. A page that belongs to you and a page that does not look identical to a parser.
• We do not monitor accounts, and we are not obliged to. What we do is ask at the moment it matters, keep a record that makes complaints answerable, and act on what reaches us.
• We are not a filter, and we do not market ourselves as one. The safeguards on this page reduce misuse and make it traceable. They do not make it impossible, and we would be lying if we said otherwise.

None of this is legal advice, and nothing on this page or in our support replies is advice you can rely on about a specific copy you are considering. Section 6.9 of the Terms has three questions worth answering yourself first.

If you have seen wpgraft used in a way this page rules out, such as a cloned site, an impersonation or a copy of work you own, write to [email protected]. Put Misuse report in the subject line, tell us what you saw and where, and give us a way to reach you. If you are the rights holder, the Copyright complaints page is the faster route and gets a formal answer.

You do not need an account with us to report anything.

Računarsko programiranje GUGUNOVIĆ Saša Gugunović s.p. Kozarska Dubica
JIB 4513290400009
Kodunaška 4, Kozarska Dubica, Bosnia and Herzegovina

[email protected] is one mailbox for everything: support, billing, privacy, copyright complaints, misuse reports and security disclosures. Put the subject in the subject line and it reaches the right place. Answered by a person.

See also: Acceptable use · Copyright complaints · Terms of service · Privacy policy