Operator details, the retention schedule, service providers and applicable legal basis will be confirmed before launch.
Who handles your information
Clijaro’s operator details will be added before public launch.
For questions about a website request or your information, contact support@clijaro.com.
What you provide
Demo and Beta forms collect your name, company, work email, country, team size, services and operational needs. You may also provide a phone number, current software, approximate customer/site numbers and an optional message. Contact enquiries collect your name, email, optional company, enquiry topic and message.
Why we use it
We use these details to respond to your enquiry, arrange a product demonstration, assess Beta applications and help onboard approved companies. Submitting a request does not create a Clijaro company or user account and does not subscribe you to marketing emails.
Where requests are stored
Website enquiries are stored separately from the operational Clijaro application. Authorised staff can review requests. Notifications are intended for the Clijaro team using our role addresses. When enabled, our website sends the details needed to process your request to Make, which delivers team notifications and applicant acknowledgements through our email provider. Requests are saved before delivery is attempted. Local previews do not send email unless delivery is explicitly configured.
Hosting and email providers, any international transfers and their safeguards will be documented before public launch.
Security and spam prevention
We validate form entries and use a hidden spam-check field, a short-lived form token and submission limits. For rate limiting, we temporarily retain a keyed hash derived from the connection address or submitted email, rather than the raw address in the rate-limit record. Expired rate-limit records are removed by the notification maintenance command.
The interactive product demo
The mini-demo uses fictional records. Demo changes and edited notes stay in page memory and reset when you reload. Demo interaction events are kept locally; no analytics collector or advertising tracking is configured. Please use fictional text when trying the demo.
Cookies
The request forms use an essential security cookie to prevent cross-site form submissions. An essential session cookie lets you view your own request confirmation. A staff session is also used when authorised reviewers sign in. The public website does not mirror your operational Clijaro login.
How long we keep requests
The retention period for enquiries and applications will be confirmed before public launch. Local test requests remain in the separate website database until an authorised reviewer removes them.
Your choices and requests
You can ask us about the information associated with your request, ask for corrections or ask us to delete it. Depending on applicable law, you may also have rights to access, restrict or object to processing, receive a portable copy, and complain to your data protection regulator.
Before public launch
This draft must be completed with the operator’s identity, applicable legal basis, retention periods, recipients and any transfer details. It is not a substitute for the operational application’s own privacy information.
Draft version: September 2026