← DoAi

Privacy & Cookie Settings

This notice describes privacy behavior implemented by DoAi's website and workspace shell. It does not replace separate terms that may apply to connected third-party services.

DoAi's public analytics paths are designed to be cookieless. There are no optional advertising or analytics cookies to enable or disable on this page, so DoAi does not show a consent toggle that would imply such cookies exist.

If your browser sends Global Privacy Control or Do Not Track, DoAi suppresses its first-party page-view measurement and Clics product-event measurement. You can control those browser privacy signals in your browser or privacy software.

Analytics

DoAi uses a cookie-free first-party page-view event when browser privacy preferences permit analytics. Public pages use their normal path. Authenticated application routes are reduced to the coarse path /app, and account routes are reduced to /account.

The event is limited to the coarse page path, referring hostname, screen dimensions, and server-side request metadata. It does not include conversation text, prompts, filenames, user IDs, email addresses, authentication tokens, or connected-service content. DoAi does not use advertising networks for this first-party event.

The public site serves a pinned copy of the Clics tracker for cookieless aggregate measurement. Before sending, DoAi reduces page and referrer URLs to origin and a bounded route, collapses published routes to /p and unknown application routes to /app, keeps only approved UTM campaign parameters limited to 120 characters, and removes URL fragments. Clics receives those bounded URLs plus product-scoped events such as signup completion, first chat, response completion, page engagement, navigation, and feedback. DoAi does not send conversation text, prompts, filenames, account identifiers, authentication tokens, URL fragments, or connected-service content to either analytics path.

Support and product feedback

When you choose to send product feedback or contact DoAi Support, DoAi collects the name you provide together with the feedback or support fields needed to handle the submission. Depending on the form, those fields can include a feedback rating or reason, support category, message, the DoAi page path where the submission came from, and whether it came from the in-product feedback prompt or support page.

Names and support-message text are stored through DoAi's first-party support path and are not copied into Clics product analytics or DoAi's operational audit-log details. Support submissions are used to understand product problems and respond to support needs. Do not submit passwords, API keys, payment-card numbers, authentication tokens, or other secrets through feedback or support forms.

Privacy preference signals

The first-party page-view and Clics product-event paths are not sent when Global Privacy Control is enabled or when the browser reports Do Not Track. Support and product-feedback submissions are user-initiated communications and are sent only when you choose to submit them.

Authenticated workspace data

The signed-in workspace can process account-owned content such as conversations, files, projects, tasks, or connected-service context when those features are used. Authentication and access controls are separate from website analytics.

Security

Security reporting information is published at /.well-known/security.txt.

Changes

This notice may be updated when implemented data flows change. The update date above is machine-readable and visible to users.