Security
Security built into screen operations.
Screens are public by definition, which makes who may change them the question that matters.
Authentication
Accounts sign in to a workspace; players pair as devices rather than sharing a person's credentials.
Role-based access
Roles decide who can design, who can publish and who can administer. Advanced RBAC is available from Business.
Secure transport
Traffic between players, the platform and the browser runs over encrypted connections.
Credential protection
API keys are issued and revoked in the workspace, and a device credential belongs to the device rather than to a user.
Logging and monitoring
Operational logging, with an audit log of workspace actions on Premium and Enterprise.
Backup and recovery
Published versions are retained so a screen can be returned to a previous known good state.
Governance
Controls for organizations that need them.
Publishing policy
Restrict who may publish to which screens. Available from Business.
Approval workflow
Require review before a publication reaches a screen. Available from Premium.
Audit log
A record of what was changed and by whom. Available from Premium.
Data processing
A Data Processing Agreement and a published subprocessor list.
On certifications
Layarva does not hold ISO 27001, SOC 2 or any comparable certification, and this site will not imply otherwise. If a certification is required for your procurement process, tell us during the conversation rather than after it — we would rather say no early than be discovered later.
Security questionnaire to fill in?
Send it over. We will answer what we can and say so where we cannot.