No. An official API benchmark keeps that label. It is not called ChatGPT, Gemini, Perplexity, AI Overview or another consumer experience unless a permitted, matched fidelity study supports that exact claim.

No. An answer can mention a brand without citing it; a citation may not create a visit; a visit may not convert. Ekvidu is designed to keep those events separate and use owner-authorised analytics only when available.

The target record includes the frozen question, provider/model or benchmark, access method, locale, time, status, answer, mention, citation/source detail and evidence lineage. Coverage includes invalid, retried, cancelled and not-run cells rather than hiding them.

There is no approved public price or checkout. Future pricing depends on measured provider, storage and support cost during dogfood, plus useful observation volume, brands, users and reporting needs.

The intended workflow uses account and organisation details, authorised brand/domain configuration, prompts, competitors, observed provider answers and sources, annotations, usage/security records and—only after separate approval—billing and support data. The privacy route lists current gaps.

There is no paid public subscription to cancel today. Self-service export, deletion, retention, legal-hold and backup-expiry journeys are planned but not yet complete, so this build must not promise a finished deletion service or timeframe.

The production target is an owner-operated deployment on Coolify with separately isolated web, API, worker and data responsibilities. That is an internal operating architecture, not a promise of an on-premises or customer-managed distribution.

No. A useful follow-up must be fresh and compatible with the baseline. Even then, it shows an observed change under recorded conditions; it does not by itself establish exclusive causality.