AAron Rainbolt: I propose that the exact way in which age information is stored by the daemon should be left implementation-defined. For Kicksecure, the way we implement it will almost certainly store only the age bracket and require users to explicitly reconfigure their age once they are old enough to move from one age bracket to another. Other implementations may choose to store the date of birth or the age and date on which the age was set so that they can automatically update the age bracket as time passes. This interface will be provided *on the system bus* (NOT the session bus!), and the D-Bus service that provides these services should run as root. The file containing the user-to-age mappings should be owned by root and should not be world-readable, to prevent leaking the user's specific age to malicious applications.