Subprocessors

1. What “subprocessor” means here

A subprocessor is a service provider Anphase Ltd uses to process information on its behalf when operating hosted svc.nz. The label is used transparently and does not by itself decide the legal role of every provider for every data flow.

This page covers the hosted service. A self-hosted svc.nz operator chooses its own infrastructure and providers.

2. Amazon Web Services

Provider

Amazon Web Services (AWS)

Purpose

Application compute, private object and metadata storage, key and secret management, infrastructure logs, monitoring, alerts, and service email delivery.

Primary region

Sydney, Australia (ap-southeast-2).

Data involved

Stored content and metadata, hashed credential state, audit events, request and error metadata, support or contact email when AWS email delivery is used.

The storage bucket blocks public access, requires encrypted transport, and uses server-side encryption. S3 bucket versioning keeps non-current metadata versions for recovery; those non-current versions are configured to expire after seven days. The content-addressed blob pool has no time-based deletion lifecycle, because bytes shared between boxes cannot be expired by age without removing data another box still refers to. Stored bytes are instead removed by a reference-aware collection process the operator runs, and object storage keeps a non-current copy of anything it removes for seven days.

3. Cloudflare

Provider

Cloudflare

Purpose

Authoritative DNS, reverse proxying, edge caching for public assets, TLS delivery, bot and abuse controls, and protection of the AWS origin.

Location

Cloudflare’s global network; request processing may occur at an edge outside New Zealand or Australia.

Data involved

IP address, requested hostname and path, headers, timestamps, device and network signals, security events, and public cached assets. Capability headers may transit Cloudflare on their way to the origin.

The AWS origin requires a secret added at the Cloudflare boundary so directly addressing the raw origin does not bypass edge controls. Capabilities are still bearer credentials; the edge boundary is not a substitute for narrow scope, rotation, or client-side encryption.

4. Services you direct

A webhook destination you configure, a recipient to whom you send a capability, your own HTTP client or automation platform, and an email provider you use to contact us are not selected as svc.nz subprocessors for your content. They process information because you direct or choose them. Review their terms and privacy practices.

Webhook deliveries contain matching operation metadata, not stored object bodies, under the current implementation. A destination URL and optional shared secret are stored as part of the box configuration.

5. Provider safeguards

We select established infrastructure providers, limit their use to operating and securing the service, scope service permissions, and configure security and retention controls appropriate to the private trial. Overseas service-agent processing is handled consistently with the New Zealand Privacy Act 2020; the Privacy Policy explains locations, disclosures, and rights.

No supplier can make an early private trial risk-free. Keep another copy of important bytes, use client-side encryption for sensitive plaintext, and do not use the hosted trial for data requiring a formal data-processing agreement or compliance certification.

6. Changes to this list

We will update this page before or when a new material subprocessor begins processing hosted service data. Because capability-only users may have no account email, publication here is the primary notice. Where we have a suitable contact channel and a change is material, we will try to provide an additional notice.

Questions about a provider can be sent to svc@anphase.co.nz.