Australian hosting, audited access, and isolated credentials.
Customer Zero is operated by IKMJ (Ikigai & Majime Pty Ltd), an active Australian private company registered in Victoria. Where we don't hold a certification yet, each entry names the control behind it so you can check it yourself.
Hosting in Melbourne & data sovereignty
- Region
- Melbourne, Victoria
The entire production stack runs on Google Cloud Platform in Melbourne, Victoria. Customer data does not leave Australia.
- Replication
- Single-region, no cross-region failover
Data is not copied to overseas regions. Enterprise customers can request disaster-recovery details under NDA.
- Operating entity
- IKMJ (Ikigai & Majime Pty Ltd)
An active Australian private company registered in Victoria that operates Customer Zero. ikigaimajime.com.au
Credential isolation & the churn cascade
Credential reference architecture
Source-system credentials (access tokens, service accounts, OAuth refresh tokens, and API keys) are never persisted in the application database. They live in Google Secret Manager as opaque versioned resource references, and the application resolves them at use.
projects/…/secrets/…/versions/NPlaintext access tokens do not appear in any application table, log line, or error payload. The secret-manager client recursively redacts secret references from logs before they reach the structured log sink. Rotating a compromised credential takes one secret-version bump, and the next request uses the new value without an application redeploy.
Database-level churn cascade
When a subscription flips to is_active = false, a database trigger atomically deactivates its instances, transitions them to CHURNED, and revokes derived grants. The trigger ships as migration 20260811012200_churn_cascade_trigger, so no application path can leave a derived grant active past its parent subscription.
subscription.is_active = false
→ instances deactivated
→ state = CHURNED
→ derived grants revoked
(one transaction, in the database) Every state-changing action (provisioning, granting, rotating, revoking, source connection, source churn) writes an immutable AuditEvent row in the same database transaction as the change it records. Audit rows cannot be edited afterward.
Audit trail
Authenticated operators can read their own tenant's audit log through GET /audit-events. Each event carries an actor, a verb, a target resource, and a structured payload, enough to reconstruct any authorisation decision after the fact.
Access control & tenant scope
Tenant scope comes from the server, not the request. The clientId and subscriptionId that gate every query come from the authenticated session cookie, not from any client-supplied parameter. The service layer rejects a cross-tenant probe before it reaches Prisma, and writes the rejection to the audit log.
Access grants are instance-scoped. A user with access to Google Ads (Acme HQ) does not automatically have access to Google Ads (Acme APAC). Each instance carries its own grant record naming the source instance, the consumer user, and the AI client runtime (Claude, ChatGPT, Gemini Enterprise) the grant is valid for.
Transport & browser security
| Control | Setting | What it does |
|---|---|---|
| HSTS | max-age=31536000; includeSubDomains; preload | Browsers refuse plaintext HTTP for the entire customerzero.ikmj.com.au subtree for the lifetime of the preload list. |
| Content Security Policy | script-src 'self' | Scripts load only from the site's own origin. The policy blocks unsafe-eval and remote stylesheets, forbids framing from any origin (frame-ancestors 'none'), and disables cross-origin embedding. |
| Permissions Policy | Camera, microphone, geolocation, payment, USB all disabled | Asks the browser to deny every sensor and device class the platform does not use. |
| Session | HttpOnly, Secure, SameSite=Lax cookie + CSRF token | Client JavaScript cannot read the session cookie (__session), and it is never sent over plaintext. Tenant scope is derived from it on the server. |
| CSRF token | Session-bound token in X-CSRF-Token header | Every state-changing request made with the session cookie must carry this token, so a third-party page cannot act on a signed-in session. |
Operational transparency
Source connections report four status classes: Healthy, Needs attention, Stale, and Access lost. Each source reports its status independently, so operators can see which connection failed.
Every state-changing endpoint requires an Idempotency-Key header. Replays within the 24-hour TTL return the stored response without re-running business logic, so a double-submitted form cannot double-charge an account or issue a credential twice.
Compliance status
Customer Zero does not currently hold SOC 2, ISO 27001, or IRAP certification. Pursuing those certifications is on the roadmap, and this page will be updated as each is earned.
Enterprise customers and procurement teams can request a security questionnaire response, a current sub-processor list, and the platform's data-flow diagram from sales@customerzero.app.