Privacy, data, and cookie settings
Utility Atlas is a browser-first collection of small utilities. This page explains what the PHP deployment stores, how production JavaScript errors are reported, and how advertising consent works.
Data processing
Text, files, and tool inputs are processed in your browser whenever the tool supports it. Execution history stores only time, action, status, duration, result size, and output type in this browser for up to 30 days and 20 runs. It never stores input or result content, filenames, location, permission state, or device payloads. Server endpoints receive only the request data required for the selected feature.
Location and device permissions
Location, camera, microphone, screen capture, and device APIs are requested only after an explicit user action and browser permission prompt. Location coordinates and device payloads are used only in the current browser session to display the requested result; they are not sent to the server, analytics, or execution history. You can clear the result, close the page, or revoke permission in browser or operating-system settings. The browser or operating system may separately retain your permission choice.
Aggregated visit statistics
Public page visits are counted by date and two-letter country code. IP addresses, requested page paths, user agents, and tool input or output are not stored in the statistics tables. When the server does not provide a country region, the browser language region may be used as an estimate.
JavaScript error tracking
Eligible production utility pages use PostHog only to report uncaught JavaScript exceptions and unhandled promise rejections. Automatic interaction capture, page views, page leave, dead clicks, heatmaps, performance capture, console logs, session recording, surveys, persistent identifiers, and person profiles are disabled. Tool inputs, outputs, DOM text, form fields, URL queries, and error-message values are removed or generalized before an exception event is sent.
Temporary result sharing
When you explicitly create a result share, only the output snapshot and summary metadata are stored. The original input is not included. The shared result is automatically deleted after 7 days, and expired rows are removed whenever the sharing feature is accessed.
Advertising and consent
Eligible production pages may load Google AdSense Auto ads. Interactive work areas remain structurally identifiable so they can be excluded from automatic in-page placements. Google Privacy & Messaging is used to request and store consent where required. You can reopen the consent controls from the footer link on any regular page.
Your choices
Clear browser storage to remove local preferences and execution-history metadata. Use the footer consent link to review or revoke advertising choices. If the consent dialog is unavailable, this page remains available as the fallback explanation.
Microsoft Clarity analytics
Eligible production pages use Microsoft Clarity to understand page visits, clicks, scrolling, and session playback. Clarity masks input fields by default, and Utility Atlas additionally masks the full tool workspace, including input and result areas. The Clarity tag is not loaded when the browser sends Do Not Track or Global Privacy Control signals. Cookie use and analytics features follow the Clarity project consent settings and the visitor’s region.