For groups that cannot
simply “join a waitlist.”
Global and luxury retailers evaluate technology through security, privacy, integration, and store operations — not a signup form. This is how a Nova6 engagement actually runs, written for the people who have to approve it.
Four workstreams,
one accountable team.
Security & privacy review
DPIA support, data-processing agreement, biometric consent model, retention schedule, and penetration-test summary shared under NDA before any store work begins.
Integration architecture
Catalog, inventory, pricing, and imagery ingested from your existing PIM or feed. Checkout hands off to your POS and e-commerce stack rather than replacing them.
Flagship pilot
One or two flagship doors, a defined shopper journey, agreed success metrics, and a fixed evaluation window — before any group-wide rollout commitment.
Commerce intelligence reporting
Conversion, AR engagement, try-on lift, and assortment signal delivered to your merchandising and CRM teams in a format they can act on.
Under 90 days,
with an exit at every stage.
Scoping & security
Architecture review with your IT, security, and privacy teams. DPA, data-flow map, and residency plan agreed in writing.
Catalog integration
Product feed ingestion, imagery pipeline, size and fit model tuned to your assortment, staged in a non-production environment.
Flagship install
Aura Mirror installed in the pilot door, staff training, and a soft-launch period with your visual merchandising and store teams.
Measure & decide
Results reviewed against the metrics agreed in phase one. Extend, adjust, or stop — with your data exported either way.
Timelines are the standard Nova6 pilot scope and are confirmed per retailer during phase one. Nova6 is pre-general-availability; SOC 2 Type II and ISO 27001 certification are in progress.
What your security team will ask about.
- Explicit, revocable shopper opt-in before any capture
- Encryption in transit and at rest; retailer-owned data, exportable on request
- EU data residency; GDPR, CCPA and BIPA-aligned architecture
- SSO, role-based access, and audit logging for retailer staff accounts
Four questions we’ll ask you.
- Which flagship doors are in scope, and in which markets?
- Who owns the security and privacy sign-off on your side?
- What does your product feed look like today, and who maintains it?
- Which metric would make this a success for your merchandising team?
Talk to our team.
Tell us who you are and we’ll come back with an architecture and pilot outline scoped to your group — not a generic deck.