Use this page
For harassment, privacy violations, scams, illegal material, threats, or other harmful content.
svc.nz does not routinely inspect or index stored bodies. A precise report is how the operator learns that something is wrong and finds the box or object that needs attention.
For harassment, privacy violations, scams, illegal material, threats, or other harmful content.
The Copyright page asks for ownership, identification, and authority details needed for a rights claim.
The Security page covers good-faith testing, safe-harbour boundaries, and disclosure.
Email svc@anphase.co.nz with the subject “svc.nz abuse report”. Reports are handled by Anphase Ltd, the New Zealand operator of the hosted service.
This address is not continuously monitored and is not an emergency service. Reports are reviewed as operator capacity allows, with credible risks to safety, children, and active compromise prioritised.
A useful report contains:
Do not send passwords, account keys, encryption keys, refresh capabilities, or live access capabilities. Do not send child sexual abuse material or other illegal imagery as an attachment. Provide a safe locator and contact the appropriate authority.
If you want a notice handled under sections 23–25 of New Zealand’s Harmful Digital Communications Act 2015, say so clearly. A valid notice of complaint must state:
If we use the statutory safe-harbour process, the Act may require us to send the author a copy of a valid notice, removing identifying details where you do not consent, and give the author 48 hours to submit a counter-notice. If the author cannot be contacted after reasonable steps, or does not respond in time, the process may require disabling the specific content within the statutory timeframe. We may still remove content under the Terms even if an author objects.
Official guidance and complaint forms are available from the New Zealand Ministry of Justice. Netsafe is the approved agency for harmful digital communications and may also be able to help.
We may ask for clarification or proof of authority, check metadata and available records, preserve relevant evidence, restrict a capability or object while reviewing, notify an identifiable account holder, or refer the matter to a hosting provider, rights holder, Netsafe, law enforcement, or another appropriate body where lawful.
Possible outcomes include no action, a request for more information, throttling, capability invalidation, disabling an object or box, account suspension, deletion of references, or referral. The response depends on the report, available evidence, law, technical limits, urgency, and risk to others.
Because boxes usually do not carry an email address or verified identity, we may be unable to contact the person who stored the content. We will not disclose a reporter’s or author’s personal information except with consent or where otherwise permitted or required by law.
If someone faces an immediate risk of death or serious harm, contact emergency services in the affected location. In New Zealand, call 111 for an emergency. For suspected child sexual exploitation, contact New Zealand Police or the appropriate child-protection or law-enforcement body in your country. For harmful digital communications in New Zealand, Netsafe provides support.
After contacting the appropriate authority, you may also notify svc.nz with the safe locator and authority reference number. Do not delay emergency action while waiting for an email response from us.
If we can identify and contact you, we may tell you that content or access has been restricted and explain the general reason, unless notice would be unlawful, expose someone to risk, compromise an investigation, or reveal confidential security information.
You can respond with context, evidence of rights or consent, and the box or object details. For a statutory HDCA counter-notice, the response must include the information required by the Act and arrive within the applicable 48-hour period. A response does not guarantee restoration where the content breaches the Terms or law.
Disabling or deleting a box or version 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 the mechanism. We may preserve information where reasonably necessary for safety, investigation, legal compliance, or legal claims.
This process is intended to make complaints easy to submit and assess; it is not legal advice.