Cookie Policy
This Cookie Policy explains how TABLELOOP LTD ("we", "us", "our") uses cookies and similar technologies on tableloop.work and in connection with our digital library solutions demonstrations. It should be read with our Privacy Policy and Terms of Service.
Cookies are small text files placed on your device when you visit a website. They help websites function, remember preferences, and understand usage. Similar technologies include local storage, session storage, pixels, and software development kits in mobile contexts.
We comply with PECR and UK GDPR. Non-essential cookies require consent. Essential cookies may be used without consent where strictly necessary to provide a service you request.
1. Who Operates This Website
TABLELOOP LTD, 82a James Carter Road, Mildenhall, United Kingdom, IP28 7DE. Contact: help@tableloop.work, +447446967065.
2. How We Use Cookies
We use cookies to operate our website securely, remember consent choices, measure performance, and improve content about library software development services.
We do not sell cookie data. We minimise identifiers and configure analytics to reduce personal data where possible.
3. Categories of Cookies
3.1 Strictly Necessary
Required for navigation, security, load balancing, form submission, and consent storage. Cannot be disabled without impairing core functions.
3.2 Functional
Remember language, region, or interface preferences. Require consent where not strictly necessary.
3.3 Performance and Analytics
Collect aggregated statistics on page views, funnels, and errors to improve tableloop.work.
3.4 Marketing
We limit marketing cookies on our corporate site. Any retargeting pixels require explicit consent before activation.
4. Cookie Details
The following table describes cookies commonly deployed. Names and durations may change following updates; material changes will be reflected here.
- consent_preferences: first-party, stores cookie choices, twelve months, strictly necessary after initial consent.
- session_id: first-party, maintains secure session during browsing, session duration, strictly necessary.
- csrf_token: first-party, prevents cross-site request forgery on forms, session duration, strictly necessary.
- analytics_id: first-party or processor, distinguishes visits for statistics, thirteen months, analytics with consent.
- error_log_ref: first-party, correlates diagnostic events, twenty-four hours, performance with consent.
5. Third-Party Cookies
Embedded maps or media may set third-party cookies governed by respective providers. We assess embeds before use and provide notice where cookies are likely.
Third-party analytics or tag managers, if enabled, process data under their policies and our data processing agreements.
6. Consent Management
On first visit, a consent banner allows acceptance, rejection of non-essential cookies, or granular selection.
You may withdraw consent at any time by clearing cookies, adjusting browser settings, or contacting help@tableloop.work.
7. Browser Controls
Browsers enable blocking, deletion, and alerts for cookies. Refer to documentation for Chrome, Firefox, Safari, Edge, and mobile equivalents.
Blocking all cookies may prevent use of contact forms or preference memory.
8. Do Not Track
Industry standards for Do Not Track signals are inconsistent. We honour cookie consent choices rather than DNT headers alone.
9. Updates
We review this Cookie Policy when deploying new site features or analytics tools. Last updated June 2025.
10. Contact
Questions: help@tableloop.work, +447446967065, 82a James Carter Road, Mildenhall, United Kingdom, IP28 7DE. See privacy-policy.html for broader data protection information.
11. Cookie Lifespan and Renewal
Persistent cookies expire automatically at the end of their defined lifetime. Returning visitors may receive renewed cookies unless they have cleared storage or withdrawn consent.
Consent renewal prompts may appear periodically or when cookie policies change materially, allowing you to update preferences without searching browser settings.
12. Relationship with Similar Technologies
Local storage may retain interface preferences without transmitting data on each request. Such storage is cleared when you clear site data in browser settings.
Pixels in email newsletters, if used, are disclosed in campaign privacy notices and honour marketing unsubscribe requests independently of website cookie consent.
13. Cookies in Client Demonstrations
Password-protected demo environments for archive management software may issue additional session cookies required for authentication and role simulation.
Demonstration data is synthetic unless otherwise agreed; demo cookies should not be confused with production patron portal cookies operated by client institutions.
14. Managing Consent for Institutional Users
Institutional procurement teams evaluating our website on behalf of libraries may configure group policies centrally; individual staff should still review notices applicable to personal browsing on corporate devices.
15. Updates to Cookie Technology
We monitor regulatory and browser ecosystem changes affecting cookies, including third-party cookie deprecation, and adjust implementations to maintain lawful operation of tableloop.work.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.
Users may adjust browser settings to block or delete cookies, though essential site functions may be impaired if strictly necessary cookies are disabled.
We distinguish between first-party cookies set by tableloop.work and third-party cookies set by integrated services, describing each category in plain language.
Performance cookies help us understand navigation paths on service pages so we can improve documentation for archive management software prospects.
Security cookies may be deployed to mitigate automated abuse of contact forms and to protect infrastructure from credential-stuffing attempts.
We do not use cookies to make automated decisions producing legal or similarly significant effects without explicit disclosure and a valid lawful basis.
Consent banners present equal prominence to accept and reject options for non-essential cookies in line with ICO guidance on cookie compliance.
Cookie lifetimes are minimised; analytics identifiers rotate periodically where the technology provider supports configurable expiry intervals.
We review whether each cookie remains necessary during annual privacy programme reviews and remove obsolete technologies where possible.
Demonstration portals for digital library solutions may set additional functional cookies; those environments display separate notices where required.
Mobile browsers may store cookies differently; users should consult device settings for Safari Intelligent Tracking Prevention and equivalent controls.
Where we deploy tag managers, only tags corresponding to consented categories fire; blocked tags are suppressed at runtime rather than merely hidden.
We do not combine cookie data with offline direct marketing lists without a clear lawful basis and opportunity to object.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.
Users may adjust browser settings to block or delete cookies, though essential site functions may be impaired if strictly necessary cookies are disabled.
We distinguish between first-party cookies set by tableloop.work and third-party cookies set by integrated services, describing each category in plain language.
Performance cookies help us understand navigation paths on service pages so we can improve documentation for archive management software prospects.
Security cookies may be deployed to mitigate automated abuse of contact forms and to protect infrastructure from credential-stuffing attempts.
We do not use cookies to make automated decisions producing legal or similarly significant effects without explicit disclosure and a valid lawful basis.
Consent banners present equal prominence to accept and reject options for non-essential cookies in line with ICO guidance on cookie compliance.
Cookie lifetimes are minimised; analytics identifiers rotate periodically where the technology provider supports configurable expiry intervals.
We review whether each cookie remains necessary during annual privacy programme reviews and remove obsolete technologies where possible.
Demonstration portals for digital library solutions may set additional functional cookies; those environments display separate notices where required.
Mobile browsers may store cookies differently; users should consult device settings for Safari Intelligent Tracking Prevention and equivalent controls.
Where we deploy tag managers, only tags corresponding to consented categories fire; blocked tags are suppressed at runtime rather than merely hidden.
We do not combine cookie data with offline direct marketing lists without a clear lawful basis and opportunity to object.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.
Users may adjust browser settings to block or delete cookies, though essential site functions may be impaired if strictly necessary cookies are disabled.
We distinguish between first-party cookies set by tableloop.work and third-party cookies set by integrated services, describing each category in plain language.
Performance cookies help us understand navigation paths on service pages so we can improve documentation for archive management software prospects.
Security cookies may be deployed to mitigate automated abuse of contact forms and to protect infrastructure from credential-stuffing attempts.
We do not use cookies to make automated decisions producing legal or similarly significant effects without explicit disclosure and a valid lawful basis.
Consent banners present equal prominence to accept and reject options for non-essential cookies in line with ICO guidance on cookie compliance.
Cookie lifetimes are minimised; analytics identifiers rotate periodically where the technology provider supports configurable expiry intervals.
We review whether each cookie remains necessary during annual privacy programme reviews and remove obsolete technologies where possible.
Demonstration portals for digital library solutions may set additional functional cookies; those environments display separate notices where required.
Mobile browsers may store cookies differently; users should consult device settings for Safari Intelligent Tracking Prevention and equivalent controls.
Where we deploy tag managers, only tags corresponding to consented categories fire; blocked tags are suppressed at runtime rather than merely hidden.
We do not combine cookie data with offline direct marketing lists without a clear lawful basis and opportunity to object.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.
Users may adjust browser settings to block or delete cookies, though essential site functions may be impaired if strictly necessary cookies are disabled.
We distinguish between first-party cookies set by tableloop.work and third-party cookies set by integrated services, describing each category in plain language.
Performance cookies help us understand navigation paths on service pages so we can improve documentation for archive management software prospects.
Security cookies may be deployed to mitigate automated abuse of contact forms and to protect infrastructure from credential-stuffing attempts.
We do not use cookies to make automated decisions producing legal or similarly significant effects without explicit disclosure and a valid lawful basis.
Consent banners present equal prominence to accept and reject options for non-essential cookies in line with ICO guidance on cookie compliance.
Cookie lifetimes are minimised; analytics identifiers rotate periodically where the technology provider supports configurable expiry intervals.
We review whether each cookie remains necessary during annual privacy programme reviews and remove obsolete technologies where possible.
Demonstration portals for digital library solutions may set additional functional cookies; those environments display separate notices where required.
Mobile browsers may store cookies differently; users should consult device settings for Safari Intelligent Tracking Prevention and equivalent controls.
Where we deploy tag managers, only tags corresponding to consented categories fire; blocked tags are suppressed at runtime rather than merely hidden.
We do not combine cookie data with offline direct marketing lists without a clear lawful basis and opportunity to object.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.
Users may adjust browser settings to block or delete cookies, though essential site functions may be impaired if strictly necessary cookies are disabled.
We distinguish between first-party cookies set by tableloop.work and third-party cookies set by integrated services, describing each category in plain language.
Performance cookies help us understand navigation paths on service pages so we can improve documentation for archive management software prospects.
Security cookies may be deployed to mitigate automated abuse of contact forms and to protect infrastructure from credential-stuffing attempts.
We do not use cookies to make automated decisions producing legal or similarly significant effects without explicit disclosure and a valid lawful basis.
Consent banners present equal prominence to accept and reject options for non-essential cookies in line with ICO guidance on cookie compliance.
Cookie lifetimes are minimised; analytics identifiers rotate periodically where the technology provider supports configurable expiry intervals.
We review whether each cookie remains necessary during annual privacy programme reviews and remove obsolete technologies where possible.
Demonstration portals for digital library solutions may set additional functional cookies; those environments display separate notices where required.
Mobile browsers may store cookies differently; users should consult device settings for Safari Intelligent Tracking Prevention and equivalent controls.
Where we deploy tag managers, only tags corresponding to consented categories fire; blocked tags are suppressed at runtime rather than merely hidden.
We do not combine cookie data with offline direct marketing lists without a clear lawful basis and opportunity to object.
Cookie consent preferences are stored locally and re-evaluated when we materially change our cookie deployment or introduce new tracking technologies.
We configure analytics tools to avoid collecting full IP addresses where feasible and to aggregate usage metrics for internal improvement rather than individual profiling.
Session cookies supporting authenticated demonstrations expire when the browser session ends or after a defined inactivity interval.
We document cookie names, providers, durations, and purposes in our internal cookie register, which is updated following each website release.
Third-party embeds are assessed for cookie behaviour before integration, and alternatives are considered where consent cannot be obtained lawfully.