Managing Caller ID Data
Encryption, Retention, and Compliance
Last updated
Was this helpful?
Encryption, Retention, and Compliance
Last updated
Was this helpful?
The following outlines the policies and processes for managing caller identification (caller ID) data to ensure privacy, security, and compliance with GDPR and other data protection regulations. It covers the creation of unique identifiers, identification of returning callers, data retention policies, and privacy considerations in line with GDPR standards.
For simultaneous calls, it is the callerid that serves as a composite identifier, uniquely managing each interaction by incorporating elements such as the callid. This ensures that every call is distinctly identified, while the sessionid remains consistent throughout the user's lifetime with our system, providing a persistent reference point across multiple interactions, including parallel calls.
The encoding process aligns with GDPR standards, ensuring non-reversible data transformation for privacy protection.
Session data becomes subject to review and cleaning processes after 30 days of inactivity or at the beginning of a new call. However, the session ID itself is not deleted.
Data are retained in accordance with data protection regulations. Variables set with a 'session' lifetime are deleted after 30 days of inactivity or at the start of a new call. Variables with a 'user' lifetime remain indefinitely unless manually deleted or purged.
Anonymous or blocked numbers are treated similarly to regular calls, with limitations on certain caller ID-dependent functionalities.
Our system uses encoded caller IDs, also known as session IDs, to recognize returning callers in future interactions.
Relevant session and user variable data associated with the encoded caller ID are retrieved for personalized service.
All processes comply with GDPR, ensuring data privacy and security.
A unique , also referred to as the "user lifetime" context by some, is generated upon the first contact from a particular caller with a specific release. This ID is persistently stored in our system and maintained as long as any data associated with a customer tenant exists."
In phone 2 releases, the sessionid is a combination of the hashed (+) callerId and the release's instanceId.
Caller IDs are transformed into unique identifiers through a two-step cryptographic process involving hashing and , enhancing security and privacy. However, it's important to note that while this process is used to create a session ID from a caller ID, the caller ID that typically appears in the frontend is usually just the phone number.