Copyright complaints

1. Send a copyright notice

Email svc@anphase.co.nz with the subject “svc.nz copyright notice”. The notice should come from the rights owner or a person authorised to act for them.

Do not include a live svc.nz capability in the first notice. Send the safe object URL, box id, object name, and version. If access is required to assess material that is not otherwise available, we will agree on a safer method.

2. Information a notice should include

• your full name, organisation if relevant, email address, telephone number, and postal address;
• identification of the copyrighted work or other protected material, with an original URL, registration, publication detail, or representative list where useful;
• the exact svc.nz box id, object name, version, or safe object URL for each item complained of;
• an explanation of why the use is infringing and is not authorised by the rights owner, its agent, or law;
• a statement that you have a good-faith belief the information is accurate and that you own the relevant rights or are authorised to act for the owner;
• any territorial or timing information relevant to the rights; and
• your typed or physical signature.

Broad demands to remove an entire service, unsupported keyword lists, or reports that do not identify a locatable object may not be actionable.

3. What we do with a notice

We may check that the notice is complete, ask for clarification or evidence, inspect relevant metadata or content where reasonably necessary, restrict access while assessing risk, and consider licences, exceptions, fair dealing, public-domain status, and other context.

Where we know or have reason to believe stored material infringes copyright, we may disable the object or box, invalidate access, preserve relevant records, or take other appropriate action. Where contact is possible, we will notify the affected user as soon as reasonably practicable after deleting material or preventing access, consistent with section 92C of the Copyright Act 1994 and other applicable law.

A notice is not automatically proof of infringement. We may decline action where the claim is incomplete, implausible, abusive, outside our control, or reasonably answered by evidence of permission or lawful use.

4. If your content is affected

If you receive notice that content was restricted, you may respond to svc@anphase.co.nz with:

• your name and reliable contact details;
• the affected box, object, and version;
• why you believe the material is yours, licensed, in the public domain, covered by fair dealing or another exception, or misidentified;
• supporting documents or links; and
• a good-faith statement that your response is accurate.

We may forward the substance of a response to the claimant where lawful and reasonably necessary, normally after removing secrets and unrelated personal information. Restoration is not guaranteed and will not occur where the content independently breaches the Acceptable Use Policy or law.

5. Trade marks and other rights

For trade mark, trade secret, confidentiality, publicity, or similar claims, use the same address and clearly identify the right, owner, relevant jurisdiction, exact svc.nz object, alleged violation, and your authority. Privacy, harassment, and harmful-content reports should use the Abuse Process.

6. False or abusive claims

Do not knowingly make a false claim, misrepresent your authority, omit material context, or use this process to suppress lawful criticism, competition, research, or speech. We may reject abusive notices, share them where lawfully necessary to resolve a dispute, restrict a reporter who repeatedly misuses the process, and seek recovery for harm caused by deliberate misrepresentation where law allows.

Consider obtaining independent legal advice if ownership, licensing, fair dealing, or territorial scope is genuinely disputed. We cannot act as a court or provide legal advice to either side.

7. Technical and retention limits

svc.nz stores opaque bytes and does not search for matching works across boxes. We need a precise locator. Disabling or deleting an object removes normal API access at once; the underlying content-addressed blob is permanently erased by a reference-aware collection process that runs automatically each day, within thirty days of the last reference to it going. The Privacy Policy explains retention and deletion in detail.