Source
Customer data protection — found from sitemap — Unblu
Checked for Unblu on 27 Oct 2026
- Page
- https://docs.unblu.com/latest/knowledge-base/configuration/basics/record-retention-policies.html
- Checked
- 27 Oct 2026, 05:13 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:af822a36c9236188f746df197ba08f24d14ad1ea98ee10db4699feb4417adc5a
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Retention policy entities Report an error
“Unblu lets you specify record retention policies for: Audit log entries Conversations Person presences and related entities (persons and device info entities); this is a preview feature Webhook call log entries”
-
Retention mechanism Report an error
“A record retention policy ensures that a specific time interval has passed before entities of a certain type are marked for deletion and collected by a garbage collection job.”
-
Retention event sources Report an error
“Audit log entries: the end of the retention interval is calculated from the timestamp of the entry’s creation. Conversations: the end of the retention interval is calculated from the timestamp of when the conversation ended. Person presences and related entities: the end of the retention interval is calculated from the timestamp of when the person presence ended, that is, when the person went offline or logged out. Webhook call logs: the end of the retention interval is calculated from the timestamp of when the webhook call was executed.”
-
Conversation deletion scope Report an error
“Conversations: the conversation and everything related to it, such as: Messages Files exchanged during the conversation Bot threads Conversation-specific configuration and text property settings Canned response usages Invitations to join the conversation Any conversation recordings and their associated blobs All conversation participations, presences, state changes and sessions”
-
Presence retention preview Report an error
“This is a preview feature. It may be subject to change or removal with no further notice. To enable preview features, set com.unblu.platform.enablePreview to true.”
-
Presence retention default Report an error
“New accounts start with person presence retention disabled, and only a superadmin can enable it. While it’s disabled, Unblu never deletes the account’s person presences, device information entities, or anonymous person entities.”
-
Device info contents Report an error
“They store the name and version of the device’s operating system and browser, the raw user agent string, the device type, and the screen size. They also store the device identifier, the person the device belongs to, when Unblu last saw the device, and when two-factor authentication was last completed on it.”
-
Geolocation contents Report an error
“Unblu derives the approximate location of visitors, agents, and Branch clients from their IP address, and stores their continent, country, region, city, coordinates, and time zone. The geolocation record doesn’t contain the IP address.”
-
Audit log ip storage Report an error
“Audit log entries do, though: each one stores the IP address of the request that made the logged change, including changes a visitor’s own requests make to a conversation.”
-
Geolocation tracking disable property Report an error
“To stop Unblu from storing locations for an account, set com.unblu.platform.server.geolocation.geoLocationTrackingEnabled to false. The change only applies to new sessions.”
-
Retention configuration interface Report an error
“You can set record retention policies in the Record retention section of the Account Configuration interface, or by calling the Unblu web API endpoint /recordretention/update.”
-
Retention admin permissions Report an error
“Admins can change the retention interval for their account within the lower and upper bounds specified by the configuration properties. Superadmins can also disable retention policies entirely.”
-
Retention max interval recommendation Report an error
“Retention intervals of more than 1 year are strongly discouraged. If you need to store data for longer than that, use a dedicated archiving system.”
-
Deletion notice options Report an error
“One week before deletion; this is the default value One day before deletion The day of deletion Never”
-
Retention min intervals Report an error
“For audit logs, conversations, and person presences, the shortest permissible retention interval is one day. For webhook call logs, the shortest permissible retention interval is one hour.”
-
Retention max interval properties Report an error
“com.unblu.record_retention.webhookDeliveryLogRetentionIntervalMaximum com.unblu.record_retention.auditLogRetentionIntervalMaximum com.unblu.record_retention.presenceRetentionIntervalMaximum com.unblu.record_retention.conversationRetentionIntervalMaximum”
-
Default interval property note Report an error
“For new accounts, you can set the default retention period for each type of entity, for example with com.unblu.record_retention.conversationRetentionIntervalDefault. Note, however, that changing these configuration properties doesn’t affect the retention interval once the account’s been created.”
-
Orphan payload cleanup defaults Report an error
“com.unblu.server.storage.blob.deliveryLogOrphanPayloadCleanup.checkInterval specifies, in seconds, the interval between runs of the cleanup job for orphaned payload entries. The default value is 300. com.unblu.server.storage.blob.deliveryLogOrphanPayloadCleanup.deletionBatchSize specifies the maximum number of orphan payload entries to delete when the job is executed. The default value is 50000. com.unblu.server.storage.blob.deliveryLogOrphanPayloadCleanup.maxDeletionChunkSize specifies the maximum number of orphan payload entries deleted from each account on the Collaboration Server when the job is executed. The default value is 1000.”
-
Orphan payload cleanup disable Report an error
“The payload cleanup job is only required for cleaning up data created before the garbage collection feature was introduced. You can disable it by setting com.unblu.server.storage.blob.deliveryLogOrphanPayloadCleanup.enabled to false.”
-
Created conversation cleanup Report an error
“There’s a cleanup job that deletes conversations in the CREATED state that also match the following criteria: The engagement type is one of the request or PIN engagement types. The timestamp of when the last message was sent in the conversation is empty, that is, there were never any messages in the conversation.”
-
Created conversation cleanup properties Report an error
“com.unblu.conversation.cleanup.created.checkInterval com.unblu.conversation.cleanup.created.minTimeSinceCreation com.unblu.conversation.cleanup.created.batchSize”
-
Device cookie expiry property Report an error
“The visitor’s device cookie expires after com.unblu.identifier.deviceCookieMaxAge.”
-
Webhook blob threshold Report an error
“any blobs associated with the webhook call—this is the case if the request or response string was contained more than 5000 characters”
-
Web API retention endpoint Report an error
“For information on web API endpoints for record retention policies, refer to the RecordRetention section of the Unblu web API reference.”
Scores citing this record
- The Agent Advocate Customer data protection
- The Data Protection Officer Customer data protection
- The Shop Operator Customer data protection
- The Integrator Customer data protection
- The Skeptic Customer data protection
- The Support Lead Customer data protection