An optional feature that saves your last completed audit snapshot directly inside your own browser — so you can compare it against future audits to spot configuration changes. It is off by default and you control it entirely.
It is not a cookie. It is not a tracking mechanism. It is not analytics. It is not sent to Lensory, Azure, or any third party. The data never leaves your device.
Only you, in this browser on this device. The data is stored under the azcheck.dev origin, so only AZCheck can read it — no other website can access it.
Toggle it off in Settings (⚙ button in the app header) at any time. You can also clear it directly in your browser's developer tools under Application → Local Storage → azcheck.dev.
This feature is unrelated to cookies. AZCheck sets no cookies of any kind — not for this feature, not for anything else.
Local storage is a web browser feature that allows a website to save small amounts of data directly on your device — in your browser's own storage, not on any server. It was designed by browser vendors as a way for web applications to remember state between sessions, without needing a backend database.
Every major browser (Chrome, Firefox, Edge, Safari) implements local storage. It is completely separate from cookies. Data stored here:
azcheck.dev) — no other website can read itCookies, by contrast, are automatically included in every HTTP request your browser makes to the server — which is why they are commonly used for tracking. Local storage does not work this way and cannot be used for cross-site tracking.
If you enable local storage in Settings, AZCheck writes exactly two keys to your browser's local storage for the azcheck.dev origin:
| Key | What it contains | Purpose |
|---|---|---|
| azcheck_storage_pref | The string "true" or "false" |
Remembers whether you have enabled or disabled local storage, so the toggle reflects your last choice when you reopen the app. |
| azcheck_last_audit | A JSON object containing: generation timestamp, subscription name, resource group name, audit mode, and the array of setting rows (resource name, setting name, value). See below for the exact schema. | Stores the most recent completed audit snapshot so you can compare it against a future audit to detect configuration drift. |
The azcheck_last_audit value is a JSON object with this structure:
{
"version": 1,
"generated": "2026-04-30T12:34:56.000Z",
"subscription": "My Azure Subscription",
"resourceGroup": "my-prod-rg",
"mode": "discovery",
"rows": [
{
"resource": "my-storage-account",
"setting": "HTTPS Traffic Only",
"value": "true",
"type": "Storage Account",
"rawType": "microsoft.storage/storageaccounts",
"isErr": false,
"comment": ""
},
...
]
}
Drift detection lets you compare two audit snapshots to see what changed in your Azure resource configuration between audits. Local storage is one of two ways to load a previous snapshot for comparison:
azcheck_last_audit (replacing any previous snapshot).You can also use the "Save Snapshot" button to download a named JSON file (e.g., AZCheck_my-rg_2026-04-30_snapshot.json) and the "Compare (file)" button to load any previously saved file for comparison — no local storage required.
Use local storage if you audit the same resource group regularly and want effortless one-click comparison across sessions. Use JSON file download/upload if you want to keep a named archive of audits over time, share snapshots with colleagues, or prefer not to use browser storage at all.
Local storage is off by default. To enable it, click the ⚙ Settings button in the top-right of the audit app and use the toggle:
Turning the toggle off immediately stops any further writes to local storage. To remove data that has already been stored, you can:
https://azcheck.dev → right-click azcheck_last_audit → Delete.azcheck.dev.This is a question worth answering directly, because "local storage" and "cookies" are often lumped together in discussions about browser privacy.
azcheck.dev.azcheck.dev can read or write AZCheck's local storage. No other website can see it, read it, or interact with it in any way.SameSite=None can be read by third-party scripts embedded on a page. Local storage has no equivalent mechanism — it is always same-origin only.Local storage cannot identify you, track you across websites, or be used to build a profile of your behaviour. It cannot be read by Lensory's servers. It cannot be read by any third party. It contains only the data that you chose to store there by enabling this feature.
If you have questions about how AZCheck handles data, including this feature, contact us at privacy@lensory.io. See also our Privacy Policy and Terms of Use.