Privacy policy · Launch review

A plain-language view of how CRMZI handles information

Effective 24 September 2026. This launch policy is transparent about current product handling and the operational details still being finalised.

1. Scope

This launch privacy policy describes how CRMZI handles information used to provide its website and CRM and accounting workspace. It should be read with the Terms of Use and any onboarding or order documents supplied to an account owner.

2. Information handled

CRMZI may handle account and profile information; business and team details; client, contact, opportunity, project, proposal, invoice, transaction and account information entered by authorised users; authentication, usage and security events; subscription and billing references; and information included in support requests. Do not enter information you are not authorised to use.

3. Why information is used

Information is used to provide and secure the service, authenticate users, operate requested product functions, administer trials and subscriptions, respond to support, maintain operational records and comply with applicable legal obligations.

4. Service providers

CRMZI may rely on service providers for hosting, authentication, infrastructure, monitoring and subscription billing. Where Stripe checkout is enabled, payment details are entered into Stripe’s hosted checkout rather than a CRMZI card form. Provider, subprocessors and data-location details must be confirmed during launch onboarding when they are material to your business.

5. Business and client data

An account owner is responsible for the information their team enters, including having an appropriate basis to store client and contact information. CRMZI processes that information to provide the requested workspace functions and does not make customer records public through the marketing website.

6. Retention, export and deletion

Production retention periods, deletion timeframes and export service levels are being finalised for general availability. Launch users should confirm the current process before adding records that are subject to a specific retention, residency or deletion requirement.

7. Security

CRMZI uses signed-in access and role-based operational controls in the current product. No internet service can guarantee absolute security. Review the Trust & Security page for current safeguards and items that still require formal confirmation.

8. Access and correction

Account owners and authorised users can review many business records inside the product. Requests concerning access, correction, export or deletion should be made through the contact method provided during onboarding until a public privacy contact is published.

9. Changes and contact

This policy may change as CRMZI moves from launch review to general availability. Material commercial use should rely on the version supplied with the relevant order or onboarding documents. Privacy questions can be raised through the current onboarding or support channel.