Activity Timestamps

Cryptlex records when a license, an activation, or a user was last active. These four timestamps live on three different entities and are updated by different events, so pick the one that matches the question you are answering. All of them are shown on the corresponding pages in the admin portal and returned on the entity in the Web API.

Timestamp	Entity	Updated when
`lastUsedAt`	License	Any activation of the license is created, updated, or successfully synced
`lastSyncedAt`	Activation	That specific activation successfully syncs with the Cryptlex servers
`lastSeenAt`	User	An activation linked to the user successfully syncs
`lastLoginAt`	User	The user logs in to the customer portal

Three of these four timestamps advance only when a client reaches the Cryptlex servers, so they stay unchanged on machines that are offline or air-gapped. On those deployments, no recent activity does not mean the license is unused.

lastUsedAt

lastUsedAt is maintained at the license level and represents the most recent activity across all activations associated with the license. It is updated whenever an activation is created, updated, or successfully synchronized with the Cryptlex servers. For a license with multiple activations, the value reflects the most recent activity among all of them, so it tells you whether the license is in use at all, not which machine used it.

lastSyncedAt

lastSyncedAt is maintained at the activation level and indicates when that specific activation last successfully synchronized with the Cryptlex servers. Unlike lastUsedAt, which aggregates activity across a license, lastSyncedAt reflects the synchronization status of an individual activation, which makes it the field to check when you are diagnosing a single machine.

lastSeenAt

lastSeenAt is maintained at the user level and indicates the most recent time a user was observed using an application associated with their account. It is updated when a license activation linked to the user successfully synchronizes with the Cryptlex servers, which makes it useful for tracking recent end-user activity across your licensed applications.

lastLoginAt

lastLoginAt is maintained at the user level and indicates the most recent time the user successfully logged in to the customer portal. It is updated on successful portal authentication, so you can use it to track customer portal access.

lastLoginAt tracks customer portal logins, whereas lastSeenAt tracks application usage that results in a successful server sync from a license activation linked to the user. A user who runs your app but never opens the portal has a recent lastSeenAt and no lastLoginAt at all.

Timezones

Cryptlex stores every timestamp in UTC. This applies to the activity timestamps on this page as well as to dates such as expiresAt on licenses and feature entitlements. The Web API returns timestamps in UTC, and the SDKs return them as Unix timestamps, which are always UTC based.

The admin portal, however, displays every timestamp converted to the local timezone of the browser you are viewing it in. The conversion also applies when you set a date: picking an expiration date in the admin portal sets it to 11:59:59 PM on that date in your own local timezone, and the stored UTC value can therefore fall on the next calendar day in UTC.

When your app compares a timestamp such as expiresAt against the current time, always compare in UTC. Never localize the stored value to the machine's timezone first, because the machine's timezone has no relation to the timezone in which the date was set.

Suspending and Revoking Licenses Overview

Last updated: 8/25/2026