Acceptable Use Policy

Draft for review. This policy forms part of the Terms of Service.

Last updated: [date]

1. The principle

This is a tool for sending work to the people it belongs to. Almost everything a photographer, editor, designer or studio does falls comfortably inside it. This page exists for the small number of cases that do not.

2. Do not send

Things you have no right to send

• Work that belongs to someone else, without their permission.
• Material that infringes copyright, trade marks, design rights or patents.
• Confidential information you are not allowed to pass on.

Things that harm the person receiving them

• Viruses, ransomware, keyloggers, or any code intended to damage or take control of a device.
• Phishing kits, fake login pages, or files designed to deceive someone into giving up credentials or money.
• Files disguised as something else to get past a check — for example an executable named to look like a photograph.

Things that are illegal

• Child sexual abuse material. This is reported to the authorities without exception and without notice to the account holder.
• Content that incites violence or terrorism.
• Material that is unlawful where you are, or where your recipient is.

Things that harm other people's privacy

• Personal data about someone else that you have no lawful basis to share.
• Intimate images shared without the subject's consent.
• Doxxing: compiling someone's personal details in order to expose or endanger them.

3. Do not misuse the service itself

• Do not use it as a content delivery network, a public download mirror, or a substitute for hosting. Transfers are for delivering to named recipients, not for publishing.
• Do not use it as long-term storage or as a backup. Files are deleted at expiry, by design.
• Do not create accounts automatically, in bulk, or to get around a limit or a suspension.
• Do not attempt to guess transfer links, enumerate them, or reach files you were not given a link to.
• Do not probe, scan or stress-test the service without written permission. If you want to report a vulnerability, see section 6 — we would rather hear from you.
• Do not resell the service, or present it as your own, unless your plan expressly permits it.

4. How this is enforced

We do not monitor the content of transfers, and we cannot see inside them in the ordinary course of running the service. Enforcement is driven by reports, by automated signals about volume and file type, and by legal requirements.

When something is reported to us, we look at the specific transfer complained about and nothing else. Depending on what we find we may do nothing, suspend the single transfer, suspend the account, or — where the law requires it — report the matter and preserve evidence.

The response is meant to match the problem. A first accidental breach usually gets an explanation and a chance to fix it. Deliberate abuse, and anything in the "illegal" list above, does not.

5. If you think we got it wrong

Write to [support email] with the transfer link and what you think happened. A person will look again. If we made a mistake we will restore the transfer and say so.

6. Reporting

To report a transfer, use the report form — it reaches the right place faster than email. To report a copyright infringement specifically, see the copyright page, which explains what a notice needs to contain.

To report a security vulnerability in the service itself, email [security email]. Please give us a reasonable period to fix it before disclosing it publicly. We will not pursue you for good-faith research that respects other people's data and does not degrade the service.