Portal Terms and Conditions

Last updated: 12 June 2026. This page reflects the current portal legal source and is written for a New Zealand business context. It is not legal advice.

Contents

1. Roles and access
2. Account security and authorised use
3. Electronic records and approvals
4. Files, content, and credentials
5. Payments, third parties, AI, and operational controls
6. Suspension, updates, and liability

1. Roles and access

• Portal roles include admin, staff, client, and affiliate. Role labels do not guarantee authority beyond the access actually granted in the portal.
• Submitting a registration or access request does not create an automatic right to use the portal or receive services. We may require email confirmation, manual approval, identity checks, role assignment, payment confirmation, or additional information before access is activated or expanded.
• Authorised staff or admin users may review requests, manage users, inspect records, process payments, support projects, moderate files, and operate the portal where reasonably necessary to provide services, protect security, investigate misuse, comply with law, fix account issues, or maintain reliable records.
• You must not share access, lend credentials, use misleading business details, bypass role limits, scrape private data, upload malicious files, interfere with the portal, or allow unauthorised use of your session.

2. Account security and authorised use

• You are responsible for keeping your email access, password, sign-in code, devices, and session access secure.
• The portal may use email confirmation, passwords, one-time codes, session cookies, role checks, Turnstile, rate limits, audit logging, and account status controls.
• We may invalidate sessions, require password reset, refuse login, block submissions, restrict permissions, or suspend access if we suspect compromise, abuse, fraud, security risk, privacy risk, or policy breach.
• Actions taken through a valid session may be treated as actions of the account holder or represented organisation unless we are satisfied that the action was unauthorised and promptly reported.

3. Electronic records and approvals

Portal notices, checkboxes, buttons, typed names, drawn signatures, dates, submitted forms, approvals, legal documents, quote records, invoice records, support requests, file activity, project notes, role changes, audit logs, email confirmations, IP addresses, user agents, timestamps, document versions, and document hashes may be created, accepted, stored, and relied on electronically.

A registration checkbox may record acceptance of portal terms. A typed name or drawn signature may be used as an electronic signature. We may treat the evidence bundle connected to a signed or accepted record as proof that the user saw, accepted, approved, requested, or submitted the relevant item, unless there is clear evidence of error, fraud, or promptly reported unauthorised access.

4. Files, content, and credentials

• You must only upload or submit material you own, control, are authorised to use, or have permission to provide for the project.
• Do not upload unlawful, infringing, deceptive, harmful, malicious, private, or sensitive material unless we have agreed to receive it and a suitable secure method is used.
• Passwords, private keys, tokens, seed phrases, payment card numbers, government identity documents, and other high-risk credentials should not be placed in general notes or ordinary uploads unless we have specifically requested that method.
• We may remove, restrict, or preserve files and records where required for security, legal compliance, operational integrity, support, backup, audit, or dispute purposes.

5. Payments, third parties, AI, and operational controls

• Portal payments, invoices, subscriptions, bookings, domain requests, referrals, and support workflows are operational tools and may depend on third-party providers such as Stripe, domain registrars, DNS providers, hosting platforms, Cloudflare, Microsoft, Google, email providers, analytics systems, AI providers, plugins, themes, marketplaces, and external APIs.
• We are not responsible for third-party outages, rejected accounts, DNS propagation, provider downtime, payment processor decisions, app review outcomes, plugin vulnerabilities, or changes outside our control, except to the extent caused by our own breach of an express obligation.
• AI-assisted features may support search, drafting, website generation, content suggestions, compliance summaries, or admin assistance. AI output is draft material only and must be reviewed before reliance, publication, invoicing, scope decisions, payment decisions, or deployment.
• Where enabled, authorised admins may impersonate a user session for legitimate support, troubleshooting, account repair, quality assurance, security investigation, or operational maintenance. Impersonation activity may be logged with the admin identity, reason, timestamp, target account, and affected records.

6. Suspension, updates, and liability

We may suspend, restrict, terminate, or refuse portal access or service where reasonably necessary for security, unpaid invoices, suspected fraud, legal risk, privacy risk, abusive conduct, provider requirements, inactive accounts, unauthorised access, conflicting instructions, or protection of our users, staff, contractors, clients, systems, or providers.

We may update these terms when portal features, legal requirements, security practices, service models, pricing, third-party providers, or operational risks change. We may require a new checkbox, electronic signature, or renewed acceptance for material changes. To the maximum extent permitted by law, liability is limited and nothing in these terms excludes rights that cannot lawfully be excluded.