Other browser storage in first-party context
Is the site's own non-cookie storage deleted or capped?
A site’s own localStorage, IndexedDB and similar storage can hold the same kind of identifiers as first-party cookies, so the reasoning for capping first-party cookies applies here too.
In practice only Safari limits it in default browsing: it deletes all script-writable storage of a site the user hasn’t interacted with in 7 days of browser use. Firefox deletes the storage of known trackers after 45 days without interaction.
By browser
Brave
No restrictions- No restrictions.
Chrome
No restrictions- No restrictions.
Edge
No restrictions- No restrictions.
Firefox
Limited- All storage is purged from known trackers daily, unless the user has interacted with the site in first-party context within the last 45 days.
Safari
Limited- All script-writable storage is deleted after 7 days of browser use without interaction (click, tap, text input) with the site.
- Web apps added to the Home Screen keep their own count of days of use, so their first-party data isn’t expected to be deleted. New
History
Firefox 79 clears data from redirect trackers
Cookies and site data of known trackers are deleted daily unless the user has interacted with the site in the last 45 days.
Safari blocks all third-party cookies
Safari 13.1 blocks third-party cookies for all domains, not only classified trackers, and caps all script-writable storage at 7 days of browser use without interaction.
ITP 2.3
Script-writable storage is deleted after 7 days without interaction on sites reached via known trackers, and
document.referreris trimmed for them.