What this website collects.

When you request a demo

We store the work email, company name and workflow you submit, together with a random submission ID, a fingerprint of those details, the submission time and a request status. The ID and fingerprint help prevent a retry from creating another copy of the same request.

The team uses these details to review and respond to your request. They are available in an administrator-restricted inbox that also requires a separate operator unlock. Saving the form does not automatically send an email or book a meeting.

There is no automatic deletion schedule for demo requests in this version of the site. Contact us to ask about your submission, correct its details or request deletion. Do not put employee information, payroll records, identity documents or credentials in the form.

Website measurement

We count selected page views and actions, such as starting or completing the demo. Stored measurements contain the day, a predefined page path, an event name and a count. They do not contain visitor identifiers, analytics cookies, referrers, query strings or your submitted contact details.

Optional events sent by the browser are disabled when the browser signals Do Not Track or Global Privacy Control. A successfully saved request always adds to a separate server-generated total of submissions. That total contains no contact information and is not a count of meetings or unique visitors.

The public interactive demo

The promotion example uses fictional records in browser memory. Its sample approvals, record updates and notifications do not connect to or change a real HR or payroll system, or contact an employee. Resetting or reloading starts the example again. Selected demo actions may contribute to the aggregate measurements described above.

The guided sample application is separate from this public example. Its uploaded sample export rows become unavailable after seven days and are removed on the next workspace access. Manual deletion removes retained rows and comparison results; mapping definitions, hashes and metadata receipts remain for history. Real employee data does not belong in either demo.

Hosting, abuse prevention and sign-in

Our hosting infrastructure may process access logs that include IP addresses, browser information and request details. These infrastructure logs are separate from the aggregate measurement tables described above.

The application uses temporary, hashed network keys in server memory to limit repeated requests. It does not save the raw IP address in the demo-request or measurement tables. If you sign in to the separate guided application, its session cookie supports that sign-in; it is not an analytics identifier.

Optional scheduling

If a scheduling service has been configured, a link may appear after your request is saved. Opening it takes you to an external HTTPS website with its own privacy practices. A saved request alone does not open that service or confirm a booking.