How we are structuring Adquant for secure public launch and private product access.

The current live experience is a public marketing site with a product preview. This page explains the controls already relevant to the site today and the operating commitments we are carrying into the private application stack.

Last updated April 2, 2026

Current site surface

The public website is a static-first Next.js experience with client-side motion and no direct customer data ingestion pipeline running from the browser today. That sharply limits exposure while the deeper application stack is being built.

Planned access model

The intended product flow uses Google-based workspace sign-in, scoped workspaces, and controlled activation for brand accounts. Workspace access should remain tied to explicit onboarding, role ownership, and auditable review of generated outputs.

Data handling principles

We are designing the product around least-privilege access, clear retention boundaries, environment separation, and careful handling of brand materials submitted for DNA generation, campaign drafting, or integration sync.

Operational controls

The production target includes monitored deployments, dependency review, request logging, access review, and incident handling procedures for the private application stack. Public infrastructure and legal documents are being prepared ahead of those systems going fully live.

Security contact

If you need to report a vulnerability or request a security review before onboarding, contact hello@adquant.ai. We will route the request to the appropriate product or infrastructure owner.