Upcoming Application of Session Data Retention (Release 1.18.0)
We’d like to inform you about an upcoming application of data retention policy for session data, including GGA messages and session events. This change will be introduced with release 1.18.0, planned for early January.
Reason for the Change
Until now, session data has been stored without a formally defined retention policy. While availability of session data has been guaranteed for at least 14 days, data older than that was not subject to a fixed retention rule.
Over time, the growing volume of session data has started to cause:
- Performance degradation
- Increased demand for server storage
To ensure long-term system stability and a consistent user experience, we are introducing a clear and transparent session data retention policy.
What’s Changing
The following data retention rules will be applied:
- Full session data will be retained for 30 days after the session ends.
- After 30 days, the following data will be permanently deleted:
- Session GGA messages (including trajectory maps and session quality data)
- Session events (including termination reasons)
- Session stream data
The 30-day retention period exceeds our guaranteed 14-day availability. We plan to monitor the system and maintain this policy for as long as it remains sustainable.
The retention period may be adjusted in the future as part of ongoing system improvements. Any such changes will be communicated in advance.
How It Will Affect You
- Sessions younger than 30 days will remain fully available.
- For sessions older than 30 days, only basic metadata will be retained:
- Start date
- End date
- Duration
- Service
- Mountpoint
- User agent
Example of an expired session
What You Need to Do
- Export any GGA messages you need to keep before they exceed the 30-day retention period.
If you have any questions or concerns, feel free to reach out to our support team.