ASAPUtils Logo ASAPUtils

Privacy Policy

How ASAPUtils handles tool inputs, analytics, local browser storage, third-party requests, and session replay on informational pages.

Last Updated: August 16, 2026

This policy explains what stays on your device, what limited usage information is sent to service providers, and when a tool may contact a third party at your direction.

1. Tool inputs and outputs

ASAPUtils formatters, converters, validators, generators, and editors are designed to process tool inputs in your browser. ASAPUtils does not operate an application server that receives or stores the text, code, documents, images, or other content you enter into those local-processing tools.

One optional feature is the single exception, and it is described in full in section 4a: cloud wake-ups in the Break Reminder store a random browser push token and a list of future timestamps on an ASAPUtils-operated relay, so your device can be woken for a reminder when your browser is closed. That relay never receives your reminder text, your schedule’s meaning, or any identifier you provide. It is off unless you switch it on.

Some tools are network tools by nature. For example, the API Tester sends a request directly from your browser to the URL you enter, and peer-to-peer features communicate with the peer you choose. In those cases, the destination service or peer receives the data you choose to send and applies its own privacy and retention practices. The tool interface identifies these actions.

Local processing reduces exposure, but it does not remove risks from your device, browser extensions, malware, screen sharing, or a third-party endpoint you contact. Avoid using live secrets when a test value will do.

2. Analytics and completed-action measurement

We use Google Analytics to understand site performance and product usage. It may receive page URLs, referrer information, approximate location derived from IP address, device and browser details, and events such as the name of a tool and whether a copy, download, share, or request action completed.

Completed-action events do not include pasted text, generated output, API URLs, request headers, tokens, file names, or file contents. A numeric completion count is stored in your browser for each tool so an event can be labeled as first or repeat usage. It is not tied to an ASAPUtils account.

3. Session replay

We use Microsoft Clarity on informational and catalog pages to understand navigation and layout problems. Clarity is deliberately not loaded on individual tool pages or the AgentSpec input page, where people may enter sensitive content. Clarity may collect interaction, device, and page metadata on the non-tool pages where it is enabled.

4. Browser storage and cookies

ASAPUtils uses local storage or session storage for features such as theme preferences, recent and favorite tools, share state, embed mode, in-browser handoff between tools, and the completed-action counts described above. This data remains in your browser unless a feature explicitly says otherwise. You can remove it using your browser’s site-data controls.

Analytics and advertising providers may set or read cookies or similar identifiers according to their own policies and your browser or consent settings. The site may display Google AdSense advertising; Google may process ad-delivery and measurement data when ads are active.

4a. Break Reminder cloud wake-ups

The Break Reminder works entirely on your device by default. Its schedules, reminder text, and history are stored in your browser and are never uploaded.

Cloud wake-ups are an optional feature you turn on inside the tool. They exist because a web page cannot schedule an operating-system alarm: to be reminded when your browser is closed, something has to wake your device from outside it.

When you enable it, an ASAPUtils-operated relay stores the following, and nothing else:

  • A push token — an opaque URL your browser generates for that one device. We do not create it, cannot read anything from it, and it identifies a browser installation rather than a person.
  • A list of future timestamps — plain numbers indicating when to ping that token, capped at 200 entries and at eight days ahead.
  • A random subscription identifier we generate to reference the above.
  • Delivery bookkeeping — when the subscription was created, when a delivery last succeeded, and a count of consecutive failures. These exist only to retry sensibly and to delete subscriptions that have stopped working.

The relay does not receive, and cannot derive, your reminder text, your reminders’ names, your repeat rules, your active hours, your timezone, or any account, email, or identifier. There is no account to create. Your device evaluates its own schedule and uploads only the resulting instants.

The wake-up we send carries no content at all. Your browser composes the notification wording locally when it wakes.

Retention. Timestamps are deleted as they are used, and every stored timestamp is at most eight days in the future, so an inactive device’s data expires on its own. A subscription is deleted when you turn the feature off, when your browser reports the push token as expired or revoked, or after repeated delivery failures.

Turning it off. Use the toggle in the Break Reminder. This unsubscribes the browser and deletes the stored token and its timestamps. Clearing the site’s data in your browser also revokes the token, after which the relay discards it on its next delivery attempt.

Notification delivery itself is handled by your browser vendor’s push service (for example Google for Chrome, Mozilla for Firefox, Apple for Safari), which routes the wake-up to your device under its own privacy practices.

Links and destinations you choose to contact are governed by their own policies. We do not control how an API, peer, advertiser, analytics provider, or linked website processes information it receives.

6. Children

ASAPUtils is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact us so we can investigate.

7. Policy changes

We may update this policy as the product or its service providers change. We will publish the revised policy here and update the date above.

8. Contact

For privacy questions, email legal@asaputils.com.