Privacy Policy
Printer Triage is designed to provide printer troubleshooting information without requiring you to create an account or submit personal information.
Information you enter on the site
Printer model selections, troubleshooting answers, error codes, and messages are used to provide the requested troubleshooting experience. Printer Triage's custom analytics may record reviewed internal identifiers for a selected printer model or family and the predefined troubleshooting choices described below, but it does not store the arbitrary text of an error-message or free-form input field in the custom analytics dataset. A saved printer is stored in your browser for the current browsing session so the site can tailor troubleshooting to that printer.
The Describe what's happening problem matcher processes the description in your browser against Printer Triage's reviewed symptom, model/family, and error-code data. The raw description is not sent to a matcher service, written to persistent storage, or included in Printer Triage's custom analytics. If the matcher records an analytics event, it uses only predefined internal values such as the matched symptom, model/family context, result rank, and matcher state.
Technical information processed when you visit
Printer Triage is hosted through Cloudflare. Cloudflare may process limited technical information needed to deliver, secure, and operate the site, including information such as IP address, traffic or routing data, system information, and request details.
Website analytics
Printer Triage uses Cloudflare Web Analytics to understand aggregate page usage and performance. Cloudflare describes Web Analytics as privacy-first and states that it does not collect or use visitors' personal data or track individual users across Cloudflare customers' websites. The service may measure items such as page views, referrers, device or browser categories, geographic region, and page-performance metrics.
Printer Triage also records first-party troubleshooting events through its own Cloudflare Worker and Workers Analytics Engine. When a troubleshooting or problem-matcher interaction begins, the browser uses a randomly generated temporary session identifier stored in sessionStorage. This identifier is used only to group actions within the current browser-tab session; it is not an account, advertising identifier, or permanent cross-session profile.
The custom troubleshooting events can include internal identifiers for the troubleshooting flow, symptom, question/node reached, predefined answer chosen, “Show me how” topic, corrective step reached or attempted, selected printer brand/model/family where applicable, broad flow-end state, device/platform category, elapsed session time, and a predefined reported outcome such as whether the original problem worked after a troubleshooting step or the flow reached an unresolved endpoint. Matcher usage is represented through the same predefined event structure; the free-form description itself is not included. These identifiers are intended to describe the site's own predefined troubleshooting structure rather than collect personal information.
The custom analytics design intentionally does not write names, email addresses, typed free-form text, raw entered error-message text, raw problem-matcher descriptions, raw IP addresses, precise location, user-agent strings, cookie identifiers, or unnecessary device fingerprints into Printer Triage's custom dataset. The analytics Worker validates an allowlisted event shape and does not copy request IP, geolocation, or browser headers into that dataset. Custom analytics events are also suppressed when Global Privacy Control or Do Not Track is enabled.
Printer Triage does not use browser-close or background events to guess why a visitor left troubleshooting, and it does not collect free-form exit feedback in the current first-party analytics release.
Optional Microsoft Clarity UX analytics
If you choose Allow optional analytics, Printer Triage can load Microsoft Clarity to help us investigate usability problems. Clarity can provide session replays, heatmaps, click and scroll behavior, and signals such as dead clicks, repeated/rage clicks, or excessive scrolling. We use that information to understand whether page layouts or troubleshooting instructions are confusing; Clarity does not decide which troubleshooting branch you receive and is not the source of truth for whether your printer problem was solved.
Clarity is not loaded before you opt in. Choosing No thanks leaves Clarity unloaded and does not reduce site functionality. Global Privacy Control or Do Not Track also suppresses the optional Clarity loader. You can reopen Analytics choices from the site footer to change the site preference.
Printer Triage explicitly marks user-entry controls and selected-user-context areas for masking before Clarity is loaded. This includes input fields, text areas, drop-downs, editable text controls, the Describe what's happening field, the error-lookup result area, and the saved-printer summary. The problem-matcher field also carries an explicit Clarity mask attribute. Microsoft Clarity also masks input-box and drop-down content by default. Masking reduces what is visible in recordings, but session replay still records other page structure and interactions needed for UX analysis.
When optional analytics are allowed, Printer Triage sends Clarity a ConsentV2 signal that permits analytics storage and denies advertising storage. Microsoft may process interaction and technical data and may use Clarity cookies or other storage according to the Clarity configuration, the consent signal, and Microsoft's services. Printer Triage does not send its temporary first-party troubleshooting session_id to Clarity and does not create a shared cross-session identifier between the two analytics systems. See Microsoft's Privacy Statement for information about Microsoft's data practices.
Cookies and browser storage
Printer Triage does not currently use third-party advertising or advertising cookies. The site's temporary troubleshooting state and first-party troubleshooting analytics session identifier use sessionStorage. The optional analytics consent choice is stored in localStorage so the site can remember whether you allowed or declined Clarity without asking on every page.
If you allow Clarity, Microsoft Clarity may set analytics-related cookies or other storage as permitted by the consent signal and project settings. If you decline optional analytics, Printer Triage does not load the Clarity tracking script. If you later change an allowed preference to declined, the site sends Clarity a denial/revocation signal and remembers the new choice.
Analytics delivery is non-blocking. If Cloudflare analytics, Printer Triage's first-party analytics, Microsoft Clarity, an analytics request, or an analytics script is unavailable or blocked, the troubleshooting experience continues normally.
External links
Some troubleshooting pages link to printer manufacturers or other external resources. Those websites have their own privacy practices and policies.
Policy updates
This policy may be updated as Printer Triage adds features or services. Material changes will be reflected on this page.
Last updated: August 20, 2026