Our data expiration policy takes a long term view: some data never expires while our organization lives, some data lives a very long time, and some data expires relatively rapidly.

Data retention / expiration is often something thought about only when needed (which makes sense!). But if you decide ahead of time when and what data expires, your entire data lifecycle now has clear boundaries.

This is not yet implemented, it’s our first draft of a multiple-lifespans policy, so this is a starting point for a conversation.

Data object	Expiration
Metapage definitions	Active account: never
	Inactive account: 10 years unless otherwise by law
	Published: never
	Public but not published: 100 years
Metapage definition backups	Time machine schedule
Metapage states	Time machine schedule
Metapage files	Active account: never
	Inactive account: tbd, depends on size

Permanence: what does it mean

To keep metapages past the 100 year mark, then simply share them.

The 100 year span starts then anew.

Time machine schedule

• All within the last minute
• Last hour: one per minute
• Last 24 hours: one per hour
• Last 7 days: one per day
• Last 30 days: one per week
• Last 12 months: one per month