Delivr.ai Legal
Device Storage Disclosure
Last reviewed November 9, 2026
This page lists every cookie and other browser storage that Delivr sets or reads when its pixel runs on a website, when someone clicks a tracked email link, or when an ad measured by Delivr is shown. For each one it gives the domain, how long it lasts, and what Delivr uses it for.
The same information is published in machine-readable form at /legal/device-storage.json, in the format defined by the IAB Tech Lab's Vendor Device Storage & Operational Disclosures specification, so consent management platforms can present it to visitors. Purpose numbers refer to the purposes defined by the IAB Europe Transparency & Consent Framework.
Cookies
__pixelId
- Type
- Cookie
- Domains
- *.sitelytics.tech, delivr.ai, *
- Maximum lifetime
- 400 days
- Refreshed
- Yes
- Purposes
- 1. Store and/or access information on a device
- 3. Create profiles for personalised advertising
- 4. Use profiles to select personalised advertising
- 7. Measure advertising performance
- 8. Measure content performance
- 9. Understand audiences through statistics or combinations of data from different sources
- 10. Develop and improve services
- Special purposes
- 1. Ensure security, prevent and detect fraud, and fix errors
- Description
- Pseudonymous browser identifier: a unique number generated by Delivr's collection server, containing no name, email address or other direct identifier. It lets Delivr recognise the same browser across pages and sites that use the Delivr pixel, link pixel events, email engagement and ad impressions to that browser, sync it with advertising partners' identifiers, and match it to a hashed email address in Delivr's identity graph. Reset to its full lifetime on each page event, cookie sync and ad impression. Lifetime depends on the browser: 400 days in Chromium-based browsers, Firefox and Safari (including iOS), 180 days elsewhere. Safari may shorten it.
__pixelIdP
- Type
- Cookie
- Domains
- *.sitelytics.tech, delivr.ai, *
- Maximum lifetime
- 400 days
- Refreshed
- Yes
- Purposes
- 1. Store and/or access information on a device
- 3. Create profiles for personalised advertising
- 4. Use profiles to select personalised advertising
- 7. Measure advertising performance
- 8. Measure content performance
- 9. Understand audiences through statistics or combinations of data from different sources
- 10. Develop and improve services
- Special purposes
- 1. Ensure security, prevent and detect fraud, and fix errors
- Description
- Partitioned (CHIPS) copy of __pixelId, holding the same value with the same lifetime. Browsers that block unpartitioned third-party cookies may still allow a cookie partitioned to the site being visited. Delivr reads __pixelIdP only when __pixelId is absent, and uses it for the same purposes.
Cookie lifetime by browser
Delivr sets the same cookies in every browser but chooses their lifetime by browser family. The machine-readable file declares the longest of these, as the specification requires a single value.
| Browser | Lifetime |
|---|---|
| Chrome, Edge, Firefox, Safari, other Chromium-based browsers, and every browser on iPhone or iPad | 400 days |
| Any other browser | 180 days |
Other browser storage
The Delivr pixel script does not write to localStorage, sessionStorage, IndexedDB or any other web storage. It keeps its working state in page memory, which the browser discards when the page closes.
Domains
Delivr processes personal data on these domains. Some customers serve the pixel from a hostname on their own website and send its events there. On those websites Delivr sets the same cookies, for the same purposes, as first-party cookies on the customer’s domain. Those domains are not listed one by one, so the machine-readable file declares them with a wildcard.
- api.sitelytics.tech
- Delivr's collection server. Receives pixel events, email open and click events, ad impressions and cookie-sync requests. Sets and reads the __pixelId and __pixelIdP cookies on all of them except email opens, which set and read no cookie.
- cdn.sitelytics.tech
- Serves the Delivr pixel script. Sets and reads no cookies.
- delivr.ai
- Delivr's own website. Its /_delivr path forwards Safari visitors' pixel events to the collection server, which sets and reads __pixelId and __pixelIdP on delivr.ai as first-party cookies.
- cdn.delivr.ai
- Serves the Delivr pixel script. Sets and reads no cookies.
Mobile apps
Delivr does not provide an SDK for mobile apps, so the file lists none.
Partners the pixel calls
When the pixel runs, it may call the following partner, which sets and reads its own cookies on its own domains under its own disclosure. Those cookies are not Delivr’s and are not listed above.
Sovrn
- GVL vendor ID
- 13
- Description
- Cookie synchronization: Sovrn receives the __pixelId value and may return a hashed email address it associates with the browser.
Your choices
You can delete these cookies at any time in your browser settings. A new identifier is issued the next time your browser reaches a site that uses the Delivr pixel or follows a tracked email link.
To access or delete data Delivr holds about you, or to opt out of its sale or sharing, submit a request through our Privacy Policy. For anything else about this disclosure, write to info@delivr.ai.