A plain-language draft of how Ekvidu intends to handle data.

Data and purpose

The intended service may process account identifiers, organisation and brand configuration, verified domains, prompts, competitors, provider answers, citations, sources, annotations, usage records, support records and security events. The purpose is to operate the authorised evidence workflow, secure it, support the customer and, only after approval, administer billing.

Provider answers and prompts may contain customer-confidential material. They are treated as tenant data rather than public marketing content.

Access, retention and deletion

The design calls for least-privileged access, customer-visible scoped support grants, encrypted evidence storage and separate retention by data class. Access, export, correction, deletion, legal-hold and backup-expiry workflows still require complete implementation and acceptance before launch.

Cookies and external services

Account access requires security/session cookies. Consent-aware public analytics, identity, evidence storage, AI providers, email and billing services are subject to separate selection, configuration and disclosure gates. This draft does not name an unapproved vendor as a live subprocessor.