Version 06in force since September 18, 2026Previous versions
Cookie policy
What PINTRU stores on your device, why, and for how long. The list is complete: if an entry is not here, we do not use it.
Your cookie choices. You can review and change them at any time: open preferences. Withdrawal applies to the future and does not affect what was done before.
1. In short
- No profiling or advertising cookies. We do not use advertising networks and we do not build profiles of our readers.
- There is site measurement, but only with your consent, and it serves to understand in aggregate how the service is used. Without consent it is not loaded at all: the detail is in Measuring the site.
- The service sets four cookies, all technical: the one that stores your cookie choices, the one for your session once you have signed in, the one that lets you be recognised on sites hosting our integration, and the one that keeps operators signed in to the administration panel. None of them profiles you or follows you across sites. A visitor who has never signed in receives only the first.
- Everything else is browser local storage: a handful of technical entries, listed below one by one.
- On websites that have installed our script, no persistent identifier is written without consent and no measurement is sent.
- These legal pages load no external resources and store nothing on your device.
2. Cookies and local storage
A cookie is a small file that a website places in your browser and that the browser sends back to the server automatically with every request. Local storage is instead an area of browser memory that stays on the device: nothing is sent to the server unless the page's own code explicitly sends it.
The technical distinction does not change the rules: local storage also requires disclosure and, where it is not strictly necessary for the service you asked for, consent. That is why you find it listed here alongside the cookies.
3. What gets stored
| Entry | Type and where | What it is for | Lifetime | Necessary? |
|---|---|---|---|---|
pintru_admin |
Cookie, on the application domain | Keeps the session open for people working in the administration panel. It is never set for users of the service. It is readable only by the server, travels protected over secure connections, and does not follow the user across other websites. | 2 hours | Yes, technical |
pintru_sess |
Cookie, on the .pintru.com domain |
Keeps your session open once you have signed in, so you do not have to enter your credentials again when moving between the site and the application. It is readable only by the server, travels protected, and is not sent when you arrive from another site. | 12 months | Yes, technical |
pintru_ponte |
Cookie, on the .pintru.com domain, limited to the recognition service path |
Lets you be recognised as a registered user while you are on a third-party site hosting our integration. It is the only one the browser also sends in that context, which is why it is limited to a single path: it does not follow your browsing and is not readable anywhere else in the service. | 12 months | Yes, technical |
pintru_cc |
Cookie, on the .pintru.com domain |
Stores your cookie choices, so we do not have to ask again on every page and so they apply to both the site and the application. It is the only one every visitor receives, and it is what makes a withdrawal effective. | 6 months | Yes, technical — it is the cookie of the choice itself |
pintru_user_token |
Local storage, on the application domain | Keeps you signed in to your personal area from one page to the next, so you do not have to enter your credentials again. | Until sign-out or until site data is cleared | Yes, technical |
pintru_token |
Local storage, on the domain of the page where PINTRU is active | A random identifier that makes it possible to find again the pins created from the same device, even without an account. Which rules apply depends on where you are. On PINTRU's own pages — including the demo ones — you are there to use PINTRU: the identifier is what makes the pins you create yours, so it is strictly necessary for the service you requested and needs no consent. On a third-party website hosting the integration the situation is different, because you did not go there to use PINTRU: the identifier is written only if that website has declared the visitor's consent, and failing that it stays temporary. | 12 months from last use | On PINTRU's pages no, it is technical · on third-party websites yes |
pintru_lov_ followed by the page's domain and path |
Local storage, on the page's domain | Remembers where you moved or hid a pin on that page, so they are not shuffled again on reload. It holds coordinates and reference dimensions, no identifying data. It is written only if you move or hide a pin, and the number of entries kept is capped: the oldest are discarded. | Until site data is cleared | Display preference. This is a preference you set with a deliberate action — moving or hiding an element — and it serves only to present that choice again: it falls within the functions for which consent is not required. |
pintru_email |
Local storage, on the domain of the site hosting the embed | A leftover session entry: it is removed when you sign out of your personal area. | Until sign-out | Yes, technical |
We do not use the browser's session memory (sessionStorage) and we do not employ identification techniques based on device characteristics.
On third-party cookies, to be precise. We host nobody else's cookies: every cookie listed above is ours, set by our own domain. One of them — pintru_ponte — is however sent by the browser while you are on a third-party site, because that is exactly what it is for. Formally it remains a first-party cookie; in practice it travels in a third-party context, and we would rather write that down than let you infer it. It is limited to a single path, does not follow your browsing, and records none of the pages you visit.
4. What the extension stores
If you have installed the browser extension, it has a storage area of its own — it is not a cookie and it does not belong to the websites you visit — in which it keeps the following on your device:
| Entry | What it is for |
|---|---|
pintru_token | The random identifier by which your pins are recognised as yours, or the reference to your session if you have signed in |
pintru_api | The address of the server the extension talks to |
pintru_enabled | The switch with which you turn the extension on or off |
lov_… | The pin arrangement you chose on a given page, if you moved or hid one |
pintru_email | The address you signed in with, so it can be shown in the panel |
pintru_update | The notice, if any, that a newer version is available |
These values stay on your device and are deleted when you uninstall the extension. What the extension does and does not do with its access to pages is described in the privacy notice.
5. Third-party resources and services
- Typefaces. The fonts used by the site are served from our own infrastructure, or are those already present on your device. No page loads resources from third-party servers.
- Signing in with Google. If you choose to sign in with Google, your browser interacts with Google's services, which may set their own cookies on Google's domain under their own notices. If you do not use this sign-in method, nothing happens.
- Payment. Payment for paid plans takes place on the payment service provider's pages, which may set its own technical and anti-fraud cookies on its own domain, under its own notice. The provider's role and the seller's identity are described in the purchase and subscription terms.
- Site measurement. With your consent, PINTRU's pages load Google Tag Manager and the measurement tools configured within it: see Measuring the site. No analytics or advertising service is present in the extension or in the integration script.
6. Measuring the site
To understand how the service is used — how many people arrive, where from, which pages they read, where they stop — we use Google Tag Manager, a container that loads the measurement tools we have configured in it.
Without your consent it is not loaded at all. It is not loaded "with the tools switched off": it is simply not requested from Google, so your browser never contacts it and no data — not even your IP address — reaches it. It is the same rule our script applies on third-party websites, which is why you find it stated here in these terms.
If you consent to the statistics and measurement category, the container is loaded and activates the configured tools, which may set cookies of their own on your device. When Google Analytics is active, those cookies are _ga and _ga_ followed by the property identifier, lasting up to 13 months, and they serve to tell visits apart without knowing who you are.
Before and regardless of consent, Google's consent mode defaults stay set to denied for the four categories that concern measurement and advertising (analytics_storage, ad_storage, ad_user_data, ad_personalization): that is the declaration binding the tools, if and when they are loaded. When no container is configured, as may be the case, nothing is declared because there is nothing to bind.
- Measurement is not active on third-party websites hosting our integration, nor in the browser extension: there we are guests in someone else's house, and measurement of ours on other people's pages would be cross-site tracking, which we do not do.
- We do not use the container for advertising or profiling. If that ever changed, this page would change first, with a new version and its own date.
- You can withdraw consent at any time: withdrawal applies to the future and prevents any further loading.
Google's role as a recipient of data and the transfer outside the European Union are described in the privacy notice.
7. How to control and delete
- You can withdraw consent to measurement at any time from the cookie preferences.
- You can delete cookies and local storage from your browser settings, under the section dedicated to site data. Clearing local storage means losing the link to pins created without an account.
- You can block site cookies and storage pre-emptively from your browser settings: some features of the service will stop working.
- You can turn the extension off from its panel, or uninstall it; uninstalling removes everything it had stored.
- On websites hosting the embed, the consent choice is managed with the tools that website provides.
8. If you have installed the embed on your website
You must declare, in your own privacy notice and cookie policy, the entries our script may write on your visitors' devices, and collect consent where the law requires it before they are activated. The obligations are set out in the integration terms, the document you accept by installing the script.
| Entry | Type | Purpose | Lifetime |
|---|---|---|---|
pintru_token | Local storage, functional | Associating pins with the visitor who created them | Until site data is cleared |
pintru_lov_… | Local storage, preference | Remembering the pin arrangement chosen by the visitor on that page | Until site data is cleared |
| Usage measurement | Sent to the service, statistical | Counting loads and interactions per domain | Not stored on the device |
Until you declare consent, the first and third entries are not activated.
9. Updates
If the tools in use change, this page is updated and the date at the top changed accordingly. For the full picture of how data is processed, see the privacy notice.
Previous versions
- Version 06 September 18, 2026 ·
- Version 05 September 17, 2026
- Version 04 September 17, 2026