Add "touched" field for sync data
The “meta” collection (6) is a server readable field. It records all collections that a user may be storing on sync. The modified field indicates the last time that the collection set was altered. The modified field for collection 6 may be years different than the actual latest date a user had written data.
For business reasons, we would like to know the last time a user “touched” their data. This would assist in knowing active use and abandonment. This field could either be an extra field or could be a separate database keyed by the fxa & kid
┆Issue is synchronized with this Jira Task
➤ Jessilyn Davis commented:
We don’t NEED this - it helps make an annoying process easier - and unlocks the ability to better in-product messaging for Sync customers than the current FxA Workaround.
➤ Jessilyn Davis commented:
TBD account or device activity (or both) - and what’s the better/easier way to determine & store this the easier way (and for all the use cases - and Sync baseline metrics?). David Durst to estimate this (and then we’ll know if it’s important to prioritize). Also think about CWTS and unchecking everything - and some stuff still syncs - it still counts as a “sync” customer.
➤ David Durst commented:
I’m going to go out on a limb here and posit that we don’t need this. If the retention of Sync data is based on an Account’s being “active,” then it’s up to the Account’s SUP to define the activity window and retention period. Since an automatic deletion of an Account will trigger an automatic deletion of that Account’s Sync data, I assert that we will not – from the perspective of Sync – be asking if a user or Sync record is “active.”
And thus I think we cancel this.
➤ David Durst commented:
This is paused until we determine if Sync on its own (independent of changes to an associated FxA) has the authority to delete data. This should be determined by a Sync Service Use Policy. cc Ana Medinac