Get the right route

Questions should reach a working destination.

Ekvidu is in private development. Existing customers can use the authenticated support workspace; new visitors can create an account or inspect the public evidence method while a public contact channel is prepared.

01 / Customer benefit

What this should help you do

Keep account and product questions attached to the correct workspace and audit trail.
Avoid sending sensitive evidence, credentials or personal data through an unverified public channel.
Use a clear route for product access, existing-customer support or evidence-method questions.

02 / Deliverables

What you can expect to receive

01
Authenticated support requests with visible status history
02
A secure account entry route for approved environments
03
Public method, security, privacy and FAQ documentation
04
A future public contact channel only after ownership and retention are configured

03 / How it works

The important detail

Existing customer or tester

Sign in and open Support from the customer workspace. Requests and replies remain visible to the workspace and follow the implemented support and data-rights lifecycle.

Interested in testing Ekvidu

Create an account in an enabled environment. Access to live collection remains controlled while owner-site dogfood, provider cost and operational acceptance are being completed.

Security or privacy question

Review the public security and privacy routes first. A verified external reporting address and its handling policy must be approved before this page advertises one.

Do not send passwords, API keys or session tokens.
Do not include raw provider evidence unless an authorised support flow asks for it.
Use the authenticated data-rights workflow for export, correction or deletion requests.

04 / Limitations

Where the boundary is today

No public support email, telephone number, sales form or response-time promise is published today.
Creating an account does not guarantee beta admission, enable paid collection or start billing.
Credentials, provider keys and raw sensitive evidence must never be submitted through a general contact request.

05 / Next step

Continue with a working destination.

Existing users can reach the authenticated workspace; new users can choose Create account from the header.

Preparing the sample workspace…

Get the right route

Questions should reach a working destination.

01 / Customer benefit

What this should help you do

Keep account and product questions attached to the correct workspace and audit trail.
Avoid sending sensitive evidence, credentials or personal data through an unverified public channel.
Use a clear route for product access, existing-customer support or evidence-method questions.

02 / Deliverables

What you can expect to receive

01
Authenticated support requests with visible status history
02
A secure account entry route for approved environments
03
Public method, security, privacy and FAQ documentation
04
A future public contact channel only after ownership and retention are configured

03 / How it works

The important detail

Existing customer or tester

Sign in and open Support from the customer workspace. Requests and replies remain visible to the workspace and follow the implemented support and data-rights lifecycle.

Interested in testing Ekvidu

Create an account in an enabled environment. Access to live collection remains controlled while owner-site dogfood, provider cost and operational acceptance are being completed.

Security or privacy question

Review the public security and privacy routes first. A verified external reporting address and its handling policy must be approved before this page advertises one.

Do not send passwords, API keys or session tokens.
Do not include raw provider evidence unless an authorised support flow asks for it.
Use the authenticated data-rights workflow for export, correction or deletion requests.

04 / Limitations

Where the boundary is today

No public support email, telephone number, sales form or response-time promise is published today.
Creating an account does not guarantee beta admission, enable paid collection or start billing.
Credentials, provider keys and raw sensitive evidence must never be submitted through a general contact request.

05 / Next step

Continue with a working destination.

Existing users can reach the authenticated workspace; new users can choose Create account from the header.