Skip to content
Trust CenterDoorsecure DoorAPI
Menu
DoorAPI platform

Data Retention Notice

How retention differs between customer-controlled records and Doorsecure operational data.

Version 1.2Effective 2026-07-22DoorAPI platform services
Important

Customer-specific agreements, order forms and mandatory law may override these general provisions.

Customer data

DoorAPI does not impose one universal short retention period on customer access history. Customers often require long-term records of who accessed a location and when. Customer-controlled data is therefore generally retained until deletion by the customer, contract termination or an agreed lifecycle.

Customer responsibility

Customers acting as controller must configure retention that is necessary, proportionate and lawful for their purpose. Doorsecure provides deletion and lifecycle capabilities according to product functionality.

Session and security data

Session IP address and user agent remain until the session is destroyed. Failed-login and notification data is temporary. API logs are retained only for operational logging and removed according to the logging lifecycle.

Webhooks and commands

Successful webhook delivery records are removed. Where a webhook results in a device command, that command may remain in device-command history as an operational record.

Backups

Deleted data may persist temporarily in encrypted backups until backup rotation, after which it is overwritten according to the recovery lifecycle.