How we publish customer evidence
NeuraIQ publishes testimonials, case studies, and customer logos under a written methodology. This page documents that methodology in one place - so buyers, journalists, and enterprise procurement teams can verify what they see on our product pages.
How we verify testimonials
Every testimonial on the NeuraIQ website is drawn from a signed engagement or from written feedback recorded during a live deployment. Nothing is invented, paraphrased into stronger language, or sourced from a review site aggregator.
Where a customer has not granted written permission to publish their full name, we display initials and a role plus a general location (suburb or region). The customer's identity is on file under signed engagement records and is available for verification under NDA on request.
Metrics quoted alongside a testimonial (shrink reduction, incident counts, alert response times) are measured against that same customer's 90-day pre-deployment baseline for the same store. We do not average across customers or use industry survey figures in place of real customer results.
- Sources: signed engagement records, written customer feedback, direct deployment logs
- Names: shown in full only where written permission is on file; otherwise anonymised to initials + role + region
- Metrics: measured against each customer's own 90-day pre-deployment baseline for the same store
- Verification: available under NDA on request via admin@neuraiq.com.au
How we measure case-study results
Case-study metrics on this website are measured directly from customer deployments, not modelled. Each case study is drawn from a signed engagement.
Customer names, site locations, and store identifiers on case-study pages are withheld at each customer's request. Named attribution is added on a case-by-case basis as each customer grants written permission - not on a marketing schedule.
Reported outcomes (percentage shrink reduction, incident counts, alert latency) are calculated against the customer's own 90-day pre-deployment baseline for the same store. Where a customer's baseline is shorter than 90 days, the shorter interval is stated on the page.
- Baseline: 90 days of customer's own pre-deployment data for the same store
- Attribution: named only with written permission; otherwise anonymised to region and category
- Time-to-result: measured from deployment go-live, not from contract signature
- Verification: available under NDA via admin@neuraiq.com.au
Customer logos and named references
NeuraIQ displays a customer logo only when the customer has granted signed written permission for that specific use. We do not display logos scraped from press releases, sourced from case-study consortiums, or shown under implied consent.
Where we display a single named customer, the surrounding claim is worded to match: "Trusted by <Customer>" - not "Trusted by leading Australian pharmacies" (which would misrepresent a single-customer state as a plural one). As additional customer permissions are added, the claim scales with the count.
- Permission: written and specific to the use case shown
- Wording: 1 logo -> named singular; 2 logos -> named pair; 3+ -> plural category
- Removal: any customer can request logo removal at any time via admin@neuraiq.com.au
What we publish and what we deliberately do not
NeuraIQ operates under a written internal disclosure policy that determines what technical detail is published on marketing surfaces and what is kept behind an NDA. The policy is applied to every product page, blog post, and comparison shown here.
We publish enough for a buyer to make an informed evaluation - product category, buyer outcome, integration surface (existing CCTV / on-premises hardware / customer's own cloud tenant), commercial model (subscription vs one-off), Australian data residency, and privacy posture (on-premises, no cloud uploads). We do not publish foundation model families, ML architecture descriptors, detection technique names, ingest protocols, OEM hardware SKUs, training data sources, prompt templates, or third-party cloud AI providers used inside any product.
This is not a marketing choice. It is a deliberate risk-management position - naming those elements narrows what our engineering team can change under the same product name, and gives competitors an unnecessary head start on any replication attempt. Buyers who need this detail can request it under NDA.
- Published: category, outcome, integration surface, commercial model, data residency, privacy posture
- Withheld (public): foundation model names, ML architecture, hardware SKUs, prompt templates, training data
- Available under NDA: any of the above, with reference customer introductions where appropriate
- Verification: request via admin@neuraiq.com.au
Third-party sub-processors used by this website
Products like IntelliGuard, NeuraMate, NeuraHome, and NeuraBots run on-premises on NeuraIQ appliances - customer video, energy telemetry, and workflow data stay on the customer's own hardware. This section covers only the neuraiq.com.au marketing website and its form-submission and analytics infrastructure - not the products themselves.
The website relies on a small set of vendors. Every vendor listed below is engaged under contract; none receive customer product data (video, workflow content, energy telemetry, appliance logs).
- Vercel - static hosting, edge routing, and server-rendered pages for neuraiq.com.au. Serves HTML, images, and the /api/hubspot/submit form proxy.
- Upstash (Sydney region) - rate limiting for the HubSpot form-submission API route. Stores request-count keys tied to hashed IPs; no personal data.
- HubSpot - form submissions from /contact and /request-a-demo are proxied server-side to HubSpot; optional website tracking script loads only after cookie consent is granted.
- Google Analytics 4 - optional website analytics; loads only after cookie consent, with anonymised IP and no cross-site advertising signals.
- Google Fonts - Comfortaa and Orbitron are loaded via next/font and self-hosted at build time; no runtime call is made to Google.
How to reach NeuraIQ about an incident or verification request
The primary contact for anything time-sensitive - security incident reports, customer support escalation, journalist verification requests, procurement due diligence, or NDA access requests for withheld technical detail - is a single email address monitored by the founding team.
NeuraIQ does not yet publish product-specific SLA numbers or a formal support tier structure - those commitments only get published once we can measure and meet them consistently. Live customer engagements have contracted escalation paths agreed in writing at the time of engagement.
- Primary contact: admin@neuraiq.com.au (monitored during Australian Eastern Time business hours)
- Phone: 0434 673 004 (business hours)
- Live customer escalation: as defined in each signed engagement
- NDA access to withheld technical detail: request via admin@neuraiq.com.au