Privacy and data handling

EyeLogs keeps public product review separate from production customer data.

This page explains the public website, evaluation workspaces, and how production customer data is handled only after buyer-specific implementation terms are agreed.

Current public website

What the public site may collect.

ConsultationMeeting requestsName, email, phone, company, country version, product interest, preferred date/time, and notes may be sent to the EyeLogs backend when available.
CalendarGoogle Calendar handoffWhen you submit a meeting request, the site opens a calendar event so you can save the appointment details in your own calendar.
Local backupBrowser fallbackIf backend capture is unavailable, the browser may store a local copy of your request on your own device so the flow does not fail silently.
WorkspacesEvaluation and production accessPublic product workspaces are separated from contracted production tenants. Production data should be entered only after access, storage, retention, and support terms are agreed.
Production rollout

What must be agreed before real customer data is used.

Tenant access User roles Data migration Retention policy Deletion process Audit access Backups Support owner