Cookies Policy
Small records. Clear purposes.
Cookies remember a session, a guest visit or a language. They do not contain a copy of the file you open.
Last updated: 8 November 2026
The site’s own cookies
Purpose / LifetimeSession & security
app_session
Keeps your session, sign-in state and form security checks working. Created when a feature needs a session, such as authentication or the viewer.
30 days
Guest usage
guest_key
A random identifier used to associate usage attempts with a guest and support usage limits. Created when an opening attempt starts; IP addresses are also used for limits.
365 days
Preference
lang
Remembers English, Italian or German for supported pages and account screens. Set when visiting a page if the remembered language differs or is missing.
365 days
These first-party cookies apply to this site’s installation path. They use HttpOnly and SameSite=Lax, and Secure on HTTPS. Lifetimes run from when a cookie is set; a later setting can start a new period.
Analytics & third parties
Google Tag Manager: configuration matters
When configured, Google Tag Manager loads on page visits, including a fallback iframe when JavaScript is disabled. Tags published inside the container determine any additional analytics cookies, their names and their expiry. We do not claim that a particular Google Analytics cookie is always present.
Product events provide page path, language, device category and technical interaction fields such as format, error code, counts and size bands. Our event code does not include file content, file names, certificate details or fingerprints. Google and any configured tags can receive network and browser information when their resources load.
There is currently no built-in consent banner, preference centre or analytics opt-out. A configured container loads immediately; with no container ID it does not load. Browser cookie blocking does not necessarily block the container or its network requests.
Google privacy notice →Beyond cookies
When the analytics script is active, sessionStorage uses unwrapdoc:checkout to remember the package between checkout and payment confirmation. It is removed on confirmation or when the browser ends that tab’s storage session. This stores a package identifier, not payment-card data or document content. Google sign-in and payment checkout can use their own cookies or storage under their providers’ policies.
To return from sign-in to the viewer, sessionStorage uses unwrapdoc:auth-started for the login or registration action until the return is handled or the tab’s storage session ends. The sign-in completion page briefly writes and immediately removes unwrapdoc-auth in localStorage to signal other tabs; the signal contains sign-in status and a time, not your document or password.
You control your browser storage
Inspect or remove
Open your browser’s privacy or site-data settings, find this site and inspect, block or clear its cookies and storage. The controls and session-restoration behaviour depend on your browser.
Expect a fresh session
Removing app_session signs you out of that browser session and can interrupt forms or checkout. Blocking it can prevent sign-in and viewer requests. Removing lang resets the remembered language; removing guest_key resets that browser identifier but does not remove usage records or IP-based limits.
Manage records separately
Clearing browser storage does not delete your account, activity or payment records, cancel a subscription or erase downloaded files. Use account settings or contact us for a personal-data request.