Local preferences and technologies used by the site.
Last updated:
Cookies
Account pages use technical session and request protection cookies for registration, sign-in and email confirmation. Sessions expire after 120 minutes of inactivity by default. Public pages for tools without an account requirement continue to work without these cookies.
Theme preference
Your light/dark choice is saved in browser localStorage under io-theme until you clear site data. It contains only the chosen theme and is not sent to the server. Without a saved choice, the device theme is used.
Tool data
Most entered data and results stay in page memory until you leave or reload. The PDF editor is an exception: autosave keeps the document and edits in IndexedDB on this device, across reloads, without automatic expiry. Remove them with “Delete local save” in the editor or by clearing browser site data. Downloading the PDF does not delete the local copy. Files for conversion are uploaded and processed temporarily on the server as described in the privacy notice.
Consent and new technologies
The theme preference follows the user’s choice. We do not use advertising profiling. Cookieless Matomo does not by itself establish an exemption from consent: its actual configuration and applicable conditions remain under review. New nonessential technologies will require updated information and consent where required.
Favorites
Favorites are available to registered users. We store only the selected tool IDs in your account database until you remove them with the star or delete your account; backups follow the hosting retention policy. Files, entered text and results are excluded. The IDs of the last three tools opened are saved only in this browser’s localStorage under instrumenta.recent-tools.v1 until you clear site data. They are not sent to the server and contain no files, entered text or results. Account favorites do not use localStorage.
Broken link checker: find links and source pages
The scan continues in the background. URLs, references and progress are encrypted on the server and remain private for 24 hours, accessible from the same session or verified account. You can pause, resume or delete the report. Page contents are not saved; some rendering resources use an encrypted temporary cache lasting one hour. Your browser stores a report identifier to reopen it in the same session; deleting the report also removes this reference.
Website crawling for sitemap generation
Scanning uses the site’s technical session to protect results and a random code in the tab’s sessionStorage to reconnect after reloading. URLs are not saved in sessionStorage. These are functional elements, not advertising identifiers; the code is removed on deletion or when the scan is found to have expired.
Optional accounts and service emails
Account pages use technical session and request protection cookies for registration, sign-in and email confirmation. Sessions expire after 7 days of inactivity by default. Public pages for tools without an account requirement continue to work without these cookies.
Aggregate statistics
Aggregate usage counting updates counters by tool, day and outcome. It does not read or write cookies or browser storage and does not assign visitor identifiers. The browser sends only the tool and outcome, never entered values. Counters use a 365-day retention window with daily cleanup. See the privacy notice for details.
To check conversion performance, when technical collection is enabled we keep one record per operation for 30 days: tool, timestamps, wait, duration, outcome, error category and file size bands. A technical code identifies the operation without identifying the visitor or enabling downloads. We include no IP addresses, names, contents, options, passwords or results and use no cookies or visitor identifiers. Records are deleted through daily cleanup. These data help diagnose errors and delays and size the service.
To monitor website errors, we retain daily counts and technical details for 30 days: category, tool, page path without query strings or fragments, language, asset build, allowed resource path, technical error name, line and column, available HTTP status, and first and last occurrence. We also derive a client category (crawler, automation, other or unknown) without retaining the full user agent. We do not collect free-form messages, stack traces, files, entered text or results. Abuse protection uses an IP-derived key with a secret and a 10-minute expiry, separate from the counts. Administrator access also requires a one-use email code valid for 10 minutes; the cache retains only a cryptographic check of the code and the attempt count.
Cookieless Matomo
We measure page views with Matomo, operated by the controller at analytics.pietropetrocchi.it (site 9), separately from tool counters. Tracking cookies and browser feature detection are disabled. We send only the canonical page URL and title, without query strings, fragments or referrers; form, click, download, heatmap and session recording tracking are not enabled.
Matomo still receives connection data, including IP address and user agent, and may process technical identifiers: cookieless does not mean anonymous. We respect Do Not Track and Global Privacy Control by not loading the tracker when enabled.
Retention in days: not confirmed. Analytics hosting country: Switzerland. Privacy settings, identifiers, retention and the applicable conditions for consent exemption must be checked on the Matomo instance.