How Venia approaches data.

Collect with a purpose

Venia is designed to collect resident personal information only when it supports a defined product, operational, security, support, or legal purpose.

Venia-controlled records

Venia is designed to maintain its own authoritative property, resident, staff, credential, permission, activity, device, and operational records rather than relying on a hardware provider as the sole source of customer data.

Infrastructure and access-control providers may process information needed to execute physical access functions, but they do not define Venia's customer or business records.

Property separation

Venia's system is designed so information and access belonging to one property are separated from other customer properties. Permissions determine which properties, residents, entrances, and actions a user may access.

Sensitive actions

Actions involving entrances, credentials, permissions, and other sensitive property operations are designed to be attributable to an authorized person or system identity and produce appropriate operational records.

Secrets and credentials

Production secrets such as API keys, access tokens, database credentials, and integration secrets are intended to remain outside application source code and limited to authorized systems and personnel.

Retention

Venia determines retention based on the type of information and why it is needed rather than applying one arbitrary period to every record.

Security, audit, installation, support, and property-operation records may need to be retained longer than transient or unnecessary resident information. Sensitive resident information should be deleted or anonymized when it no longer serves a legitimate purpose, subject to legal and contractual requirements.

Backups and recovery

Venia's production design requires backups of critical customer and business data and a recovery process intended to prevent software, database, or infrastructure failures from permanently destroying critical property records.

Vendors and integrations

Venia may use infrastructure, hosting, communications, support, and access-control providers where necessary to operate the service.

Access to personal information should be limited to what is reasonably necessary for each provider's role.

Security incidents

Venia maintains operational processes intended to identify, investigate, contain, recover from, and document security incidents. Where an incident creates a legal notification obligation, Venia will provide notice as required by applicable law.

No sale of resident access history

Venia does not sell resident access history for advertising or unrelated third-party marketing.

Questions

Questions about privacy or data practices may be sent to privacy@veniaentry.com.