Ekvidu is operated by Aleksander Celewicz under the Auvoris name. Aleksander is currently responsible for deciding how personal information is used. Auvoris is not yet a limited company.

For privacy questions or requests, email hello@auvoris.com and mention Ekvidu. This is the contact published on the Auvoris website. If responsibility later transfers to a registered company, this notice will be updated and affected users informed.

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.

The local launch-list implementation stores an email address, the consent version, registration time, a hashed withdrawal receipt and, after withdrawal, its time. The browser also keeps the email and withdrawal receipt in session storage for retry and withdrawal. Saving information on a server is retention, even when it is only used to run the service. A launch request is not an account or a grant of access.

The local implementation also records when a receipt is issued, when its registration permission expires and whether it has been used. Invitation records hold identifiers, preparation and attempt times, and an outcome: accepted, not accepted or uncertain. Acceptance by an email service would not prove that an email reached your inbox or was read.

Launch contact is optional and based on your consent to hear when Ekvidu access opens. It is not consent to unrelated Auvoris marketing. You can browse the public website without joining the launch list.

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.

In the current local launch-list implementation, withdrawal marks a request as withdrawn but does not erase its email address. It must not be presented as deletion. A finite retention schedule and verified erasure process are required before public collection is enabled.

Locally implemented expiry rules make a launch request eligible for erasure 12 months after registration, 30 days after withdrawal, or 30 days after the first recorded invitation acceptance, whichever comes first. These are product retention choices, not statutory periods. Production scheduling and backup expiry have not been verified, so these periods are not yet an operational promise.

The receipt's permission to register expires after 24 hours; that does not mean the saved launch request expires after 24 hours. Browser session restoration can also preserve the browser's receipt. Withdrawal and later erasure are separate steps.

You can contact hello@auvoris.com to ask about information held about you, request correction or deletion, or raise a privacy concern. Depending on the processing and applicable law, rights also include access, restriction and portability. You can object to processing based on legitimate interests and withdraw consent where consent is used. These rights have legal limits; they are not a promise that every record can always be removed immediately.

If you still have your browser receipt, use Withdraw this request in the launch form. If you have lost it or changed devices, email hello@auvoris.com and mention Ekvidu and your withdrawal or deletion request. You do not need an Ekvidu account to contact us. Contacting us does not itself confirm that a record exists or has been deleted; address verification and request handling remain necessary.

You can also complain to the UK Information Commissioner's Office at ico.org.uk. You do not have to contact Ekvidu first.

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.