Question
Microsoft Clarity data persistence latency after project deletion
Nia Maple
0 reputation · 06 Jan 2024, 03:12 UTC
100.3K views1
Loading…
0 reputation · 06 Jan 2024, 03:12 UTC
There is specific uncertainty regarding the lifecycle of session recordings and metadata once a project is officially deleted. Although the dashboard reflects the deletion immediately, the documentation does not specify the exact Time-to-Live (TTL) for the underlying data purge on Microsoft infrastructure.
What is the documented duration for the permanent purging of session recordings after a project is deleted? Can session data be retrieved via the API for a short window after the project is removed from the UI?
33275 reputation · 06 Jan 2024, 12:48 UTC
Microsoft Clarity does not publish a documented time-to-live for permanently purging session recordings after a project is deleted. There is no confirmed documentation that session data remains retrievable through the Clarity API after the project is removed from the dashboard. Treat project deletion as potentially irreversible.
The backend may retain deleted project data for an undetermined period before permanent purge, but that interval is unpublished. Because it is undocumented, it cannot be relied on as a recovery window, and Microsoft may change retention behavior without versioned notice.
No safe command or API call can verify post-deletion retrieval on a deleted production project. Do not test API access against a deleted project ID; assume access is revoked unless documentation explicitly permits it.
If the project is already deleted, open a support ticket with Microsoft Clarity and provide the project ID and approximate deletion time. If you are planning a deletion, export recordings while the project is still active.
Use comments to ask for clarification. Post a solution as an answer.
33,275 reputation · 06 Jan 2024, 14:50 UTC
Because Microsoft Clarity does not publish a documented TTL for backend purge after project deletion, the absence of a stated recovery window should be treated as an operational signal rather than a gap to probe casually. Dashboard removal and infrastructure erasure are distinct events; the former is immediate, while the latter may depend on regional privacy compliance and internal replication schedules that are not user-configurable.
For teams that need certainty, the safe pattern is to assume the API becomes unusable for that project immediately after deletion. Before removing any project, export recordings and metadata through the Clarity API to your own storage. If you must characterize the behavior for your tenant, use a disposable test project rather than production data: export via API, delete the project, then call the same endpoints to observe whether they return errors or empty results. Confirm any observed window with Microsoft support before relying on it.
clarity