Takedown & Abuse Policy

1. Scope

This policy covers notices about content distributed through yasync.com transfer links: copyright infringement (DMCA and equivalent claims), malware, child sexual abuse material (CSAM), doxxing and dumped personal data, and any other content that is illegal under German law, EU law, or the law applicable to the notifier.

The development deployment stores the notice and offers an authenticated admin kill switch, but no staffed review, legal decision, notification, appeal, or preservation workflow is operational. A launch process must limit authorised review to the reported transfer, document the decision, and remove unlawful content in line with the privacy policy and terms.

2. Copyright: DMCA takedown notices (17 U.S.C. § 512)

This section records the information a future staffed DMCA process must handle; yasync does not currently claim an operational US safe-harbour process or registered designated agent. Under 17 U.S.C. § 512(c)(3), your written notice must include all six of the following elements:

1. A physical or electronic signature of the copyright owner or of a person authorized to act on the owner’s behalf.
2. Identification of the copyrighted work claimed to have been infringed — or, if multiple works are covered by a single notice, a representative list of those works.
3. Identification of the material claimed to be infringing and information reasonably sufficient to permit us to locate it — for yasync.com this means the exact transfer link (yasync.com/t/…) and, where a transfer contains multiple files, the file name(s) concerned.
4. Information reasonably sufficient to permit us to contact you: name, address, telephone number, and email address.
5. A statement that you have a good-faith belief that use of the material in the manner complained of is not authorized 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 authorized to act on behalf of the owner of the exclusive right that is allegedly infringed.

Incomplete notices may not create actual knowledge under § 512. A launch-ready process must explain missing information where the notice permits contact. Knowingly material misrepresentations can make you liable for damages under 17 U.S.C. § 512(f).

3. DMCA counter-notice procedure required before launch

No counter-notice channel or staffed restoration workflow is operational in development. Before launch, a counter-notice under 17 U.S.C. § 512(g)(3) must be able to include:

• your physical or electronic signature;
• identification of the material that was removed or disabled and the location at which it appeared before removal (the transfer link);
• a statement under penalty of perjury that you have a good-faith belief the material was removed or disabled as a result of mistake or misidentification;
• your name, address, and telephone number, and a statement that you consent to the jurisdiction of the federal district court for your judicial district (or, if you are outside the United States, any judicial district in which we may be found) and that you will accept service of process from the person who filed the original notice or their agent.

A launch-ready process must forward a valid counter-notice to the original notifier and handle the statutory court-action and restoration windows. No such forwarding or restoration is currently claimed. Transfers on the free tiers expire after 24 hours regardless, so restoration is often moot in practice.

4. EU: notice and action under the Digital Services Act (Art. 16 DSA)

Anyone — individuals and entities alike — can notify us of content they consider illegal under EU law or the law of an EU member state. The report form is the electronic intake portion of the planned notice-and-action mechanism. It stores a notice and returns a case ID, but review, decisions, notifications, and redress are not staffed. A complete notice for that future process contains:

• a sufficiently substantiated explanation of why you consider the content to be illegal;
• the exact electronic location of the content — the transfer link (yasync.com/t/…) and, where relevant, the file name(s);
• your name and email address — except for notices concerning offences under Articles 3 to 7 of Directive 2011/93/EU (child sexual abuse material), which may be submitted anonymously;
• a statement confirming your good-faith belief that the information and allegations in the notice are accurate and complete.

Our commitments when you file a notice:

• the form confirms durable receipt immediately and returns a case ID (Art. 16(4) DSA);
• before public launch, a staffed process must review and decide in a timely, diligent, non-arbitrary, and objective manner (Art. 16(6) DSA);
• before public launch, our case-handling process must notify you of the decision and available redress options (Art. 16(5) DSA); outbound decision email is not enabled in development;
• before public launch, where the uploader is reachable, our case-handling process must provide a statement of reasons for any restriction — what was restricted, the facts and legal or contractual ground, and how to contest it (Art. 17 DSA) — unless we are legally prevented from doing so.

Before launch, the staffed process must also implement the warning and proportionate suspension rules for manifestly unfounded notices under Art. 23 DSA.

5. Repeat-infringer procedure required before launch

The terms prohibit repeat infringement, but the strike, notification, appeal, and termination workflow is not operational in this development deployment. Before launch it must ensure that:

• substantiated decisions can be linked to an account and recorded as strikes;
• repeated strikes within a defined reasonable period can lead to account termination after prior warning — or immediately where the violation is severe (in particular CSAM or malware);
• creating new accounts to circumvent a termination is prohibited, and we may use technical measures to prevent it — including for anonymous senders;
• affected users are informed of the decision and reasons and can respond, as described in our terms.

6. Law enforcement

A reachable law-enforcement and Art. 11 DSA authority contact is not configured in this development deployment and must be published before launch (see the compliance page). The operating procedure must request the legal basis, exact transfer link(s), and scope of data sought, and support communication in English or German.

Before launch, the authority procedure must disclose data only on a valid German or EU legal basis and must include a counsel-approved preservation/legal-hold path. The current trash window is an operational recovery mechanism, not a claimed legal-hold system.

No CSAM reporting claim is made for this development deployment. Counsel must determine the exact statutory reporting channels and the operator must staff and test the escalation runbook before launch.

7. Related pages

• Report form — the fastest way to file a notice.
• Terms of service — acceptable use and what happens on violations.
• Privacy policy — what we store about reports and reporters.
• Compliance — DSA points of contact and our processors.