Terms overview

EyeLogs production use starts after scope, access, data, and support terms are agreed.

EyeLogs can design, build, deploy, integrate, train, support, and maintain business software. A production rollout requires a written scope covering users, data, integrations, hosting, support, acceptance checks, and unsupported boundaries.

Important boundaries

What buyers should understand before relying on a product.

Evaluation accessPublic workspacesPublic app workspaces are for evaluation, workflow review, and implementation planning. Contracted production tenants use agreed backend, data, access, and support controls.

ComplianceNo certification claimRisk, tax, payroll, accounting, or compliance outputs require buyer validation, professional review, and implementation-specific controls.

SupportMaintenance scopeSupport levels, response times, release cadence, backups, monitoring, and escalation paths are agreed during implementation.

Go-liveAcceptance requiredA product should go live only after auth, data, roles, audit, retention, integrations, and buyer-specific workflows pass acceptance checks.