The waitlist
This website stores the email address you provide, along with your optional name, agent preference, and use-case message. It also records the registration time and the version of the waitlist notice. The purpose is to register your interest and contact you about early access.
The form does not ask for payment details, API keys, credentials, screenshots, or access to your accounts. Please do not include confidential information in the use-case field. Joining does not create a paid subscription.
Protecting submissions
Waitlist records are held in the website’s hosted database and are not published. The form limits repeated submission attempts using a short-lived keyed hash derived from the request’s network address. The hash changes every ten minutes; old entries are removed during later submissions.
The animated logo
The hero logo responds to pointer movement only within your browser. This animation does not store or transmit cursor coordinates. It has a reduced-motion alternative.
The Clario product
Our priorities are purposeful permissions, visible actions, review before sensitive changes, and understandable data handling. These are design principles. Specific processing locations, providers, retention periods, and disconnection behavior have not yet been announced.
Agent choice and data
Individuals will use their own compatible agent rather than being required to use an agent hosted in Clario’s cloud. Existing context and memory are available only to the extent supported and authorized by that agent. Bringing an agent does not guarantee on-device processing: the runtime, model providers, and connected tools determine the data flow.
Enterprise infrastructure
Our planned paid enterprise service will help organizations run the intelligence behind Clario in a customer-controlled environment. We can adapt compatible existing infrastructure or help establish a new environment. This is intended for organizations that want control over where their intelligence runs, rather than a required external Clario-hosted agent.
Deployment architecture, provider dependencies, permissions, retention, and maintenance responsibilities will be agreed for each setup. Customer-controlled hosting does not by itself prevent a configured model provider or connected service from receiving information.
Before public rollout
A complete privacy policy, contact channel, retention schedule, and process for removal requests will be provided before the public rollout. This page explains the current website behavior and product direction; it is not a substitute for those final product terms.