Cookie Policy
This Cookie Policy explains how COGNALY LTD uses cookies and similar technologies on cognaly.mobi. Read it with our Privacy Policy. Contact: contact@cognaly.mobi, +44 7701 334455, 12 Chequers Orchard, IVER, SL0 9NH United Kingdom.
What cookies are
Cookies are small text files stored on your device. They may be session or persistent. Similar technologies include local storage, pixels and tags.
For "What cookies are", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
How we use cookies
COGNALY LTD uses cookies for core functions, limited preferences, consented analytics where enabled, and security. We do not sell personal data via cookies or make solely automated significant decisions through them.
For "How we use cookies", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Essential cookies
Essential cookies support security, load distribution and remembering consent choices. They are necessary and do not require PECR consent but are listed for transparency.
For "Essential cookies", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Analytics cookies
Analytics cookies, if used with consent, measure page use, coarse geography, device category and referrals with minimisation settings where feasible.
For "Analytics cookies", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Preference cookies
Preference cookies remember choices such as dismissed notices and are optional.
For "Preference cookies", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Third-party cookies
Google Maps embeds for 12 Chequers Orchard, IVER, SL0 9NH United Kingdom may set third-party cookies on interaction under Google policies.
For "Third-party cookies", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Consent and control
Non-essential cookies require consent where PECR requires it. You may withdraw consent by clearing cookies and revisiting settings. Browser controls can block cookies; blocking essentials may impair the site.
For "Consent and control", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Retention
Session cookies end with the browser session. Persistent cookies have finite durations. Analytics retention is limited consistently with our Privacy Policy.
For "Retention", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Updates
We update this Policy when tools or laws change and revise the effective date.
For "Updates", contact contact@cognaly.mobi with questions. COGNALY LTD inventories production tags and removes obsolete scripts.
Implementation detail 1
Detail 1: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 2
Detail 2: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 3
Detail 3: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 4
Detail 4: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 5
Detail 5: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 6
Detail 6: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 7
Detail 7: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 8
Detail 8: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 9
Detail 9: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 10
Detail 10: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 11
Detail 11: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 12
Detail 12: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 13
Detail 13: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 14
Detail 14: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 15
Detail 15: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 16
Detail 16: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 17
Detail 17: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 18
Detail 18: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 19
Detail 19: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 20
Detail 20: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 21
Detail 21: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.
Implementation detail 22
Detail 22: before deploying a script on cognaly.mobi, COGNALY LTD classifies it as essential or optional, identifies identifiers and recipients, and keeps optional tags off until consent where required. Inventories are checked against the live codebase after redesigns. Report inconsistencies to contact@cognaly.mobi with browser, time and behaviour notes. Clearing data on one device does not clear another. Server logs are separate from cookies but may be used in security investigations under the Privacy Policy. If a banner is shown, reject for non-essential cookies will be as easy as accept where guidance requires it.