> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/releases-and-announcements/announcements/apple-implements-7-day-cap-on-script-writable-storage.md). # Apple implements 7-day cap on script-writable storage In February 2019, [Apple announced](https://webkit.org/blog/8613/intelligent-tracking-prevention-2-1/) that "Intelligent Tracking Prevention" (ITP) would cap the expiry of client-side cookies to seven days. As third-party scripts moved to other means of first-party storage such as LocalStorage, Apple decided to strengthen their policy to all script-writable storage. This change means that after seven days of Safari use without user interaction on a website, Apple will delete all script-writable storage, including first-party cookies and LocalStorage.\ \ Below are the script-writable storage forms affected (excluding some legacy website data types): * Indexed DB * LocalStorage * Media keys * SessionStorage * Service Worker registrations and cache ### Re-collect consent on websites The new policy will impact websites utilizing the Didomi CMP on websites. Since February 2019, Didomi has used LocalStorage to avoid the consent re-collection for a website.Now that all script-writable storage is deleted, a website will be forced to re-collect end-user consent if seven days have lapsed since the end-user's last interaction with the website. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.didomi.io/releases-and-announcements/announcements/apple-implements-7-day-cap-on-script-writable-storage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.