Data storage & retention (TTL)

Technical overview of data retention, TTL fields, cleanup jobs, and file limits in Sessy.

What this page covers

This page describes the current technical storage and retention behavior in Sessy, based on backend cleanup functions and upload validation rules.

Sessions: storage model and TTL

On creation, each session document gets _meta.ttl set to 3 years. During cleanup, session documents older than 3 years are removed.

Newsletters: automatic cleanup and image retention

A scheduled cleanup job runs removes newsletters older than 1 year:

• Published newsletters: isPublished == true and publishedAt < oneYearAgo
• Draft newsletters: isPublished == false and createdAt < oneYearAgo

During cleanup:

• Referenced newsletter images (imageRefs) are deleted from Storage.
• The newsletter is deleted.

Newsletter image upload limits

• Max size per image: 5 MB
• Allowed types: JPEG, PNG, GIF, WEBP

Member attachments: limits

Member attachments limits:

• Max size per attachment file: 2 MB
• Max cumulative attachment storage per member: 10 MB

Because there is no strict file-count cap, the effective max number depends on file sizes (for example, around 5 files if each is close to 2 MB). When the storage limit is reached, the upload is rejected. The employee must delete old attachments before uploading new ones.

Other automated cleanup jobs

Backend user activation records

• Collection: backendUserActivation
• Retention: records older than 90 days are removed

Device tokens

Device tokens are used to send push notifications to users. To avoid sending messages to old devices, inactive tokens older than 90 days are removed.

• Scope: users and mirrored member token fields
• Retention: inactive tokens older than 90 days are removed