Privacy, in plain language.

Information we handle

When you contact Qallor, we may collect your name, work contact details, organisation, workflow description, expected call volume, current systems, and correspondence.

For a contracted demo, pilot, or service, the agreed workflow may involve caller or customer details, call metadata, conversation transcripts, recordings where enabled, system events, and operational outcomes. The exact data set should be documented in the service scope.

How we use it

• Reply to enquiries and prepare tailored demonstrations.
• Design, test, operate, support, and improve an agreed voice workflow.
• Connect calls to customer systems and produce the agreed records, handoffs, and analytics.
• Protect the service, investigate faults, and meet legal obligations.

Website analytics

We use PostHog to understand how this website is used. It records pages viewed, clicks on labelled elements such as navigation and call-to-action buttons, page performance measurements, and technical details including browser, device type, referring page, and an approximate location derived from your IP address. This is stored in your browser using cookies and local storage.

Analytics is limited to the website. The contents of a contact brief are not sent to our analytics provider: when a form is submitted we record that a submission happened and which use case was selected, not your name, email address, company, or the workflow you described.

PostHog processes this data on infrastructure in the United States. You can block it with browser privacy settings, a tracking blocker, or by declining cookies in your browser, and the website will continue to work normally.

Calls, AI, and recording

Production call flows should identify that the caller is interacting with an AI assistant. If recording is enabled, the workflow should include an appropriate recording disclosure and any consent process required for the use case.

Qallor and the customer agree which party provides notices, manages calling permissions, supplies approved content, and receives human escalations before a production pilot begins.

Service providers and overseas processing

Qallor relies on cloud hosting, telephony, AI model, communications, integration, and security providers to deliver the service. Our current platform infrastructure is primarily hosted in Google Cloud's asia-south1 region in India. Data may also be processed or stored by providers in other countries.

We do not guarantee that data or model processing remains in New Zealand or Australia. Relevant processing locations, access, and safeguards should be reviewed and agreed for each production use case.

Sharing

We share information with service providers only as needed to operate the website or deliver the agreed service, and with customer-authorised systems and people. We may also disclose information when required by law, to protect people or the service, or as part of a business transaction subject to appropriate safeguards. We do not sell personal information.

Retention, access, and deletion

We keep information for as long as reasonably needed for the purpose collected, service operation, security, dispute handling, and legal obligations. Pilot-specific retention and deletion arrangements should be agreed in writing; this notice does not promise automatic recording-retention controls.

You may ask to access, correct, or delete personal information by emailing hello@qallor.com. We may need to verify the request and may retain information where law or a legitimate operational requirement allows. Rights under applicable privacy law, including the New Zealand Privacy Act 2020 where it applies, are not limited by this notice.

Security and changes

We use administrative and technical measures intended to protect information, but no online or voice service can be guaranteed completely secure. We may update this notice as the service changes and will publish the revised date on this page.

Contact

For privacy questions or requests, email Qallor at hello@qallor.com. The formal contracting entity and any additional privacy contact details should also appear in the signed service documents.